Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 May 2020 09:43:13 -0700
From:      David Christensen <dpchrist@holgerdanske.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: SSD woes - boot
Message-ID:  <b5a1c463-e522-f9f1-8bd5-d092953d797b@holgerdanske.com>
In-Reply-To: <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org>
References:  <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2020-05-06 02:56, Christoph Kukulies wrote:
> Since yesterday, when I ran smartcontrol against my drives - don’t know whether it has to do with that but I’m mentioning it just FWIW -
> my Kingston 240 GB SSD suddenly was no longer visible in the ASRock MB’2 BIOS. (ASRock939A790GMH).
> 
> Strange, isn’t 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’t 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?

You a whipping a dead horse:

https://lists.freebsd.org/pipermail/freebsd-questions/2020-April/288944.html


David



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?b5a1c463-e522-f9f1-8bd5-d092953d797b>