Could be … I’m scratching my head over this. Some further info:
oldcpu@linux-mtpj:~> df -Th
Filesystem Type Size Used Avail Use% Mounted on
**/dev/sdb5 ext4 48G 8.1G 39G 18% /**
devtmpfs devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs tmpfs 7.8G 88K 7.8G 1% /dev/shm
tmpfs tmpfs 7.8G 2.2M 7.8G 1% /run
tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/sdb1 vfat 256M 22M 235M 9% /boot/efi
/dev/sda8 ext4 1.7T 1.4T 316G 82% /home
/dev/sda3 ext4 24G 137M 23G 1% /tmp
/dev/sda2 ext4 24G 1.7G 22G 8% /var
where sdb5 is /
and
oldcpu@linux-mtpj:~> cat /etc/fstab
UUID=a3e11907-0165-4f01-b4c1-810029999214 / ext4 acl,user_xattr 1 1
UUID=920507c2-cbbd-46c9-b8e4-ee957e695a39 /var ext4 acl,user_xattr 1 2
UUID=6c8b134f-0f7c-4736-ab94-37f0a0942ad0 /tmp ext4 acl,user_xattr 1 2
UUID=2b1e462b-8e51-49e7-a9b3-2a933a7fe88d swap swap defaults 0 0
UUID=7EC6-8D89 /boot/efi vfat umask=0002,utf8=true 0 0
UUID=f8961aad-eefe-4a9d-9792-f259455334ca /home ext4 defaults 1 2
and
oldcpu@linux-mtpj:~> 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,size=8170152k,nr_inodes=2042538,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
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/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
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/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
**/dev/sdb5 on / type ext4 (ro,relatime,data=ordered)**
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
/dev/sdb1 on /boot/efi type vfat (rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sda8 on /home type ext4 (rw,relatime,data=ordered)
/dev/sda3 on /tmp type ext4 (rw,relatime,data=ordered)
/dev/sda2 on /var type ext4 (rw,relatime,data=ordered)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,mode=755)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
so /sdb5 is mounted as ro (which I think means read only)
Further I note in quoted thread this was suggested.
oldcpu@linux-mtpj:~> systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: active (exited) since Tue 2015-10-06 18:27:38 CEST; 2h 48min ago
Docs: man:systemd-remount-fs.service(8)
http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
Process: 473 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=0/SUCCESS)
Main PID: 473 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-remount-fs.service
and
oldcpu@linux-mtpj:~> dmesg | grep mount
1.783771] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: data=ordered
1.834488] EXT4-fs (sdb5): re-mounted. Opts: data=ordered
1.841039] EXT4-fs (sdb5): re-mounted. Opts: data=ordered
2.156793] EXT4-fs (sdb5): re-mounted. Opts: acl,user_xattr
3.265913] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
3.294534] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr
3.345053] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: acl,user_xattr
although I do not know what that indicates/brings to the table.
I noted in post#29 you suggested:
Login as root (“su” should work too, but I’m not sure, “sudo” will not work with a read-only /) and run “mount / -o rw,remount” to get back a writable filesystem. (or press ‘e’ at the boot menu and remove “ro” from the line starting with “linux” or “linuxefi”)
Then enter YaST->Software Management and revert all red packages with systemd and udev in the name to the previous versions (use the “Versions” tab, or “Update Unconditionally” should work too).
Do you recommend I try this ?