SOLVED Parity Check Crashing Web/Network Interface

Updated Nov 17:

after doing some tests below and playing with hardware I am up and running! I  swapped out the power supply and am now only using the mobo's onboard sata controller.

thanks everyone for your input

Original message:

Hello,

I am currently running 5.0 beta 13 and my unRaid seems to drop and kill all network connections shortly after starting a Parity check. I am able to log on directly to the box, but all network communication is killed. I have been trying to use unRaid since July, and i would say 90% of the time I cannot complete a Parity check without it crashing.

I have attached my syslog before i started the Parity check, and then the terminal view of the syslog when the parity crashed. I don't see anything that stands out.

Any help would be appreciated.

cheers

syslog.txt

syslog.txt_during_parity.txt

I did not see anything in your syslog that seems amiss. Have you tried v. 4.7? Have you tried running a memcheck? What motherboard are your running? How much memory do you have? Any extra controller cards? Strip down the system and then start changing parts. Did you preclear your disks (not required but helps find problems).

memtest:

http://lime-technology.com/forum/index.php?topic=10698.0

preclear disk:

http://lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#Preclear_Disk

You are using an older computer with power hungry CPU. If your PSU is the original one it is possible that it is not good enough especially if the system temperature raises running the parity check without a proper cooling. The components do age just like us...

Good luck.

Thanks for your input... I will play around with it again tomorrow.

Yes, it is an older mobo and cpu... a pentium 4 ht... The power supply is newer though. But I will look into that.

The motherboard has 4 SATA slots, i have the parity drive on the mobo controller, and i have a pci sata controller that has the other 2 drives on it. I initially had all drivers on that and had the mobo sata controller disabled, but i thought i would try the moving the parity off onto its own controller.

I guess what confuses me most is that the machine still runs when it freezes. Just all network connectivity appears to be cut off/shut down. I am going to try another network card as well to see if that could be the issue.

i will let you know how i make out...

The MB SATA ports are definitely faster than having two drives on a PCI bus. The PCI bus will only support a single drive at full speed across all of the PCI slots. In general the MB SATA ports will perform better than controller card ports.

well today, when it checks parity it crashes the whole machine. can't even connect to the machine itself.

I have tried putting all the drives on the mobo's sata, and the machine will load, i will get the logon screen then it imediately restarts.

i guess by a new mobo?!?!