September 18, 200817 yr I am trying to add a 500gig Western Digital drive. Each time I try to assign it and add it to the array, it reverts back to "not installed" after about 4% of the clearing process. Not too sure what's goin on with that. All the previous drives I've added, I haven't had any problems with. Here's some system info: Parity: 750GB Samsung Sata 500GB Seagate Sata 500GB Maxtor Sata 400GB Seagate IDE 300GB Seagate Sata 200GB Maxtor IDE 160GB Samsung IDE Flash Drive: Lexar 1GB Motherboard is an old Dell with a Pentium 4 (2.8ghz). 1gig ram Promise SATAII150/SATA300 TX4: 4 port Sata Card The new drive is connected to one of the Sata ports on the card. I am attaching the syslog. Not sure what other info would/could help or is needed. I hope this is specific enough. I don't post in forums too often. thanks for any help.
September 18, 200817 yr Author Don't know if this is 'normal'...but my syslog was too large to attach. I cut it in half...to post in 2 parts.
September 18, 200817 yr Well, it appears as if the new disk has tons of errors when unRAID attempts to write to it. It has written thousands of lines to your syslog as it tries. It is trying to write to /dev/sdc1. I'm assuming that is your new drive. If you are lucky, it will just be a loose cable on the drive, or a defective cable. If you are not as lucky, it is as good a time as any to return the new drive under warranty. Here is where the errors started in the syslog: [pre] Aug 27 13:13:15 Tower kernel: md7: new disk Aug 27 13:14:08 Tower emhttp: ... clearing 3% complete Aug 27 13:14:17 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 27 13:14:17 Tower kernel: ata4.00: port_status 0x20200000 Aug 27 13:14:17 Tower kernel: ata4.00: cmd ca/00:7f:51:8f:d3/00:00:00:00:00/e1 tag 0 dma 65024 out Aug 27 13:14:17 Tower kernel: res 51/04:5f:7f:7f:d3/00:00:00:00:00/e1 Emask 0x1 (device error) Aug 27 13:14:17 Tower kernel: ata4.00: status: { DRDY ERR } Aug 27 13:14:17 Tower kernel: ata4.00: error: { ABRT } Aug 27 13:14:18 Tower kernel: ata4.00: failed to read native max address (err_mask=0x1) Aug 27 13:14:18 Tower kernel: ata4.00: HPA support seems broken, will skip HPA handling Aug 27 13:14:18 Tower kernel: ata4.00: failed to set xfermode (err_mask=0x1) Aug 27 13:14:18 Tower kernel: ata4: failed to recover some devices, retrying in 5 secs Aug 27 13:14:23 Tower kernel: ata4: soft resetting link Aug 27 13:14:24 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 27 13:14:24 Tower kernel: ata4.00: failed to set xfermode (err_mask=0x1) Aug 27 13:14:24 Tower kernel: ata4: limiting SATA link speed to 1.5 Gbps Aug 27 13:14:24 Tower kernel: ata4.00: limiting speed to UDMA/133:PIO3 Aug 27 13:14:24 Tower kernel: ata4: failed to recover some devices, retrying in 5 secs Aug 27 13:14:29 Tower kernel: ata4: hard resetting link Aug 27 13:14:29 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 27 13:14:29 Tower kernel: ata4.00: failed to set xfermode (err_mask=0x1) Aug 27 13:14:29 Tower kernel: ata4.00: disabled Aug 27 13:14:30 Tower kernel: ata4: EH complete Aug 27 13:14:30 Tower kernel: sd 4:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 Aug 27 13:14:30 Tower kernel: end_request: I/O error, dev sdc, sector 30642001 Aug 27 13:14:30 Tower kernel: Buffer I/O error on device sdc1, logical block 30641938 Aug 27 13:14:30 Tower kernel: lost page write due to I/O error on sdc1 Aug 27 13:14:30 Tower kernel: Buffer I/O error on device sdc1, logical block 30641939 Aug 27 13:14:30 Tower kernel: lost page write due to I/O error on sdc1 Aug 27 13:14:30 Tower kernel: Buffer I/O error on device sdc1, logical block 30641940 Aug 27 13:14:30 Tower kernel: lost page write due to I/O error on sdc1 Aug 27 13:14:30 Tower kernel: Buffer I/O error on device sdc1, logical block 30641941 Aug 27 13:14:30 Tower kernel: lost page write due to I/O error on sdc1 Aug 27 13:14:30 Tower kernel: Buffer I/O error on device sdc1, logical block 30641942 Aug 27 13:14:30 Tower kernel: lost page write due to I/O error on sdc1 Aug 27 13:14:30 Tower kernel: Buffer I/O error on device sdc1, logical block 30641943 Aug 27 13:14:30 Tower kernel: lost page write due to I/O error on sdc1 [/pre] have fun... unRAID is telling you the truth. That drive is not responding, and therefore, to it, not installed. Joe L.
September 18, 200817 yr Don't know if this is 'normal'...but my syslog was too large to attach. I cut it in half...to post in 2 parts. It is not normal... It is filled with error messges from the new disk.
September 18, 200817 yr Author Hey, thanks a bunch for the quick reply. I'm gonna switch cables tomorrow when I wake up and hope that fixes it. *at one point I did run reiserfsck (new to me) on the disk and it came up with no errors. **As for the /dev/sdc1 : when i ran the disk check, the new disk was /dev/md7. The disk is brand new though, so it's definitely covered by warranty though...lucky for me
September 18, 200817 yr Author I just swapped cables and same thing. Got to 3% clearing then after hitting refresh the drive switches to 'not installed'. I guess it's time to take it outta my box and return the drive.
September 19, 200817 yr Is the drive connected directly to the MB, or are you using some type of backplane? If it is using a backplane, try attaching the cable directly to the drive.
September 19, 200817 yr Author It was attached directly to the drive. I actually took the drive back and swapped it for a Hitachi Deskstar and it's working so far. It cleared without incident and the parity check is at 75%, going strong. I'm guessing it was just a bunk drive, but after reading about issues with the WD's, I figured I'd keep them outta my box...hehehe. Thanks again for the help
Archived
This topic is now archived and is closed to further replies.