Can anyone figure out why /home is mounting read-only at boot?
Here’s my fstab:
# /etc/fstab
# Created by anaconda on Sat Apr 18 17:14:21 2015
#
# Accessible filesystems, by reference, are maintained under ‘/dev/disk’
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/fedora_new–host–5-root / ext4 defaults 1 1
UUID=058cc312-d471-41b9-a346-6ecf7dd2484b /boot ext4 defaults 1 2
#/dev/mapper/fedora_new–host–5-home /home ext4 defaults 1 2
/dev/mapper/fedora_new–host-home /home ext4 defaults 1 2
/dev/mapper/fedora_new–host–5-swap swap swap defaults 0 0
Note that /dev/mapper/fedora_new–host–5-root is an SSD (as is boot), and /dev/mapper/fedora_new–host-home is a physical hard drive.
And here’s /proc/mounts:
sysfs /sys sysfs rw,seclabel,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,seclabel,nosuid,size=7787916k,nr_inodes=1946979,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,seclabel,nosuid,nodev 0 0
devpts /dev/pts devpts rw,seclabel,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,seclabel,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,seclabel,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,seclabel,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
/dev/mapper/fedora_new–host–5-root / ext4 rw,seclabel,relatime,data=ordered 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=24,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
tmpfs /tmp tmpfs rw,seclabel 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,seclabel,relatime 0 0
mqueue /dev/mqueue mqueue rw,seclabel,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
/dev/sdb1 /boot ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/mapper/fedora_new–host-home /home ext4 ro,seclabel,relatime,data=ordered 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
tmpfs /run/user/42 tmpfs rw,seclabel,nosuid,nodev,relatime,size=1559960k,mode=700,uid=42,gid=42 0 0
tmpfs /run/user/1000 tmpfs rw,seclabel,nosuid,nodev,relatime,size=1559960k,mode=700,uid=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
[Update a while later]
OK, clearly the disk is getting corrupted. I put in a file check option in the fstab, and it (temporarily) mounted it read-write at boot, but after working a while it became remounted read-only.
Any suggestions?
[Update a while later]
I had a spare 2T drive that I hooked up, and made it /home at boot (it was an old original, and the new drive was actually backup of it, so it had a lot of the data on it already). It’s working fine so far, except that when I copied my Gnome user configuration data over and rebooted, it decided that I wanted to have a Spanish desktop. I’ve changed the system settings to en_US, and even ‘localectl status’ give me:
System Locale: LANG=en_US
VC Keymap: us
X11 Layout: us
I can’t figure out where in the configuration files it’s getting the idea that I want to compute en Espanol, but while I can stumble along in it, it’s quite annoying.
[Wednesday-morning update]
OK, I determined that the language is changed in Gnome in “Settings,” but in the Spanish interface, that gets translated into “Configuracion,” so I was looking in the wrong place. So, now all is well, as far as I can tell. And as of this morning both the old and the new drive remain read/write. So still not sure what the problem was, but it seems to be a lot better now.
[Update a while later]
Wow. That drive had been causing problems I hadn’t even realized. My system had been running like molasses, with lots of runaway processes (like in Chrome). That’s completely disappeared. It’s like greased lightning now, even with several instances and many dozens of tabs open in Firefox.
When I have had filesystems mounted read-only, it’s because the system says that fsck needs to be run on it. Check your messages in /var/log/dmesg and /var/log/messages
Well, I ran e2fsck on it immediately prior to booting (there were problems). Apparently its getting repeatedly corrupted.
Check your messages in /var/log/dmesg and /var/log/messages
Neither file exists.
OK, I ran ‘dmesg | less’ and am not seeing anything obvious. In fact, there’s no mention of /dev/mapper/fedora-new–host-home.
What happens if you try “mount -o remount,rw /home” to set it read-write manually?
It says it can’t do it, it’s write protected.
Do you guys enjoy solving these sorts of problems or something? Why not try my own alternative:
1. Have a panic attack
2. Get a Mac
3. Repeat steps 1 and 2.
(Enjoy solving these sorts of problem?) I used to work at a Web hosting company. So I used to run into this all the time. This was before solid-state drives, so when a drive crashed it was usually pretty obvious.
This is almost always either bad ram or a bad hard drive controller.
The disk is detecting corruption, and switching it to read-only as a protective measure. If you replace the drive and still have issues, probably some RAM died.
Kicking myself that I didn’t run an extensive memory test when I was out of town last week. I ran it overnight with not obvious problems, a few weeks ago.
So it could be a bad drive or controller. I’d suggest running “badblocks -n DRIVE” overnight to see if any errors crop up.
/dev/mapper/fedora_new–host-home /home ext4 ro,seclabel,relatime,data=ordered 0 0
says to mount read only (ro). But not being able to manually remount as read-write …
– does something have an open file in that folder? (I know, error message doesn’t fit, but I’ve seen some horridly misleading error messages.)
– I presume you tried the remount as root.
Yes, I tried the remount as root.
Its a little dangerous, but try it with the options “errors=continue” and “debug”:
/dev/mapper/fedora_new–host-home /home ext4 defaults,errors=continue,debug 0 0
This should write more information to syslog and it won’t remount as read only, which I believe is the default. A complete list of fun is here:
https://www.kernel.org/doc/Documentation/filesystems/ext4.txt