Date: Fri, 3 Apr 2009 16:47:01 -0700 (PDT) From: snott <skye@f4.ca> To: freebsd-questions@freebsd.org Subject: Re: Recovering partitions from disk image? Message-ID: <22878294.post@talk.nabble.com> In-Reply-To: <alpine.BSF.2.00.0904031711330.28953@wonkity.com> References: <22862006.post@talk.nabble.com> <22872988.post@talk.nabble.com> <alpine.BSF.2.00.0904031711330.28953@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 media and dd to each > partition, using dd's skip option to skip over previous partition data. > OK, I can see how that would work. I don't really have a spare computer/drive to muck around with though, at least not easily. If I can work directly on the disk image that would be much better. Could I fix the bsdlabel on the disk.img and mount it with mdconfig? I noticed scan_ffs can output a bsdlabel config file. Something like: # scan_ffs -sl disk.img > disk.label # bsdlabel -w -f disk.img auto # write a fresh default label # bsdlabel -e -f disk.img # and load in scan_ffs output # mdconfig -a -t vnode -f disk.img -u 0 If that looks like it might work, should I fsck the disk image before or after mounting with mdconfig or not at all? Do I risk kernel panic without fsck? Thanks, Skye -- View this message in context: http://www.nabble.com/Recovering-partitions-from-disk-image--tp22862006p22878294.html Sent from the freebsd-questions mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22878294.post>