Comments on: Mounting a hard disk image including partitions using Linux

By: Steve

Steve — Fri, 13 Jan 2012 16:52:19 +0000

At least for Ubuntu Lucid, mounting offsets well beyond a 32-bit limit works flawlessly. Thanks for saving me a ton of time and copying!

I really prefer to image the whole drive so that I get boot sectors, etc and it can boot from a restored image with zero hassle. I just always thought that it came with the drawback of not being able to access the partitions in these images…

By: killermist

killermist — Mon, 09 Jan 2012 01:34:28 +0000

In the line:
#mount -o loop,ro,offset=1184440320 test2 /mnt/rabbit
Was “test2″ supposed to be “test2″, or was it supposed to be “hda.img”?
That could make a difference.

By: japzone

japzone — Tue, 03 Jan 2012 19:01:09 +0000

@16
Thanks a ton! Testdisk is infinitely better! I’ve been trying ChromeOS builds from Hexxah but since they’re built automatically sometimes they are corrupted. Using Testdisk I can quickly check to make sure that everything is ok. Testdisk even allows filebrowsing and much more! Will be using this tool from now on.

By: eSoul

eSoul — Sun, 18 Dec 2011 01:20:12 +0000

I know its an old article, but I wanted to comment that the reason your command to mount your offset partition inside your original disk image did not work could be because of a possible typo.

# parted hda.img
GNU Parted 1.7.1
Using /data/rabbit/disk_image/test2

You say the disk image is hda.img with your parameter for parted, but then parted says you are using a whole other file (/data/rabbit/disk_image/test2). When I run parted, my output is like so:

esoul@dionysus:/twoTB/eSoulBackup$ sudo parted ./taylor.dd
GNU Parted 2.3
Using /twoTB/eSoulBackup/taylor.dd

I know the version numbers are different and mine is newer, but it doesn’t have any effect on using mount to mount the partition at an offset. What really kills it for could be your mount parameters —

#mount -o loop,ro,offset=1184440320 test2 /mnt/rabbit

This fails possibly because you are not in the same folder as test2. Either cd to the directory or put the full path to the disk image and all is fine. Like so —

esoul@dionysus:/twoTB/eSoulBackup$ sudo mount -o ro,loop,offset=1573912576 taylor.dd /mnt/temp
esoul@dionysus:/twoTB/eSoulBackup$

No errors, no complaints, I can list directory contents just fine.

This is also a disk image with a NTFS file system and a “hidden” partiton before it. I have plenty of disk images sitting on my backup server and everyone of them will mount partitions inside of the device image with no problems.

By: Liam

Liam — Sun, 04 Dec 2011 23:18:25 +0000

This article just saved my life, figuratively. Thank you so much!

By: Mikko Rantalainen

Mikko Rantalainen — Sat, 01 Oct 2011 09:16:26 +0000

One word: kpartx

For example: http://perbu.livejournal.com/1157.html

By: Craig Forster

Craig Forster — Tue, 30 Aug 2011 01:52:00 +0000

Using parted to work out the partition offsets allowed me to salvage some important files from a VirtualBox disk image that I converted to a raw image as it wouldn’t boot. Thanks!

By: How to create FS image and mount

How to create FS image and mount — Wed, 13 Jul 2011 09:41:30 +0000

[...] if=/dev/your-device of=~/Desktop/your-device-image.img for a complete explanation see this post: http://www.andremiller.net/content/m…ns-using-linux with regards, [...]

By: mvsroot

mvsroot — Tue, 10 May 2011 22:32:30 +0000

An easy way to mount a partition is the follwing command:
IMG=”hda.img”;PART=1;mount -o loop,ro,offset=$(parted $IMG -s unit b print|awk ‘$1==’$PART’ {sub(/B/,”",$2);print $2}’) $IMG /mnt/rabbit
.
If you must copy this partition you can use similar subcommands to calculate the offset. You can use the bc command to calculate skip and count if the blocksize (bs) is larger as 1.

By: Create/Mount Hard Drive Image « Pyr0g

Create/Mount Hard Drive Image « Pyr0g — Mon, 07 Feb 2011 21:14:08 +0000

[...] How to create and mount a hard drive image. [...]