Unraid 5.06. I had a drive go bad recently. I was having write failures. SMART showed it failing reallocated Sector Ct with 635. I could still read from the drive so I copied all my files from it to another drive that had sufficient space. Once all the files were copied to the other drive, I attempted to delete the files from the defective drive but I could not. I replaced the drive with a new one after doing preclear and unraid recognized the new drive as a replacement for the old one and copied all the files to the new drive. After the rebuild, I ran parity check and had 5 errors.

 

Now, the new drive shows the same files that were on the old drive but I cannot delete them and I am getting errors as shown in the attached syslog. What do I do now to get the files removed from the drive and get back to normal?

syslog.txt

A rebuilt drive will typically have all its data just like the drive that was replaced, including any file corruption, etc.

 

You said you had copied data from the drive to others. Do you need any of the data on that disk now? What is the file system?

 

You said Unraid 5.06 so the file system is Reiser. You posted in V6 support so I wasn't sure at first.

Sorry about post in v6. I do not need any data on the new drive.

Are you sure all of the files were copied? If there was corruption, it is possible some files were lost and they might be recoverable. Maybe you should try this on the rebuilt disk:

 

Check Disk Filesystems

OK, ran reiserfsck; copy attached. Do you concur that I should run the --fix-fixable command?

reiserfsck_output.txt

OK, ran reiserfsck; copy attached. Do you concur that I should run the --fix-fixable command?

Yes

OK, ran fixable and attached report resulted. Do you concur that I now run --rebuild-tree ?

fix_fixable_report.txt

OK, ran fixable and attached report resulted. Do you concur that I now run --rebuild-tree ?

Since you already copied off everything you could I would say you've got nothing to lose and maybe something to gain.

If there's nothing worth saving on the drive, it would be a lot faster to just re-format it, start clean.

OK, finished the tree rebuild overnight and the drive now appears to be performing normally. I do have an empty lost+found file that I can't seem to delete so I may do the reformat on top of what I've done so far if I can't figure out how to get rid of it.

 

Trurl, thanks very much for your guidance!

OK, finished the tree rebuild overnight and the drive now appears to be performing normally. I do have an empty lost+found file that I can't seem to delete so I may do the reformat on top of what I've done so far if I can't figure out how to get rid of it.

How did you try and delete the lost+found file?  If you tried via the share then it would have failed because of permissions issues (as it will have been created as being owned by root).  If done from a console/telnet session where you are logged in as root I would expect it to work. 

I tried rm "lost+found" via telnet and was told the directory did not exist; do I have to specify a particular drive? If so, how do I do that?

I tried rm "lost+found" via telnet and was told the directory did not exist; do I have to specify a particular drive? If so, how do I do that?

You have to specify the path to the folder if not already at its owner.

 

Probably the best (and safest) thing to is

newperms "/mnt/user/lost+found"

which would reset the permissions so that the removal of the files can be done via the share.  That gives you a chance to check them out just in case you want to keep them.

 

When the share is empty you can go into the Shares tab in the GUI and remove the share from there which will also delete the lost+found folder.

 

Finally got the lost+found folder deleted using rm -rf /mnt/disk11/lost+found/.

 

Thanks to all for your help!!