Bug#856590: systemd: Unspecified problems mounting /usr partition
Thanks Michael, and sorry for the delay. I can confirm that this issue is fixed after the latest update to my system. -- Joel Cross j...@kazbak.co.uk On Tue, 20 Jun 2017, at 09:59 PM, Michael Biebl wrote: > Am 20.06.2017 um 22:54 schrieb Michael Biebl: > > Unfortunately the problem is not reproducible here (tried with a VM with > > several attached disks and a split /usr on the second disk). > > I take that back. I just installed live-config-systemd in the test VM > and that completely hosed the systemd and I'm getting the exact same > error message as you. > > I'll be waiting for confirmation from you that purging the > live-config-systemd package solves your problem before re-assigning the > issue. > > Regards, > Michael > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature)
Bug#856590: systemd: Unspecified problems mounting /usr partition
Am 20.06.2017 um 22:54 schrieb Michael Biebl: > Unfortunately the problem is not reproducible here (tried with a VM with > several attached disks and a split /usr on the second disk). I take that back. I just installed live-config-systemd in the test VM and that completely hosed the systemd and I'm getting the exact same error message as you. I'll be waiting for confirmation from you that purging the live-config-systemd package solves your problem before re-assigning the issue. Regards, 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#856590: systemd: Unspecified problems mounting /usr partition
Am 20.06.2017 um 22:54 schrieb Michael Biebl: > Mar 29 21:23:39 abijah systemd[268]: > /lib/systemd/system-generators/live-config-getty-generator failed with > error code 2. > > How exactly did you install the system? > This file seems to belong to live-config-systemd, can you try and purge > that package? I just noticed that there are already similar bugs filed against live-config-systemd: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855085 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827665 They look very related afaics and should probably be bumped to RC. 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#856590: systemd: Unspecified problems mounting /usr partition
Am 20.06.2017 um 12:32 schrieb Joel Cross: > Dear Michael/Maintainers, > > Just to update you on this: it has been 2 months since my last > submission, and I am still having the same problem. Has anyone had the > chance to look into what the cause could be here? Unfortunately the problem is not reproducible here (tried with a VM with several attached disks and a split /usr on the second disk). I did notice in your journal log the following error message: Mar 29 21:23:39 abijah systemd[268]: /lib/systemd/system-generators/live-config-getty-generator failed with error code 2. How exactly did you install the system? This file seems to belong to live-config-systemd, can you try and purge that package? 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#856590: systemd: Unspecified problems mounting /usr partition
Dear Michael/Maintainers, Just to update you on this: it has been 2 months since my last submission, and I am still having the same problem. Has anyone had the chance to look into what the cause could be here?
Bug#856590: systemd: Unspecified problems mounting /usr partition
On Wed, 12 Apr 2017, at 02:28 PM, Michael Biebl wrote: > Am 12.04.2017 um 22:11 schrieb Joel Cross: > > Mar 29 21:25:09 abijah systemd[1]: > > dev-disk-by\x2duuid-F0C4F042C4F00C9A.device: Job > > dev-disk-by\x2duuid-F0C4F042C4F00C9A.device/start failed with result > > 'timeout'. > > Mar 29 21:25:09 abijah systemd[1]: > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device: > > Job > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device/start > > timed out. > > Mar 29 21:25:09 abijah systemd[1]: Timed out waiting for device > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device. > > Mar 29 21:25:09 abijah systemd[1]: Dependency failed for > > /dev/disk/by-uuid/0797ee37-d1b9-49ea-a865-c73682cd96a7. > > Mar 29 21:25:09 abijah systemd[1]: > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.swap: > > Job > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.swap/start > > failed with result 'dependency'. > > Mar 29 21:25:09 abijah systemd[1]: > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device: > > Job > > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device/start > > failed with result 'timeout'. > > Mar 29 21:25:09 abijah systemd[1]: > > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device: > > Job > > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device/start > > timed out. > > Mar 29 21:25:09 abijah systemd[1]: Timed out waiting for device > > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device. > > Mar 29 21:25:09 abijah systemd[1]: Dependency failed for /home. > > Mar 29 21:25:09 abijah systemd[1]: Dependency failed for Local File Systems. > > Mar 29 21:25:09 abijah systemd[1]: local-fs.target: Job > > local-fs.target/start failed with result 'dependency'. > > Mar 29 21:25:09 abijah systemd[1]: local-fs.target: Triggering OnFailure= > > dependencies. > > Mar 29 21:25:09 abijah systemd[1]: home.mount: Job home.mount/start failed > > with result 'dependency'. > > Mar 29 21:25:09 abijah systemd[1]: > > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device: > > Job > > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device/start > > failed with result > > Your problem doesn't look like it's related to /usr, but /home and swap, > as configured in /etc/fstab, failing. > > Can you please verify that that you have in /etc/fstab actually matches > your current configuration. Hi, I'm pretty sure the failure actually occurs with all three partitions, but it is more severe with /usr because I cannot use the 'nofail' option to ignore the failure. Here's the relevant part of my /etc/fstab: UUID=1ac3a9b3-2ced-4e6c-9378-f8c94ac2983e /usrext4 rw,errors=remount-ro,commit=600 0 1 # /dev/sda7 UUID=868996eb-2b9d-42eb-9bcc-2b23b89dc11b /home ext4 rw,errors=remount-ro0 0 # /dev/sdb4 UUID=0797ee37-d1b9-49ea-a865-c73682cd96a7 swapswap sw,nofail 0 0 Here's the output of `lsblk -o NAME,UUID,LABEL`: NAME UUID LABEL sda ├─sda1 7876BEE376BEA174 SYSTEM ├─sda2 ├─sda3 F2DAFCDFDAFCA151 Recovery ├─sda4 C281-C9E0HP_TOOLS ├─sda5 F0C4F042C4F00C9A ├─sda6 033d10f2-5402-4632-bed0-5e24842cf1b7 ├─sda7 868996eb-2b9d-42eb-9bcc-2b23b89dc11b HOME └─sda8 84f3e7a4-c3af-4ac1-a789-cc554395a50b sdb ├─sdb1 06ad2c23-eac6-4a49-9623-79d9e4a02bbe Boot ├─sdb2 1ac3a9b3-2ced-4e6c-9378-f8c94ac2983e User ├─sdb3 13dc09db-ec38-480a-ac28-fd0ed1a952f8 └─sdb4 0797ee37-d1b9-49ea-a865-c73682cd96a7 Swap And here's the relevant parts of the output of 'mount' after booting the system (pressing ctrl-d after the timeout) - notice that /usr and /home are mounted correctly: /dev/sdb2 on /usr type ext4 (rw,relatime,errors=remount-ro,commit=600,data=ordered) /dev/sda7 on /home type ext4 (rw,relatime,errors=remount-ro,data=ordered) And the output of `swapon -v: NAME TYPE SIZE USED PRIO /dev/sdb4 partition 9.3G 0B -1 -Joel
Bug#856590: systemd: Unspecified problems mounting /usr partition
Am 12.04.2017 um 22:11 schrieb Joel Cross: > Mar 29 21:25:09 abijah systemd[1]: > dev-disk-by\x2duuid-F0C4F042C4F00C9A.device: Job > dev-disk-by\x2duuid-F0C4F042C4F00C9A.device/start failed with result > 'timeout'. > Mar 29 21:25:09 abijah systemd[1]: > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device: > Job > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device/start > timed out. > Mar 29 21:25:09 abijah systemd[1]: Timed out waiting for device > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device. > Mar 29 21:25:09 abijah systemd[1]: Dependency failed for > /dev/disk/by-uuid/0797ee37-d1b9-49ea-a865-c73682cd96a7. > Mar 29 21:25:09 abijah systemd[1]: > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.swap: > Job > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.swap/start > failed with result 'dependency'. > Mar 29 21:25:09 abijah systemd[1]: > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device: > Job > dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d49ea\x2da865\x2dc73682cd96a7.device/start > failed with result 'timeout'. > Mar 29 21:25:09 abijah systemd[1]: > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device: > Job > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device/start > timed out. > Mar 29 21:25:09 abijah systemd[1]: Timed out waiting for device > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device. > Mar 29 21:25:09 abijah systemd[1]: Dependency failed for /home. > Mar 29 21:25:09 abijah systemd[1]: Dependency failed for Local File Systems. > Mar 29 21:25:09 abijah systemd[1]: local-fs.target: Job local-fs.target/start > failed with result 'dependency'. > Mar 29 21:25:09 abijah systemd[1]: local-fs.target: Triggering OnFailure= > dependencies. > Mar 29 21:25:09 abijah systemd[1]: home.mount: Job home.mount/start failed > with result 'dependency'. > Mar 29 21:25:09 abijah systemd[1]: > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device: > Job > dev-disk-by\x2duuid-868996eb\x2d2b9d\x2d42eb\x2d9bcc\x2d2b23b89dc11b.device/start > failed with result Your problem doesn't look like it's related to /usr, but /home and swap, as configured in /etc/fstab, failing. Can you please verify that that you have in /etc/fstab actually matches your current configuration. -- 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#856590: systemd: Unspecified problems mounting /usr partition
(Apologies all - it seems I accidentally sent these logs only to Michael before) On Mon, 27 Mar 2017, at 10:43 PM, Michael Biebl wrote: > > When you are dropped into the recovery shell, please save the output of > udevadm info /sys/class/block/sdb2 > and attach it to the bug report. > A complete log from the boot (journalctl -alb) would be helpful as well. > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) Hi Michael, Here's the log output, as requested. P: /devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sdb/sdb2 N: sdb2 S: disk/by-id/ata-OCZ-AGILITY3_OCZ-PG7Z95NS8R3W5E4Y-part2 S: disk/by-id/wwn-0x5e83a97e0f922dcc-part2 S: disk/by-label/User S: disk/by-partuuid/57f4c922-02 S: disk/by-path/pci-:00:1f.2-ata-5-part2 S: disk/by-uuid/1ac3a9b3-2ced-4e6c-9378-f8c94ac2983e E: DEVLINKS=/dev/disk/by-uuid/1ac3a9b3-2ced-4e6c-9378-f8c94ac2983e /dev/disk/by-label/User /dev/disk/by-partuuid/57f4c922-02 /dev/disk/by-path/pci-:00:1f.2-ata-5-part2 /dev/disk/by-id/ata-OCZ-AGILITY3_OCZ-PG7Z95NS8R3W5E4Y-part2 /dev/disk/by-id/wwn-0x5e83a97e0f922dcc-part2 E: DEVNAME=/dev/sdb2 E: DEVPATH=/devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sdb/sdb2 E: DEVTYPE=partition E: ID_ATA=1 E: ID_ATA_DOWNLOAD_MICROCODE=1 E: ID_ATA_FEATURE_SET_APM=1 E: ID_ATA_FEATURE_SET_APM_CURRENT_VALUE=254 E: ID_ATA_FEATURE_SET_APM_ENABLED=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_ERASE_UNIT_MIN=2 E: ID_ATA_FEATURE_SET_SMART=1 E: ID_ATA_FEATURE_SET_SMART_ENABLED=1 E: ID_ATA_ROTATION_RATE_RPM=0 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_BUS=ata E: ID_FS_LABEL=User E: ID_FS_LABEL_ENC=User E: ID_FS_TYPE=ext4 E: ID_FS_USAGE=filesystem E: ID_FS_UUID=1ac3a9b3-2ced-4e6c-9378-f8c94ac2983e E: ID_FS_UUID_ENC=1ac3a9b3-2ced-4e6c-9378-f8c94ac2983e E: ID_FS_VERSION=1.0 E: ID_MODEL=OCZ-AGILITY3 E: ID_MODEL_ENC=OCZ-AGILITY3\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_PART_ENTRY_DISK=8:16 E: ID_PART_ENTRY_NUMBER=2 E: ID_PART_ENTRY_OFFSET=1026048 E: ID_PART_ENTRY_SCHEME=dos E: ID_PART_ENTRY_SIZE=106954752 E: ID_PART_ENTRY_TYPE=0x83 E: ID_PART_ENTRY_UUID=57f4c922-02 E: ID_PART_TABLE_TYPE=dos E: ID_PART_TABLE_UUID=57f4c922 E: ID_PATH=pci-:00:1f.2-ata-5 E: ID_PATH_TAG=pci-_00_1f_2-ata-5 E: ID_REVISION=2.25 E: ID_SERIAL=OCZ-AGILITY3_OCZ-PG7Z95NS8R3W5E4Y E: ID_SERIAL_SHORT=OCZ-PG7Z95NS8R3W5E4Y E: ID_TYPE=disk E: ID_WWN=0x5e83a97e0f922dcc E: ID_WWN_WITH_EXTENSION=0x5e83a97e0f922dcc E: MAJOR=8 E: MINOR=18 E: PARTN=2 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=4698411 -- Logs begin at Wed 2017-03-29 21:23:39 CST, end at Wed 2017-03-29 21:25:17 CST. -- Mar 29 21:23:39 abijah kernel: Linux version 4.9.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170221 (Debian 6.3.0-8) ) #1 SMP Debian 4.9.13-1 (2017-02-27) Mar 29 21:23:39 abijah kernel: Command line: BOOT_IMAGE=/vmlinuz-4.9.0-2-amd64 root=UUID=033d10f2-5402-4632-bed0-5e24842cf1b7 ro quiet splash resume=UUID=84f3e7a4-c3af-4ac1-a789-cc554395a50b Mar 29 21:23:39 abijah kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 29 21:23:39 abijah kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 29 21:23:39 abijah kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 29 21:23:39 abijah kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 29 21:23:39 abijah kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Mar 29 21:23:39 abijah kernel: x86/fpu: Using 'eager' FPU context switches. Mar 29 21:23:39 abijah kernel: e820: BIOS-provided physical RAM map: Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0x-0x0009d7ff] usable Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0x0009d800-0x0009] reserved Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0x000e-0x000f] reserved Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0x0010-0xace3efff] usable Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0xace3f000-0xacebefff] reserved Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0xacebf000-0xacfbefff] ACPI NVS Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0xacfbf000-0xacffefff] ACPI data Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem 0xacfff000-0xacff] usable Mar 29 21:23:39 abijah kernel: BIOS-e820: [mem
Bug#856590: systemd: Unspecified problems mounting /usr partition
Hi, Le 31/03/2017 à 10:21, Michael Biebl a écrit : The udevadm info dump you attached shows that TAGS=:systemd: is missing for all your partitions, thus systemd doesn't consider them ready. The flag is no more missing, and the boot problem is still present. udevadm info /dev/sda6 P: /devices/pci:00/:00:16.1/:0c:00.0/host2/target2:0:0/2:0:0:0/block/sda/sda6 N: sda6 S: disk/by-partuuid/000586b9-06 S: disk/by-path/pci-:0c:00.0-scsi-0:0:0:0-part6 S: disk/by-uuid/08511bfb-ef79-432c-b792-c455ec64679e E: DEVLINKS=/dev/disk/by-partuuid/000586b9-06 /dev/disk/by-path/pci-:0c:00.0-scsi-0:0:0:0-part6 /dev/disk/by-uuid/08511bfb-ef79-432c-b792-c455ec64679e E: DEVNAME=/dev/sda6 E: DEVPATH=/devices/pci:00/:00:16.1/:0c:00.0/host2/target2:0:0/2:0:0:0/block/sda/sda6 E: DEVTYPE=partition E: ID_BUS=scsi E: ID_FS_TYPE=ext3 E: ID_FS_USAGE=filesystem E: ID_FS_UUID=08511bfb-ef79-432c-b792-c455ec64679e E: ID_FS_UUID_ENC=08511bfb-ef79-432c-b792-c455ec64679e E: ID_FS_VERSION=1.0 E: ID_MODEL=Virtual_disk E: ID_MODEL_ENC=Virtual\x20disk\x20\x20\x20\x20 E: ID_PART_ENTRY_DISK=8:0 E: ID_PART_ENTRY_NUMBER=6 E: ID_PART_ENTRY_OFFSET=46874624 E: ID_PART_ENTRY_SCHEME=dos E: ID_PART_ENTRY_SIZE=7811072 E: ID_PART_ENTRY_TYPE=0x83 E: ID_PART_ENTRY_UUID=000586b9-06 E: ID_PART_TABLE_TYPE=dos E: ID_PART_TABLE_UUID=000586b9 E: ID_PATH=pci-:0c:00.0-scsi-0:0:0:0 E: ID_PATH_TAG=pci-_0c_00_0-scsi-0_0_0_0 E: ID_REVISION=1.0 E: ID_SCSI=1 E: ID_TYPE=disk E: ID_VENDOR=VMware E: ID_VENDOR_ENC=VMware\x20\x20 E: MAJOR=8 E: MINOR=6 E: PARTN=6 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=2997221 That tag is set in /lib/udev/rules.d/99-systemd.rules. Is that file missing? This file is present. Do you have any custom udev rules in /etc/udev/rules.d ? ls -l /etc/udev/rules.d/ -rw-r--r-- 1 root root 789 Mar 6 2012 70-persistent-cd.rules Another (probably unrelated) observation is, that your /etc/fstab uses type ext4 while the udev info shows ID_FS_TYPE=ext3 Oups, this morning, i'm converting ext3 to ext4, you should consider the following /etc/fstab: # proc/proc procdefaults0 0 # / was on /dev/sda1 during installation UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1 / ext3 errors=remount-ro 0 1 # /home was on /dev/sda7 during installation UUID=60dac49d-8399-4a6f-9ded-7adc952fc33e /home ext4 defaults 0 2 # /tmp was on /dev/sda6 during installation UUID=08511bfb-ef79-432c-b792-c455ec64679e /tmp ext3 defaults 0 2 # /var was on /dev/sda5 during installation UUID=66610011-7694-4574-ba2f-7ab34169b037 /var ext3 defaults 0 2 # swap was on /dev/sda2 during installation UUID=840f5b96-d8ce-4ad5-9750-330cb69bf691 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/sda7 is now converted: udevadm info /dev/sda7 [...] S: disk/by-uuid/60dac49d-8399-4a6f-9ded-7adc952fc33e E: DEVLINKS=/dev/disk/by-path/pci-:0c:00.0-scsi-0:0:0:0-part7 /dev/disk/by-p artuuid/000586b9-07 /dev/disk/by-uuid/60dac49d-8399-4a6f-9ded-7adc952fc33e E: DEVNAME=/dev/sda7 [...] E: ID_FS_TYPE=ext4 E: ID_FS_USAGE=filesystem [...] The problem is still present with this /etc/fstab configuration. In any case, we shouldn't hijack this bug report. It's probably not the same issue. If you think it's not related, I can open a new bug report. Thanks -- *Emmanuel DECAEN*
Bug#856590: systemd: Unspecified problems mounting /usr partition
Am 31.03.2017 um 09:13 schrieb Emmanuel DECAEN: > Hi, > > The system boots correctly using sysV grub option, but randomly fails > during boot using systemd (grub default). > > /etc/fstab: > # > proc/proc procdefaults0 0 > # / was on /dev/sda1 during installation > UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1 / ext4 errors=remount-ro > 0 1 > # /home was on /dev/sda7 during installation > UUID=60dac49d-8399-4a6f-9ded-7adc952fc33e /home ext4 defaults > 0 2 > # /tmp was on /dev/sda6 during installation > UUID=08511bfb-ef79-432c-b792-c455ec64679e /tmp ext4 defaults > 0 2 > # /var was on /dev/sda5 during installation > UUID=66610011-7694-4574-ba2f-7ab34169b037 /var ext4 defaults > 0 2 > # swap was on /dev/sda2 during installation > UUID=840f5b96-d8ce-4ad5-9750-330cb69bf691 none swap sw > 0 0 The udevadm info dump you attached shows that TAGS=:systemd: is missing for all your partitions, thus systemd doesn't consider them ready. That tag is set in /lib/udev/rules.d/99-systemd.rules. Is that file missing? Do you have any custom udev rules in /etc/udev/rules.d ? Another (probably unrelated) observation is, that your /etc/fstab uses type ext4 while the udev info shows ID_FS_TYPE=ext3 In any case, we shouldn't hijack this bug report. It's probably not the same issue. -- 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#856590: systemd: Unspecified problems mounting /usr partition
Hi, The system boots correctly using sysV grub option, but randomly fails during boot using systemd (grub default). /etc/fstab: # proc/proc procdefaults0 0 # / was on /dev/sda1 during installation UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1 / ext4 errors=remount-ro 0 1 # /home was on /dev/sda7 during installation UUID=60dac49d-8399-4a6f-9ded-7adc952fc33e /home ext4 defaults 0 2 # /tmp was on /dev/sda6 during installation UUID=08511bfb-ef79-432c-b792-c455ec64679e /tmp ext4 defaults 0 2 # /var was on /dev/sda5 during installation UUID=66610011-7694-4574-ba2f-7ab34169b037 /var ext4 defaults 0 2 # swap was on /dev/sda2 during installation UUID=840f5b96-d8ce-4ad5-9750-330cb69bf691 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Regards, -- *Emmanuel DECAEN*
Bug#856590: systemd: Unspecified problems mounting /usr partition
Am 30.03.2017 um 23:07 schrieb Emmanuel DECAEN: > Hi, > > I have the same of problem on multiple servers with systemd/232-19. > > You will find journalctl -alb et udevadm info in attachments. Your journal shows problems with /var, /tmp, /home and swap. Makes me wonder if your /etc/fstab is actually correct. -- 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#856590: systemd: Unspecified problems mounting /usr partition
Control: tags -1 + moreinfo Am 02.03.2017 um 19:20 schrieb Joel Cross: > -- Subject: Unit dev-sdb2.device has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Unit dev-sdb2.device has failed. > -- > -- The result is timeout. > Mar 02 11:26:47 abijah systemd[1]: dev-sdb2.device: Job dev-sdb2.device/start > failed with result 'timeout'. > Mar 02 11:26:47 abijah systemd[1]: dev-disk- > by\x2duuid-06ad2c23\x2deac6\x2d4a49\x2d9623\x2d79d9e4a02bbe.device: Job dev- > disk-by\x2duuid-06ad2c23\x2dea > Mar 02 11:26:47 abijah systemd[1]: Timed out waiting for device dev-disk- > by\x2duuid-06ad2c23\x2deac6\x2d4a49\x2d9623\x2d79d9e4a02bbe.device. > > Please let me know if you'd like me to attach any other logs. When you are dropped into the recovery shell, please save the output of udevadm info /sys/class/block/sdb2 and attach it to the bug report. A complete log from the boot (journalctl -alb) would be helpful as well. -- 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
