Snap 2200
 

Hi

A customer has just brought us a 2200 that went wrong. they removed the drives and mounted them on windows thinking they could get the data back.

LBA 0 of both drives now contain empty Windows Partition tables. So does anyone know the start position of the Data area on these drives ?

It is configured as RAID 0 as the data is different on the drives.

Mark

Re: Snap 2200
 

You best bet would be to contact Douglas with Front Line Recovery service, 1-866-279-2985. Since the HD were in raid 0 you may be SOL. If windows did not overwrite/format the HD he may be able to do it. Since your in the UK, you may need to contact the Snap Dealer and see if they know of anyone that can recover a SnapOS.. The files system is a heavly modified XFS system. Most recovery services do not have the special custom software needed to do the recovery. Douglas use to work for Quanitum (before SnapAppliance) bousght them in the HD dept. He knows these inside out.

Good luck, to bad you were not in RAID 1 Mirror.

Re: Snap 2200
 

Thanks for the reply ..

I can work at the File system level, if I can find out where the data start is on the drives. I have found where the stripes are using large text blocks and JPG files, but the data breaks do not correspond so what I'm looking at now is if there are different data start offsets. I've still got my head buried in these disks, but if anyone can point me in the right direction it would really help me have a weekend :)

The last one I looked at was a 4xxx series with RAID 5 and managed to get all data off it. So it could be that the customer has done more than they said.

Thanks again though.

Mark

Re: Snap 2200
 

Snap changed the starting blocks on a couple of OS's. If I recall it's determined by drive size. They took the total blocks divided by 7 or 8. I know the block info is stored in the 4-5% of the HD. This is where the drives fail at. Douglas may be able to help if you can reach him.

Re: Snap 2200
 

I'm actually getting somewhere with this .. For those that are interested. I think the data partition starts with a signature UFSXImg0

So, looks like it is a UNIX (based) partition. It is at this point where the data starts to differ - up to this point the data is mainly mirrored, but with minor differences - could be intentional could be errors in the system.

I'm still working on the offsets and if I can find any obvious XFS partitions.

Mark