On 3/14/19 5:17 PM, Michal Soltys wrote: > On 3/14/19 5:09 PM, Michal Soltys wrote: >> On 3/14/19 4:57 PM, Hans van Kranenburg wrote: >>> On 3/14/19 4:44 PM, Michal Soltys wrote: >>>> >>>> <cut> >>>> >>>> Occasionally, during reboots (all of them clean of course) I get: >>>> >>>> devid 2 uuid <uuid> is missing >>>> failed to ready system array: -2 >>>> open_ctree faield >>>> >>>> Which drops me into initramfs commandline. >>> >>> It might try to mount before all disks are visible. This can happen when >>> e.g. a raid controller needs a little bit more time to initialize. >>> >>> Try adding rootdelay=10 to your linux command line, or any other number, >>> and then look at logging when booting (so no quiet on your linux command >>> line). >>> >> >> It remains unmountable from initramfs's commandline with both disks >> (partitions) present. Filesystem is mounted formally via uuid, so it >> needs both disks present before udev/blkid can pick the correct devices. When using UUID in fstab/initramfs, all btrfs devices show up having the same UUID, so if any of them is present, it can try mounting. > E.g. > > mount /dev/sdr2 /newroot -> fails Are you typing this manually? And what's the error? Does it complain about the devid of sds2? > mount /dev/sds2 /newroot -> ok While doing this you trigger the system to have a look, and at that moment it will suddenly discover the disk, and now it sees them both and it mounts... > umount /newroot > mount /dev/sdr2 /newroot -> ok ...even when using sdr2, because when doing the things above all disks got discovered. It's of course possible you have another problem.My suggestion was just a been-there-done-that. But, in that case posting more logging might help. >>>> When that happens, one of the partitions is mountable, the other is >>>> not. >>>> Mounting the filesystem via the "good" one also fixes the "bad" one. >>>> >>>> Tested with 4.20.11 and 5.0.2 kernels. >>>> >>>> Any idea what could be wrong ? >>>> Does btrfs require full umount via pivoted initramfs during shutdown ? Hans
