[SOLVED] Mounting .img file (chromiumos.img); can't mount it?? Help please?

linus72 · 11-27-2009, 07:19 PM

OK
I tried many things
hitting chromiumos.img with file gets this

Code:

root@PartedMagic:/media/hda4/root/Desktop/chromiumos# file chromiumos.img
chromiumos.img: x86 boot sector; partition 1: ID=0x83, starthead 0, startsector 1, 1945600 sectors; partition 2: ID=0x82, starthead 0, startsector 1945601, 1945600 sectors; partition 3: ID=0x83, active, starthead 63, startsector 3891201, 1945600 sectors, code offset 0x31

Note that I can mount the Ubuntu UNR.img easily with just

Code:

mount -o loop unr.img mnt

but, this doesn't work on the chromiumos.img
why not

here's unr.img's file

Code:

root@PartedMagic:/media/hdb1# file ubuntu-9.04-netbook-remix-i386.img
ubuntu-9.04-netbook-remix-i386.img: x86 boot sector, code offset 0x58, OEM-ID " mkdosfs", sectors/cluster 8, Media descriptor 0xf8, heads 64, sectors 1939136 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 1890, serial number 0x49ed21ff, label: "           "

big difference?

how can I mount the chromiumos.img??
thanks

linus72 · 11-27-2009, 07:52 PM

OK
I found this most helpful
http://panoskrt.wordpress.com/2009/0...in-image-file/

luckily kpartx is available in 9.04

However, after doing kpartx -a & -l
I get this

Code:

root@phalanx:~/Desktop/chromiumos# kpartx -a chromiumos.img
root@phalanx:~/Desktop/chromiumos# kpartx -l chromiumos.img
loop0p1 : 0 1945600 /dev/loop0 1
loop0p2 : 0 1945600 /dev/loop0 1945601
loop0p3 : 0 1945600 /dev/loop0 3891201

But, I can't mount it???

The directions say:

Code:

Checking which loop device was used to mount the partitions:

# kpartx -l /foo/bar/disk.img
loop1p1 : 0 8177022 /dev/loop1 63

The disk image has one partition and is mapped to /dev/loop1p1. You can now mount the partition:

# mount /dev/mapper/loop1p1 /mnt/img

I tried again mounting it everywhere
I made /mnt/img

it still says it needs fs type?
maybe its swap?

linus72 · 11-27-2009, 08:11 PM

OK
I've confirmed that after issuing

Code:

root@phalanx:~/Desktop/chromiumos# kpartx -a chromiumos.img
root@phalanx:~/Desktop/chromiumos# kpartx -l chromiumos.img
loop0p1 : 0 1945600 /dev/loop0 1
loop0p2 : 0 1945600 /dev/loop0 1945601
loop0p3 : 0 1945600 /dev/loop0 3891201

I can then mount partitions 1 (a empty ext2/3 partition-just a "lost&found folder) and 3

Code:

mkdir /mnt/img
mount -o loop /dev/mapper/loop0p1 /mnt/img
mkdir /mnt/img1
mount -o loop /dev/loop0p3 /mnt/img1

partition 3 holds the filesystem
it is NOT a squashfs fs, it is the filesystem extracted
as with a reg hd install (sad)

partition 2

Code:

partition 2: ID=0x82, starthead 0, startsector 1945601, 1945600 sectors;

82 is a swap partition ain't it??

why would anyone want to have a user dd a linux system
onto usb, creating 3 partitions
One of which is a No-No-for-USB swap partition??!

chromiumos.img is here; though I suggest you investigate prior to dd'ing it to USB!
http://carbon.hexxeh.net/chromiumos/

the post this thread is about is here
http://www.linuxquestions.org/questi...56#post3770956

And I'll mark this thread "semi-solved"!