Hi!

 

I have been using unRAID for 5 months without any issues up to now.

I was transfering a file to Disk1 with ftp and when it was done I didn't see anything in the directory. I did a refresh and then it showed.

 

I noticed in the main screen that Disk1 didn't show the temperature and that the parity disk hade a red ball next to it.

 

So I tried to access the disk in putty but I got /bin/ls: reading directory .: Input/output error

So I ran a smartcl and got

root@Tower:/mnt/disk1# smartctl  -a  -d  scsi  /dev/sdb

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

Short INQUIRY response, skip product id

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

 

Now I'm getting a little panic and I tried to search through the forum and can't really find what I would do.

 

What would my next step be?

Shut down the array and check cables and then try to enable the array again?

Drive to the store and replace the WD disk?

Create a RMA with WD and request a replacement?

Run other tests if possible?

 

I would really apprechiate som guidance on where to start.

 

info.zip

Stop writing to the array immediately and try to shutdown cleanly.

The syslog errors indicate hardware failure on the parity drive.

 

I've not seen this error before, so Wait for a second opinion to be sure, but I think the parity drive is fatal and unrecoverable.

Plan on buying a replacement. (or RMA)

---

You also have one Write error on Disk #1. That could be a more typical 'storage' error, and could get cleaned up automatically when you bring the array online after its fixed.  But maybe not, if the data written to #1 is actually corrupted as a result of the failure of parity.

 

Therefore, if you remember, write down the names of the files you transferred to the array. (are they in your FTP log? if so save a copy). After you repair the array, you may find that drive#1 still has a file error...and that's likely to be one of the files that was being written when the parity broke.

 

With the list of files, you'll have the list of likely suspects that need to be recopied to Disk#1.

Thanks DaleWilliams!

 

Ok, I could do a clean shutdown without any problems. I checked the cables and two of them was not quite attached to the controller card (bummer).

I restarted unRAID without mounting the array and now the parity disk got a blue ball and it says "New parity disk installed".

Disk1 seems ok and right now I'm doing a offline smartcl on the parity drive.

 

What would be the best thing to do?

Replace parity with a new? and start array to rebuild?

 

 

 

I hope it was just the cables!

 

I tend to get nervous with this type of problem...so I tend to do a lot of testing--just to be sure everything is okay.

Here's what I'd do:

 

There's a Long SMART test...I'd run that on Parity.

http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report

 

And I'd run Reiserfsck on disk#1, to be sure the file system is okay.

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

And finally, If you have the list of files from the FTP session, I'd check those files to be sure they are good.

 

Thank you DaleWilliams for helping me out. Everything seems fine now. I replaced the parity disk with a 4TB WD Red and ran a Reiserfsck on Disk1 which had zero errors 

 

 

Cool! I'm glad its fixed!