[opensuse-support] 15.0 most boots halt in emergency mode
# inxi -b System: Host: i2134 Kernel: 4.12.14-lp150.12.48-default x86_64 bits: 64 Desktop: Trinity R14.0.6 Distro: openSUSE Leap 15.0 Machine: Type: Desktop System: Apple product: iMac7,1 v: 1.0 serial: QP7440XDX89 Mobo: Apple model: Mac-F42386C8 v: PVT serial: 1 UEFI: Apple v: IM71.88Z.007A.B03.0803051705 date: 03/05/08 CPU: Dual Core: Intel Core2 Duo T7700 type: MCP speed: 1794 MHz min/max: 800/2400 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] driver: radeon v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz OpenGL: renderer: AMD RV630 (DRM 2.50.0 / 4.12.14-lp150.12.48-default LLVM 5.0.1) v: 3.3 Mesa 18.0.2 Network: Device-1: Broadcom Limited BCM4321 802.11a/b/g/n driver: b43-pci-bridge Device-2: Marvell 88E8058 PCI-E Gigabit Ethernet driver: sky2 Drives: Local Storage: total: 931.51 GiB used: 26.31 GiB (2.8%) Info: Processes: 156 Uptime: N/A Memory: 3.84 GiB used: 486.4 MiB (12.4%) Shell: bash inxi: 3.0.32 # journal -b | grep ailed: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt full journal: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-201903292030.txt # cat /etc/fstab: LABEL=EFI /boot/efi vfat codepage=437 0 0 LABEL=st10swapper swap swap defaults 0 0 LABEL=st10suseleap / ext4 noatime 1 1 LABEL=st10linuxnext /disks/s151 ext4 noatime 1 2 LABEL=st10susehome /home ext4 noatime 1 2 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part2 /macsys hfsplus ro,nofail 0 0 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus force,uid=501,gid=100,umask=002,noatime,nofail 0 0 I don't see any clues to why this happens on most boots. Immediate Ctrl-D always triggers successful init completion. Can anyone see what I am missing to cause this? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/03/2019 03.07, Felix Miata wrote:
# inxi -b System: Host: i2134 Kernel: 4.12.14-lp150.12.48-default x86_64 bits: 64 Desktop: Trinity R14.0.6 Distro: openSUSE Leap 15.0 Machine: Type: Desktop System: Apple product: iMac7,1 v: 1.0 serial: QP7440XDX89 Mobo: Apple model: Mac-F42386C8 v: PVT serial: 1 UEFI: Apple v: IM71.88Z.007A.B03.0803051705 date: 03/05/08 CPU: Dual Core: Intel Core2 Duo T7700 type: MCP speed: 1794 MHz min/max: 800/2400 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] driver: radeon v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz OpenGL: renderer: AMD RV630 (DRM 2.50.0 / 4.12.14-lp150.12.48-default LLVM 5.0.1) v: 3.3 Mesa 18.0.2 Network: Device-1: Broadcom Limited BCM4321 802.11a/b/g/n driver: b43-pci-bridge Device-2: Marvell 88E8058 PCI-E Gigabit Ethernet driver: sky2 Drives: Local Storage: total: 931.51 GiB used: 26.31 GiB (2.8%) Info: Processes: 156 Uptime: N/A Memory: 3.84 GiB used: 486.4 MiB (12.4%) Shell: bash inxi: 3.0.32 # journal -b | grep ailed: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt
Home failed to mount. Also swap. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. composed on 2019-03-29 03:19 (UTC+0100):
http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt
Home failed to mount. Also swap.
So I saw, many many times so far. However, as soon as I get get logged in, df shows normal output: e.g.: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda6 32652052 7945520 23024820 26% / /dev/sda1 376616 17160 359456 5% /boot/efi /dev/sda2 36997232 14084668 22912564 39% /macsys /dev/sda7 32652148 2314252 28656184 8% /disks/s151 /dev/sda8 409582904 456500 409110020 1% /home /dev/sda4 450428928 19289192 431139736 5% /home/macdata Going to reboot now to try to get Andrei answered with better log/journal.... -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
30.03.2019 5:07, Felix Miata пишет:
# inxi -b System: Host: i2134 Kernel: 4.12.14-lp150.12.48-default x86_64 bits: 64 Desktop: Trinity R14.0.6 Distro: openSUSE Leap 15.0 Machine: Type: Desktop System: Apple product: iMac7,1 v: 1.0 serial: QP7440XDX89 Mobo: Apple model: Mac-F42386C8 v: PVT serial: 1 UEFI: Apple v: IM71.88Z.007A.B03.0803051705 date: 03/05/08 CPU: Dual Core: Intel Core2 Duo T7700 type: MCP speed: 1794 MHz min/max: 800/2400 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] driver: radeon v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz OpenGL: renderer: AMD RV630 (DRM 2.50.0 / 4.12.14-lp150.12.48-default LLVM 5.0.1) v: 3.3 Mesa 18.0.2 Network: Device-1: Broadcom Limited BCM4321 802.11a/b/g/n driver: b43-pci-bridge Device-2: Marvell 88E8058 PCI-E Gigabit Ethernet driver: sky2 Drives: Local Storage: total: 931.51 GiB used: 26.31 GiB (2.8%) Info: Processes: 156 Uptime: N/A Memory: 3.84 GiB used: 486.4 MiB (12.4%) Shell: bash inxi: 3.0.32 # journal -b | grep ailed: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt full journal: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-201903292030.txt
It's not full. Entries start at 20:49:12; at 20:49:16 systemd times out waiting for device to appear. Default timeout is 90 seconds, which means at least 86 seconds are missing in output. There are also no kernel boot messages or initrd messages.
# cat /etc/fstab: LABEL=EFI /boot/efi vfat codepage=437 0 0 LABEL=st10swapper swap swap defaults 0 0 LABEL=st10suseleap / ext4 noatime 1 1 LABEL=st10linuxnext /disks/s151 ext4 noatime 1 2 LABEL=st10susehome /home ext4 noatime 1 2
/dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part2 /macsys hfsplus ro,nofail 0 0 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus force,uid=501,gid=100,umask=002,noatime,nofail 0 0
I don't see any clues to why this happens on most boots. Immediate Ctrl-D always triggers successful init completion. Can anyone see what I am missing to cause this?
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Andrei Borzenkov composed on 2019-03-30 07:15 (UTC+0300):
Felix Miata composed:
http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt full journal: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-201903292030.txt
It's not full. Entries start at 20:49:12; at 20:49:16 systemd times out waiting for device to appear. Default timeout is 90 seconds, which means at least 86 seconds are missing in output. There are also no kernel boot messages or initrd messages.
Immediately prior boot (graphical.target; did not stop in emergency mode): full: 144kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-full-RL5-201903300026.txt ailed grep'd: 1.2kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-RL5-201903300026.txt Current boot (multi-user.target): dmesg: 76kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-dmesg-RL3-201903300120.txt full: 124kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-full-RL3-201903300120.txt ailed grep'd: 2.4kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-RL3-201903300120.txt # sorted mount excerpts: /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/sda2 on /macsys type hfsplus (ro,relatime,umask=22,uid=0,gid=0,nls=utf8) /dev/sda4 on /home/macdata type hfsplus (rw,noatime,umask=2,uid=501,gid=100,nls=utf8) /dev/sda6 on / type ext4 (rw,noatime,data=ordered) /dev/sda7 on /disks/s151 type ext4 (rw,noatime,data=ordered) /dev/sda8 on /home type ext4 (rw,noatime,data=ordered) # sorted df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 376616 17160 359456 5% /boot/efi /dev/sda2 36997232 14084668 22912564 39% /macsys /dev/sda4 450428928 19289192 431139736 5% /home/macdata /dev/sda6 32652052 7945912 23024428 26% / /dev/sda7 32652148 2314252 28656184 8% /disks/s151 /dev/sda8 409582904 456500 409110020 1% /home -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/03/2019 07.07, Felix Miata wrote:
Andrei Borzenkov composed on 2019-03-30 07:15 (UTC+0300):
Felix Miata composed:
http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt full journal: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-201903292030.txt
It's not full. Entries start at 20:49:12; at 20:49:16 systemd times out waiting for device to appear. Default timeout is 90 seconds, which means at least 86 seconds are missing in output. There are also no kernel boot messages or initrd messages.
This is the on that matters:
full: 124kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-full-RL3-201903300120.txt
Mar 30 01:21:02 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Job dev-disk-by\x2dlabel-st10susehome.device/start timed out. But I don't understand the timestamps, almost everything is logged at "Mar 30 01:20:50". You have almost no space for the log: Mar 30 01:20:57 i2134 systemd-journald[374]: System journal (/var/log/journal/cffc04f423524d27ba260972e6732ea5) is 3.0M, max 1.0M, 0B free. network has problems: Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Firmware file "b43/ucode11.fw" not found Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode11.fw" not found Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Please open a terminal and enter the command "sudo /usr/sbin/install_bcm43xx_firmware" to download the correct firmware for this driver version. For an off-line installation, go to http://en.opensuse.org/HCL/Network_Adapters_(Wireless)/Broadcom_BCM43xx and follow the instructions in the "Installing firmware from RPM packages" section. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. composed on 2019-03-30 14:27 (UTC+0100):
Felix Miata wrote:
Andrei Borzenkov composed on 2019-03-30 07:15 (UTC+0300):
It's not full. Entries start at 20:49:12; at 20:49:16 systemd times out waiting for device to appear. Default timeout is 90 seconds, which means at least 86 seconds are missing in output. There are also no kernel boot messages or initrd messages.
This is the on that matters:
full: 124kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-full-RL3-201903300120.txt
Mar 30 01:21:02 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Job dev-disk-by\x2dlabel-st10susehome.device/start timed out.
Systemd seems to be lying about the sequence of events: fstab: LABEL=st10susehome /home ext4 noatime 1 2 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus force,uid=501,gid=100,umask=002,noatime,nofail 0 0 That fstab was created last June. I have no recollection how I got the hfs added filesystems added to fstab, possibly YaST. nofail I'm sure I added. Search for force in man fstab produces nothing. current journal: Mar 30 13:54:09 i2134 systemd[1]: Dependency failed for /home/macdata. Mar 30 13:54:09 i2134 systemd[1]: home-macdata.mount: Job home-macdata.mount/start failed with result 'dependency'. Mar 30 13:54:09 i2134 systemd[1]: dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device: Job dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device/start failed with result 'timeout'. /home needs to be mounted before /home/macdata can be mounted, right? So it shouldn't try to mount /home/macdata until mounting /home succeeds. When I commented out the hfs lines in fstab there was no stop in emergency mode on next boot, but the 15.1 Grub menu appeared instead of the Grub 15.0 menu. On next boot, the Grub 15.0 menu was back, but it stopped in emergency again: Mar 30 14:36:25 i2134 systemd[1]: Dependency failed for /boot/efi. Mar 30 14:36:25 i2134 systemd[1]: Dependency failed for Local File Systems. Mar 30 14:36:25 i2134 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Mar 30 14:36:25 i2134 systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'. Mar 30 14:36:25 i2134 systemd[1]: dev-disk-by\x2dlabel-EFI.device: Job dev-disk-by\x2dlabel-EFI.device/start failed with result 'timeout'. Yet, /boot/efi is mounted, accessible and has 95% freespace. This is multiboot. 15.1 has no such mounting trouble. Not getting the expected boot screen on reboot or power up has been randomly occurring ever since the upgrade from Snow Leopard to El Capitan. My forum thread about this iMac ordeal: https://forums.opensuse.org/showthread.php/535388-Installation-on-a-Mac
But I don't understand the timestamps, almost everything is logged at "Mar 30 01:20:50".
I have no real idea. I suspect a defective firmware upgrade accompanied the Snow Leopard to El Capitan upgrade, but no idea how to find any proof.
You have almost no space for the log:
Mar 30 01:20:57 i2134 systemd-journald[374]: System journal (/var/log/journal/cffc04f423524d27ba260972e6732ea5) is 3.0M, max 1.0M, 0B free.
This too has to be bogus. Freespace on / is consistently 74%. Installed RAM is 4GB, same as maximum supported RAM.
network has problems:
Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Firmware file "b43/ucode11.fw" not found Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode11.fw" not found Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Please open a terminal and enter the command "sudo /usr/sbin/install_bcm43xx_firmware" to download the correct firmware for this driver version. For an off-line installation, go to http://en.opensuse.org/HCL/Network_Adapters_(Wireless)/Broadcom_BCM43xx and follow the instructions in the "Installing firmware from RPM packages" section.
This is an iMac. It apparently has no BIOS facility to disable unneeded devices. AFAICT, b43* is for (unneeded/unwanted) wireless. I found nothing in systemctl grep net of list-units or list-unit-files to suggest how to disable attempts to use wireless. So I've been ignoring those b43* messages that to me are just noise. Ethernet gets the job done without all the extra brain damaging radiation (or does it?). -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/03/2019 19.49, Felix Miata wrote:
Carlos E. R. composed on 2019-03-30 14:27 (UTC+0100):
Systemd seems to be lying about the sequence of events: fstab: LABEL=st10susehome /home ext4 noatime 1 2 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus force,uid=501,gid=100,umask=002,noatime,nofail 0 0
That fstab was created last June. I have no recollection how I got the hfs added filesystems added to fstab, possibly YaST. nofail I'm sure I added. Search for force in man fstab produces nothing.
Ah.
current journal: Mar 30 13:54:09 i2134 systemd[1]: Dependency failed for /home/macdata. Mar 30 13:54:09 i2134 systemd[1]: home-macdata.mount: Job home-macdata.mount/start failed with result 'dependency'. Mar 30 13:54:09 i2134 systemd[1]: dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device: Job dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device/start failed with result 'timeout'.
/home needs to be mounted before /home/macdata can be mounted, right?
So that's why the emergency mode. It tries /home/macdata before. The second try without doing anything, /home is already mounted, so succeeds. Trick dev1 /firstone type options 1 2 dev2 /firstone/two type options 1 3
network has problems:
Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Firmware file "b43/ucode11.fw" not found Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode11.fw" not found Mar 30 01:21:01 i2134 kernel: b43-phy0 ERROR: Please open a terminal and enter the command "sudo /usr/sbin/install_bcm43xx_firmware" to download the correct firmware for this driver version. For an off-line installation, go to http://en.opensuse.org/HCL/Network_Adapters_(Wireless)/Broadcom_BCM43xx and follow the instructions in the "Installing firmware from RPM packages" section.
This is an iMac. It apparently has no BIOS facility to disable unneeded devices. AFAICT, b43* is for (unneeded/unwanted) wireless. I found nothing in systemctl grep net of list-units or list-unit-files to suggest how to disable attempts to use wireless. So I've been ignoring those b43* messages that to me are just noise. Ethernet gets the job done without all the extra brain damaging radiation (or does it?).
Argh. An imac. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. composed on 2019-03-30 15:37 (UTC+0100):
Felix Miata wrote:
Carlos E. R. composed on 2019-03-30 19:27 (UTC+0100):
Systemd seems to be lying about the sequence of events: fstab: LABEL=st10susehome /home ext4 noatime 1 2 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus force,uid=501,gid=100,umask=002,noatime,nofail 0 0
That fstab was created last June. I have no recollection how I got the hfs added filesystems added to fstab, possibly YaST. nofail I'm sure I added. Search for force in man fstab produces nothing.
Ah.
current journal: Mar 30 13:54:09 i2134 systemd[1]: Dependency failed for /home/macdata. Mar 30 13:54:09 i2134 systemd[1]: home-macdata.mount: Job home-macdata.mount/start failed with result 'dependency'. Mar 30 13:54:09 i2134 systemd[1]: dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device: Job dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device/start failed with result 'timeout'.
/home needs to be mounted before /home/macdata can be mounted, right?
So that's why the emergency mode.
So it would seem, but...
It tries /home/macdata before. The second try without doing anything, /home is already mounted, so succeeds.
Trick
dev1 /firstone type options 1 2 dev2 /firstone/two type options 1 3
No help (as I expected, from man fstab: The sixth field (fs_passno). This field is used by fsck(8) to determine the order in which filesystem checks are done at boot time. The root filesystem should be specified with a fs_passno of 1. Other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. Defaults to zero (don't fsck) if not present.): # /etc/fstab: LABEL=EFI /boot/efi vfat codepage=437 0 0 LABEL=st10swapper swap swap defaults 0 0 LABEL=st10suseleap / ext4 noatime 1 1 LABEL=st10linuxnext /disks/s151 ext4 noatime 1 2 LABEL=st10susehome /home ext4 noatime 1 2 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part2 /macsys hfsplus ro,nofail 1 3 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus uid=501,gid=100,umask=002,noatime,nofail 1 3 # journalctl -b | grep ailed | egrep -v 'b43|kbd' Mar 30 21:50:24 i2134 systemd-udevd[456]: Process 'hid2hci --method=csr --devpath=/devices/pci0000:00/0000:00:1a.0/usb1/1-1' failed with exit code 1. Mar 30 21:50:24 i2134 kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -71 Mar 30 21:50:25 i2134 systemd[1]: Dependency failed for /home/macdata. Mar 30 21:50:25 i2134 systemd[1]: home-macdata.mount: Job home-macdata.mount/start failed with result 'dependency'. Mar 30 21:50:25 i2134 systemd[1]: dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device: Job dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart4.device/start failed with result 'timeout'. Mar 30 21:50:25 i2134 systemd[1]: Dependency failed for /home. Mar 30 21:50:25 i2134 systemd[1]: Dependency failed for Local File Systems. Mar 30 21:50:25 i2134 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Mar 30 21:50:25 i2134 systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'. Mar 30 21:50:25 i2134 systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/st10susehome. Mar 30 21:50:25 i2134 systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-st10susehome.service: Job systemd-fsck@dev-disk-by\x2dlabel-st10susehome.service/start failed with result 'dependency'. Mar 30 21:50:25 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Job dev-disk-by\x2dlabel-st10susehome.device/start failed with result 'timeout'. Mar 30 21:50:25 i2134 systemd[1]: Dependency failed for /macsys. Mar 30 21:50:25 i2134 systemd[1]: macsys.mount: Job macsys.mount/start failed with result 'dependency'. Mar 30 21:50:25 i2134 systemd[1]: dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart2.device: Job dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A1LQPM\x2dpart2.device/start failed with result 'timeout'. Mar 30 21:50:25 i2134 systemd[1]: Dependency failed for /boot/efi. Mar 30 21:50:25 i2134 systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'. Mar 30 21:50:25 i2134 systemd[1]: dev-disk-by\x2dlabel-EFI.device: Job dev-disk-by\x2dlabel-EFI.device/start failed with result 'timeout'. Mar 30 21:50:26 i2134 systemd-udevd[445]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99. Other than the init stoppage and the failure messages, boot seems totally normal. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 31/03/2019 04.35, Felix Miata wrote:
Trick dev1 /firstone type options 1 2 dev2 /firstone/two type options 1 3 No help (as I expected, from man fstab: The sixth field (fs_passno). This field is used by fsck(8) to determine the order in which filesystem checks are done at boot time. The root filesystem should be specified with a fs_passno of 1. Other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. Defaults to zero (don't fsck) if not present.):
It is an old trick. No warranty that systemd honours it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Hello, Am Sonntag, 31. März 2019, 04:35:50 CEST schrieb Felix Miata:
Carlos E. R. composed on 2019-03-30 15:37 (UTC+0100):
It tries /home/macdata before. The second try without doing anything, /home is already mounted, so succeeds.
Trick
dev1 /firstone type options 1 2 dev2 /firstone/two type options 1 3
No help (as I expected, from man fstab: [...]
Try to create a file /etc/systemd/system/firstone-two.mount.d/after.conf with the following content: [Unit] After=firstone.mount After the next boot, check systemctl cat firstone-two.mount It should list the addition at the end. (obviously you'll need to replace "firstone" and "two" with your real mountpoints everywhere) Even if that helps, please open a bugreport. systemd should detect this dependency itsself, and first mount the parent directory. Regards, Christian Boltz -- Dieser Indizierungsmurks. Semantikgefuckel, dass das System unbenutzbar macht. Aber gut, dass man zwei Knie hat, in die man sich schießen kann. [Lars Müller in opensuse-de] -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
31.03.2019 18:53, Christian Boltz пишет:
Hello,
Am Sonntag, 31. März 2019, 04:35:50 CEST schrieb Felix Miata:
Carlos E. R. composed on 2019-03-30 15:37 (UTC+0100):
It tries /home/macdata before. The second try without doing anything, /home is already mounted, so succeeds.
Trick
dev1 /firstone type options 1 2 dev2 /firstone/two type options 1 3
No help (as I expected, from man fstab: [...]
Try to create a file /etc/systemd/system/firstone-two.mount.d/after.conf
with the following content:
[Unit] After=firstone.mount
After the next boot, check systemctl cat firstone-two.mount It should list the addition at the end.
(obviously you'll need to replace "firstone" and "two" with your real mountpoints everywhere)
Even if that helps, please open a bugreport. systemd should detect this dependency itsself, and first mount the parent directory.
This is irrelevant. Startup fails die to timeout waiting for block device for (all) mount points, not because mount point itself is missing. The problem is that it happens 12 seconds after boot (the whole boot sequence until logs are taken is about 1 minute) while device job timeout should be 90 seconds. There is tiny chance that timeouts are different for unknown reasons. Output of systemctl show '*.device' '*.mount' -p JobTimeoutUSec -p JobRunningTimeoutUSec may be interesting. Otherwise hopefully it can be reproduced with debug level logs; booting with systemd.log_level=debug printk.devkmsg=on log_buf_len=16M could give some clue what happens. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Andrei Borzenkov composed on 2019-03-31 22:56 (UTC+0300):
This is irrelevant. Startup fails die to timeout waiting for block device for (all) mount points, not because mount point itself is missing. The problem is that it happens 12 seconds after boot (the whole boot sequence until logs are taken is about 1 minute) while device job timeout should be 90 seconds.
There is tiny chance that timeouts are different for unknown reasons. Output of
systemctl show '*.device' '*.mount' -p JobTimeoutUSec -p JobRunningTimeoutUSec
214 lines of "JobTimeoutUSec=infinity" 213 blank lines in between them
may be interesting. Otherwise hopefully it can be reproduced with debug level logs; booting with
systemd.log_level=debug printk.devkmsg=on log_buf_len=16M
could give some clue what happens.
# journalctl -b # from within last boot: 97kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311830.txt # journalctl -b # from within current boot: 132kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311842.txt -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
01.04.2019 1:47, Felix Miata пишет:
Andrei Borzenkov composed on 2019-03-31 22:56 (UTC+0300):
This is irrelevant. Startup fails die to timeout waiting for block device for (all) mount points, not because mount point itself is missing. The problem is that it happens 12 seconds after boot (the whole boot sequence until logs are taken is about 1 minute) while device job timeout should be 90 seconds.
There is tiny chance that timeouts are different for unknown reasons. Output of
systemctl show '*.device' '*.mount' -p JobTimeoutUSec -p JobRunningTimeoutUSec
214 lines of "JobTimeoutUSec=infinity" 213 blank lines in between them
There should have been two lines for each unit. Are you sure you are not misspelled it?
may be interesting. Otherwise hopefully it can be reproduced with debug level logs; booting with
systemd.log_level=debug printk.devkmsg=on log_buf_len=16M
could give some clue what happens.
# journalctl -b # from within last boot: 97kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311830.txt # journalctl -b # from within current boot: 132kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311842.txt
It is useless. Looking at one of your other logs Mar 30 01:20:57 i2134 systemd-journald[374]: System journal (/var/log/journal/cffc04f423524d27ba260972e6732ea5) is 3.0M, max 1.0M, 0B free. You restricted your persistent journal to 1M so most logs are hopelessly incomplete. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Andrei Borzenkov composed on 2019-04-01 07:12 (UTC+0300):
Felix Miata composed:
Andrei Borzenkov composed on 2019-03-31 22:56 (UTC+0300):
This is irrelevant. Startup fails die to timeout waiting for block device for (all) mount points, not because mount point itself is missing. The problem is that it happens 12 seconds after boot (the whole boot sequence until logs are taken is about 1 minute) while device job timeout should be 90 seconds.
There is tiny chance that timeouts are different for unknown reasons. Output of
systemctl show '*.device' '*.mount' -p JobTimeoutUSec -p JobRunningTimeoutUSec
214 lines of "JobTimeoutUSec=infinity" 213 blank lines in between them
There should have been two lines for each unit. Are you sure you are not misspelled it?
.bash_history showed I had left off the last 4 characters. Now: http://fm.no-ip.com/Tmp/SUSE/Leap/syctl-showmount-201904010110.txt
may be interesting. Otherwise hopefully it can be reproduced with debug level logs; booting with
systemd.log_level=debug printk.devkmsg=on log_buf_len=16M
could give some clue what happens.
# journalctl -b # from within last boot: 97kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311830.txt # journalctl -b # from within current boot: 132kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311842.txt
It is useless.... You restricted your persistent journal to 1M so most logs are hopelessly incomplete.
Why I did this last June I have no recollection. I have restored the original /etc/systemd/journald.conf file. These are from the two boots following the restoration: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201904010100.txt 1.2M http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201904010110.txt 1.1M -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
01.04.2019 8:32, Felix Miata пишет:
Andrei Borzenkov composed on 2019-04-01 07:12 (UTC+0300):
Felix Miata composed:
Andrei Borzenkov composed on 2019-03-31 22:56 (UTC+0300):
This is irrelevant. Startup fails die to timeout waiting for block device for (all) mount points, not because mount point itself is missing. The problem is that it happens 12 seconds after boot (the whole boot sequence until logs are taken is about 1 minute) while device job timeout should be 90 seconds.
There is tiny chance that timeouts are different for unknown reasons. Output of
systemctl show '*.device' '*.mount' -p JobTimeoutUSec -p JobRunningTimeoutUSec
214 lines of "JobTimeoutUSec=infinity" 213 blank lines in between them
There should have been two lines for each unit. Are you sure you are not misspelled it?
.bash_history showed I had left off the last 4 characters. Now: http://fm.no-ip.com/Tmp/SUSE/Leap/syctl-showmount-201904010110.txt
JobRunningTimeoutUSec=5s Well, that could be too low. That's certainly not standard. You changed it. Apr 01 01:00:21 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Installed new job dev-disk-by\x2dlabel-st10susehome.device/start as 151 ... Apr 01 01:00:26 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Job dev-disk-by\x2dlabel-st10susehome.device/start timed out. 5 seconds Apr 01 01:00:26 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Changed dead -> plugged It is possible that there is some device that takes longer and delays processing so devices are detected late.
may be interesting. Otherwise hopefully it can be reproduced with debug level logs; booting with
systemd.log_level=debug printk.devkmsg=on log_buf_len=16M
could give some clue what happens.
# journalctl -b # from within last boot: 97kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311830.txt # journalctl -b # from within current boot: 132kb http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201903311842.txt
It is useless.... You restricted your persistent journal to 1M so most logs are hopelessly incomplete.
Why I did this last June I have no recollection. I have restored the original /etc/systemd/journald.conf file. These are from the two boots following the restoration: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201904010100.txt 1.2M http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnlb-full-201904010110.txt 1.1M
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Andrei Borzenkov composed on 2019-04-01 21:22 (UTC+0300): Thank you much!!!
Felix Miata composed:
.bash_history showed I had left off the last 4 characters. Now: http://fm.no-ip.com/Tmp/SUSE/Leap/syctl-showmount-201904010110.txt JobRunningTimeoutUSec=5s
Well, that could be too low. That's certainly not standard. You changed it.
I don't know why. Last June 23. I found no clues among the forums or my mailing mailing lists posts from that week. I do remember discussion of inexplicable boot delays some time last year related to Wicked or NetworkManager, but not when, nor how that could be related to this, only that by changing some timeout values somewhere the delays were mitigated. I have reverted to the original /etc/systemd/system.conf file and the emergency mode stopovers have been absent on the past 3 boots. :-D
Apr 01 01:00:21 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Installed new job dev-disk-by\x2dlabel-st10susehome.device/start as 151
...
Apr 01 01:00:26 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Job dev-disk-by\x2dlabel-st10susehome.device/start timed out.
5 seconds
Apr 01 01:00:26 i2134 systemd[1]: dev-disk-by\x2dlabel-st10susehome.device: Changed dead -> plugged
It is possible that there is some device that takes longer and delays processing so devices are detected late. ...
systemd.log_level=debug printk.devkmsg=on log_buf_len=16M
With the reversion, but with the above extra cmdline options still in place: # journalctl -b | grep ailed | wc -l 585 http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201904011630.txt (85kb) With those removed, 9: Apr 01 16:40:52 i2134 kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -71 Apr 01 16:40:52 i2134 kernel: b43 ssb0:0: Direct firmware load for b43/ucode11.fw failed with error -2 Apr 01 16:40:52 i2134 kernel: b43 ssb0:0: Direct firmware load for b43/ucode11.fw failed with error -2 Apr 01 16:40:52 i2134 kernel: b43 ssb0:0: Direct firmware load for b43-open/ucode11.fw failed with error -2 Apr 01 16:40:52 i2134 kernel: b43 ssb0:0: Direct firmware load for b43-open/ucode11.fw failed with error -2 Apr 01 16:40:48 i2134 systemd-udevd[398]: Process 'hid2hci --method=csr --devpath=/devices/pci0000:00/0000:00:1a.0/usb1/1-1' failed with exit code 1. Apr 01 16:40:50 i2134 systemd-udevd[421]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99. Apr 01 16:40:56 i2134 kbdsettings[544]: kbdrate: Failed waiting for kbd controller! Apr 01 16:40:59 i2134 kbdsettings[544]: kbdrate: Failed waiting for kbd controller! -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Felix Miata
Andrei Borzenkov composed on 2019-04-01 21:22 (UTC+0300):
Thank you much!!!
Felix Miata composed:
.bash_history showed I had left off the last 4 characters. Now: http://fm.no-ip.com/Tmp/SUSE/Leap/syctl-showmount-201904010110.txt JobRunningTimeoutUSec=5s
Well, that could be too low. That's certainly not standard. You changed it.
I don't know why. Last June 23. I found no clues among the forums or my mailing mailing lists posts from that week. I do remember discussion of inexplicable boot delays some time last year related to Wicked or NetworkManager, but not when, nor how that could be related to this, only that by changing some timeout values somewhere the delays were mitigated.
the timeout value was for wicked which defaulted to 30 seconds. I altered mine to 8 seconds and then to 10 just to be safe. systemd-analyze shows my networked drives require 6+ seconds normally and the few extra seconds doesn't bother me. from Richard Brown: <quote> The biggest hindrance to openSUSE boot times generally was in the past wicked and the way it honours /etc/sysconfig/network WAIT_FOR_INTERFACES and it's default value of "30" </quote> and that was the *only* change necessary to reduce 20-30 seconds off boot time on the particular box. you have apparently gone further with changes. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Christian Boltz composed on 2019-03-31 17:53 (UTC+0200):
Felix Miata composed:
Carlos E. R. composed on 2019-03-30 15:37 (UTC+0100):
It tries /home/macdata before. The second try without doing anything, /home is already mounted, so succeeds.
Trick
dev1 /firstone type options 1 2 dev2 /firstone/two type options 1 3
No help (as I expected, from man fstab: [...]
Try to create a file /etc/systemd/system/firstone-two.mount.d/after.conf
with the following content:
[Unit] After=firstone.mount
# cat /etc/systemd/system/home.mount.d/after.conf [Unit] After=home.mount # reboot
After the next boot, check systemctl cat firstone-two.mount It should list the addition at the end.
(obviously you'll need to replace "firstone" and "two" with your real mountpoints everywhere)
# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz root=LABEL=st10suseleap noresume ipv6.disable=1 net.ifnames=0 consoleblank=0 systemd.log_level=debug printk.devkmsg=on log_buf_len=16M 3 # systemctl cat home-macdata.mount # /run/systemd/generator/home-macdata.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) [Mount] Where=/home/macdata What=/dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 Type=hfsplus Options=uid=501,gid=100,umask=002,noatime,nofail # journalctl -b | grep ount http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-mount-201903311858.txt
Even if that helps, please open a bugreport. systemd should detect this dependency itsself, and first mount the parent directory.
No help that I can detect. Besides, it's not only home-macdata.mount that's being reported to fail and causing emergency but after Ctrl-D found when init completes to be normally mounted according to df, /etc/mtab and more. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hello, Am Montag, 1. April 2019, 01:18:05 CEST schrieb Felix Miata:
Christian Boltz composed on 2019-03-31 17:53 (UTC+0200):
Try to create a file
/etc/systemd/system/firstone-two.mount.d/after.conf
with the following content:
[Unit] After=firstone.mount
# cat /etc/systemd/system/home.mount.d/after.conf
That should be /etc/systemd/system/home-macdata.mount.d/after.conf ((you missed the "-macdata" part - better use the real paths from the beginning to avoid such "translation errors" ;-) Regards, Christian Boltz --
Warum versucht Ihr, die Leute zu völlig unnötiger Arbeit zu zwingen? Eine geheime Verschwoerung mit Bestattungsunternehmern zur Herzinfarktverbreitung. [> Gordon Cichon und Michael Matz in suse-programming]
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (5)
-
Andrei Borzenkov
-
Carlos E. R.
-
Christian Boltz
-
Felix Miata
-
Patrick Shanahan