Date: Thu, 7 May 2020 12:21:59 -0700 From: David Christensen <dpchrist@holgerdanske.com> To: freebsd-questions@freebsd.org Subject: Re: SSD woes - boot Message-ID: <1df1667c-3b5e-6668-2bad-d7c0e2da897e@holgerdanske.com> In-Reply-To: <20200507112813.91e445a39bffbcdb906f05e8@sohara.org> References: <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org> <b5a1c463-e522-f9f1-8bd5-d092953d797b@holgerdanske.com> <E35B2E1F-8BEB-458C-97BF-3EF030CA0643@kukulies.org> <20200507112813.91e445a39bffbcdb906f05e8@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-05-07 03:28, Steve O'Hara-Smith wrote: > On Thu, 7 May 2020 11:16:25 +0200 > Christoph Kukulies <kuku@kukulies.org> 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. But, two out of three is better than zero out of three with device nodes. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1df1667c-3b5e-6668-2bad-d7c0e2da897e>