Toonight I upgrade to 5.0b6 from 5.0b4, I noticed a tick box on the page and excuse my ignorance but I can't remember the verbage of it, but I thought I was doing right by checking the box and after a few minutes I noticed it was clearing the drives.  At 1% I realized it was probably erasing the drives, panicked and initiated a reboot (I was working with it over SSH).  Upon rebooting, my 2 data drives showed up as unformatted.  I stopped and started the array several times and showed unformatted each time.  I SSH'd back in, and nothing showed up under the /dev folder.  I manually created a disk1 folder and tried mount -t reiserfs /dev/sdb /mnt/disk1 and received an error trying to mount.  I even went as far as downloading a live Ubuntu cd put my drive in an external USB case and tried to browse the disk and it would not mount in Ubuntu either.

 

Am I "screwed", or is there any way to salvage the data on these disks?  I'm hoping there's something that can be done.  My setup is the free basic version, with 1 - 2TB parity drive, 1 - 1TB drive and 1 - 2TB drive.

 

Thanks in advance for anyone's help.

Toonight I upgrade to 5.0b6 from 5.0b4, I noticed a tick box on the page and excuse my ignorance but I can't remember the verbage of it, but I thought I was doing right by checking the box and after a few minutes I noticed it was clearing the drives.  At 1% I realized it was probably erasing the drives, panicked and initiated a reboot (I was working with it over SSH).  Upon rebooting, my 2 data drives showed up as unformatted.  I stopped and started the array several times and showed unformatted each time.  I SSH'd back in, and nothing showed up under the /dev folder.  I manually created a disk1 folder and tried mount -t reiserfs /dev/sdb /mnt/disk1 and received an error trying to mount.  I even went as far as downloading a live Ubuntu cd put my drive in an external USB case and tried to browse the disk and it would not mount in Ubuntu either.

 

Am I "screwed", or is there any way to salvage the data on these disks?  I'm hoping there's something that can be done.  My setup is the free basic version, with 1 - 2TB parity drive, 1 - 1TB drive and 1 - 2TB drive.

 

Thanks in advance for anyone's help.

 

A syslog would be helpful.  Directions are in the troubleshooting link in my sig

I should have added, in my troubleshooting I wiped my flash drive and did a fresh install of 4.7.  The syslog I have is from 4.7.  The syslog is too long to post here. You can view it at http://iwebdirect.com/syslog.txt

 

Thanks again for your help!

You basically need to partition the disks again and then run reiserfsck on them to try and recover the data.

 

I think you could just assign only the data disks and start the array and unRAID will partition them again. Get the starting sector of the partition right for the disks so it matches the origional starting sector. Then, the disks will appear blank so run reiserfsck on them to see what files it can recover.

 

Why are you trying to run unstable beta release on a production server (ie a server with what appears to be important data)? If you had read the initial posts you'd have known that 5.0b6 has damaged drive partitions on at least 2 people.

 

Peter

You may be able to easily reconstruct the MBR records in moments and run a reiserfsck on the drives to verify if your data is there or not. It worked in my situation.

 

See this utility here: http://lime-technology.com/forum/index.php?topic=5072.msg47122#msg47122

 

 

Below is a link to a post when I was but a newbie.  In the post are precise instructions of how to answer the prompts that reiserfsck will ask when rebuilding the RFS disk.  Thought it might be helpful for anyone trying to recover from the MBR reinitialize bug.

 

Data Recovery Experience

Thanks to everyone for your help, When I get home tonight I will try the suggestions mentioned above. @lionelhutz, apparently from your ending post I'm an idiot, so I guess call it a newbie mistake.  My household is mainly Mac and I was trying out the AFP shares.  If I can recover the data or worst case start over, I will be going with 4.7 or the latest stable release from here on out.

 

I did notice this morning the message at the top of the forums about 5.0b6 clobbering data disks, this would've been nice to know just a day prior. Live and learn I guess...

I did notice this morning the message at the top of the forums about 5.0b6 clobbering data disks, this would've been nice to know just a day prior. Live and learn I guess...

This is the reason they are beta.  Unless you are an experienced linux user or have a test array it is suggested to NOT use the betas.

 

AFP is a nice feature to have, but until 5.0 is stable don't use it on a production array.

This has definitely been a hard lesson to learn. So I will only use the latest stable releases and not be so eager to use the latest offerings.

You need to at least as a minimum wait for some people to test a beta release and report on the operation. If you read about any bad issues then do not use it. In all cases, wait for user feedback and then decide yourself if you'll take the risk or not.

 

This release appears to misread the MBR on some disks and assume they are new. In your case, it sounds like unRAID started to clear them so they could be added to the array.

 

These days, it seems there is much "beta" software that never does turn into released software.

 

The 5.0B6 release (as well as other 5.0B5 etc) would have been more appropriately called alpha software.

 

I'm running 4.7b1. A bunch of people loaded it without issues so I also loaded it and did some testing and provided feedback on the results. In the end, 4.7b1 became 4.7 release. So, some beta versions do work OK.

 

I do feel that a release like this should not be on the main download page as a "NEW" and "HOT" item.

 

Peter