Page 1 of 5 123 ... LastLast
Results 1 to 10 of 44

Thread: Cannot install or update via zypper dup or YaST

  1. #1

    Default Cannot install or update via zypper dup or YaST

    Cannot install or update via zypper dup or YaST

    Please let me know what system information you need to be able to help.
    Thank you for the help

    Code:
    # zypper dup
    The target filesystem is mounted as read-only. Please make sure the target filesystem is writeable.
    openSUSE Tumbleweed 64-bit / Cinnamon

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    14,870
    Blog Entries
    3

    Default Re: Cannot install or update via zypper dup or YaST

    Is the root file system full?

    Check the output of
    Code:
    df /
    If you are using "btrfs" (likely), then check the output of:
    Code:
    btrfs filesystem df /
    openSUSE Leap 15.2; KDE Plasma 5.18.5;

  3. #3

    Default Re: Cannot install or update via zypper dup or YaST

    Quote Originally Posted by nrickert View Post
    Is the root file system full?

    Check the output of
    Code:
    df /
    If you are using "btrfs" (likely), then check the output of:
    Code:
    btrfs filesystem df /
    Code:
    df /
    Filesystem     1K-blocks     Used Available Use% Mounted on
    /dev/sda3       41975640 19893480  21729816  48% /
    Code:
    btrfs filesystem df /
    Data, single: total=21.01GiB, used=17.74GiB
    System, DUP: total=32.00MiB, used=16.00KiB
    Metadata, DUP: total=768.00MiB, used=610.91MiB
    GlobalReserve, single: total=35.09MiB, used=0.00B
    openSUSE Tumbleweed 64-bit / Cinnamon

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    28,058

    Default Re: Cannot install or update via zypper dup or YaST

    And of course check if there are any file systems mounted read-only
    Code:
    mount
    Henk van Velden

  5. #5

    Default Re: Cannot install or update via zypper dup or YaST

    This is the first time I have installed with btrfs.
    There are some things I am not familiar with.
    If there is anything that needs to change, please let me know.


    Code:
    mount
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,size=4023064k,nr_inodes=1005766,mode=755,inode64)
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,size=1613712k,nr_inodes=819200,mode=755,inode64)
    tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
    cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
    pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
    none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
    cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
    cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
    cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
    cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    /dev/sda3 on / type btrfs (ro,relatime,space_cache,subvolid=266,subvol=/@/.snapshots/1/snapshot)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17202)
    tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
    debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
    mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=409600,inode64)
    /dev/sda3 on /.snapshots type btrfs (ro,relatime,space_cache,subvolid=265,subvol=/@/.snapshots)
    /dev/sdc2 on /linux-back9-LXQT type btrfs (rw,relatime,ssd,space_cache,subvolid=256,subvol=/@)
    /dev/sdc2 on /linux-back9-LXQT/boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/boot/grub2/i386-pc)
    /dev/sdc2 on /linux-back9-LXQT/opt type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/opt)
    /dev/sdc2 on /linux-back9-LXQT/boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@/boot/grub2/x86_64-efi)
    /dev/sdc2 on /linux-back9-LXQT/srv type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/srv)
    /dev/sdc2 on /linux-back9-LXQT/usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=260,subvol=/@/usr/local)
    /dev/sdc2 on /linux-back9-LXQT/var type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/var)
    /dev/sdc2 on /linux-back9-LXQT/root type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/root)
    /dev/sda3 on /boot/grub2/x86_64-efi type btrfs (ro,relatime,space_cache,subvolid=263,subvol=/@/boot/grub2/x86_64-efi)
    /dev/sda3 on /srv type btrfs (ro,relatime,space_cache,subvolid=260,subvol=/@/srv)
    /dev/sda3 on /root type btrfs (ro,relatime,space_cache,subvolid=261,subvol=/@/root)
    /dev/sda3 on /usr/local type btrfs (ro,relatime,space_cache,subvolid=259,subvol=/@/usr/local)
    /dev/sda3 on /var type btrfs (ro,relatime,space_cache,subvolid=258,subvol=/@/var)
    /dev/sda3 on /opt type btrfs (ro,relatime,space_cache,subvolid=262,subvol=/@/opt)
    /dev/sda3 on /boot/grub2/i386-pc type btrfs (ro,relatime,space_cache,subvolid=264,subvol=/@/boot/grub2/i386-pc)
    /dev/sdc1 on /windows-D type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
    /dev/sdb1 on /home type ext4 (rw,relatime,data=ordered)
    /dev/sdb2 on /backups type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
    /dev/sda1 on /windows-C type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806856k,nr_inodes=201714,mode=700,uid=1000,gid=100,inode64)
    gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
    tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
    openSUSE Tumbleweed 64-bit / Cinnamon

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    28,058

    Default Re: Cannot install or update via zypper dup or YaST

    This one:
    Code:
    /dev/sda3 on / type btrfs (ro,relatime,space_cache,subvolid=266,subvol=/@/.snapshots/1/snapshot)
    But why? So YaST is only reporting the truth and of course can not write to a ro file sytem

    I am no Btrfs user. But looking in the logs might help. Maybe browse through
    Code:
    dmesg
    Henk van Velden

  7. #7
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,315
    Blog Entries
    1

    Default Re: Cannot install or update via zypper dup or YaST

    Quote Originally Posted by idee View Post
    Code:
    # zypper dup
    The target filesystem is mounted as read-only. Please make sure the target filesystem is writeable.
    zypper tells all. Check your journal and post the output of: 'journalctl -b --grep btrfs'.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  8. #8
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    2,097

    Default Re: Cannot install or update via zypper dup or YaST

    Quote Originally Posted by idee View Post
    Code:
    df /
    Filesystem     1K-blocks     Used Available Use% Mounted on
    /dev/sda3       41975640 19893480  21729816  48% /
    Code:
    btrfs filesystem df /
    Data, single: total=21.01GiB, used=17.74GiB
    System, DUP: total=32.00MiB, used=16.00KiB
    Metadata, DUP: total=768.00MiB, used=610.91MiB
    GlobalReserve, single: total=35.09MiB, used=0.00B
    Some 3 GiB free may not be enough for a "zypper dup", then the system went read-only to avoid corruption?
    Maybe deleting some snapshots might fix things.
    Tumbleweed Gnome on i7 4720HQ + Geforce GTX960M
    testing Leap 15.3

  9. #9

    Default Re: Cannot install or update via zypper dup or YaST

    Quote Originally Posted by karlmistelberger View Post
    zypper tells all. Check your journal and post the output of: 'journalctl -b --grep btrfs'.
    Code:
    journalctl -b --grep btrfs
    An error was encountered while opening journal file or directory /var/log/journal/bc10c50387c1432d9d156b75d0632527/user-1000@4f3fafb1534243adb22a06ddd4de7597-0000000000009680-0005b7cba0016030.journal, ignoring file: Input/output error
    -- Logs begin at Tue 2020-11-17 19:00:38 CST, end at Fri 2021-01-01 00:29:07 CST. --
    Dec 29 09:30:51 localhost dracut-cmdline[181]: Using kernel command line parameters: rd.driver.pre=btrfs root=UUID=14c5d68e-7778-48e8-adb7-4c164d951>
    Dec 29 09:30:52 localhost kernel: Btrfs loaded, crc32c=crc32c-generic, assert=on
    Dec 29 09:30:54 localhost kernel: BTRFS: device label LXQT devid 1 transid 549 /dev/sdc2 scanned by systemd-udevd (276)
    Dec 29 09:30:54 localhost kernel: BTRFS: device label Cinnamon devid 1 transid 78936 /dev/sda3 scanned by systemd-udevd (256)
    Dec 29 09:30:55 localhost kernel: BTRFS info (device sda3): disk space caching is enabled
    Dec 29 09:30:55 localhost kernel: BTRFS info (device sda3): has skinny extents
    Dec 29 09:30:55 localhost kernel: BTRFS info (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 22, gen 0
    Dec 29 15:31:00 localhost kernel: BTRFS info (device sda3): disk space caching is enabled
    Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): disk space caching is enabled
    Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): has skinny extents
    Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): bdev /dev/sdc2 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0
    Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): enabling ssd optimizations
    Dec 29 15:31:43 localhost kernel: BTRFS warning (device sda3): csum failed root 266 ino 465476 off 36995072 csum 0xdc0d8280 expected csum 0x5ae50870>
    Dec 29 15:31:43 localhost kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 23, gen 0
    Dec 29 15:31:44 localhost systemd[1]: Started Watch /etc/sysconfig/btrfsmaintenance.
    Dec 29 15:31:52 localhost systemd[1]: Started Balance block groups on a btrfs filesystem.
    Dec 29 15:31:52 localhost systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
    Dec 29 15:31:57 localhost kernel: BTRFS warning (device sda3): csum failed root 266 ino 379878 off 4603904 csum 0x4ca94851 expected csum 0x365f0628 >
    Dec 29 15:31:57 localhost kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 24, gen 0
    Dec 29 15:32:00 localhost.localdomain kernel: BTRFS warning (device sda3): csum failed root 266 ino 379787 off 32075776 csum 0x0ed9b851 expected csu>
    Dec 29 15:32:00 localhost.localdomain kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 25, gen 0
    Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:20 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:20 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:21 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:21 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    Dec 29 15:32:21 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
    openSUSE Tumbleweed 64-bit / Cinnamon

  10. #10

    Default Re: Cannot install or update via zypper dup or YaST

    Quote Originally Posted by OrsoBruno View Post
    Some 3 GiB free may not be enough for a "zypper dup", then the system went read-only to avoid corruption?
    Maybe deleting some snapshots might fix things.
    This is my first try with btrfs.
    How do I remove the snapshots?
    How do I limit them?
    openSUSE Tumbleweed 64-bit / Cinnamon

Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •