On Tue, 28 May 2013 20:34:30 +0200 Quentin Lefebvre <qlefebvre_...@yahoo.com> wrote: > You can try to uncomment the line > > GRUB_DISABLE_LINUX_UUID=true > > in /etc/default/grub, and then run > > update-grub . > > You should have linux lines with > > root=/dev/mapper/... > > in your /boot/grub/grub.cfg file, which seems to solve the bug.
Right. I think that with some RAID formats there is no header on the physical disks, so the kernel can find partition tables on physical disk devices as well as on the RAID device, and there may be multiple devices matching a UUID. If this happens, selection by UUID is effectively random. The 'Device or resource busy' error message suggests that we tried to mount a physical disk device that's already part of a RAID device. The kernel prevents it from being used for both purposes at once (which is just as well, because the RAID would be corrupted otherwise). Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.
signature.asc
Description: This is a digitally signed message part
