Hey all, On 22 September 2014 18:09, M G Berberich <berbe...@fmi.uni-passau.de> wrote: > Hello, > > Am Montag, den 22. September schrieb Dimitri John Ledkov: > >> It is my understanding that udev rules should be sufficient. >> Could you please provide your /etc/fstab to reproduce this failure to boot? >> Are you attempting to do initramfs-less boot with rootfs on btrfs? > > --------------------------------------------------------------------------- > # /etc/fstab: static file system information. > # > #<file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > > /dev/sda2 / ext4 errors=remount-ro,discard 0 > 1 > /dev/sda1 /boot ext2 defaults 0 2 > /dev/sda3 /var ext4 discard 0 2 > tmpfs /tmp tmpfs defaults,size=8g 1 2 > /dev/sdd1 /scratch ext4 defaults,noatime 0 2 > /dev/sdb /home btrfs subvol=home 0 0 > /dev/sdb /data btrfs subvol=data,noatime 0 0 > … > --------------------------------------------------------------------------- > > /boot is ext2 > /, /var is ext4 >
My understanding is that after udevd is started, systemd-udev-trigger.service should be started, which then should trigger events that would cause btrfs udev to run and successfully execute btrfs scan for all btrfs formatted drives. However, it also seems to be non-trivial to setup initramfs-less debian system, hence I can't debug this locally. Original bug reporter, Can you obtain udevd logs of events that happen when you boot with and without your custom job to fix things? Can someone from systemd experts say whether or not systemd-udev-trigger is run before local-fs target? Original bug reporter, Can you change before/after/wants on the udevd units such that systemd-udev-trigger unit is executed before local-fs target and see if that resolves your problem or not? -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
