Dne Út 6. října 2015 08:36:59, John Young napsal(a):
We have a number of new HP workstations on which I have done a new installation of openSUSE 13.2. The installations all seemed to have gone normally and the systems all ran fine for a day or so. But then the root partition was remounted read-only on several of them.
Normally, one expects this if one is having disk errors, but I booted from an installation disk and ran fsck and the partition came back as clean. I rebooted the box and the root partition was again mounted read-only (or at least NOT remounted read-write).
If I boot in recovery mode, I can manually remount the root partition read-write and manually bring up the network and everything seems to run normally. But if I do a clean shutdown and reboot, the root partition is again not mounted read-write.
In the short run, I have a really ugly work-around of putting the commands to remount the root partition read-write and ifup the network in /etc/init.d/after.local, but I really don't like that and I don't understand why the root partition is not being properly mounted even though there do not seem to be any disk errors.
Has anyone seen this? Any ideas where to look?
Do You have Btrfs on affected partitions? If so, do You have snapper active? If You boot, You can check by „snapper list“ and if You see list of snapshots, You can revert or delete unneeded snapshots like „snapper delete 1-5“. I had this problem several times because of snapshots used all free space (check „df -h“), so that I had to limit number of snapshots. See manual for details: https://en.opensuse.org/Portal:Snapper Finally, I had voltage problem and Btrfs got corrupted (“btrfs check“ didn't help), so I had to reinstall... :-( -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/