Mounting NTFS Drive Image, Offset Not Working?

English Applications
1

Hello,

I have an image of an NTFS drive created with dd_rescue. The image was of the entire device, not just a partition. I am trying to mount this under Suse 11.1 using a loopback device and specifying the offset value.

However, not matter what I try, I can not seem to make this work.

When I actually go to mount it the mount command hangs interminably, or results in an error:

Callandor:~ # Cannot create link /etc/mtab~
Perhaps there is a stale lock file?

Perhaps I am missing something easy here, but it seem darn neigh impossible to get this to actually work.

I would really appreciate any suggestions anyone may have - I am about out of option.

Cheers,

Pete

Callandor:~ # fdisk -lu /virtual/80GBNotebookDrive.dd.img
You must set cylinders.
You can do this from the extra functions menu.

Disk /virtual/80GBNotebookDrive.dd.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders, total 0 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x7ec87ec8

                        Device Boot      Start         End      Blocks   Id  System

/virtual/80GBNotebookDrive.dd.img1 * 63 78124094 39062016 7 HPFS/NTFS

Callandor:~ # losetup /dev/loop4 /virtual/80GBNotebookDrive.dd.img -o 32768
Callandor:~ # file -s /dev/loop4
/dev/loop4: Hitachi SH big-endian COFF object, not stripped

Callandor:~ # losetup -o 32256 /dev/loop5 /virtual/80GBNotebookDrive.dd.img
Callandor:~ # file -s /dev/loop5
/dev/loop5: x86 boot sector

Regardless of what offset I use, I get . . .

Callandor:~ #mount -o loop,offset=32256 /virtual/80GBNotebookDrive.dd.img /mnt/image/

Callandor:~ # Cannot create link /etc/mtab~
Perhaps there is a stale lock file?

What really runs . .

Callandor:~ # ps aux | grep mount
root 5702 0.0 0.0 2552 896 pts/2 S+ 17:18 0:00 mount -o loop,offset=32256 /virtual/80GBNotebookDrive.dd.img /mnt/image/
root 5704 0.1 0.0 2596 1040 pts/2 S+ 17:18 0:00 /sbin/mount.ntfs /dev/loop0 /mnt/image/ -o rw,offset=32256
root 5706 0.0 0.0 2544 768 pts/2 S+ 17:18 0:00 /bin/mount -i -f -t fuseblk -o rw,allow_other,blksize=4096 /dev/loop0 /mnt/image
root 5708 0.0 0.0 2264 680 pts/3 S+ 17:18 0:00 grep mount

I have also tried . . .

Callandor:~ # losetup -o 32256 /dev/loop5 /virtual/80GBNotebookDrive.dd.img
Callandor:~ # file -s /dev/loop5
/dev/loop5: x86 boot sector
Callandor:~ # mount -t ntfs /dev/loop5 /mnt/image/
Cannot create link /etc/mtab~
Perhaps there is a stale lock file?

2

Heheh . . .

Yea, it is rather puzzling. .

Anyone have any suggestions?

Cheers,
Pete

3

If you don’t get a response here, try posting to the openSUSE General Mail List - Communicate - openSUSE. People there may be able to give a detailed reply.

4

Thanks for the suggestion, I’ve never used the support mailing list - that is a great idea. I just sent off a message to it!

Cheers,
Pete