Help not sure where to go here..using unraid 4.7 final

 

My friends unraid server i setup was working fine then he lost a disk 4 and when i got the new disk i ran a preclear on it then added it to the array and formatted and rebuilt the array. it finished rebuilding this morning and now there is no data on the drive but before the rebuild i could see data on disk 4. attached is the syslog...

 

 

thanks

James

syslog_after_Rebuild.zip

The cache drive is having problems: disk0: [8,0] (sda) WDC WD20EARS-00M WD-WMAZA1453803 size: 1953514552

 

What was the problem with disk4?

The cache drive is having problems: disk0: [8,0] (sda) WDC WD20EARS-00M WD-WMAZA1453803 size: 1953514552

 

What was the problem with disk4?

 

are you saying that the parity drive is bad too? i believe that is my disk 0.

 

disk 4 died and would not spin up.

 

thanks

James

It appears the parity drive had some errors during the rebuild. I would try running the reiserfsck checks on the disk4 and specified in the wiki. Make sure you use the right device, md4.

 

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

 

Peter

 

It appears the parity drive had some errors during the rebuild. I would try running the reiserfsck checks on the disk4 and specified in the wiki. Make sure you use the right device, md4.

 

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

 

Peter

 

 

i just ran the reiserfsck and below is the resluts, does this mean i am out of luck? how can this happen?

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

###########

reiserfsck --check started at Sun Apr 10 17:55:37 2011

###########

Replaying journal: Done.

Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed

Checking internal tree.. finished

Comparing bitmaps..finished

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 1

        Internal nodes 0

        Directories 5

        Other files 1

        Data block pointers 0 (0 of them are zero)

        Safe links 0

###########

reiserfsck finished at Sun Apr 10 17:59:02 2011

###########

root@Tower:~#

 

thanks

James

OK, how did you add it to the array? You should not have had to format it. unRAID should have said something along the lines of disk4 being replaced and then you had to check a box before starting the array. You should have never been required to format the disk during this procedure.

 

Peter

OK, how did you add it to the array? You should not have had to format it. unRAID should have said something along the lines of disk4 being replaced and then you had to check a box before starting the array. You should have never been required to format the disk during this procedure.

 

Peter

 

after the original disk failed i unassigned it from the array disks then physically removed it and rma'd it out. once the replacement came in i installed it to the same physical location then ran the preclear. once that was done i added it to the devices and the unraid showed that there was a unformatted drive. i selected the format checkmark and proceeded onward. the unraid formatted the drive and proceeded to rebuild the array automatically. and that is where i am now, before the rebuild i could navigate to the disk4 and see all the data and access it normally.

 

thanks

James

The parity drive appears to be giving problems and he's got a mess of files problems on the cache and data disks. He's getting a bunch of disk full errors and duplicate file errors.

 

I don't know what happened with the rebuild or what to suggest. I think there is an option like scan whole partition for reiserfsck to try and recover missing/deleted files. The syslog says the rebuild was kicked off. After that, it gets lost in a bunch of file errors and duplicate files and parity disk errors so it's hard to know what happened exactly.

 

Peter

 

When you unassigned the disk, did you restore or initconfig the array? That might have been a fatal extra step since it told the array to recompute parity as if the bad disk didn't exist. Then you lost the ability to rebuild it.

This is also why when you added the new disk, it just formatted it as if it were a fresh disk new to the array.

 

I think the correct way would have been to just remove the bad disk and replace it with the new disk and start the array which would have rebuilt the contents of the old disk onto the new one.

 

Hopefully I'm wrong and you can recover your data another way.

 

 

OK, how did you add it to the array? You should not have had to format it. unRAID should have said something along the lines of disk4 being replaced and then you had to check a box before starting the array. You should have never been required to format the disk during this procedure.

 

Peter

 

after the original disk failed i unassigned it from the array disks then physically removed it and rma'd it out. once the replacement came in i installed it to the same physical location then ran the preclear. once that was done i added it to the devices and the unraid showed that there was a unformatted drive. i selected the format checkmark and proceeded onward. the unraid formatted the drive and proceeded to rebuild the array automatically. and that is where i am now, before the rebuild i could navigate to the disk4 and see all the data and access it normally.

 

thanks

James

This thread describes how to recover files: http://lime-technology.com/forum/index.php?topic=619.0

If you actually did what you said above I believe you DID NOT rebuild correctly.

 

You used the format button to format the replacement drive. This is not how it is supposed to be done.

 

Did you by chance read the text beside the "Start" and "Format" buttons?  What you would have found is that you needed to add the new drive, assign it on the devices page, go back to the main page and START the array.  A data rebuild would have started at that point.