February 27, 201016 yr I've set up a new unRaid box a month ago and simply added files until I was sure it was stable. Now I'm trying to install the parity drive and get the same result each time 288 errors and the parity doesn't work. Because of the disk write errors in the log, I replaced the sata cable to the parity drive but get exactly the same results. Anyone got any ideas? This is an AMD Athlon II on a gigabyte board : 2 X 1GB DDR2-800 SDRAM (Kingston) 4 X WD Caviar Green: 1.5TB, SATA II, IntelliPower (5400-7200rpm), 32MB, GreenPower Thermaltake ToughPower 700W, ATX 12V 2.2 + EPS 12V, SLi Certified, 80 Plus Active PFC, Modular, Retail Thermaltake M9, ATX, Midtower (Black) AMD ATHLON IIX2 245 2900M AM365W(ADX245OCGQBOX) GIGABYTE SKT.AM2/AM2+ AMD740G +SB700,2D.DDR2-800MHZ,SATA,LAN AUDIO, M.ATX(GA-MA74GM-S2) CHENBRO 5-3 SATA II HD STORAGEKIT BLACK(SK33502-BK)
February 27, 201016 yr I've set up a new unRaid box a month ago and simply added files until I was sure it was stable. Now I'm trying to install the parity drive and get the same result each time 288 errors and the parity doesn't work. Because of the disk write errors in the log, I replaced the sata cable to the parity drive but get exactly the same results. Anyone got any ideas? This is an AMD Athlon II on a gigabyte board : 2 X 1GB DDR2-800 SDRAM (Kingston) 4 X WD Caviar Green: 1.5TB, SATA II, IntelliPower (5400-7200rpm), 32MB, GreenPower Thermaltake ToughPower 700W, ATX 12V 2.2 + EPS 12V, SLi Certified, 80 Plus Active PFC, Modular, Retail Thermaltake M9, ATX, Midtower (Black) AMD ATHLON IIX2 245 2900M AM365W(ADX245OCGQBOX) GIGABYTE SKT.AM2/AM2+ AMD740G +SB700,2D.DDR2-800MHZ,SATA,LAN AUDIO, M.ATX(GA-MA74GM-S2) CHENBRO 5-3 SATA II HD STORAGEKIT BLACK(SK33502-BK) Post a copy of your syslog. No way to know what is happening otherwise. Instructions are in the wiki under troubleshooting.
February 27, 201016 yr The disk has been disabled by the OS because it is not responding after several attempts at resetting it to have it respond. Unfortunately, the unRAID software does not know it is disabled until it tries to write to the drive. as a result of it being disabled, the attempts to write to it fail. (and apparently there are 288 "writes" queued in the buffer cache when it finally decided to get to the physical disk... and they all fail) It might be a defective drive, or a defective port on the disk controller, or a defective power cable to the drive. (Most likely is it is a defective drive) Only way to know for sure is to get a SMART report on the drive (if it will respond) Type: smartctl -a -d ata /dev/sda and post the output. Then type hdparm -N /dev/sda hdparm -N /dev/sdb hdparm -N /dev/sdc hdparm -N /dev/sdd to see the HPA problem Also type hdparm -i /dev/sda hdparm -i /dev/sdb hdparm -i /dev/sdc etc... to see how the drive reports its geometry and capabilities. All of your drives seem to have an HPA (host protected area) You must have a Gigabyte motherboard. This might be an issue when you go to add a new data drive in the future that does not have an HPA, as it will be too big. You should probably remove the HPA on the parity drive before adding it to the array, once you get one that works, and probably need to disable the creation of the HPA in your BIOS, as it only complicates your life and causes hair-loss. (You'll be pulling out your hair when it bytes your tail at the worst time) Feb 25 17:40:54 tower kernel: ata1.00: HPA detected: current 2930277168, native 18446744072344861488 Feb 25 17:40:54 tower kernel: ata1.00: ATA-8: WDC WD15EADS-00P8B0, 01.00A01, max UDMA/133 Feb 25 17:40:54 tower kernel: ata1.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 31/32) Feb 25 17:40:54 tower kernel: ata1.00: configured for UDMA/133 Feb 26 16:46:35 tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 26 16:46:35 tower kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Feb 26 16:46:35 tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 26 16:46:35 tower kernel: ata1.00: status: { DRDY } Feb 26 16:46:35 tower kernel: ata1: hard resetting link Feb 26 16:46:42 tower kernel: ata1: link is slow to respond, please be patient (ready=0) Feb 26 16:46:45 tower kernel: ata1: softreset failed (device not ready) Feb 26 16:46:45 tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 26 16:46:50 tower kernel: ata1.00: qc timeout (cmd 0xec) Feb 26 16:46:50 tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 26 16:46:50 tower kernel: ata1.00: revalidation failed (errno=-5) Feb 26 16:46:50 tower kernel: ata1: hard resetting link Feb 26 16:46:57 tower kernel: ata1: link is slow to respond, please be patient (ready=0) Feb 26 16:47:00 tower kernel: ata1: softreset failed (device not ready) Feb 26 16:47:00 tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 26 16:47:10 tower kernel: ata1.00: qc timeout (cmd 0xec) Feb 26 16:47:10 tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 26 16:47:10 tower kernel: ata1.00: revalidation failed (errno=-5) Feb 26 16:47:10 tower kernel: ata1: hard resetting link Feb 26 16:47:17 tower kernel: ata1: link is slow to respond, please be patient (ready=0) Feb 26 16:47:20 tower kernel: ata1: softreset failed (device not ready) Feb 26 16:47:20 tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 26 16:47:30 tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100) Feb 26 16:47:30 tower kernel: ata1.00: revalidation failed (errno=-5) Feb 26 16:47:30 tower kernel: ata1.00: disabled
Archived
This topic is now archived and is closed to further replies.