September 9, 201114 yr Suddenly my parity disk went red. So I stopped the array, marked parity check and started the array. After that the unraid gui went short unresponsive and after a few seconds the array is started without the parity, which gets 384 Errors. I don't know the reason for the errors, so I ask you. I hope the drive is not broken. I'm using the latest Beta 12a The Parity is a WD20ears unjumpered and I transfered before 1,5TB of Data per LAN to my array without any problems. Syslog.txt
September 9, 201114 yr Line 1060: Sep 9 10:44:51 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen Line 1061: Sep 9 10:44:51 Tower kernel: ata5.00: irq_stat 0x08000000, interface fatal error Line 1062: Sep 9 10:44:51 Tower kernel: ata5: SError: { Handshk } Line 1063: Sep 9 10:44:51 Tower kernel: ata5.00: failed command: WRITE DMA EXT Run a smart test on the parity drive and post here. http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_problems_by_keyword Handshk errors are typically interface (cabling) issues.. http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_Interface_Issues
September 9, 201114 yr Author Thanks! Smart Status: Failing Get data off disk and run advanced tests below for more information SMART Information: Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. SMART Extended Test: Disk must be spun up before running tests I used the option "spin up" on the mainmenum, but the SMART Extended Test says the same. //edit: I changed power and sata cable and there are no errors in the first few minutes. I report back! Thanks again!
Archived
This topic is now archived and is closed to further replies.