opensuse tumbleweed won't boot

ultra99 · 12-12-2018, 05:38 PM

Quote:

Originally Posted by mrmazda

That's 3 out of 5 requested - still waiting on your TW's fstab, and the output of 'journalctl -b | grep ailed', the latter of which should come from either the same boot as the output of 'efibootmgr -v', lsblk & blkid, or an identically performed boot and subsequent login and command sequence.

sorry, what the command? fstab?

yancek · 12-12-2018, 05:45 PM

fstab is a text file generally residing in the /etc directory so either navigate to that location with whatever text editor you use or open a terminal and run:

Quote:

cat /etc/fstab

Either way should show the content of the file.

ultra99 · 12-12-2018, 06:04 PM

Quote:

Originally Posted by yancek

fstab is a text file generally residing in the /etc directory so either navigate to that location with whatever text editor you use or open a terminal and run:

Either way should show the content of the file.

fstab

Code:

UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /                       btrfs  defaults                      0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
UUID=bb3af949-f2d6-4351-93c6-82a504803137  swap                    swap   defaults                      0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /var                    btrfs  subvol=/@/var                 0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /root                   btrfs  subvol=/@/root                0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=330521ed-89e3-432b-b24f-599a4c108752  /home                   xfs    defaults                      0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=2b57bca1-4be8-48aa-956d-f043e65ef3ed  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=D563-909C                             /boot/efi               vfat   defaults                      0  0

Code:

