SSD woes - boot

Polytropon freebsd at
Thu May 7 19:28:26 UTC 2020

On Thu, 7 May 2020 12:21:59 -0700, David Christensen wrote:
> On 2020-05-07 03:28, Steve O'Hara-Smith wrote:
> > On Thu, 7 May 2020 11:16:25 +0200
> > Christoph Kukulies <kuku at> wrote:
> > 
> >> Now I got to figure out the UUID labeling thing - maybe :)
> > 
> > 	I've just been going three rounds with labelling an iscsi and
> > finally found a solution which may be useful to you since gpt and glabel
> > labels just vanish with iscsi restarts.
> > 
> > 	If kern.geom.label.disk_ident.enable is set to 1 (/boot/loader.conf
> > for persistence) then when a drive is discovered /dev/diskid/<serial_number>
> > gets created.
> That is an intriguing alternative.  I expect it will solve the use-case 
> of adding, removing, and rearranging drives and adapters within a 
> computer.  I also expect it will solve the use-case of moving the system 
> device from one computer to another computer.  But, I expect it will 
> fail to solve the use-case of moving a raw system image from one device 
> to another device using dd(1), because the new device will have a 
> different serial number.

Maybe UFSIDs can help here? When dd'ing a whole disk, the ID of
the UFS filesystem will probably be copied 1:1, so the ID will
be identical. However, this only works for UFS exclusively, if
that scope is enough for your desired application. Please see
my previous posts for more information about UFSIDs.

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

More information about the freebsd-questions mailing list