This is driving me bonkers, as above, within a few minutes of running a parity check, I lose all connectivity to my tower. I'm hoping someone can help (syslog attached)

I'm running 5.0 beta12a

 

I've included a list of hardware. I have to say though, I don't think parity check was an issue until I dabbled with user shares securities through the web interface. I've since returned the settings to default. Would a newer version of unraid help?

 

ASUS M4A7BLT-M LE

AMD Athlon II X2 245e Energy Effici 1

4GB (2x2GB) Corsair Dominator DDR3 1

650W Corsair CMPSU-650TXUK TX, 86% 1

Supermicro AOC-SASLP-MV8, 8-Port SA 1

2Tb Samsung HD204UI/Z4, SpinPoint E

 

2TB Hitachi HDS5C3020ALA632 CoolSpi

Adaptec INT MSASX4 TO 4XSATAX1 Cabl

45cm Akasa Day Glo Blue UV Right an 1

3TB Seagate ST3000DM001 Barracuda 

3TB Hitachi 0S03230 Deskstar 5K3000

unraid.txt

See here: http://lime-technology.com/forum/index.php?topic=9880.0

 

Attach the entire syslog.

Apologies, I have now done that. Can anyone help?

 

thanks

Provide a full syslog from a boot before starting the check and also a list of hardware could help.

here you go mate, hope this enlightens you

fullsyslog.txt

What are the HW specs? What SATA cards?

I've included a list of hadrware. I have to say though, I don't think parity check was an issue until I dabbled with user shares securities through the web interface. I've since retunred the settings to default. Would a newer version of unraid help?

 

ASUS M4A7BLT-M LE

AMD Athlon II X2 245e Energy Effici 1

4GB (2x2GB) Corsair Dominator DDR3 1

650W Corsair CMPSU-650TXUK TX, 86% 1

Supermicro AOC-SASLP-MV8, 8-Port SA 1

2Tb Samsung HD204UI/Z4, SpinPoint E

 

2TB Hitachi HDS5C3020ALA632 CoolSpi

Adaptec INT MSASX4 TO 4XSATAX1 Cabl

45cm Akasa Day Glo Blue UV Right an 1

3TB Seagate ST3000DM001 Barracuda 

3TB Hitachi 0S03230 Deskstar 5K3000

There is know incompatibility between the Supermicro AOC-SASLP-MV8 and b12. Please read the announcements thread. Try beta 14.

Ok, I had no idea. Thanks for that, I will give it a go and post the results here

Well, I've updated to the latest beta and one of the hdd's has red balled, so at least I've found the culprit and can replace accordingly. Quite why the previous release couldn't pick this up is beyond me, i guess it was the compatibility issues with running 5.0 beta12a, using a super micro card AOC-SASLP-MV8, but never mind. I can have her up and running again once i get the new hdd through.

 

Thanks for your input guys, it's much appreciated