I had a pretty new disk that was disabled.  I tried to rebuild on the same disk but that failed with errors and was still disabled.  I bought a new drive and installed that after backing up my 'config/super.dat' and 'config/disk.cfg' files.  I used this process to replace the disabled disk with the new disk.

#  backup 'config/super.dat' and 'config/disk.cfg' files to workstation

# Stop the array

# Power down

# Replace hard drive with new drive.

# Turn on

# Replaced drive appears with blue dot

# Tick the "I'm sure" check box, and press "Start will bring the array on-line, start Data-Rebuild, and then expand the file system."

But when I turn on the system I never get a blue dot.  It says Not Installed.  Also, there is never a check box next to Start.  Just next to Restore (but I know not to push that).

I know my array is unprotected and I hope I can still re-build my disk9 onto my new drive and be back in business.  Does anyone know how I can get back on track?

Thanks for any help.

 

 

Here is a link to my most current syslog.txt and the one from when I first noticed the disabled disk.

http://www.mediafire.com/?sharekey=a8d8bd6aef4aa1d0bda4076e811714c8e04e75f6e8ebb871

 

I had a pretty new disk that was disabled.  I tried to rebuild on the same disk but that failed with errors and was still disabled.  I bought a new drive and installed that after backing up my 'config/super.dat' and 'config/disk.cfg' files.  I used this process to replace the disabled disk with the new disk.

#  backup 'config/super.dat' and 'config/disk.cfg' files to workstation

# Stop the array

# Power down

# Replace hard drive with new drive.

# Turn on

# Replaced drive appears with blue dot

# Tick the "I'm sure" check box, and press "Start will bring the array on-line, start Data-Rebuild, and then expand the file system."

But when I turn on the system I never get a blue dot.  It says Not Installed.  Also, there is never a check box next to Start.  Just next to Restore (but I know not to push that).

I know my array is unprotected and I hope I can still re-build my disk9 onto my new drive and be back in business.  Does anyone know how I can get back on track?

Thanks for any help.

 

 

Here is a link to my most current syslog.txt and the one from when I first noticed the disabled disk.

http://www.mediafire.com/?sharekey=a8d8bd6aef4aa1d0bda4076e811714c8e04e75f6e8ebb871

 

If you do not see the new disk as installed, and do not see it on the "devices" page to assign it to the slot, then I suspect one of your cables to that drive is defective or not seated properly. 

 

Did you assign the new drive to the slot on the devices page?  (It could be as simple as that if you did not perform that step)

 

Joe L.

I agree with Joe, it looks like you have either a bad cable or bad port.  The ATA bus error's on Feb 12 and Feb 22 (and Feb 25 with the new drive) definitely look like a bad cable with BadCRC errors.  The drives, new and old, are probably completely fine.  Because of the errors that occurred almost immediately, sdl was disabled even before the Device Inventory was logged, should probably have been dropped from the list, not allowed to even be visible to you.

Thanks very much JoeL and Robj!  You were absolutely correct.  I replaced my cable and of course I am re-building the data as we speak.  I have had this trouble before and replaced another drive based on the same symptoms.  I am naturally so hesitant to think cable failure or hardware failure.  I had wire tied all my cables nice and neat and am pre-disposed to not want to mess with that and re-cable everything.  So I try to make everything a software issue. 

 

Oh well, thanks for the lesson.  Now I'm going to go back to my supposedly "bad" drives and try to use them to replace one or two of my smaller (and older) drives in my array.  Does this seem wise?  Should I run SMART tests on them from a laptop prior to putting in the array?  Burn in with the preclear script?  Just wondering what the best practice is here.  These drives are probably good but were pulled due to disk disabled most likely from a bad cable.

 

Thanks again, very much for all the help and advise.

Thanks very much JoeL and Robj!  You were absolutely correct.  I replaced my cable and of course I am re-building the data as we speak.  I have had this trouble before and replaced another drive based on the same symptoms.  I am naturally so hesitant to think cable failure or hardware failure.  I had wire tied all my cables nice and neat and am pre-disposed to not want to mess with that and re-cable everything.  So I try to make everything a software issue. 

 

Oh well, thanks for the lesson.  Now I'm going to go back to my supposedly "bad" drives and try to use them to replace one or two of my smaller (and older) drives in my array.  Does this seem wise?  Should I run SMART tests on them from a laptop prior to putting in the array?  Burn in with the preclear script?  Just wondering what the best practice is here.  These drives are probably good but were pulled due to disk disabled most likely from a bad cable.

 

Thanks again, very much for all the help and advise.

 

If you want to check the ones you had previously thought bad you can run the preclear script that JoeL created.  I use it on all of my disks before I add them to the array.  I usually do at least 2 cycles on it.