Hello,

 

During the monthly parity resync process (last night), the resync process worked ok for the first two hours then I started to received notifications "unRaid Failure Notification - One or more disks are disabled or invalid".  The disabled disk was disk #4.  I also stopped the array this morning after receiving the disabled disk notification.

 

First a bit of background and then my question.

 

[*]On 2/6/12 I accidentally deleted files/folders in a unraid share (disk #4).  After a bit of research on these boards, I found a discussion that explained how to recover the deleted files/folders.

However, initially I started executing the undelete/recover commands below from console with the array stopped, then realizing that the array needed to be started for the commands to be executed, I started the array and successfully issued the commands.

[*]I was able to recover the files/folders and the array (including disk#4) ran successfully until this morning when the monthly resync process started.  From 2/6/12 through 2/29/12 I was able to read and write from disk #4 with no problems.  Then I received the disabled disk message.

[*]The only resyncs have been (2/1/12) - successful and (3/1/12) - unsuccessful.

 

 

 

Questions

• Do I really have a failed disk (disk #4) or is this somehow related to the process I used to recover files on 2/6/12?  Remember on 2/6/12 I started executed commands below and stopped the array before realizing that the array needed to be running for the commands to be executed.
  
• What steps do I take next and how do I ensure I don't lose any data?
   
  

 

I've attached the syslog to this message...lots of repetitive information.  If there is any other info needed, please let me know.

 

I also am trying to run a smart report ("smartctl  -a  -d  ata  /dev/sdc") on drive #4 but am getting "Smartctl open device: /dev/sdc failed: No such device".

 

Thanks,

moose

 

stop samba  [all your shares will disappear from network]

killall smbd nmbd

 

un-mount the disk  (md1=disk1, md2=disk2, md10-disk10,  etc.  Use the correct disk for your needs. this example is for disk1)

umount /dev/md1

note the above command is umount, not unmount.

 

run reiserfsck on the disk to rebuild the file tree.  Any files that can be recovered will.  This process could take many hours for a large disk as the entire disk will need to be scanned.

reiserfsck --rebuild-tree -S /dev/md1

 

It will ask you to confirm the rebuild of the file tree. Make certain you answer Yes (three letters, Capital "Y", lower case "es")

Anything else will be considered as "no"

 

re-mount the disk  (again, use the correct "md" and "disk" for your situation)

mount /dev/md1 /mnt/disk1

 

re-start samba

/usr/sbin/smbd -D

/usr/sbin/nmbd -D

 

your deleted files (any that could be recovered) will be in a lost+found folder on the disk.

syslog-2012-03-01.zip

Please post the entire syslog. zip it if needed.

Did disk4 show up during boot?

Give details in system. Num of drives, make and model of power supply and any add on cards

 

Sent from my SGH-I727R using Tapatalk

I've added all my system details and attached the full syslog (zipped).  I didn't notice the drive had failed until after I left for work this morning, however now that I'm home I went down to the basement where the server is kept (cooler in basement) and the drive is making a clicking sound ~ once a second, so it might appear the drive does indeed have mechanical failure.

 

marcusone, disk #4 did show up during boot and I believe was good until the re-sync process started (I did not receive any automated emails indicating this drive failed until the re-sync).  I just rebooted the server and now disk #4 is showing "not installed".  Before this last reboot, I think disk #4 indicated "disabled".

 

I'm attaching the new syslog since I rebooted.

 

The drive has failed, correct?  Since there is no further protection from a drive failure and I don't have enough free space to recover protection in the array, I should turn off the unRAID server until I get a replacement drive, correct?

syslog-2012-03-01_b.zip

If making steady clicking sounds and not able to run smart or other diagnostics i would say that its dead and RMA if possible.

 

Get a new drive of same thing r larger to replace and have unraid rebuild. I agree safest to leave server off until then.

 

Sent from my SGH-I727R using Tapatalk

Clicking is usually terminal. Try to get a SMART report nonetheless. A SMART report will confirm its status.

Thank you.  I could not get a smart report.  The drive was definitely bad.  Fortunately the Seagate drive was still under warranty (5 years) and I was able to RMA it.  The replacement drive will be here next week.

 

Before sending the drive back to Seagate I tried the "freezer trick" and Darik's Boot and Nuke, however the disk wiping process only completed about 30% before the drive warmed up and started failing again (clicking sound).  Seagate's policy is that they destroy all data if they refurbish the drive for another user, so I was comfortable getting a warranty replacement drive.