# journalctl -b | grep ailed
Dec 12 18:58:10 linux-zcxg kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Dec 12 18:58:10 linux-zcxg kernel: platform USBC000:00: failed to claim resource 0: [mem 0x9cfde764-0x9cfdf763]
Dec 12 18:58:10 linux-zcxg kernel: acpi USBC000:00: platform device creation failed: -16
Dec 12 18:58:11 linux-zcxg systemd-vconsole-setup[338]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
Dec 12 18:58:11 linux-zcxg kernel: kfd kfd: Failed to resume IOMMU for device 1002:15dd
Dec 12 18:59:40 linux-zcxg systemd[1]: Dependency failed for Resume from hibernation using device /dev/disk/by-uuid/a781546b-1c19-4944-a441-52318c2c6a5e.
Dec 12 18:59:40 linux-zcxg systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a781546b\x2d1c19\x2d4944\x2da441\x2d52318c2c6a5e.service: Job systemd-hibernate-resume@dev-disk-by\x2duuid-a781546b\x2d1c19\x2d4944\x2da441\x2d52318c2c6a5e.service/start failed with result 'dependency'.
Dec 12 18:59:40 linux-zcxg systemd[1]: dev-disk-by\x2duuid-a781546b\x2d1c19\x2d4944\x2da441\x2d52318c2c6a5e.device: Job dev-disk-by\x2duuid-a781546b\x2d1c19\x2d4944\x2da441\x2d52318c2c6a5e.device/start failed with result 'timeout'.
Dec 12 18:59:41 linux-zcxg systemd-vconsole-setup[436]: KD_FONT_OP_SET failed, fonts will not be copied to tty7: Invalid argument
Dec 12 18:59:41 linux-zcxg kernel: BTRFS warning (device nvme0n1p13): csum failed root 267 ino 88062 off 1355776 csum 0x98f94189 expected csum 0x7699a32f mirror 1
Dec 12 18:59:41 linux-zcxg kernel: BTRFS warning (device nvme0n1p13): csum failed root 267 ino 88062 off 1724416 csum 0x98f94189 expected csum 0xfd08760e mirror 1
Dec 12 18:59:41 linux-zcxg kernel: BTRFS warning (device nvme0n1p13): csum failed root 267 ino 88062 off 1695744 csum 0x98f94189 expected csum 0x8e6e7be8 mirror 1
Dec 12 18:59:41 linux-zcxg kernel: BTRFS warning (device nvme0n1p13): csum failed root 267 ino 88062 off 1699840 csum 0x98f94189 expected csum 0xc312604e mirror 1
Dec 12 18:59:41 linux-zcxg kernel: BTRFS warning (device nvme0n1p13): csum failed root 267 ino 88062 off 1703936 csum 0x98f94189 expected csum 0xf2a44665 mirror 1
Dec 12 18:59:41 linux-zcxg systemd-vconsole-setup[474]: KD_FONT_OP_SET failed, fonts will not be copied to tty7: Invalid argument
Dec 12 18:59:41 linux-zcxg kernel: cmi: probe of SMB0001:00 failed with error -5
Dec 12 18:59:42 linux-zcxg systemd-udevd[501]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99.
Dec 12 18:59:42 linux-zcxg systemd-udevd[505]: Process '/usr/sbin/alsactl restore 1' failed with exit code 99.
Dec 12 18:59:42 linux-zcxg systemd-udevd[511]: Process '/usr/sbin/tlp auto' failed with exit code 4.
Dec 12 18:59:42 linux-zcxg systemd-vconsole-setup[638]: KD_FONT_OP_SET failed, fonts will not be copied to tty7: Invalid argument
Dec 12 18:59:42 linux-zcxg systemd-vconsole-setup[732]: KD_FONT_OP_SET failed, fonts will not be copied to tty7: Invalid argument
Dec 12 18:59:50 linux-zcxg kwin_x11[1859]: "\"fsrestore1\" - conversion of \"481,481,0,0\" to QRect failed"
Dec 12 18:59:50 linux-zcxg kwin_x11[1859]: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Dec 12 18:59:50 linux-zcxg kwin_x11[1859]: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Dec 12 18:59:50 linux-zcxg kwin_x11[1859]: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
Dec 12 18:59:50 linux-zcxg kwin_x11[1859]: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"
Dec 12 18:59:50 linux-zcxg kwin_x11[1859]: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed"
Dec 12 18:59:50 linux-zcxg pulseaudio[1910]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Dec 12 18:59:50 linux-zcxg NetworkManager[1383]: <info>  [1544659190.6194] device (wlp4s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Dec 12 18:59:50 linux-zcxg NetworkManager[1383]: <warn>  [1544659190.6203] device (wlp4s0): Activation: failed for connection 'New 802-11-wireless connection'
Dec 12 18:59:50 linux-zcxg NetworkManager[1383]: <info>  [1544659190.6216] device (wlp4s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 12 18:59:53 linux-zcxg PackageKit[2144]: refresh-cache transaction /1_aeadcecc from uid 1000 finished with failed after 208ms
Dec 12 18:59:53 linux-zcxg plasmashell[1868]: PK error: "Download (curl) error for 'http://download.opensuse.org/tumbleweed/repo/non-oss/repodata/repomd.xml':\nError code: Connection failed\nError message: Could not resolve host: download.opensuse.org\n" type: "repo-not-available"
Dec 12 18:59:53 linux-zcxg plasmashell[1868]: plasma-pk-updates: Transaction "/1_aeadcecc" finished with status "failed" in 0 seconds
Dec 12 18:59:55 linux-zcxg dbus-daemon[1754]: [session uid=1000 pid=1754] Activated service 'org.kde.kwalletd' failed: Failed to execute program org.kde.kwalletd: No such file or directory

mrmazda · 12-12-2018, 10:37 PM

Next openSUSE boot, at the grub screen, strike the e key, cursor down to where you find the resume=UUID=foobarbazdingdongblah string, remove it all, then proceed with boot. How long did boot take?

ultra99 · 12-13-2018, 06:26 AM

Quote:

Originally Posted by mrmazda

Next openSUSE boot, at the grub screen, strike the e key, cursor down to where you find the resume=UUID=foobarbazdingdongblah string, remove it all, then proceed with boot. How long did boot take?

it took longer, 2 min 5 sec.

mrmazda · 12-13-2018, 06:33 AM

This time, replace resume=UUID=foobarbazdingdongblah with noresume. When boot completes, show us again how long it took, plus result of

Code:

systemd-analyze blame

ultra99 · 12-13-2018, 06:40 AM

Quote:

Originally Posted by mrmazda

This time, replace resume=UUID=foobarbazdingdongblah with noresume. When boot completes, show us again how long it took, plus result of

Code:

systemd-analyze blame

2 min 10 sec.

mrmazda · 12-13-2018, 06:54 AM

plus result of

Code:

systemd-analyze blame

ultra99 · 12-13-2018, 04:41 PM

Quote:

Originally Posted by mrmazda

plus result of

Code:

systemd-analyze blame

2 min 0 sec

Code:

systemd-analyze blame
          6.227s dev-nvme0n1p13.device
          3.047s display-manager.service
          2.886s postfix.service
          2.530s plymouth-quit-wait.service
          1.537s btrfsmaintenance-refresh.service
          1.248s apparmor.service
           948ms firewalld.service
           940ms home.mount
           730ms systemd-journal-flush.service
           729ms dev-disk-by\x2duuid-bb3af949\x2df2d6\x2d4351\x2d93c6\x2d82a504803137.s>
           709ms systemd-rfkill.service
           709ms systemd-backlight@backlight:amdgpu_bl0.service
           706ms systemd-random-seed.service
           675ms plymouth-start.service
           629ms ModemManager.service
           621ms kbdsettings.service
           570ms polkit.service
           567ms systemd-logind.service
           329ms iscsi.service
           326ms initrd-switch-root.service
           275ms udisks2.service
           249ms NetworkManager.service
           218ms upower.service
           133ms initrd-parse-etc.service
            97ms systemd-udev-trigger.service
            91ms user@1000.service
            91ms systemd-vconsole-setup.service
            73ms systemd-udevd.service
lines 1-28

Does any of the problems I'm experiencing has do with NVme or AMD cpu?

mrmazda · 12-14-2018, 10:49 PM

Quote:

Originally Posted by ultra99

Does any of the problems I'm experiencing has do with NVme or AMD cpu?

I don't think so, but I'm still rather green on nvme and very green on btrfs. Let's see

Code:

systemd-analyze critical-chain

If I can't tell from that, I'm out of ideas other than asking at https://forums.opensuse.org/forumdis...p/672-Hardware where I know there are frequent posters more familiar with them.

ultra99 · 12-15-2018, 06:06 AM

Quote:

Originally Posted by mrmazda

I don't think so, but I'm still rather green on nvme and very green on btrfs. Let's see

Code:

systemd-analyze critical-chain

If I can't tell from that, I'm out of ideas other than asking at https://forums.opensuse.org/forumdis...p/672-Hardware where I know there are frequent posters more familiar with them.

2 min

Code:

systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @24.500s
└─display-manager.service @21.617s +2.882s
  └─systemd-user-sessions.service @21.605s +9ms
    └─remote-fs.target @21.603s
      └─iscsi.service @21.193s +400ms
        └─network.target @21.182s
          └─wpa_supplicant.service @22.985s +45ms
            └─dbus.service @19.399s
              └─basic.target @19.381s
                └─sockets.target @19.381s
                  └─iscsid.socket @19.381s
                    └─sysinit.target @19.376s
                      └─apparmor.service @18.089s +1.286s
                        └─var.mount @17.930s +130ms
                          └─dev-disk-by\x2duuid-2b57bca1\x2d4be8\x2d48aa\x2d956d\x2df04>
lines 1-18/18 (END)

mrmazda · 12-15-2018, 03:17 PM

Yours is so different from mine I don't know what to make of it. Mine are on mSATA in Kaby Lake motherboard M.2 socket. Each is on an 8GB EXT4 /:

Code:

Tumbleweed:
multi-user.target @5.414s
└─kbdsettings.service @3.327s +2.086s
  └─basic.target @3.326s
    └─sockets.target @3.325s
      └─dbus.socket @3.324s
        └─sysinit.target @3.324s
          └─systemd-timesyncd.service @3.283s +40ms
            └─systemd-tmpfiles-setup.service @3.265s +13ms
              └─local-fs.target @3.262s
                └─usr-local.mount @3.240s +20ms
                  └─systemd-fsck@dev-disk-by\x2dlabel-k25p04usrlcl.service @3.173s +65ms
                    └─local-fs-pre.target @3.157s
                      └─lvm2-monitor.service @426ms +2.730s
                        └─lvm2-lvmetad.service @450ms
                          └─lvm2-lvmetad.socket @424ms
                            └─system.slice
                              └─-.slice
openSUSE 15.0:
multi-user.target @3.955s
└─kbdsettings.service @1.874s +2.080s
  └─basic.target @1.871s
    └─sockets.target @1.870s
      └─avahi-daemon.socket @1.869s
        └─sysinit.target @1.864s
          └─systemd-timesyncd.service @1.849s +13ms
            └─systemd-tmpfiles-setup.service @1.838s +8ms
              └─local-fs.target @1.837s
                └─home.mount @1.821s +14ms
                  └─systemd-fsck@dev-disk-by\x2dlabel-k25p05home.service @1.744s +73ms
                    └─local-fs-pre.target @1.720s
                      └─lvm2-monitor.service @165ms +1.553s
                        └─lvm2-lvmetad.service @188ms
                          └─lvm2-lvmetad.socket @164ms
                            └─-.slice
Debian 10 Buster:
graphical.target @2.729s
└─udisks2.service @1.700s +1.028s
  └─basic.target @1.683s
    └─sockets.target @1.681s
      └─dbus.socket @1.680s
        └─sysinit.target @1.679s
          └─systemd-timesyncd.service @1.511s +166ms
            └─systemd-tmpfiles-setup.service @1.486s +17ms
              └─local-fs.target @1.480s
                └─home.mount @1.447s +23ms
                  └─systemd-fsck@dev-disk-by\x2dlabel-k25p05home.service @1.394s +51ms
                    └─dev-disk-by\x2dlabel-k25p05home.device @1.342s