My Unraid system has been running fine until a couple of days ago, but now every time I rip a Bluray to it, it freezes. When I reboot the system, the parity drive has a red ball beside it. Smartctl didn't find any errors so I reinstated the drive. But the same thing keeps happening everytime I rip a Bluray.  I was wondering if somebody with more linux experience than me would be kind enough to have a look at my syslog and maybe help diagnose the problem?

 

 

Many thanks

 

 

 

santan.

 

I'm new to this but those errors appear to be a generic hardware error. It also appears to happen on many drives making it harder to diagnose. Try checking your cabling and such. Is there something common between those drives (ATA5 to ATA8) such as all being on the motherboard. A better description of your system might help.

 

You appear to have SATA drives but are using PATA mode. Try switching the bios to use AHCI mode.

 

Peter

 

Thanks for your help, I thought that may be the case. I think it is probably the motherboard (Asus P5Kc) which has compatibility issues with Unraid. For some reason Asus didn't include AHCI with this board so I am stuck with IDE. However I did update the Bios and changed SATA mode from Enhanced IDE to compatible mode and touch wood that seems to be working at the moment.

 

 

Thanks again

 

Santan

I agree with Peter.  It looks like there are 4 drives in a row, on ATA5 through ATA8 (sdb,sdc,sdd,sde), with identical exception Emask (frozen, timeout) errors.

That makes me think it is the same disk controller, or its driver/module, that has somehow been corrupted.  That error is becoming more common over the last year, but is not very helpful.  It often indicates the drive is no longer responsive, but in your case, it does respond to resets, but not drive commands!  In my experience, there have been no cases of drive or data loss or damage, with this error, after powering off and rebooting.

 

I would suggest running a reiserfsck on each of those data drives (not the parity drive), because there were Reiser errors reported.  Probably nothing wrong, but better to check.  The errors were probably reported because ReiserFS could not update the unresponsive drives.  See Check Disk Filesystems.

 

Hopefully, this will be a rare event, and changing the BIOS mode may change which modules service it.

 

When posting your syslog, it is best to include the entire thing, zipped if necessary.

Thanks RobJ,

 

I'm not sure why I was getting controller errors as it was a standard ICH9 but unfortunatly the errors persisted after I changed the Bios settings. Unraid kept redballing different drives so after a bit of hunting around the net I found a refurbed Asus P5B-E which people seem to be using succesfully with Unraid. I installed it this morning and it is syncing the parity drive at the moment so hopefully things should work now...

 

 

 

I think it is probably the motherboard (Asus P5Kc) which has compatibility issues with Unraid.

 

Forgive my being picky here, just a technical point, but it is probably more accurate to say a motherboard has compatibility issues with Linux, or a particular version of the Linux kernel, rather than with unRAID.

 

It does seem suspicious that ASUS did not enable AHCI support, the ICH9 should have had it.