[Bug 1202840] New: system crash after update of "filesystem"
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 Bug ID: 1202840 Summary: system crash after update of "filesystem" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: ub22@gmx.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Falkon/22.08.0 Chrome/87.0.4280.144 Safari/537.36 Build Identifier: After filesystem update at snapshot 20220821 and now 20220826 - my system crashed. Also in the shell a command like ls don't work anymore like /usr/bin/ls not found. Only Hard reset works - but base system crash so they can't find the initrd anymore. Possible steps to fix the Issue: * Disable TPM 2.0 in UEFI BIOS (so in other way a read only snapshoot don't work) * Boot previous read only snapshoot * open a super user terminal and execute "snapper rollback && reboot" * After login at first the "Systemeinstellungen" must be opened and the path to the backup must be set. Afterwards the ~/.local/share/kwalletd/kdewallet.kwl must be restored from previous backup * open a super user terminal again and run "zypper ref ; unmount ~/bin ; zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin" * But this time als ( 13/283) Installing: filesystem-84.87-7.1.x86_64 ..................................................................................................................[error] Installation of filesystem-84.87-7.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): r ( 13/283) Installing: filesystem-84.87-7.1.x86_64 ..................................................................................................................[error] Same issue as before # ls bash: /usr/bin/ls: No such file or directory After successfull update I plane at the next boot to enable TPM 2.0 again (not done till now). Reproducible: Always Steps to Reproduce: 1. zypper (d)up or update over KDE update tool 2. NFS and bind mounts (e.g. ~/bin for the main user) 3. See also above Actual Results: System crash again and I need to repeat the procedure :-( Expected Results: zypper up/dup runs propperly at least on all automatic graphical updates Beside the data loss (kwallet) the replay takes a while. Additional there are since some years, time to time updates from "filesystem" hanging on PC (I expect due to NFS and bind mounts)! This us not accepteable for a standard user. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c1 --- Comment #1 from ulfbart <ub22@gmx.net> --- Created attachment 861144 --> http://bugzilla.opensuse.org/attachment.cgi?id=861144&action=edit Shut down messages on the tty1 after crash -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c2 --- Comment #2 from ulfbart <ub22@gmx.net> --- Created attachment 861145 --> http://bugzilla.opensuse.org/attachment.cgi?id=861145&action=edit Boot error message after boot -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c3 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net Summary|system crash after update |[usrmerge] system crash |of "filesystem" |after update of | |"filesystem" --- Comment #3 from Felix Miata <mrmazda@earthlink.net> --- The 20220821 upgrade was attempted against an (old Athlon64 CPU) installation apparently last updated 3 years ago, long before usrmerge. This was included in his mailing list thread: <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/FLG35JUUTUCJB3EC7P6YUQ2D2JOO4UKR/> -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c4 --- Comment #4 from ulfbart <ub22@gmx.net> --- # inxi -Fz System: Kernel: 5.19.2-1-default arch: x86_64 bits: 64 Console: pty pts/3 Distro: openSUSE Tumbleweed 20220824 Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50 v: 0623 serial: <filter> Mobo: ASUSTeK model: PN50 serial: N/A UEFI: ASUSTeK v: 0623 date: 05/13/2021 CPU: Info: 8-core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP cache: L2: 4 MiB Speed (MHz): avg: 1550 min/max: 1400/2000 cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 2000 6: 2000 7: 1400 8: 1400 Graphics: Device-1: AMD Renoir driver: amdgpu v: kernel Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 3840x2160~60Hz OpenGL: renderer: AMD RENOIR (LLVM 14.0.6 DRM 3.47 5.19.2-1-default) v: 4.6 Mesa 22.1.7 Audio: Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.19.2-1-default running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.56 running: yes [...shorted] -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c5 --- Comment #5 from ulfbart <ub22@gmx.net> --- Additional info: at update at snapshot 20220821, after rollback the #zypper ref ; unmount ~/bin ; zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin works fine. But now with 20220826 this won't work (see my Description) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c6 ulfbart <ub22@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P0 - Crit Sit --- Comment #6 from ulfbart <ub22@gmx.net> --- Du to the fact an zypper up/dup is not possible, all security fixes like the zlib issue are not possible to be updated! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mrmazda@earthlink.net | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c7 --- Comment #7 from ulfbart <ub22@gmx.net> --- About this issue: # ls bash: /usr/bin/ls: No such file or directory ASSI (alias Achim) send me the following (thanks for info :-) ):
Try the fix mentioned in the FAQ part of
https://en.opensuse.org/openSUSE:Usr_merge Why and how the UsrMerge wasn't completed much earlier on your system remains to be determined if that is the reason for your troubles.
OK, but there was nothing really helpful: # /usr/lib64/ld-linux-x86-64.so.2 /usr/bin/ln -s /usr/lib64/ld-linux-x86-64.so.2 /lib64/ld-linux-x86-64.so.2 /usr/bin/ln: failed to create symbolic link '/lib64/ld-linux-x86-64.so.2': File exists # /usr/lib64/ld-linux-x86-64.so.2 /usr/bin/ln -s /usr/lib64/libc.so.6 /lib64/libc.so.6 /usr/bin/ln: failed to create symbolic link '/lib64/libc.so.6': File exists # cd /usr; ln -s . /usr/usr OK, was working What I did (I don't know if this was an good idea - I will see after the zypper dup: # ls -l / bin -> usr/bin lib -> usr/lib lib64 -> usr/lib64 to # ls -l / bin -> /usr/bin lib -> /usr/lib lib64 -> /usr/lib64 After the changes (see previous mail) and a new zypper dup: # zypper ref ; unmount ~/bin ; zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin Repository 'Mozilla' is up to date. Repository 'Haupt-Repository (NON-OSS)' is up to date. Repository 'Haupt-Repository (OSS)' is up to date. Repository 'Hauptaktualisierungs-Repository' is up to date. Repository 'packman' is up to date. All repositories have been refreshed. Error: Try the command: umount Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following package is going to be upgraded: filesystem 1 package to upgrade. Overall download size: 67.7 KiB. Already cached: 0 B. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): Retrieving package filesystem-84.87-7.1.x86_64 (1/1), 67.7 KiB ( 1.3 KiB unpacked) Retrieving: filesystem-84.87-7.1.x86_64.rpm .........................................................................................................................[done] Checking for file conflicts: ........................................................................................................................................[done] error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed error: filesystem-84.87-6.1.x86_64: erase skipped (1/1) Installing: filesystem-84.87-7.1.x86_64 ......................................................................................................................[error] Installation of filesystem-84.87-7.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): r error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed error: filesystem-84.87-6.1.x86_64: erase skipped (1/1) Installing: filesystem-84.87-7.1.x86_64 ......................................................................................................................[error] Installation of filesystem-84.87-7.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. And journalctl -xe Sep 03 18:33:06 x dbus-daemon[1113]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.316' (uid=0 pid=3> Sep 03 18:33:06 x systemd[1]: Starting DBus interface for snapper... ������ Subject: A start job for unit snapperd.service has begun execution ������ Defined-By: systemd ������ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ������ ������ A start job for unit snapperd.service has begun execution. ������ ������ The job identifier is 13285. Sep 03 18:33:06 x dbus-daemon[1113]: [system] Successfully activated service 'org.opensuse.Snapper' Sep 03 18:33:06 x systemd[1]: Started DBus interface for snapper. ������ Subject: A start job for unit snapperd.service has finished successfully ������ Defined-By: systemd ������ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ������ ������ A start job for unit snapperd.service has finished successfully. ������ ������ The job identifier is 13285. Sep 03 18:33:13 x [RPM][747]: Transaction ID 631381c9 started Sep 03 18:33:13 x [RPM][747]: install filesystem-84.87-7.1.x86_64: success Sep 03 18:33:13 x [RPM][747]: erase filesystem-84.87-6.1.x86_64: success Sep 03 18:33:13 x [RPM][747]: install filesystem-84.87-7.1.x86_64: failure Sep 03 18:33:13 x [RPM][747]: 1 elements failed, 0 scripts failed Sep 03 18:33:13 x [RPM][747]: Transaction ID 631381c9 finished: -1 Sep 03 18:33:16 x [RPM][782]: Transaction ID 631381cc started Sep 03 18:33:16 x [RPM][782]: install filesystem-84.87-7.1.x86_64: success Sep 03 18:33:16 x [RPM][782]: erase filesystem-84.87-6.1.x86_64: success Sep 03 18:33:16 x [RPM][782]: install filesystem-84.87-7.1.x86_64: failure Sep 03 18:33:16 x [RPM][782]: 1 elements failed, 0 scripts failed Sep 03 18:33:16 x [RPM][782]: Transaction ID 631381cc finished: -1 lines 1059-1133/1133 (END) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202840 http://bugzilla.opensuse.org/show_bug.cgi?id=1202840#c8 ulfbart <ub22@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from ulfbart <ub22@gmx.net> --- I find it now with support and idea from Carlos :-) (see factory mailing list) # zypper cc -a # zypper in --download-only filesystem Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: filesystem 1 package to upgrade. Overall download size: 0 B. Already cached: 67.7 KiB. Download only. Continue? [y/n/v/...? shows all options] (y): In cache filesystem-84.87-7.1.x86_64.rpm (1/1), 67.7 KiB ( 1.3 KiB unpacked) # find /var/cache/zypp -iname "filesystem*rpm" /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm # rpm -ivh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [100%] error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed OK - /root/bin was not unmounted! # lsof ~/bin lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME watch_new 13762 root 255r REG 0,64 42322 18314290398 /root/bin/watch_new.sh (192.168.2.2:/home/users/Gemeinsame_Dokumente/bin) *^^^^^^^^^ - ups my monitoring script is blocking to unmount ~/bin !!!* OK stopped watch_new.sh and it looks better :-D # rpm -Uvh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm erifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [ 50%] Cleaning up / removing... 2:filesystem-84.87-6.1 ################################# [100%] *Tschacka :-) - solved* *Lessons learned, in the future command line for zypper dup is use: # zypper ref ; unmount ~/bin && zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin Thanks for support :-) But still curious that my remote NFS mounted ~/bin makes still trouble to update the "filesystem" package. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com