Noticed files were missing on the server, checked and two drives have errors.  1 drive with errors is still green but reporting 0 degress temperature, and 1 drive with errors is red-balled.

 

What are my next steps?  What reports do I run and post to try and figure out what to do?

 

Thank you!

Rory

We need your syslog file.

I can't telnet to my server.

 

I started the "stop array" process, now it just has all the drives showing "unmounting" for the last 5 minutes, and the telnet session cannot connect.  "Could not open connection to host , on port 23: Connection failed"

 

*now when I try to access the server through my web browser, it cannot find anything*

I power cycled (twice, the first time 3 drives were missing, I checked connections and re-booted again)

Now I have 1 red-balled drive and my drives are accessible.

 

I have attached my syslog file for review.

 

*edit smartctl also attached*

 

*edit*

Ran the short Smart test, then re-ran the smart report, it is attached as well.

 

Thank you for the help,

 

Rory

 

syslog_-_2011-09-01.txt

smart20110901.txt

smartAfterShortTest.txt

Can someone please review the attachments about my drive so I know what to do with it?

 

I have copied data over to the server since it has been red-balled, so should I re-build it onto the existing drive, or replace the drive and re-build onto a new drive?

I don't think I should use the "trust" procedure as I have written data to it, is that correct?

 

Thank you,

Rory

Rebuild the red drive:

 

1. Stop the array and un-assign the drive.

2. Start the array and then stop the array.

3. Reassign the drive and start the array.

So the drive doesn't look like it is going bad then?

 

I followed your instructions and the re-build is started, thank you.

 

Rory

Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

 

Not failing according to the smart report.  The red ball indicates a write to the drive failed.  What was the last write you made to the drive, any indications at that time?

 

I'm not that familiar with Seagate drives..but this would be something I would investigate further

Command_Timeout        0x0032  100  099  000    Old_age  Always      -      4295032833

 

<related to loose cables/faulty PSU>

 

It has been sitting red-balled for a while now, I don't remember what I was doing when I noticed it.

 

I'm not sure what the Command_Timeout means.

 

I'll let the re-build run and if I have any further problems I will replace it.

 

Thank you everyone,

Rory

http://kb.acronis.com/content/9123

 

The smart report indicates a "100" for the command timeout which means it is not failing.  The Raw value is high, but no idea how that value correlates to the # of failed command responses.

 

btw, you will lose data when 2 drives are redballed at the same time...

 

Yeah, I know 2 red-balled drives would mean lost data, which is why I wanted to get an answer as to whether the drive was bad or not.

 

Re-build is underway, thanks again.

Rory

Success:  Drive re-built with no Parity or drive errors.

 

Rory

Run a parity check to verify the rebuild.