Leen de Braal wrote:
I have a raid1 system with 2x 400GB SATA drives. System has been frozen several times in the last 2 weeks. I have been checking memory overnight, no problems, checked harddisks with manufacturertools, no problems found. So I think, that maybe there is something wrong somewhere in the filesystem, but how do I check? Using reiserfsck from rescuedisk on the partitions does not work. Running the rescuedisk does not freeze the system btw. So I do suspect (one of) the harddrives. What can I use to check??
Telepathic guess: you might have a driver modules problem. Unfortunately you do not mention what version of Suse you use or what hardware is involved (mainboard, lan adapter, sata controller) or even if it is a hardware raid or software raid.
9.2, kernel is 2.6.8-24.17-default Intel D865PERL mobo with P4-2.4, 512MB RAM software raid, 2x 400GB Seagate SATA Machine has been running fine for over 6 weeks
I would try to check the logs shortly before the time you experienced a system freeze, try to find common causes for those freezes. Also try to provoke a system freeze (if it's not a production system in use).
Log gives errors: kernel: ata2: status=0x51 { DriveReady SeekComplete Error } kernel: ata2: error=0x40 { UncorrectableError } This was the first freeze. Hung hard, I pulled power to reboot the machine. After that, it ran for 3 days and gave same errors, this time five pairs of those lines in about 10 minutes, but it kept on logging (cronjobs and MARKs) until I rebooted again. I think it already hung, because I could not log in, I could just type in my username, but machine did not respond with Password:-prompt. Today I have been testing this machine further, and at some point I was running a rescue system, and saw that raid was being resyncd (cat /proc/mdstat). I let it go until it was ready, and now it seems to run fine (at least for the last 2 hours). Will keep it monitored though. This machine is my first with raid, so bear with me seeming stupid about this. Still have some questions: - are those errors due to harddrive problems? - or is it due to misconfiguration in software raid? (done it with yast) - is it something software raid should correct (I expected that raid was for redundancy and corrected errors?)
You could check the SMART parameters of the disks with smartmon tools.
These drives seem not to have smart, at least manufacturertools say so
Sandy
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444