Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I have a RAID5 software raid in Centos 5.8 that keeps going read-only. A disk dropped out of raid a few weeks back, but when I added it back in, everything worked fine... for a while. Now mdadm shows all the disks are happy and working fine. I pulled the drives (Seagates) and tested them using Seagate Diagnostics and both short and long drive tests come up clean, but the problem persists.
I have run fsck several times and it always finds errors, and fixes them. The array will then remount fine for a few hours and then problems again.
They are also in a JBOD, but the other drives in the JBOD that are not RAID are working without issue.
These are fairly new drives (less than 1 year). I'm not sure what else to test. Any better drive diagnostic software out there? Any help would be great!
You might want to investigate the drive controller(s), connections and cables. If the drives themselves are alright it sounds like your issue is at a lower level causes writes to not get committed properly.
Have you checked what S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) says about the drives? I recently had a hard disk failure in my RAID array that I suspected for a while but nothing detected till finally my S.M.A.R.T. report gave me enough confidence to determine which drive was failing and replace it. http://pkgs.org/centos-5-rhel-5/cent....i386.rpm.html
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.