Gene Heskett wrote: > On Friday 12 November 2021 08:49:21 Dan Ritter wrote: > > > Gene Heskett wrote: > > > The man page we have goes on and on for megabytes without ever > > > giving an example. > > > > > > I thought maybe it could scan for devices so that I could build an > > > mdadm.conf but it wont do a --scan by itself. > > > > You are looking for > > > > mdadm --detail --scan > > > Null return on stretch version of mdadm. Supposedly up to date as of an > hour ago.
That would be expected if you don't have any current mdadm devices. > Not in the stretch man page. And its sounding as if I should do that > during the bullseye install to get the more capable mdadm, but will the > devices have the same names? With the reputation for volatility of > device names a mistake there could destroy 23 years of data. After you have set them up, mdadm.conf has things like this: ARRAY /dev/md/0 metadata=1.2 name=debian:0 UUID=aeac6271:676b1852:04f077d6:fcd285d6 ARRAY /dev/md/1 metadata=1.2 name=debian:1 UUID=d74ff881:2e966c37:ec6ef1ec:75b8cdce ARRAY /dev/md/2 metadata=1.2 name=debian:2 UUID=7c56166b:0d5aed8b:a9d03c45:e9b8080c And during boot, the system will look for all drives/partitions that fit that UUID for assembly, regardless of whether they are currently named /dev/hdc3, /dev/sdq, or /dev/nvme0np1. -dsr-
