Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: "timed out waiting for dev-sda.device"
On 9/9/18 6:59 AM, Michael Biebl wrote: >> systemd version is 220-2, attaching my /etc/fstab. > > Since you reopened the bug report, would you mind testing with the > latest version and report back if it's still reproducible? I haven't run into this issue for a while anymore. While I don't use btrfs anymore, the machine still has a swap partition and that one gets activated without any problems. Feel free to close this bug report. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: "timed out waiting for dev-sda.device"
Hi On Sun, 28 Jun 2015 17:04:04 +0200 John Paul Adrian Glaubitz wrote: > > Ok, so should we close the bug and reopen once you can reproduce > > it again? > > I am still running into this issue on one of our Debian sh4 buildds: > > [ 15.236000] BTRFS: device fsid 834d6bda-7796-4cdf-aa09-8695ec50c03a [ > OK ] Started Flush Journal to Persistent Storage. > devid 1 transid 58297 /dev/sda2 > [ TIME ] Timed out waiting for device dev-ttySC1.device. > [DEPEND] Dependency failed for Serial Getty[ TIME ] Timed out waiting > for device dev-di...\x2daa09\x2d8695ec50c03a.device. > [DEPEND] Dependency failed for /srv/chroots/buildd-sid. > [DEPEND] Dependency failed for /srv/chroots/buildd-sid/sys. > [DEPEND] Dependency failed for Local File Systems. > [DEPEND] Dependency failed for /srv/chroots/buildd-sid/proc. > [DEPEND] Dependency failed for /srv/chroots/buildd-sid/dev/pts. > [ TIME ] Timed out waiting for device > dev-di...\x2db405\x2d60154827bd8a.device. > [DEPEND] Dependency failed for > /dev/disk/by-...a6e-58e4-47de-b405-60154827bd8a. > > systemd is waiting for the swap device as well as a btrfs filesystem > which contains the chroot for sbuild. It also waits for the serial > console ttyS0 which is actually used to boot the board (Renesas > SH-7785LCR) as I don't use a video adapter. > > I added "nofail" to the fstab entries in question but that doesn't help. > The only working solution is commenting the fstab entries for swap > and the btrfs chroot out, then reboot the machine and mount the > partitions manually once the machine has come up. > > systemd version is 220-2, attaching my /etc/fstab. Since you reopened the bug report, would you mind testing with the latest version and report back if it's still reproducible? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
Ok, so should we close the bug and reopen once you can reproduce it again? I am still running into this issue on one of our Debian sh4 buildds: [ 15.236000] BTRFS: device fsid 834d6bda-7796-4cdf-aa09-8695ec50c03a [ OK ] Started Flush Journal to Persistent Storage. devid 1 transid 58297 /dev/sda2 [ TIME ] Timed out waiting for device dev-ttySC1.device. [DEPEND] Dependency failed for Serial Getty[ TIME ] Timed out waiting for device dev-di...\x2daa09\x2d8695ec50c03a.device. [DEPEND] Dependency failed for /srv/chroots/buildd-sid. [DEPEND] Dependency failed for /srv/chroots/buildd-sid/sys. [DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for /srv/chroots/buildd-sid/proc. [DEPEND] Dependency failed for /srv/chroots/buildd-sid/dev/pts. [ TIME ] Timed out waiting for device dev-di...\x2db405\x2d60154827bd8a.device. [DEPEND] Dependency failed for /dev/disk/by-...a6e-58e4-47de-b405-60154827bd8a. systemd is waiting for the swap device as well as a btrfs filesystem which contains the chroot for sbuild. It also waits for the serial console ttyS0 which is actually used to boot the board (Renesas SH-7785LCR) as I don't use a video adapter. I added nofail to the fstab entries in question but that doesn't help. The only working solution is commenting the fstab entries for swap and the btrfs chroot out, then reboot the machine and mount the partitions manually once the machine has come up. systemd version is 220-2, attaching my /etc/fstab. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 # UNCONFIGURED FSTAB FOR BASE SYSTEM UUID=aa6ba676-a156-488f-8022-28aefaed50d8 / ext4errors=remount-ro 0 1 UUID=b8f60a6e-58e4-47de-b405-60154827bd8a none swap sw,nofail 0 0 #/dev/sda3 noneswapsw 0 0 # chroots UUID=834d6bda-7796-4cdf-aa09-8695ec50c03a /srv/chroots/buildd-sid btrfs defaults,subvol=buildd-base,noatime,nodiratime,nofail 0 0 #/dev/vg/buildd /org/chroots/buildd-sid btrfs defaults,noatime,subvol=buildd-base 0 0 #/dev/hda5 /org/chroots/buildd-sid/var/cache/apt/archives btrfs defaults,subvol=aptarchives 0 2 #/dev/hda5 /org/chroots/buildd-sid/var/lib/apt/lists btrfs defaults,subvol=aptlists 0 2 # chroot procs proc/srv/chroots/buildd-sid/proc procdefaults0 0 sysfs /srv/chroots/buildd-sid/sys sysfs defaults 0 0 /dev/pts /srv/chroots/buildd-sid/dev/pts nonebind 0 0
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
Well, this is frustrating: now I can't reproduce the problem either. (Reverted /etc/fstab to its previous state, rebooted several times with no problems.) To me this suggests some sort of race condition inside udev, and perhaps I should just file a new bug if the problem comes back. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
Am 11.05.2014 18:14, schrieb Zack Weinberg: Well, this is frustrating: now I can't reproduce the problem either. (Reverted /etc/fstab to its previous state, rebooted several times with no problems.) To me this suggests some sort of race condition inside udev, and perhaps I should just file a new bug if the problem comes back. Ok, so should we close the bug and reopen once you can reproduce it again? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
Package: systemd Version: 204-10 Severity: important I have /home spread over two entire disks using btrfs (applied directly to the physical disks; there is no intervening dm/LVM/whatever). These disks have no disklabels. They are referred to in /etc/fstab by device name. # grep ^/dev /etc/fstab | column -t /dev/sdb1 / ext4 noatime,errors=remount-ro 0 1 /dev/sdb2 none swap sw 0 0 /dev/sda /home btrfssubvol=/home 0 2 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto0 0 systemd hangs the boot waiting for dev-sda.device, eventually times out and provides an emergency shell, from which I can observe that /dev/sda exists and manually mounting /home succeeds. I have been unable to figure out what it was waiting for. Here is some stuff that seems like it might be relevant. All of these commands were run under a system booted with sysvinit, because one can't file a bug report from the emergency shell ;-/ but the only difference I can recall from the output in the emergency shell is that udevadm info had SYSTEMD_READY=0 in there when running under systemd. # ls -l /dev/sd* brw-rw 1 root disk 8, 0 May 10 09:56 /dev/sda brw-rw 1 root disk 8, 16 May 10 09:56 /dev/sdb brw-rw 1 root disk 8, 17 May 10 09:56 /dev/sdb1 brw-rw 1 root disk 8, 18 May 10 09:56 /dev/sdb2 brw-rw 1 root disk 8, 20 May 10 09:56 /dev/sdb4 brw-rw 1 root disk 8, 32 May 10 09:56 /dev/sdc brw-rw 1 root disk 8, 48 May 10 09:56 /dev/sdd # blkid /dev/sdb2: UUID=1e04942e-c69b-4430-84f3-1622ef1afe75 TYPE=swap /dev/sdb4: UUID=10C8D0B8C8D09D72 TYPE=ntfs /dev/sdb1: UUID=eaf36848-eadc-4138-b2a9-db3d8ce82f34 TYPE=ext4 /dev/sdc: LABEL=store UUID=ec93d2c2-7937-40f8-aaa6-c20c9775d93a UUID_SUB=71e4e0ba-c475-4097-9219-4faf87b9b1d9 TYPE=btrfs /dev/sda: LABEL=store UUID=ec93d2c2-7937-40f8-aaa6-c20c9775d93a UUID_SUB=5bda918b-2e06-45ae-9b96-03b2f2b0b338 TYPE=btrfs # lsblk -f NAME FSTYPE LABEL MOUNTPOINT sdabtrfs store sdb ├─sdb1 ext4 / ├─sdb2 swap [SWAP] └─sdb4 ntfs sdcbtrfs store # udevadm info -qall -p /sys/class/block/sda P: /devices/pci:00/:00:1f.2/ata1/host0/target0:0:1/0:0:1:0/block/sda N: sda S: disk/by-id/ata-WDC_WD5000AAKX-00U6AA0_WD-WCC2ET237617 S: disk/by-id/wwn-0x50014ee2b28542c6 S: disk/by-label/store S: disk/by-uuid/ec93d2c2-7937-40f8-aaa6-c20c9775d93a E: DEVLINKS=/dev/disk/by-id/ata-WDC_WD5000AAKX-00U6AA0_WD-WCC2ET237617 /dev/disk/by-id/wwn-0x50014ee2b28542c6 /dev/disk/by-label/store /dev/disk/by-uuid/ec93d2c2-7937-40f8-aaa6-c20c9775d93a E: DEVNAME=/dev/sda E: DEVPATH=/devices/pci:00/:00:1f.2/ata1/host0/target0:0:1/0:0:1:0/block/sda E: DEVTYPE=disk E: ID_ATA=1 E: ID_ATA_DOWNLOAD_MICROCODE=1 E: ID_ATA_FEATURE_SET_HPA=1 E: ID_ATA_FEATURE_SET_HPA_ENABLED=1 E: ID_ATA_FEATURE_SET_PM=1 E: ID_ATA_FEATURE_SET_PM_ENABLED=1 E: ID_ATA_FEATURE_SET_PUIS=1 E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0 E: ID_ATA_FEATURE_SET_SECURITY=1 E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0 E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=86 E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=86 E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1 E: ID_ATA_FEATURE_SET_SMART=1 E: ID_ATA_FEATURE_SET_SMART_ENABLED=1 E: ID_ATA_SATA=1 E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1 E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1 E: ID_ATA_WRITE_CACHE=1 E: ID_ATA_WRITE_CACHE_ENABLED=1 E: ID_BTRFS_READY=1 E: ID_BUS=ata E: ID_FS_LABEL=store E: ID_FS_LABEL_ENC=store E: ID_FS_TYPE=btrfs E: ID_FS_USAGE=filesystem E: ID_FS_UUID=ec93d2c2-7937-40f8-aaa6-c20c9775d93a E: ID_FS_UUID_ENC=ec93d2c2-7937-40f8-aaa6-c20c9775d93a E: ID_FS_UUID_SUB=5bda918b-2e06-45ae-9b96-03b2f2b0b338 E: ID_FS_UUID_SUB_ENC=5bda918b-2e06-45ae-9b96-03b2f2b0b338 E: ID_MODEL=WDC_WD5000AAKX-00U6AA0 E: ID_MODEL_ENC=WDC\x20WD5000AAKX-00U6AA0\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_REVISION=15.01H15 E: ID_SERIAL=WDC_WD5000AAKX-00U6AA0_WD-WCC2ET237617 E: ID_SERIAL_SHORT=WD-WCC2ET237617 E: ID_TYPE=disk E: ID_WWN=0x50014ee2b28542c6 E: ID_WWN_WITH_EXTENSION=0x50014ee2b28542c6 E: MAJOR=8 E: MINOR=0 E: SUBSYSTEM=block E: USEC_INITIALIZED=66534 -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (501, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-5 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.2-1 ii libgcrypt11 1.5.3-4 ii libkmod2
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
Am 10.05.2014 16:18, schrieb Zack Weinberg:
Package: systemd
Version: 204-10
Severity: important
I have /home spread over two entire disks using btrfs (applied directly to
the physical disks; there is no intervening dm/LVM/whatever). These disks
have no disklabels. They are referred to in /etc/fstab by device name.
# grep ^/dev /etc/fstab | column -t
/dev/sdb1 / ext4 noatime,errors=remount-ro 0 1
/dev/sdb2 none swap sw 0 0
/dev/sda /home btrfssubvol=/home 0 2
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto0 0
systemd hangs the boot waiting for dev-sda.device, eventually times out
and provides an emergency shell, from which I can observe that /dev/sda
exists and manually mounting /home succeeds. I have been unable to figure
out what it was waiting for.
Here is some stuff that seems like it might be relevant. All of these
commands were run under a system booted with sysvinit, because one can't
file a bug report from the emergency shell ;-/ but the only difference I
can recall from the output in the emergency shell is that udevadm info
had SYSTEMD_READY=0 in there when running under systemd.
As long as SYSTEMD_READY=0 is set, systemd doesn't treat the device as
available. That explains the timeout.
Looking at /lib/udev/rules.d/64-btrfs.rules, it's probably
IMPORT{builtin}=btrfs ready $devnode
which sets ID_BTRFS_READY=0.
It's unclear to me though why that rule would behave differently under
systemd. Support for btrfs was added in [0]. the btrfs builtin does
nothing else then poke /dev/btrfs-control and apparently that reports
that the device is not ready yet.
CCing Kay here, maybe that rings a bell with him and he can help us here.
Michael
[0]
http://lists.freedesktop.org/archives/systemd-commits/2012-September/002503.html
# ls -l /dev/sd*
brw-rw 1 root disk 8, 0 May 10 09:56 /dev/sda
brw-rw 1 root disk 8, 16 May 10 09:56 /dev/sdb
brw-rw 1 root disk 8, 17 May 10 09:56 /dev/sdb1
brw-rw 1 root disk 8, 18 May 10 09:56 /dev/sdb2
brw-rw 1 root disk 8, 20 May 10 09:56 /dev/sdb4
brw-rw 1 root disk 8, 32 May 10 09:56 /dev/sdc
brw-rw 1 root disk 8, 48 May 10 09:56 /dev/sdd
# blkid
/dev/sdb2: UUID=1e04942e-c69b-4430-84f3-1622ef1afe75 TYPE=swap
/dev/sdb4: UUID=10C8D0B8C8D09D72 TYPE=ntfs
/dev/sdb1: UUID=eaf36848-eadc-4138-b2a9-db3d8ce82f34 TYPE=ext4
/dev/sdc: LABEL=store UUID=ec93d2c2-7937-40f8-aaa6-c20c9775d93a
UUID_SUB=71e4e0ba-c475-4097-9219-4faf87b9b1d9 TYPE=btrfs
/dev/sda: LABEL=store UUID=ec93d2c2-7937-40f8-aaa6-c20c9775d93a
UUID_SUB=5bda918b-2e06-45ae-9b96-03b2f2b0b338 TYPE=btrfs
# lsblk -f
NAME FSTYPE LABEL MOUNTPOINT
sdabtrfs store
sdb
├─sdb1 ext4 /
├─sdb2 swap [SWAP]
└─sdb4 ntfs
sdcbtrfs store
# udevadm info -qall -p /sys/class/block/sda
P: /devices/pci:00/:00:1f.2/ata1/host0/target0:0:1/0:0:1:0/block/sda
N: sda
S: disk/by-id/ata-WDC_WD5000AAKX-00U6AA0_WD-WCC2ET237617
S: disk/by-id/wwn-0x50014ee2b28542c6
S: disk/by-label/store
S: disk/by-uuid/ec93d2c2-7937-40f8-aaa6-c20c9775d93a
E: DEVLINKS=/dev/disk/by-id/ata-WDC_WD5000AAKX-00U6AA0_WD-WCC2ET237617
/dev/disk/by-id/wwn-0x50014ee2b28542c6 /dev/disk/by-label/store
/dev/disk/by-uuid/ec93d2c2-7937-40f8-aaa6-c20c9775d93a
E: DEVNAME=/dev/sda
E:
DEVPATH=/devices/pci:00/:00:1f.2/ata1/host0/target0:0:1/0:0:1:0/block/sda
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_PUIS=1
E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=86
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=86
E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BTRFS_READY=1
E: ID_BUS=ata
E: ID_FS_LABEL=store
E: ID_FS_LABEL_ENC=store
E: ID_FS_TYPE=btrfs
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=ec93d2c2-7937-40f8-aaa6-c20c9775d93a
E: ID_FS_UUID_ENC=ec93d2c2-7937-40f8-aaa6-c20c9775d93a
E: ID_FS_UUID_SUB=5bda918b-2e06-45ae-9b96-03b2f2b0b338
E: ID_FS_UUID_SUB_ENC=5bda918b-2e06-45ae-9b96-03b2f2b0b338
E: ID_MODEL=WDC_WD5000AAKX-00U6AA0
E:
ID_MODEL_ENC=WDC\x20WD5000AAKX-00U6AA0\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=15.01H15
E: ID_SERIAL=WDC_WD5000AAKX-00U6AA0_WD-WCC2ET237617
E: ID_SERIAL_SHORT=WD-WCC2ET237617
E: ID_TYPE=disk
E: ID_WWN=0x50014ee2b28542c6
E: ID_WWN_WITH_EXTENSION=0x50014ee2b28542c6
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E:
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
Addendum: changing /etc/fstab to name partitions via UUID=... allows a successful boot. This does not excuse the failure to boot when device names are used. zw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747629: systemd: boot fails w/ multi-whole-disk btrfs /home: timed out waiting for dev-sda.device
tags 747629 + moreinfo unreproducible thanks Am 10.05.2014 16:18, schrieb Zack Weinberg: Package: systemd Version: 204-10 Severity: important I have /home spread over two entire disks using btrfs (applied directly to the physical disks; there is no intervening dm/LVM/whatever). These disks have no disklabels. They are referred to in /etc/fstab by device name. I just tried to reproduce your issue, but failed to do so. What I did: - setup a VirtualBox environment with / on ext4 - added two disks /dev/sdb and /dev/sdc - ran mkfs.btrfs /dev/sdb /dev/sdc - added /dev/sdb /mnt btrfs defaults 0 0 to fstab - rebooted with systemd - system came up fine with /mnt being mounted correctly. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
