Hey All,

 

Scary situation (for me anyways).  My unRAID array won't come online and the whole system takes a good 5 min to boot up and the web interface is incredibly slow.  Take a couple minutes to navigate and took about 4 minutes to to log in AFTER I entered credentials. 

 

I am afraid something bad is really happening.

 

Here is a screen shot and a syslog.  I know the screen shot says that disk8 is missing but it certainly is installed and the bios is detecting it so not sure where to go next.

 

I am of course freaking out a little.  Any help would be greatly appreciated.  Right now the I have NOT brought the array online

 

When did this start happening?  Just about 30 min ago AFTER a reboot.  The array was going VERY (reading and writing) slow for a couple says now so I decided to do a reboot.  I checked all the balls first before stopping the array and ALL balls were green.

syslog.txt

Here is the screenshot

I am by no means any sort of expert in unRAID

BUT i found this

 

Physical Drive Issues

 

These are actual errors from the drive itself, perhaps a failing drive, or perhaps just failing sectors. In general, you will always want to Obtain a SMART report for the drive.

[edit] Drive media issue #1

 

A typical example:

 

ata3.00: cmd 60/00:10:4f:80:81/04:00:66:00:00/40 tag 2 ncq 524288 in

        res 41/40:64:eb:80:81/85:03:66:00:00/40 Emask 0x409 (media error) <F>

ata3.00: status: { DRDY ERR }

ata3.00: error: { UNC }

 

These are almost always associated with bad sectors. They should be confirmed by examining a SMART report. See the Troubleshooting page, Obtaining a SMART report section. Then run a SMART long test (instructions in same section), to locate the bad sectors. You may need to seek advice as to what to do next, as it will depend on your specific situation.

 

as this error occurs in you log

 

i got the info from this page

http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues

i guess you got 2 choices start troubleshooting http://lime-technology.com/wiki/index.php/Troubleshooting

OR replace the drive if you think it's not the cables and then rebuild from parity

So unRAID is saying that /dev/sdb is acting up.  So I tried to run a SMART command on it but here are the results.

 

root@NAS:~# smartctl -a -A /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

 

Smartctl open device: /dev/sdb failed: No such device

 

So apparently my system is saying there is no device located on sdb.  What does sdb corespond to in terms of SATA channels?  Is it SATA 2?  It is odd because my BIOS is detecting all the drives and all drives have SMART enabled on them in the bios and there are no errors there.

So unRAID is saying that /dev/sdb is acting up.  So I tried to run a SMART command on it but here are the results.

 

root@NAS:~# smartctl -a -A /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

 

Smartctl open device: /dev/sdb failed: No such device

That implies a drive that was there has gone offline.

 

So apparently my system is saying there is no device located on sdb.  What does sdb corespond to in terms of SATA channels?  Is it SATA 2?  It is odd because my BIOS is detecting all the drives and all drives have SMART enabled on them in the bios and there are no errors there.

There is no fixed relationship between the name and a particular drive - the names are assigned dynamically as the system boots.  Normally they would be assigned in a given order as they are recognised by the system, but if a drive is playing up this can change the order.  The fact that /dev/sdb is missing means that it was there when the system first booted, but has since gone offline for some reason.

 

I would assume that the drive that unRAID shows as missing is the culprit.  The problem could be that the drive is failing, or it could be something more mundane like the cabling to the drive having been disturbed.  If you can you might want to consider removing the drive and attaching it to a Windows system so that you can run the manufacturers diagnostic tools against it to check it out.

Just keeping the thread up to date.

 

Thanks for all the feedback and ideas thus far.

 

I have found the harddrive that is going offline.  Turns out that by RAID controller lists the serials upon initializing so it made determining the physical drive much easier.

 

I have moved the drive to other controllers as well as reseated the cable and tested a new cable.  All with the same results.  I am going to go with the idea it is a bad HDD so I will get a replacement and update the thread once I do.

 

Again thanks all for the help and support thus far...I love this community we have here!

Well it looks like the HDD was bad...got a new one in and the array is rebuilding...disaster adverted...odd that the drive boots fine then fails

 

Oh well time for an RMA...thanks all!

can you change the status to solved please