February 3, 201016 yr Unregistered 3 disk Unraid system. Just now adding parity drive to array. 2 data disks already in system that have data on them. All 3 drives are Seagate barricuda 500 GB and are showing 488,386,552 bytes in Unraid web gui. Parity drive shows orange ball. Command area says "Stopped. New parity disk installed." I assume I supposed to click the check box for "I'm sure I want to do this" and then click the "Start will bring the array on-line and start Parity-Sync." button. So I did this. Very briefly the disk1 and disk2 show as "Unformatted" and then the parity drive shows "0C" temperature. So I refresh and the Command area says "Stopped. New parity disk installed." again, the parity disk continues to say "0C" degrees and nothing is happening. Since the Wiki manual only has this brief passage (which is far far too vague) it's difficult for me to determine if I'm seeing an error or if it is quietly rebuilding the parity disk. Could someone help fill in the gap for me and describe what I should be seeing so I can figure out if it is performing correctly? ... 4.Power up the unit. 5.Start the array. 6.Wait for Parity-Sync to complete.
February 3, 201016 yr Unregistered 3 disk Unraid system. Just now adding parity drive to array. 2 data disks already in system that have data on them. All 3 drives are Seagate barricuda 500 GB and are showing 488,386,552 bytes in Unraid web gui. Parity drive shows orange ball. Command area says "Stopped. New parity disk installed." I assume I supposed to click the check box for "I'm sure I want to do this" and then click the "Start will bring the array on-line and start Parity-Sync." button. So I did this. Very briefly the disk1 and disk2 show as "Unformatted" and then the parity drive shows "0C" temperature. So I refresh and the Command area says "Stopped. New parity disk installed." again, the parity disk continues to say "0C" degrees and nothing is happening. Since the Wiki manual only has this brief passage (which is far far too vague) it's difficult for me to determine if I'm seeing an error or if it is quietly rebuilding the parity disk. Could someone help fill in the gap for me and describe what I should be seeing so I can figure out if it is performing correctly? ... 4.Power up the unit. 5.Start the array. 6.Wait for Parity-Sync to complete. Only way to know what is happening is to see a copy of the syslog. Instructions in the wiki under troubleshooting. I would think the array should show "Started" and show that a parity sync is in progress. ... but I've not done this with any recent versions of unRAID, my array has been running for years. It almost sounds as if your parity disk has stopped responding. Joe L.
February 3, 201016 yr Can do! I have attached the syslog. These lines in the log seem to indicate that the new parity drive has stopped responding. Feb 3 03:27:41 Queeg kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen Feb 3 03:27:41 Queeg kernel: ata3: SError: { PHYRdyChg } Feb 3 03:27:41 Queeg kernel: ata3: hard resetting link Feb 3 03:27:41 Queeg kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen Feb 3 03:27:41 Queeg kernel: ata1: SError: { PHYRdyChg CommWake } Feb 3 03:27:41 Queeg kernel: ata1: hard resetting link Feb 3 03:27:42 Queeg kernel: ata3: SATA link down (SStatus 0 SControl 310) Feb 3 03:27:42 Queeg kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 3 03:27:42 Queeg kernel: ata1.00: configured for UDMA/100 Feb 3 03:27:42 Queeg kernel: ata1: EH complete Feb 3 03:27:47 Queeg kernel: ata3: hard resetting link Feb 3 03:27:47 Queeg kernel: ata3: SATA link down (SStatus 0 SControl 310) Feb 3 03:27:52 Queeg kernel: ata3: hard resetting link Feb 3 03:27:52 Queeg kernel: ata3: SATA link down (SStatus 0 SControl 310) Feb 3 03:27:52 Queeg kernel: ata3.00: disabled Feb 3 03:27:52 Queeg kernel: ata3: EH complete Feb 3 03:27:52 Queeg kernel: ata3.00: detaching (SCSI 2:0:0:0) Feb 3 03:27:52 Queeg kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache Feb 3 03:27:52 Queeg kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 Feb 3 03:27:52 Queeg kernel: sd 2:0:0:0: [sdc] Stopping disk Feb 3 03:27:52 Queeg kernel: sd 2:0:0:0: [sdc] START_STOP FAILED Feb 3 03:27:52 Queeg kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 I'd double check the connections to it. Possibly a loose connector? The linux OS tried several times to reset it, but failed before disabling the disk.
February 3, 201016 yr Author It's building the parity disk now. I think it was a hard drive fan attached to the parity drive (which I have disconnected) or possibly it's the sata or power connectors which I re-seated just in case. Now it's building so I'm relieved. I still would like to see some more details in the wiki manual describing that when parity is rebuilding there is progress information on the web page. Everyone seeing it fail the first time (like me) won't know what they should be seeing, if anything. There are some raid systems that provide no information while rebuilding so I could have waited hours before finding out. Thanks, Dave
Archived
This topic is now archived and is closed to further replies.