Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 May 2020 01:10:35 -0300
From:      Anatoli <me@anatoli.ws>
To:        freebsd-questions@freebsd.org
Subject:   Re: SSD woes - boot
Message-ID:  <be376761-f8b1-f008-2af2-99698da90838@anatoli.ws>
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
> You a whipping a dead horse:
>
>
https://lists.freebsd.org/pipermail/freebsd-questions/2020-April/288944.html

> (Linux implements PARTUUID's for the BIOS/MBR case [1]. I have been
> unable to figure out how to do this on FreeBSD.)


To have a FreeBSD equivalent to linux UUID partition identifiers in
/etc/fstab, set a label for a partition (gpart for GPT, glabel for MBR),
`X` is the partition number as reported by `gpart show`.

gpart modify -i X -l <label> ada0
glabel label <label> da1s1a

Then in the /etc/fstab you can use something like ('rootfs', 'home' and
'swap' being the actual labels assigned to the partitions):
/dev/label/rootfs   /       ufs  rw  1   1
/dev/label/home     /home   ufs  rw  2   2
/dev/label/swap     none    swap sw  0   0

And this would work no matter how and where you connect the disk.

Also, the FreeBSD bootloader knows to detect different installs (e.g.
multiple FreeBSDs, say release, current and stable) on the same disk
only if the disk is MBR partitioned.


On 6/5/20 13:43, David Christensen wrote:
> 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
> _______________________________________________
> 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: <http://docs.FreeBSD.org/cgi/mid.cgi?be376761-f8b1-f008-2af2-99698da90838>