so write a short article about how you did this and why using "hardware
RAID" solutions is bad, and put it on your website.
it's AT LEAST funny that your hardware raid instead of protecting -
rendered your data inaccessible.
___
freebsd-questions@fre
If anyone's interested, the last post I made about doing a bsdlabel, fsck,
mdconfig etc on the damaged disk image worked. I have recovered all my
files! Hooray!!!
Skye
--
View this message in context:
http://www.nabble.com/Recovering-partitions-from-disk-image--tp22862006p22889910.html
Sent
Warren Block wrote:
>
> Looks like scan_ffs is reporting block size. I'd take a spare computer
> with a blank disk and do a minimal FreeBSD install on it, setting the
> units to blocks in the partition screen and duplicating the values given
> by scan_ffs. Then connect your read-only image
On Fri, 3 Apr 2009, snott wrote:
Update: I figured out how to get scan_ffs to read a file by looking at the
program source (if it starts with / then it considers it a regular file to
read instead of a device) and got the following results which matches well
with the TestDisk output.
$ scan_ffs
Update: I figured out how to get scan_ffs to read a file by looking at the
program source (if it starts with / then it considers it a regular file to
read instead of a device) and got the following results which matches well
with the TestDisk output.
$ scan_ffs -s /recovery/disk0.img
ufs1 at 108
Hello FreeBSD gurus,
I recently had the pleasure of trying to recover a failed RAID1 array. It
consisted of two 120GB disks in mirrored configuration. Both drives have a
ton of bad sectors, so bad that the 3ware RAID card stopped recognizing that
there was a mirror at all. Having no other opti
