Date: Thu, 7 May 2020 11:16:25 +0200 From: Christoph Kukulies <kuku@kukulies.org> To: David Christensen <dpchrist@holgerdanske.com> Cc: freebsd-questions@freebsd.org Subject: Re: SSD woes - boot Message-ID: <E35B2E1F-8BEB-458C-97BF-3EF030CA0643@kukulies.org> In-Reply-To: <b5a1c463-e522-f9f1-8bd5-d092953d797b@holgerdanske.com> References: <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org> <b5a1c463-e522-f9f1-8bd5-d092953d797b@holgerdanske.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Today I went into my local computer store and bought me a new SATA = cable. Connected the Kingston SSD with the new cable and it got recognized immediately.=20 Anyway, I booted, but still hit the wrong disk (with F5 which was = preset). I hit F1. Got into the FreeBSD boot(8) prompt >> FreeBSD/i386 BOOT Default: 0:ad(0,a) boot: After some fiddling - ? gave me a directory listing but could not much = do with that - I found that everything I typed, like lsdev, ended up in being appended to the Default line, like: Default: 0:ad(0,a)lsdev So I type /boot/loader and - voila - I hit it, landed exactly in the = desired disk/partition. Now I got to figure out the UUID labeling thing - maybe :) =E2=80=94 Christoph > Am 06.05.2020 um 18:43 schrieb David Christensen = <dpchrist@holgerdanske.com>: >=20 > On 2020-05-06 02:56, Christoph Kukulies wrote: >> Since yesterday, when I ran smartcontrol against my drives - don=E2=80=99= t know whether it has to do with that but I=E2=80=99m mentioning it just = FWIW - >> my Kingston 240 GB SSD suddenly was no longer visible in the ASRock = MB=E2=80=992 BIOS. (ASRock939A790GMH). >> Strange, isn=E2=80=99t it, that a power fail or unclean = shutdown/dismount can cause the drive being no longer visible to the = BIOS. >> To test whether it was still alive, I took it out of the system, put = it into an ICY box and connected it to a FreeBSD (11) VM I have running = under Parallels on my MacbookPro. >> It got recognized on the USB bus and after I ran an fsck against it = and put it back into the BIOS, it was recognized again. >> So far so good. But now, due to some misordering in the hard disk = numbering scheme in the BIOS I can=E2=80=99t aim at the right partition = to boot. >> With the old F1/F5 bootload of FreeBSD it always boots the wrong = partition . >> Is there a better bootloader available which offers me a larger = choice, that eventually finds all bootable partitions on all disks in = the system? >=20 > You a whipping a dead horse: >=20 > = https://lists.freebsd.org/pipermail/freebsd-questions/2020-April/288944.ht= ml >=20 >=20 > David > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E35B2E1F-8BEB-458C-97BF-3EF030CA0643>