[SOLVED] Image of a whole disk. Mounting one of its partitions.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Image of a whole disk. Mounting one of its partitions.
Kernel 2.6.21.5, Slackware 12.0
Hi:
I have disk.img, an image of a whole disk, comprising track 0, a FAT32 partition and an ext3 partition. Is it possible to mount one of these partitions? A command like 'mount ./disk.img /mnt -t<some_type> -o loop' will fail, because disk.img should be a filesystem and is not.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Should be doable by using mount ./disk.img /mnt -t<some_type> -o loop,offset=<some uint> where the offset uint could be found from the partition table?
Should be doable by using mount ./disk.img /mnt -t<some_type> -o loop,offset=<some uint> where the offset uint could be found from the partition table?
yes, true - but finding the correct offset is some tedious work. Of course, you could simply try multiples of the sector size (normally 512 bytes) until you get something reasonable.
But, you're right, that information is in the partition table, which is in the very first sector of the disk image. The actual starting sector for the first partition is the DWORD at offset 01C6h, for the second partition at 01D6h (see Explanation for details).
This assumes that you still use traditional partitioning; GPT is a bit more sophisticated.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.