From owner-freebsd-questions@freebsd.org Mon Sep 2 11:32:18 2019 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A419CDA8DF for ; Mon, 2 Sep 2019 11:32:18 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MSc12c7Vz4bck for ; Mon, 2 Sep 2019 11:32:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([178.12.113.112]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPA (Nemesis) id 1MFKX3-1hyMd81lxx-00Fn4W; Mon, 02 Sep 2019 13:32:11 +0200 Date: Mon, 2 Sep 2019 13:32:09 +0200 From: Polytropon To: "Thomas D. Dean" Cc: freebsd-questions@freebsd.org Subject: Re: Install from .iso Fails Message-Id: <20190902133209.847ed08e.freebsd@edvax.de> In-Reply-To: <61dd60cd-7fed-aea5-6878-61c9cc1b12aa@wavecable.com> References: <74e749a3-b544-9bd5-d33a-31a05ede550d@wavecable.com> <0aa49415-4e1b-afe8-8e2a-b14935838ba0@wavecable.com> <7ebb0c1b-335e-8b8e-0c1e-1e95ffe050b9@gmail.com> <4f85bc7f-ace1-457c-211a-207acbb755a2@wavecable.com> <20190901220511.b90fab1d.freebsd@edvax.de> <61dd60cd-7fed-aea5-6878-61c9cc1b12aa@wavecable.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:xPHy84rZy2KeHn3fOFxfPfMGUsHP0HO9Q6Vc35hO2h+k8deMzyU lOdvUkdjzA9zNqP7+N1q8v5ILapYvqh4z2xeEqek95gK528FZxYNP/1H9yToD+3hnd5sP2X yzKLDIwfUpaSL6sUvxx7mXWTIm+7qKCAl2iEIPAN6aPW7FY8eXNggFLBHNYvMhyFDs5DsPt wI+81h+ti+b6k3k0frMmQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:l/NvudSlrhQ=:AqoBtYg/tiZVydjsI1+BLO AMhWJjXm4XC+6APYbyP/TLvk1kNaxihwZHFHurpzIACnjU5H79tpMMW0CKOXVV6nkuEdEkOLB 0xV54cLwQJABb8QwMkDdJUMRRo3xu8vMwHcNtdOPiO4XrASl07U/0IU6wBJqsNWHYu9RsVNUI WN3fMRSkCxA+aRaYJsNxygZU/E7BFmI42FGIBk1TbDwAoucshhQCO55dLEbWbmm4AytActsEg GtW8Cg/lVEKOFO30ANNqDgkYLXsiUiY8ez2xhqBLPJmkIST9kLAwrsAlb6k6zaEdSefg+iuQF gi/H45qB4zc6crbkNzDiEAIIH0xOzNkhgJ/oy1k4wm+9RuHlH6kxLR7ILRZqwF0XveZHbFtWc FLt44EWGD35WmHNpy/p4h0y/NxM4uFthrGyKVKUpTG3B9CFPzwg16XEFtmdUWZ4njwimbQmYd MGB4RW22R0VDFtOYxmji8ITd6luvvUY46zKsbhwMPHH1vfBkB4yfA0yTmzGh+MJ8hi3bFb4hD 7PRgz+d3ggYmfViUQvArJXPIONqcK2C9n4qDl6hlrt320Ag3wes+z2nVUELKEVPDxfgH9neaG +3bbyJF5Wh5imF7vwa+5l0uXVhJql8U8xlUItsGZyFJO5w9ZZfykr8z9GgsvOTkK2fATHzUKv GwKtXAaCe3OPEfktSTdOWi19FrUyuXTgjtHAWr1nOWEQiirOEDKT4+AExfW5oq49esw60TvlE a67PlRYT3P9h+7pkgiCI0eyIdzXmk1uBISFce8tGGmmOkUtm9Y1c0+r/mQnIFAzArUHxu2ykt +aJUWeRpHTZQlaAU4fk9Vd368AvTg== X-Rspamd-Queue-Id: 46MSc12c7Vz4bck X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.130) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [5.97 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[112.113.12.178.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.876,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.988,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.999,0]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[130.126.227.212.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[130.126.227.212.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(0.70)[ip: (2.73), ipnet: 212.227.0.0/16(-1.38), asn: 8560(2.18), country: DE(-0.01)] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 11:32:18 -0000 On Sun, 1 Sep 2019 16:55:53 -0700, Thomas D. Dean wrote: > On 9/1/19 1:05 PM, Polytropon wrote: > > On Sun, 1 Sep 2019 12:37:21 -0700, Thomas D. Dean wrote: > >> On 9/1/19 3:17 AM, MJ wrote: > >>> > >>> > >>> On 1/09/2019 2:49 pm, Thomas D. Dean wrote: > >>>> On 8/31/19 8:58 PM, Thomas D. Dean wrote: > >>>>> On 8/31/19 8:49 PM, Thomas D. Dean wrote: > >>>>>> I tried to install FreeBSD and failed. > >>>>>> > >>>>>> I downloaded FreeBSD-12.0-RELEASE-amd64-bootonly.iso, burned a CD, > >>>>>> and booted. > >>>>>> > >>>>>> The boot sequence did not complete.=A0 It was in a loop > >>>>>> ... > >>>>>> xchi resetting the controller > >>>>>> ... > >>>>>> xchi resetting the controller > >>>>>> > >>>>>> I could get to the ptty that was logged in as root.=A0 ps -ax seem= ed OK. > >>>>>> > >>>>>> I think I had FreeBSD on this machine several years ago. > >>>>>> > >>>>>> Motherboard ASUS P9X79 PRO > >>>>>> Intel(R) Core(TM) i7-3930K CPU > >>>>>> > >>>>>> Any ideas? > >>>>>> > >>>>>> Tom Dean > >>>>> > >>>>> Typo: xhci rather than xchi. > >>>>> > >>>>> =A0From a Linux console, > >>>>> > >>>>> =A0> lsusb > >>>>> Bus 002 Device 005: ID 0cf3:3005 Atheros Communications, Inc. AR3011 > >>>>> Bluetooth > >>>>> Bus 002 Device 004: ID 04f2:0939 Chicony Electronics Co., Ltd > >>>>> Bus 002 Device 003: ID 045e:0768 Microsoft Corp. Sidewinder X4 > >>>>> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matchi= ng > >>>>> Hub > >>>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > >>>>> Bus 006 Device 002: ID 2109:0810 VIA Labs, Inc. VL81x Hub > >>>>> Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > >>>>> Bus 005 Device 002: ID 2109:3431 VIA Labs, Inc. Hub > >>>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > >>>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > >>>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > >>>>> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matchi= ng > >>>>> Hub > >>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > >>>>> _______________________________________________ > >>>> > >>>> I switched to ttyv3 and killed all the bsdinstall processes.=A0 Then= , I > >>>> started bsdinstall.=A0 Looked good.=A0 When bsdinstalled started loo= king > >>>> on the web for components to install, all the components were not fo= und. > >>>> > >>>> pub/FreeBSD/releases/amd64/amd64/12.0-RELEASE/base.txz no address > >>>> record found. > >>>> > >>> > >>> I wouldn't go around killing install processes and then expect to hav= e a > >>> cogent system. > >>> > >>> If you are stuck with something, like the XHCI error, try a verbose b= oot: > >>> > >>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall= -start.html > >>> > >>> > >>> It may, or may not, illuminate the issue a bit more. > >>> > >>>> But, the install did do one thing. > >>>> > >>>> I tried to install on ata3.=A0 bsdinstall actually created partitons= on > >>>> that disk. > >>>> > >>>> BUT, BSDINSTALL ALSO STABBED ATA0 AND MADE IT UNBOOTABLE.=A0 Thanks. > >>> > >>> Yikes, boot manager perhaps? Is this a multi-OS system? What's the bo= ot > >>> manager you are using? > >>> > >>>> > >>>> I guess FreeBSD install is just broken. > >>> > >>> Maybe the web-based-install-everything-by-download is, but I doubt it. > >>> Is the network showing an IP when you're booting and what's its route > >>> table look like? Can you ping a known web site, ie, google.com > >>> (indicating name resolution & some network operation)? > >>> > >> I chose DHCP to start the network and did not see any error messages. = I > >> did not ping anything. > >=20 > > You should verify that the network can be reached, routing > > and name resolution work. If you see no error message, you > > _could_ take that for granted, but it's always useful to > > make sure it _really_ works. > >=20 > > This is the primary reason I use DVD #1: It allows me to > > install a fully working OS, a point from where I can configure > > network as needed, and then perform installation from external > > sources. No "half-baked" things. ;-) > >=20 > >=20 > >=20 > >> I did not choose to install a MBR, maybe this is some default? > >=20 > > Did you choose automatic layout? Today, MBR is not the > > default anymore. GPT is. There are only very few reasons > > one would choose to use MBR partitioning. > >=20 > >=20 > >=20 > >> Killing all the install processes BEFORE they did anything should not > >> cause a problem. > >=20 > > Depends on when a certain step is being performed, e. g., > > editing or creating a partition table before initializing > > filesystems, initializing filesystems before copying files. > >=20 > >=20 > >=20 > >> Looking back over several years' notes I think this is a USB 3.0 probl= em. > >> > >> USB 3.0 is why I switched to Linux. It is necessary for some of my > >> projects. > >=20 > > Yes, this is a problem sometimes. > >=20 >=20 > I killed all the bsdinstall stuff before I answered any of the=20 > questions. As soon as the first install box appeared, I switched to=20 > ttyv3(?) where root was logged in. Before selecting keyboard model. So you don't want to use bsdinstall? I could understand that... ;-) > I use grub at the console to choose the system to boot [...] Okay, so you already have a boot manager in place. In this case, you only need to add FreeBSD boot code at the beginning of the desired disk, and _not_ make any changes to the first disk (i. e., the boot disk) of the system. After installing FreeBSD to the desired disk, add an entry to the GRUB configuration that hands over control to that particular disk to boot FreeBSD. Dealing with individual disks makes this easy. However, you _could_ do the following: Detach all disks except the one you want to put FreeBSD on. Install it using bsdinstall as if it would be a typical single-disk installation; use the normal boot section (not the boot manager). Add labels to the partitions. Now this disk would boot fine as-is. Re-attach the other disks, and add the GRUB entry as mentioned before for the FreeBSD disk. > [...] and I login at a=20 > console prompt. In my .bash_profile, I startx. I use TWM because it is= =20 > least intrusive. I use emacs in an xterm for development. Interesting setup. > I have a multi-os system. > sata6g_1 HD0 SSD ubuntu 18.04 > sata6g_2 HD1 WD5000 Ubuntu 18.04 > sata3g_3 HD2 WD5000 windows 7 - not used > sata3g_4 HD3 WD5000 empty - this is where I tried to install FreeBSD > sata3g_5 HD4 WD5000 windows 7 secondary plex- not used > sata3g_6 DVD DRW-24B3LT > sata6g_E1 (empty) > sata6g_E2 (empty) >=20 > After starting bsdinstall on ttyv3(?), I chose the automatic layout. If I remember correctly, that would create the partitions as needed, _and_ add the regular boot code. > OK, that does not seem to be a reasonable way to go. Check the instructions on what the best way is. Multi-OS setups are not very typical, they're not really covered in the documentation. But that doesn't stop you from integrating FreeBSD - I have done that many years ago without any problems. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-bsdinstall= .html https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-parti= tioning.html I think the guided partitioning is a better way to allocate disk space. You _could_ also do a manual install (from the 3rd console, i. e., using gpart and newfs to prepare the target disk, and then install the FreeBSD components to that new target). > I will download the DVD set. Is it possible that I get reasonable USB=20 > 3.0 support from the full DVD rather than the net install? Those aren't different in terms of kernel (which is responsible for USB support). But with DVD #1 (the only one you need) you can install the full OS, and boot into a fully working OS after- wards, to make further configurations, like network, ports to add, and so on. > What do I need to do to avoid scribbling on sata6g_1 HD0? That=20 > contains grub. Definitely. Your GRUB configuration is best changed by booting into Linux and using the GRUP setup tool to add a FreeBSD entry ("chain loader"). Maybe the thread "Booting FreeBSD via GRUB" in the FreeBSD forum can be helpful here: https://forums.freebsd.org/threads/booting-freebsd-via-grub.60422/ --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...