Replacing failed HD, please help

[luca]

This morning I found an email alert that disk8 had failed:

 

Subject:unRaid Failure Notification - One or more disks are disabled or invalid.

Status update for unRAID  FS1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Status:

 

ERROR: The unRaid array needs attention. One or more disks are disabled or invalid.

 

Disk 8=DISK_DSBL

 

I followed the procedure  http://lime-technology.com/wiki/index.php?title=Replacing_a_Data_Drive to replace it.

 

I replaced the failed drive with a new one, but the new drive does not show up, now disk8 shows as "not installed". I stopped the array, thinking I could assign the drive manually. The array took forever to stop, probably over 5 minutes. Under the "devices" tab, the slot for disk8 was empty, as though as there was actually no drive there.

 

Syslog shows a few of these errors:

Apr 27 09:07:23 FS1 kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen

Apr 27 09:07:23 FS1 kernel: ata2: edma_err_cause=00000020 pp_flags=00000000, SError=00180000

Apr 27 09:07:23 FS1 kernel: ata2: SError: { 10B8B Dispar }

Apr 27 09:07:23 FS1 kernel: ata2: hard resetting link

 

Unfortunately I have no idea what that means. I run the server headless, so I could not check if the new drive was getting recognized from the BIOS. I run a parity check just a few days ago, and it came out fine as usual (zero errors). I am using unraid 4.5.1 / unmenu 1.3.

 

- edit: attached syslog

syslog-2010-04-27.zip

[Joe L.]

This morning I found an email alert that disk8 had failed:

 

Subject:unRaid Failure Notification - One or more disks are disabled or invalid.

Status update for unRAID  FS1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Status:

 

ERROR: The unRaid array needs attention. One or more disks are disabled or invalid.

 

Disk 8=DISK_DSBL

 

I followed the procedure  http://lime-technology.com/wiki/index.php?title=Replacing_a_Data_Drive to replace it.

 

I replaced the failed drive with a new one, but the new drive does not show up, now disk8 shows as "not installed". I stopped the array, thinking I could assign the drive manually. The array took forever to stop, probably over 5 minutes. Under the "devices" tab, the slot for disk8 was empty, as though as there was actually no drive there.

 

Syslog shows a few of these errors:

Apr 27 09:07:23 FS1 kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen

Apr 27 09:07:23 FS1 kernel: ata2: edma_err_cause=00000020 pp_flags=00000000, SError=00180000

Apr 27 09:07:23 FS1 kernel: ata2: SError: { 10B8B Dispar }

Apr 27 09:07:23 FS1 kernel: ata2: hard resetting link

 

Unfortunately I have no idea what that means. I run the server headless, so I could not check if the new drive was getting recognized from the BIOS. I run a parity check just a few days ago, and it came out fine as usual (zero errors). I am using unraid 4.5.1 / unmenu 1.3.

 

- edit: attached syslog

Since you are running cache_dirs and an older version of unRAID you must press the "Stop" button twice to stop the array.  That is why the array did not stop.

 

All indications are that the new drive you installed is not working.

It could easily be a bad SATA cable to the drive

A loose SATA cable to the drive

A bad power cable to the drive

A loose power cable to the drive

A bad disk controller port

Any of the above would infer the original drive was fine, just not connected ...

Or

A bad replacement disk drive.

 

Can't tell from the syslog other than Linux does not see the drive.  I'd power down, re-seat the cables and power back up.

 

DO NOT press the button labeled "restore"  Pretend it is labeled "Delete Disk Configuration and Parity"  It is NOT what you want to do once the disk is visible to Linux.  (You need the parity data to be able to re-construct the files on the old disk onto its replacement)

 

Once the disk is in place it will probably show up on its own on the main page.  You'll need to check the checkbox under "Start" to enable "Start" and then press "Start"

 

Joe L.

[luca]

Since you are running cache_dirs and an older version of unRAID you must press the "Stop" button twice to stop the array.   That is why the array did not stop.

 

All indications are that the new drive you installed is not working.

It could easily be a bad SATA cable to the drive

A loose SATA cable to the drive

A bad power cable to the drive

A loose power cable to the drive

A bad disk controller port

Any of the above would infer the original drive was fine, just not connected ...

Or

A bad replacement disk drive.

 

Joe, it was a bad power cable splitter...    It was seated properly, it just stopped working. I replaced it and now the drive is getting recognized and is showing up with a blue dot on unraid main.

I guess this means that the original drive is probably OK. Unrelated question: is there a pre-clear for windows? 

[Joe L.]

Joe, it was a bad power cable splitter...    It was seated properly, it just stopped working. I replaced it and now the drive is getting recognized and is showing up with a blue dot on unraid main.

I guess this means that the original drive is probably OK.[/quoe]Yes.

Unrelated question: is there a pre-clear for windows? 

No

But you can easily put unRAID on a spare flash drive along with the pre-clear script, then boot it on your windows box.

Don't assign any drives to the unRAID array, and make darned certain you don't clear the windows boot disk, (there is NO un-do.  It will let you shoot yourself in the foot, an it will be very painful)

 

It will let you clear any attached drive.

 

Joe L.