[opensuse] Trouble Mounting NTFS Drive Image - Loop Offset not working?
Hi Everyone, This is my first email to the support mailing list - I've been being more active on the forums, but am new to the mailing list. I ran into an issue and it was recommended to me that I give it a shot asking for advice here. The issue I am having is described in http://forums.opensuse.org/applications/408967-mounting-ntfs-drive-image-off... In a nutshell, 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? (More info with output from the way I am creating the loop device and the offset can be found in the above forum post if you would like to see the specifics.) This is a curious matter for me, and I would like to get it resolved and would much appreciate any suggestions anyone may have. Thank you for your time. Cheers, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Mar 4, 2009 at 6:40 PM,
Hi Everyone,
This is my first email to the support mailing list - I've been being more active on the forums, but am new to the mailing list. I ran into an issue and it was recommended to me that I give it a shot asking for advice here.
The issue I am having is described in http://forums.opensuse.org/applications/408967-mounting-ntfs-drive-image-off...
In a nutshell, 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?
(More info with output from the way I am creating the loop device and the offset can be found in the above forum post if you would like to see the specifics.)
This is a curious matter for me, and I would like to get it resolved and would much appreciate any suggestions anyone may have.
Thank you for your time.
Cheers, Pete
The mount command looks right. And like you I can't remember if the offset should be 63 * 512 or 64 * 512. The easy way to check is do a "od -cv /dev/loop4 | head". (Obviously use your loop device.) A ntfs partition has the word NTFS in the first sector. ie. the sector your offset should point to. Can you mount / unmount anything? I'm guessing not. Also, do you really have /etc/mtab~. I don't. It may be as simple as deleting that. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-03-04 at 18:54 -0500, Greg Freemyer wrote:
Also, do you really have /etc/mtab~. I don't. It may be as simple as deleting that.
The "~" means it is a backup file, usually created by the editor "joe". Which is strange, as mtab is an automatically created and maintained file. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmvO5YACgkQtTMYHG2NR9XTSwCeMHf3Ifk/9wdx1WxZgF2H+lTb cAgAn27bl4Vgz/bMIHivJO3fV/nJFkCO =nFra -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer wrote:
The mount command looks right. And like you I can't remember if the offset should be 63 * 512 or 64 * 512.
The easy way to check is do a "od -cv /dev/loop4 | head". (Obviously use your loop device.)
A ntfs partition has the word NTFS in the first sector. ie. the sector your offset should point to.
Can you mount / unmount anything? I'm guessing not.
Also, do you really have /etc/mtab~. I don't. It may be as simple as deleting that.
Greg
Hi Greg, Thanks for your suggestions. The od one was a good idea for sure - good to know NTFS is plainly in the first sector. I did actually delete any mtab files with rm /etc/mtab* I can mount other things okay, that is part of the strangeness of it. First, here is an example of mounting an ext3 virtual file system - which works fine. Then there is an example of the NTFS attempt (and output of the od you recommended.) Still no joy though: I have an idea - could mount be failing due to inconsistencies in the NTFS file system? I reimaged this back onto a drive and after chkdsk ran on it, the Windows system booted up and is running fine. (I'd still like to be able to get at files in this image though). Perhaps mount is failing due to this? *************************************** Ext3 Virtual File System - Mounts Okay: *************************************** Callandor:/virtual # dd if=/dev/zero of=ext3fs.img bs=1024 count=10000 10000+0 records in 10000+0 records out 10240000 bytes (10 MB) copied, 0.265593 s, 38.6 MB/s Callandor:/virtual # mkfs.ext3 ext3fs.img mke2fs 1.41.1 (01-Sep-2008) ext3fs.img is not a block special device. Proceed anyway? (y,n) y ... Callandor:/virtual # mount -o loop ext3fs.img /mnt/ Callandor:/virtual # ls /mnt/ lost+found Callandor:/virtual # touch /mnt/test Callandor:/virtual # ls /mnt lost+found test Callandor:/virtual # df -h /dev/loop0 9.5M 1.1M 7.9M 13% /mnt However, I still get the same when trying to mount to ntfs drive image Callandor:/virtual # mount -o loop,offset=32256 /virtual/80GBNotebookDrive.dd.img /mnt/image/ Interminable hang . . . *************************** NTFS Loopback Offset - no go **************************** Callandor:/virtual # losetup -o 32256 /dev/loop5 /virtual/80GBNotebookDrive.dd.img Callandor:/virtual # file -s /dev/loop5 /dev/loop5: x86 boot sector Callandor:/virtual # od -cv /dev/loop5 | head 0000000 353 R 220 N T F S \0 002 \b \0 \0 0000020 \0 \0 \0 \0 \0 370 \0 \0 ? \0 377 \0 ? \0 \0 \0 0000040 \0 \0 \0 \0 200 \0 200 \0 377 023 250 004 \0 \0 \0 \0 0000060 \0 \0 \f \0 \0 \0 \0 \0 ? 201 J \0 \0 \0 \0 \0 0000100 366 \0 \0 \0 001 \0 \0 \0 374 177 334 < 226 334 < H 0000120 \0 \0 \0 \0 372 3 300 216 320 274 \0 | 373 270 300 \a 0000140 216 330 350 026 \0 270 \0 \r 216 300 3 333 306 006 016 \0 0000160 020 350 S \0 h \0 \r h j 002 313 212 026 $ \0 264 0000200 \b 315 023 s 005 271 377 377 212 361 f 017 266 306 @ f 0000220 017 266 321 200 342 ? 367 342 206 315 300 355 006 A f 017 Callandor:/virtual # mount -t ntfs /dev/loop5 /media/disk/ Interminable hang . . . Or Callandor:/virtual # Cannot create link /etc/mtab~ Perhaps there is a stale lock file? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Mar 5, 2009 at 9:53 AM, Pete Eby
Greg Freemyer wrote:
The mount command looks right. And like you I can't remember if the offset should be 63 * 512 or 64 * 512.
The easy way to check is do a "od -cv /dev/loop4 | head". (Obviously use your loop device.)
A ntfs partition has the word NTFS in the first sector. ie. the sector your offset should point to.
Can you mount / unmount anything? I'm guessing not.
Also, do you really have /etc/mtab~. I don't. It may be as simple as deleting that.
Greg
Hi Greg,
Thanks for your suggestions. The od one was a good idea for sure - good to know NTFS is plainly in the first sector.
I did actually delete any mtab files with rm /etc/mtab*
I can mount other things okay, that is part of the strangeness of it. First, here is an example of mounting an ext3 virtual file system - which works fine. Then there is an example of the NTFS attempt (and output of the od you recommended.) Still no joy though:
I have an idea - could mount be failing due to inconsistencies in the NTFS file system? I reimaged this back onto a drive and after chkdsk ran on it, the Windows system booted up and is running fine. (I'd still like to be able to get at files in this image though). Perhaps mount is failing due to this?
*************************************** Ext3 Virtual File System - Mounts Okay: ***************************************
Callandor:/virtual # dd if=/dev/zero of=ext3fs.img bs=1024 count=10000
10000+0 records in
10000+0 records out
10240000 bytes (10 MB) copied, 0.265593 s, 38.6 MB/s
Callandor:/virtual # mkfs.ext3 ext3fs.img
mke2fs 1.41.1 (01-Sep-2008)
ext3fs.img is not a block special device.
Proceed anyway? (y,n) y ...
Callandor:/virtual # mount -o loop ext3fs.img /mnt/
Callandor:/virtual # ls /mnt/
lost+found
Callandor:/virtual # touch /mnt/test
Callandor:/virtual # ls /mnt lost+found test
Callandor:/virtual # df -h /dev/loop0 9.5M 1.1M 7.9M 13% /mnt
However, I still get the same when trying to mount to ntfs drive image
Callandor:/virtual # mount -o loop,offset=32256 /virtual/80GBNotebookDrive.dd.img /mnt/image/
Interminable hang . . .
*************************** NTFS Loopback Offset - no go ****************************
Callandor:/virtual # losetup -o 32256 /dev/loop5 /virtual/80GBNotebookDrive.dd.img Callandor:/virtual # file -s /dev/loop5 /dev/loop5: x86 boot sector Callandor:/virtual # od -cv /dev/loop5 | head 0000000 353 R 220 N T F S \0 002 \b \0 \0 0000020 \0 \0 \0 \0 \0 370 \0 \0 ? \0 377 \0 ? \0 \0 \0 0000040 \0 \0 \0 \0 200 \0 200 \0 377 023 250 004 \0 \0 \0 \0 0000060 \0 \0 \f \0 \0 \0 \0 \0 ? 201 J \0 \0 \0 \0 \0 0000100 366 \0 \0 \0 001 \0 \0 \0 374 177 334 < 226 334 < H 0000120 \0 \0 \0 \0 372 3 300 216 320 274 \0 | 373 270 300 \a 0000140 216 330 350 026 \0 270 \0 \r 216 300 3 333 306 006 016 \0 0000160 020 350 S \0 h \0 \r h j 002 313 212 026 $ \0 264 0000200 \b 315 023 s 005 271 377 377 212 361 f 017 266 306 @ f 0000220 017 266 321 200 342 ? 367 342 206 315 300 355 006 A f 017
Callandor:/virtual # mount -t ntfs /dev/loop5 /media/disk/
Interminable hang . . .
Or
Callandor:/virtual # Cannot create link /etc/mtab~ Perhaps there is a stale lock file?
Did you look at dmesg? ie. dmesg | tail -20 Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer wrote:
Did you look at dmesg?
ie. dmesg | tail -20
Greg
Yep, nothing too revelatory: sr1: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray sr 13:0:0:0: Attached scsi CD-ROM sr1 sr 13:0:0:0: Attached scsi generic sg4 type 5 usb-storage: device scan complete usb 7-2: USB disconnect, address 7 kjournald starting. Commit interval 5 seconds EXT3 FS on loop0, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on loop0, internal journal EXT3-fs: mounted filesystem with ordered data mode. (I mounted the EXT3 one twice when testing, but no entry for the NTFS one.) Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Mar 5, 2009 at 9:53 AM, Pete Eby
Greg Freemyer wrote:
The mount command looks right. And like you I can't remember if the offset should be 63 * 512 or 64 * 512.
The easy way to check is do a "od -cv /dev/loop4 | head". (Obviously use your loop device.)
A ntfs partition has the word NTFS in the first sector. ie. the sector your offset should point to.
Can you mount / unmount anything? I'm guessing not.
Also, do you really have /etc/mtab~. I don't. It may be as simple as deleting that.
Greg
Hi Greg,
Thanks for your suggestions. The od one was a good idea for sure - good to know NTFS is plainly in the first sector.
I did actually delete any mtab files with rm /etc/mtab*
I can mount other things okay, that is part of the strangeness of it. First, here is an example of mounting an ext3 virtual file system - which works fine. Then there is an example of the NTFS attempt (and output of the od you recommended.) Still no joy though:
I have an idea - could mount be failing due to inconsistencies in the NTFS file system? I reimaged this back onto a drive and after chkdsk ran on it, the Windows system booted up and is running fine. (I'd still like to be able to get at files in this image though). Perhaps mount is failing due to this?
*************************************** Ext3 Virtual File System - Mounts Okay: ***************************************
Callandor:/virtual # dd if=/dev/zero of=ext3fs.img bs=1024 count=10000
10000+0 records in
10000+0 records out
10240000 bytes (10 MB) copied, 0.265593 s, 38.6 MB/s
Callandor:/virtual # mkfs.ext3 ext3fs.img
mke2fs 1.41.1 (01-Sep-2008)
ext3fs.img is not a block special device.
Proceed anyway? (y,n) y ...
Callandor:/virtual # mount -o loop ext3fs.img /mnt/
Callandor:/virtual # ls /mnt/
lost+found
Callandor:/virtual # touch /mnt/test
Callandor:/virtual # ls /mnt lost+found test
Callandor:/virtual # df -h /dev/loop0 9.5M 1.1M 7.9M 13% /mnt
However, I still get the same when trying to mount to ntfs drive image
Callandor:/virtual # mount -o loop,offset=32256 /virtual/80GBNotebookDrive.dd.img /mnt/image/
Interminable hang . . .
*************************** NTFS Loopback Offset - no go ****************************
Callandor:/virtual # losetup -o 32256 /dev/loop5 /virtual/80GBNotebookDrive.dd.img Callandor:/virtual # file -s /dev/loop5 /dev/loop5: x86 boot sector Callandor:/virtual # od -cv /dev/loop5 | head 0000000 353 R 220 N T F S \0 002 \b \0 \0 0000020 \0 \0 \0 \0 \0 370 \0 \0 ? \0 377 \0 ? \0 \0 \0 0000040 \0 \0 \0 \0 200 \0 200 \0 377 023 250 004 \0 \0 \0 \0 0000060 \0 \0 \f \0 \0 \0 \0 \0 ? 201 J \0 \0 \0 \0 \0 0000100 366 \0 \0 \0 001 \0 \0 \0 374 177 334 < 226 334 < H 0000120 \0 \0 \0 \0 372 3 300 216 320 274 \0 | 373 270 300 \a 0000140 216 330 350 026 \0 270 \0 \r 216 300 3 333 306 006 016 \0 0000160 020 350 S \0 h \0 \r h j 002 313 212 026 $ \0 264 0000200 \b 315 023 s 005 271 377 377 212 361 f 017 266 306 @ f 0000220 017 266 321 200 342 ? 367 342 206 315 300 355 006 A f 017
Callandor:/virtual # mount -t ntfs /dev/loop5 /media/disk/
Interminable hang . . .
Or
Callandor:/virtual # Cannot create link /etc/mtab~ Perhaps there is a stale lock file?
How about this sequence (works here): == # dd if=/dev/zero of=/tmp/ntfs_fs.img bs=1024 count=10000 10000+0 records in 10000+0 records out 10240000 bytes (10 MB) copied, 0.182193 s, 56.2 MB/s # mkfs.ntfs --force /tmp/ntfs_fs.img /tmp/ntfs_fs.img is not a block device. mkntfs forced anyway. The sector size was not specified for /tmp/ntfs_fs.img and it could not be obtained automatically. It has been set to 512 bytes. The partition start sector was not specified for /tmp/ntfs_fs.img and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /tmp/ntfs_fs.img and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /tmp/ntfs_fs.img and it could not be obtained automatically. It has been set to 0. Cluster size has been automatically set to 512 bytes. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. Initializing device with zeroes: 100% - Done. Creating NTFS volume structures. mkntfs completed successfully. Have a nice day. # mount -o loop /tmp/ntfs_fs.img /mnt # mount /dev/sda5 on / type ext3 (rw,acl,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda6 on /home type ext3 (rw,acl,user_xattr) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) //10.0.1.39/forensics on /I type cifs (rw,mand) //10.0.1.44/data on /T type cifs (rw,mand) //10.0.1.42/data on /Z type cifs (rw,mand) /proc on /var/lib/ntp/proc type proc (ro) gvfs-fuse-daemon on /home/gaf/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=gaf) /dev/loop0 on /mnt type fuseblk (rw,allow_other,blksize=512) # -- If that works, try doing the mkfs.ntfs at an offset sector. (See the man page.) Then do the loopback mount to the offset. If all of that works, there must be an issue with your image. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer wrote:
--
If that works, try doing the mkfs.ntfs at an offset sector. (See the man page.)
Then do the loopback mount to the offset.
If all of that works, there must be an issue with your image.
Greg
Howdy Greg, That was a good idea - make a new ntfs image and try that. This confirms there is something else awry and it is not the image I am trying to moung as I run into the same thing here. Very odd indeed.: Callandor:/virtual # dd if=/dev/zero of=ntfs_fs.img bs=1024 count=10000 10000+0 records in 10000+0 records out 10240000 bytes (10 MB) copied, 0.0948274 s, 108 MB/s Callandor:/virtual # mkfs.ntfs --force ntfs_fs.img ntfs_fs.img is not a block device. ... Callandor:/virtual # mount -o loop ntfs_fs.img /mnt Cannot create link /etc/mtab~ Perhaps there is a stale lock file? Yet of course I can mount the Ext3 image fine, and can mount thumb drives, no problem. Now here is the kicker - I can not mount an NTFS partition for another physical drive in the server! Ah ha! So something in the upgrade from 11 to 11.1 seems to have broken this. Very strange: /dev/sdb1 * 1 10453 83963691 7 HPFS/NTFS Callandor:/virtual # mount -t ntfs-3g /dev/sdb1 /media/disk ntfs-3g-mount: failed to access mountpoint /media/disk: Transport endpoint is not connected Callandor:/virtual # mount -t ntfs /dev/sdb1 /media/disk ntfs-3g-mount: failed to access mountpoint /media/disk: Transport endpoint is not connected I will start to investigate this, but just wanted to let you know what I found. Cheers, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Mar 5, 2009 at 2:20 PM, Pete Eby
Greg Freemyer wrote:
--
If that works, try doing the mkfs.ntfs at an offset sector. (See the man page.)
Then do the loopback mount to the offset.
If all of that works, there must be an issue with your image.
Greg
Howdy Greg,
That was a good idea - make a new ntfs image and try that. This confirms there is something else awry and it is not the image I am trying to moung as I run into the same thing here. Very odd indeed.:
Callandor:/virtual # dd if=/dev/zero of=ntfs_fs.img bs=1024 count=10000
10000+0 records in
10000+0 records out
10240000 bytes (10 MB) copied, 0.0948274 s, 108 MB/s
Callandor:/virtual # mkfs.ntfs --force ntfs_fs.img
ntfs_fs.img is not a block device. ...
Callandor:/virtual # mount -o loop ntfs_fs.img /mnt
Cannot create link /etc/mtab~
Perhaps there is a stale lock file?
Yet of course I can mount the Ext3 image fine, and can mount thumb drives, no problem.
Now here is the kicker - I can not mount an NTFS partition for another physical drive in the server! Ah ha! So something in the upgrade from 11 to 11.1 seems to have broken this. Very strange:
/dev/sdb1 * 1 10453 83963691 7 HPFS/NTFS
Callandor:/virtual # mount -t ntfs-3g /dev/sdb1 /media/disk ntfs-3g-mount: failed to access mountpoint /media/disk: Transport endpoint is not connected
Callandor:/virtual # mount -t ntfs /dev/sdb1 /media/disk ntfs-3g-mount: failed to access mountpoint /media/disk: Transport endpoint is not connected
I will start to investigate this, but just wanted to let you know what I found.
Cheers, Pete
Seems like you have a specific issue with your installation because it works fine here. I also upgraded from 11.0 to 11.1, so I doubt it was a generic issue with the upgrade process. I would think about reinstalling the kernel, the mount package, the ntfs-3g package etc. The boot DVD also has a installation verify feature. I have never had it help me out, but it may worth a shot. Good luck. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Pete Eby wrote:
Callandor:/virtual # mount -o loop ntfs_fs.img /mnt
Cannot create link /etc/mtab~
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Perhaps there is a stale lock file? -- Huh?? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Pete, Something doesn't pass the smell test here. Why should anything be trying to create a link to /etc/mtab~ ?? A guess would be that on your first attempt to mount the image while you still had the stray /etc/mtab~ file present, something got set somewhere (udev maybe??) that is now looking for the mtab~ file when it should be looking for mtab. Someone more familiar with where this type of persistent stuff gets stored by mount will have to chime in here, this is where my guessing ability is exhausted. ( notwithstanding,, I would still try a 'grep -ir mtab~ /etc/udev/rules/*' and see if anything jumps out) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-03-05 at 13:58 -0600, David C. Rankin wrote:
Cannot create link /etc/mtab~
Perhaps there is a stale lock file? -- Huh?? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Pete,
Something doesn't pass the smell test here. Why should anything be trying to create a link to /etc/mtab~ ??
Yes, it can be. It can be part of a procedure to edit a file creating a backup first. You link 'file' to 'file.bck', then remove 'file' - which is like a rename. Finally, you rename (or link/delete) 'file.new' to 'file'. Which makes me think: an "ls -l /etc/mtab" would show if mtab has any linked file, which doesn't show otherwise: - -rw-r--r-- 2 root root 1823 2009-03-05 14:04 /etc/mtab this ^ number If there is a link, I would try an fsck, booting from a rescue system first. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmwOEMACgkQtTMYHG2NR9WInwCghhK5eJ5VCNcdXc1nzVKEd9yb mWgAn2/lVgLpW8eEN8hg1U8Dx4zZWGZb =5Biq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-03-05 at 14:20 -0500, Pete Eby wrote: ...
Now here is the kicker - I can not mount an NTFS partition for another physical drive in the server! Ah ha! So something in the upgrade from 11 to 11.1 seems to have broken this. Very strange:
/dev/sdb1 * 1 10453 83963691 7 HPFS/NTFS
Callandor:/virtual # mount -t ntfs-3g /dev/sdb1 /media/disk ntfs-3g-mount: failed to access mountpoint /media/disk: Transport endpoint is not connected
Weird! Did you try an fsck of the root partition? Run from a rescue CD, not from your 11.1 on HD. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmwOX8ACgkQtTMYHG2NR9WmOQCeJMvcCM9Y7k5iKm480FkHAtBj WVoAn3dL6EUiT/8GAKYSJ23EoRhPogo8 =LxKR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Thursday, 2009-03-05 at 14:20 -0500, Pete Eby wrote:
...
Now here is the kicker - I can not mount an NTFS partition for another physical drive in the server! Ah ha! So something in the upgrade from 11 to 11.1 seems to have broken this. Very strange:
/dev/sdb1 * 1 10453 83963691 7 HPFS/NTFS
Callandor:/virtual # mount -t ntfs-3g /dev/sdb1 /media/disk ntfs-3g-mount: failed to access mountpoint /media/disk: Transport endpoint is not connected
Weird!
Did you try an fsck of the root partition? Run from a rescue CD, not from your 11.1 on HD.
-- Cheers, Carlos E. R.
Hey guys, Turns out all this weirdness with mounting NTFS partitions was resolved by simply reinstalling ntfs-3g and ntfsprogs - same versions, from the same repo. Apparently, in the upgrade to 11.1 the packages got a bit messed up. After reinstalling I had no issues mounting NTFS physical drives or the NTFS drive image - all worked as expected. Weird. Thanks Carlos, Greg and David for all your input, I appreciate it. Cheers, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pete Eby wrote:
Turns out all this weirdness with mounting NTFS partitions was resolved by simply reinstalling ntfs-3g and ntfsprogs - same versions, from the same repo. Apparently, in the upgrade to 11.1 the packages got a bit messed up. After reinstalling I had no issues mounting NTFS physical drives or the NTFS drive image - all worked as expected.
Wow!
Weird.
Certainly.
Thanks Carlos, Greg and David for all your input, I appreciate it.
Welcome. Thanks for telling us what the problem was :-) - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkm5lPsACgkQU92UU+smfQVINgCdE9R6CWiDwyb15IjnxnSKqvaU jH4AoJNf/dmADraCHoBSs7ITGVeZiolv =Wn4K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-03-04 at 18:40 -0500, peby@sagonet.com wrote:
In a nutshell, 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?
(More info with output from the way I am creating the loop device and the offset can be found in the above forum post if you would like to see the specifics.)
Copying from there, you do: +++ 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? ++- The error is weird, and perhaps not related. I would try to mount a partition, and also a "normal" filesystem image. Try creating an ext3 image of about 1GiB, and try loop-mounting that one: we know /that/ one has to work, it is not related to offsets or "strange" things in ntfs. If it fails with the same error, we'll know it is not related to the offset thing or ntfs, and we can concentrate on that mtab thing.
This is a curious matter for me, and I would like to get it resolved and would much appreciate any suggestions anyone may have.
It is indeed curious. [...] Googling for that error, there are over 700 entries. One sugestion is to "rm /etc/mtab~". Another hint is to use "ntfs-3g" instead of "ntfs". Or perhaps "auto", methinks. Another post says to remove every file named like /etc/mtabSOMETHING, where the something can be "~" or ".tmp" something else. Leave only the "/etc/mtab", and try again. There are more. I leave you to investigate in google, I'm off to sleep ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmvTV0ACgkQtTMYHG2NR9XvIgCfTkPqT5EIS9C2TcuGOLvW9pP6 A/YAn3HKS4GBazwRz7uTW6UgTd2lIXTr =MyYA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
Carlos E. R. -
David C. Rankin -
Greg Freemyer -
peby＠sagonet.com -
Pete Eby