Hi everyone. I just replaced Amahi with UNRAID 2 days ago. Everything has been going well as I have been transfering all my data over to reiserfs from ext4. However today something happened.

 

I have been transferring all night to a 2TB WDEARS drive. After the transfer was complete I installed unmenu but when I went to start the array it would not start. Upon further investigation it appears that my 2TB drive has no file system.

 

 

 

I get this error message when running a file system check in Unmenu:

 

Checking /dev/md3 (/dev/sdc)

Sorry, no file system detected on /dev/md3

 

/dev/md3 mounted on

 

 

Fdisk -l  shows no partition.

 

I used fdisk to prior to this on another drive. There is a small chance that I ran the command on the wrong disk. The 2TB drive is sdc and the fdisk command was run on sdd (perhaps coincidence?)

 

Can anyone help me recover from this? or should I use a recovery program and try to save data to another drive? Is this a bad hard drive? I just moved to Unraid to keep my data safe LOL

 

 

UNRAID v4.7 No Parity Drive / No Cache Drive

 

Syslog is attached

 

 

syslog.txt

Need more info. See this post: http://lime-technology.com/forum/index.php?topic=9880.0

It basically says disk3 is missing.  (Double check the connections to it, it might be as simple as a loose connection or cable)

 

Since you did not install a parity drive, there is no way to simulate the contents of the missing drive.

 

Joe L.

It basically says disk3 is missing.  (Double check the connections to it, it might be as simple as a loose connection or cable)

 

Since you did not install a parity drive, there is no way to simulate the contents of the missing drive.

 

Joe L.

 

That what it says when the drive is in the server. I have now removed it. I have tried test disk and it appears that there is no partition. So upon searching for lost partition it shows up, however Testdisk says there are no files.

 

I am thinking I will cut my losses as I think the file system has too much damage to be recovered. If anyone thinks other wise please let me know.

 

 

You could try this: http://lime-technology.com/forum/index.php?topic=619.0 But it's safer to repeat the transfer.

It basically says disk3 is missing.  (Double check the connections to it, it might be as simple as a loose connection or cable)

 

Since you did not install a parity drive, there is no way to simulate the contents of the missing drive.

 

Joe L.

 

That what it says when the drive is in the server. I have now removed it. I have tried test disk and it appears that there is no partition. So upon searching for lost partition it shows up, however Testdisk says there are no files.

 

I am thinking I will cut my losses as I think the file system has too much damage to be recovered. If anyone thinks other wise please let me know.

 

 

Unless the tools you are using to examine the disk are able to recognize reiserfs partitions they will not see anything.  (They might be only looking for MS-DOS style partitions)

 

Joe L.

I have decided to just write the data off as a loss. The data was not priceless and I can always get it back in the long run.

 

Thank you for all the help

I have decided to just write the data off as a loss. The data was not priceless and I can always get it back in the long run. But now I cannot seem to replace the 2TB drive with a 1TB. When I add the new device to the array it shows the old disk name under the new one and tell me Too many wrong and/or missing disks! I have searched around the forums and net but perhaps someone can point me in the right direction. Thanks a bunch for all of you who offered help.

You need to initialize a new configuration.

 

Stop array

Log in on system console, or via telnet

type

initconfig

Respond with "Yes" (Capital "Y", lower case "es")

 

Thank you fine sir Everything is now back on track. Hopefully no more hiccups with the next 10 TB's of data. Too bad you just couldn't convert ext4 to reiserfs.