Date: Sun, 28 Mar 2010 07:37:49 +1100 From: Peter Jeremy <peterjeremy@acm.org> To: Doug Hardie <bc979@lafn.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: FreeBSD 8.0 SCSI Boot Message-ID: <20100327203749.GH32799@server.vk2pj.dyndns.org> In-Reply-To: <548D66CF-4FAA-4D4D-949E-6D2CC509D069@lafn.org> References: <548D66CF-4FAA-4D4D-949E-6D2CC509D069@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--uAgJxtfIS94j9H4T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Mar-26 17:18:30 -0700, Doug Hardie <bc979@lafn.org> wrote: >I tried to upgrade a 7.2 system to 8.0. It uses a SCSI drive. It >works fine on 7.2. We will need some more details before we can help you. > However, it would appear that during the upgrade >process when running make delete-old (?) there is a note about make >delete-old-libs (?). Don't do that at that point. End of system. >Make installworld fails miserably. You shouldn't run either "make delete-old" or "make delete-old-libs" until you have successfully run "make installworld" - the upgrade procedure shows delete-old after installworld. Whilst delete-old will just make it harder to revert from a failed upgrade, running delete-old-libs will prevent you running installworld. When you run delete-old-libs, it warns you "Please be sure no application still uses those libraries, else you can not start such an application." One application that needs the old libraries is installworld. > Unfortunately rebooting caused numerous problems. Given that your installworld had failed - presumably leaving various FreeBSD-7.2 files lying around, whilst you deleted the libraries required by some of them, this is not surprising. > First the /etc/fstab was listed as corrupt. This is surprising. Assuming you cleanly rebooted your system, it is very unlikely that your /etc/fstab was corrupted and is more likely a problem with one of the mount programs. Can you provide the exact error message and what you then did. > Then it quit booting altogether. If it rebooted once, there's no reason why it shouldn't reboot a second time. What actions did you take between the two reboots and what exactly do you mean by "quit booting"? > A complete reload from the disc 1 goes >nowhere either. It installs just fine but when it goes to reboot, >All I get is F1 followed by a bunch of increasing #s. Any key just >adds more to the list. I have tried with both the standard and >FreeBSD boot managers with the same result. At that point, FreeBSD is using the BIOS drivers to access the SCSI disk. If you get the 'F1' prompt then the BIOS is correctly loading the boot sector (so it can access the disk) so there is no obvious reason why it isn't booting. Do you have a copy of the dmesg from 7.2? If not, can you give us some details about your motherboard (vendor/model), what SCSI controller you are using, what targets are attached and what other disks (if any) you have. Are you using a PS/2 or USB keyboard? Can you expand on what you mean by "a complete reload" - did you do a full install of FreeBSD 8.0, including partitioning and creating disk slices or did you re-use the existing slices? Are you using a "dangerously dedicated" disk? Were any disk geometry errors reported? --=20 Peter Jeremy --uAgJxtfIS94j9H4T Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuubJ0ACgkQ/opHv/APuIeWfQCaAuZPhiNGF4WqEmTAVQy0lgFY naoAnAjwS5MXH4zSgXyp0W/3yPAgXkkl =NFG3 -----END PGP SIGNATURE----- --uAgJxtfIS94j9H4T--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100327203749.GH32799>