File system becomes read-only, hardware failure or software problem?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
File system becomes read-only, hardware failure or software problem?
HP server with RADI, file system may become read-only after some time of running. Rebooting the system will recover it, but read-only again after a period of time.
Here's some information:
[zero@HP380 ~]$ uname -a
Linux HP380.xxxx 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
[zero@HP380 ~]$ mount
/dev/sda3 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
/dev/sdb1 on /home type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
[zero@HP380 ~]$ mkdir asdf
mkdir: cannot create directory `asdf': Read-only file system
[zero@HP380 xxx]# smartctl -a /dev/sdb
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: HP
Product: LOGICAL VOLUME
Revision: 3.52
User Capacity: 1,800,280,170,496 bytes [1.80 TB]
Logical block size: 512 bytes
Logical Unit id: 0x600508b1001cc7ff72230ea46040e9a3
Serial number: 5001438009F6B750
Device type: disk
Local Time is: Mon Dec 8 12:04:34 2014 CST
Device does not support SMART
Error Counter logging not supported
Device does not support Self Test logging
The message that SMART is not supported might not be literally true. Enter the BIOS when you switch on the computer and go to the hard-drive section and see if there is an option to activate SMART — it might just be switched off by default.
Still cannot find option to enable SMART in BIOS.
But one of the disk's led showed failure state. So it's definitely a disk hardware problem.
Thanks everybody for the advice.
Just a couple of points that seem to have been missed:
It doesn't surprise me that the composite RAID device does not support SMART. That is something that would apply to the individual drives.
Failure of a single drive should not cause any issues for the OS. Continuing on seamlessly in the face of such failures is what RAID is all about.
As there is nothing in the mount output about mdadm devices, this would have to be either hardware RAID or "Fake RAID" in the BIOS. As syg00 requested, more information about the RAID setup is needed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.