On Tue, 2015-07-14 at 13:52 +0200, Peter Nagel wrote: [...] > As suggested in the bug report (see message#109)
For others reading along this is in #784070 not #791794. > Problem solved ... > ... and many thanks to Phil. Huzzah! > PS: > There is still one thing I do not understand: > The file etc/mdadm/mdadm.conf (within initrd.img.*) contains an UUID > (see below) ... > > ARRAY /dev/md/0 metadata=1.2 UUID=92da2301:37626555:6e73a527:3ccc045f > name=debian:0 > spares=1 > > ... wich seems to be different from the output of ls -l /dev/disk/by-uuid: > > lrwxrwxrwx 1 root root 9 Jul 14 11:27 > c4263f89-eb0c-4372-90ae-ce1a1545613e -> ../../md0 I _think_ this is because the former is the UUID of the RAID device, while the latter is the UUID of the filesystem contained within it. Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1436886620.25044.106.ca...@debian.org
