![]() | ||
|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
![]() |
Thread Tools |
![]() |
#1 |
Cooling Neophyte
Join Date: Oct 2007
Location: NJ
Posts: 4
|
![]()
I have a 4100 that crapped the bed... So I got this program UFS explorer it actually reads SnapOS drives.
I just had to put the drives in a Intel Computer and it actually can pull data off the drive. It's working ok, If I do the RAW file recover format I am actually able to recover files.. However it's not pulling the Directory structure because I cannot locate the Master Boot Record and the File system data.... I think I may have some settings wrong when rebuilding the array with the program. Here are all the settings Raid Mode - Raid 5 (obvously) Stripe Size- Only after I changed to 64kb could I recover files... Raid Parity Distribution - Left Symmetric (backward-dynamic) I assume this is right also since it is rebuilding the data. Parity Length (stripes) - 1 (dunno if this is right) it's a txt box to enter a number no choice. Now these settings I think what I am missing to pull the MBR and FS off the drive. Controller- Reserved Sector Information: Reserved from disk start: set to 0 it's a text box to enter a number Reserved at disk end (for spanned RAID): set to 0 it's also a text box. I'm happy to say all hope is not lost on my hosed system, I just need any and all info to help me. Worst case senario I look at each important file and rename but if I could actually find the FS and MBR it would save a lot of time with my 270 gigs worth of data. the url to the program is http://www.ufsexplorer.com/ and only costs $69 bucks... Way better than the $9000 I got quoted for Disaster recovery where they will probably do the same thing. Here is a screen shot of the program and all the settings so you can see also. ![]() |
![]() |
![]() |
![]() |
#2 |
Thermophile
Join Date: May 2006
Location: Yakima, WA
Posts: 1,282
|
![]()
This is good info to have... Keep us posted...
__________________
~ 6 x Snap 4400 (SATA Converted) 2 x Snap 4500 (SATA Converted) 1 x Snap 110 5 x Snap 410 3 x Snap 520 2 x Sanbloc S50 Drives from 250GB to 2TB (PATA, SATA, and SAS) GOS v5.2.067 All subject to change, day by day...... |
![]() |
![]() |
![]() |
#3 |
Cooling Savant
Join Date: Aug 2004
Location: UK
Posts: 909
|
![]()
Definately good if it works... Especially for Joe Bloggs...
__________________
Snap Server Help Wiki - http://wiki.procooling.com/index.php/Snap_Server Snap Server 2200 v3.4.807 2x 250GB Seagate Barracuda 7200.9 w/ UNIDFC601512M Replacement Fan "Did you really think it would be that easy??" Other NAS's 1x NSLU2 w/ 512mb Corsair Flash Voyager Running Unslung 6.8b 1x NSLU2 w/ 8Gb LaCie Carte Orange Running Debian/NSLU2 Stable 4.0r0 250GB LaCie Ethernet Disk Running Windows XP Embedded |
![]() |
![]() |
![]() |
#4 |
Cooling Neophyte
Join Date: Mar 2002
Location: Washington State
Posts: 54
|
![]()
All your getting is a raw recovery, UFS explorer is not reading anything other than file headers. And u could have used "get data back", "ontrack easy recovery", and any other utility that will do what is called a raw recovery.
There is no way that ufs explorer can actually read the snap os because the superblock magic number that ufs explorer identifies ufs file systems as is not located in the same place on the snap and is not the same. So what you are going to end up with is a recovery with no file names other than 1.jpg, 2.jpg, 3.jpg. This is ok if you know exactly which type of file you need, and if you only need a hand full or so. And if it is missing the header for a particular file, then you won't see that file recovered. Douglas Snap-tech |
![]() |
![]() |
![]() |
#5 |
Cooling Neophyte
Join Date: May 2008
Location: USA
Posts: 2
|
![]()
I have several dead snap 1100 servers (bad electronics; severe electrical storm) and was able to UFS explorer to read the drives in their and pull all the data. Once you figure out the interface it's really easy.
At first, I thought it was another tool that didn't work because it was displaying these messages that the drives were corrupted. After RTM and clicking on th partition option it found everything and was easy to use. I plugged it into a Windows XP box and it just worked. It was well worth the $70. I have read alot of messages in the forum here and many could be solved with this tool. |
![]() |
![]() |
![]() |
#6 |
Cooling Neophyte
Join Date: May 2008
Location: USA
Posts: 2
|
![]()
BTW, Thanks for the forum. It helped me.
|
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
|
|