Hi, I'm still running RC8a.

 

I just had a disk disabled shortly after manually starting the mover script.

 

Syslog attached.

I deleted mover-related lines and probably around a thousand of the repeating "handle_stripe read error" lines to shorten things up for attachment.

 

smartctl doesn't seem to work and gives the following output:

Device: /1:0:0:0  Version:

scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46

>> Terminate command early due to bad response to IEC mode page

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

Also, you can see errors at the end of my syslog where I tried viewing the smart page on unmenu "mymain"

 

So... I have a new drive on it's way that probably won't get here until mid-next week. 

I was planning on keeping things running in the meantime unless that seems risky/unwise (I'd only write to the cache drive in the meantime.)

 

If I were to reseat everything and try again (the HP box I'm using uses a drive caddy, so I'm not sure anything could have loosened).. what would I do after that to test?  Reconstruct the drive?  I'm not sure what errors point towards communication issues vs physical ones with the drive itself.

 

 

 

syslog-edited-2013-04-19.txt

Try to get a SMART report after a power cycle.

Power cycling did allow for a smart report, thanks.

 

I'm guessing that 12640 reallocated sectors means the drive itself is toast, and definitely not a cable/server issue, correct?

 

The drive is still under warranty.. does anyone have any experience with an RMA in this situation?  It looks like the smart report says it hasn't crossed the failure threshold yet.. do I need to run the drive into the ground before sending it back?

 

Thanks for your help.

smart.txt

Scratch that last question about RMA, sorted it out with info off of Seagate's site. 

 

Thanks again.