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
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
On my FreeBSD 6 box, "sysctl kern.msgbuf" shows the same content as "dmesg"
But on FreeBSD 7, kern.msgbuf is empty.
Has something changed?
Thanks,
Skye
--
View this message in context:
http://www.nabble.com/sysctl-kern.msgbuf-changed-in-7.0--tp19679848p19679848.html
Sent from the freebsd-que
eman wrote:
>
> snott wrote:
>> Is there a maximum swap size limitation? I'm using a 64-bit arch and
>> only
>> seem to get about 32GB of usable swap out of a 250GB disk (all of
>> /dev/ad6)
>>
>> Thanks, Skye
>
> My first question is, why ar
Is there a maximum swap size limitation? I'm using a 64-bit arch and only
seem to get about 32GB of usable swap out of a 250GB disk (all of /dev/ad6)
Thanks, Skye
# uname -a
FreeBSD XX 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GE
