DD Image mounting & fsck issues
I have an image that I need to restore to a drive. I have been told by someone who talked to the guy who created it that it's a dd image.
If I run 'file filename' I get back the following: Code:
filename: Linux rev 1.0 ext3 filesystem data (needs journal recovery) (large files) Code:
filename: Linux rev 1.0 ext3 filesystem data Code:
mount -t ext3 -o loop filename mountpoint EXT3-fs: journal inode is deleted. mount: wrong fs type, bad option, bad superblock on /dev/loop0 and etc. I have also tried to do it the following way: Code:
losetup /dev/loop0 filename If I try to run fsck on the image I get: Code:
The filesystem size (according to the superblock) is 28760366 blocks. About My System: It's a simple Athlon 1.2GHz nothing special running Fedora Core 3. It's a fresh install. The image, if you wondered came off a Dell server about two hours away from here. The goal is to image a drive and be able to do some development and whatnot without bringing the production server down... or having to drive out there, etc. I do NOT know if the dd image was of the entire drive, or just the root partition, and there really is no way of finding this out as the contractor who did it is in the midst of being fired, and he knows it. Hopefully someone has been through something similar and can help me out. Suggetions are welcome and well appreciated. I've been googling all sorts of info for the past few days when I get time, but I never seem to get any farther. If I can't get this to work, I have to start this server from scratch, which I'd like to avoid. Anyway, TIA! |
it apears the image is corrupt. I suggest that whomever creatred the iamge just tar up the files instead (though this will have to be done from a liveCd while the server is offline. but dd-ing the drive will probably also have to be done while the drive is not in use (probably the cuase of the corruption)
|
That was my fear. I think that I'll just start from scratch instead. Thanks.
|
All times are GMT -5. The time now is 06:23 AM. |