NTFS Mount Error

[Natalie]

I'm trying to use Knoppix (version 4.0.2 2005-09-12) to back up a friend's data.

This thread (http://www.knoppix.net/forum/viewtopic.php?t=22384&highlight=ntfs+mount) was about a similar error.

When I click on "Hard Disk [hda1]", or use the commands "sudo mount /dev/hda1 /mnt/hda1" or "sudo mount /dev/hda1 /mnt/hda1/ -t ntfs -o nls=utf8,umask=0222" in the console, I get the following error:



mount: wrong fs type, bad option, bad superblock on /dev/hda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


"dmesg | tail" gives me:


NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.



Here is the output to everything Robert asked for in the thread I mentioned above.



+ cat /etc/knoppix-version
4.0.2 2005-09-12
+ cat /proc/partitions
major minor #blocks name

3 0 80043264 hda
3 1 80027766 hda1
240 0 1942016 cloop0
+ sudo fdisk -l /dev/hda /dev/hdb /dev/hdc /dev/hdd /dev/hde /dev/hdf /dev/hdg /dev/hdh
Disk /dev/hdc doesn't contain a valid partition table

Disk /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 9963 80027766 7 HPFS/NTFS
Note: sector size is 2048 (not 512)

Disk /dev/hdc: 728 MB, 728190976 bytes
255 heads, 63 sectors/track, 22 cylinders
Units = cylinders of 16065 * 2048 = 32901120 bytes

+ cat /etc/fstab
/proc /proc proc defaults 0 0
/sys /sys sysfs noauto 0 0
/dev/pts /dev/pts devpts mode=0622 0 0
/dev/fd0 /mnt/auto/floppy auto user,noauto,exec,umask=000 0 0
/dev/cdrom /mnt/auto/cdrom auto user,noauto,exec,ro 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX
/dev/hda1 /mnt/hda1 ntfs noauto,users,exec,ro,umask=000,uid=knoppix,gid=kno ppix 0 0
+ ls --color=auto -la /mnt/
total 3
drwxr-xr-x 4 root root 1024 Dec 13 17:58 .
drwxr-xr-x 9 root root 1024 Dec 13 12:57 ..
drwxr-xr-x 2 root root 0 Dec 13 17:58 auto
lrwxrwxrwx 1 root root 15 Dec 13 17:58 cdrom -> /mnt/auto/cdrom
lrwxrwxrwx 1 root root 16 Dec 13 17:58 cdrom1 -> /mnt/auto/cdrom1
lrwxrwxrwx 1 root root 16 Dec 13 17:58 floppy -> /mnt/auto/floppy
drwxr-xr-x 2 root root 1024 Dec 13 17:58 hda1
+ mount
/dev/root on / type ext2 (rw)
/ramdisk on /ramdisk type tmpfs (rw,size=402200k)
/UNIONFS on /UNIONFS type unionfs (rw,dirs=/ramdisk=rw:/KNOPPIX=ro,delete=whiteout)
/dev/hdc on /cdrom type iso9660 (ro)
/dev/cloop on /KNOPPIX type iso9660 (ro)
/UNIONFS/dev/pts on /UNIONFS/dev/pts type devpts (rw)
/proc/bus/usb on /proc/bus/usb type usbfs (rw,devmode=0666)
automount(pid2276) on /mnt/auto type autofs (rw,fd=4,pgrp=2276,minproto=2,maxproto=4)
+ df -Hl
Filesystem Size Used Avail Use% Mounted on
/dev/root 2.6M 14k 2.6M 1% /
/ramdisk 412M 5.6M 407M 2% /ramdisk
/UNIONFS 2.5G 2.0G 407M 84% /UNIONFS
/dev/hdc 729M 729M 0 100% /cdrom
/dev/cloop 2.0G 2.0G 0 100% /KNOPPIX
+ sudo mkdir /mnt/hda1
mkdir: cannot create directory `/mnt/hda1': File exists
+ sudo mount /dev/hda1 /mnt/hda1
mount: wrong fs type, bad option, bad superblock on /dev/hda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

+ dmesg
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.
hdb: No disk in drive
cdrom: open failed.
hdb: No disk in drive
cdrom: open failed.
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=6291519, sector=6291519
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 6291519
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Device read failed.
NTFS-fs error (device hda1): ntfs_read_inode_mount(): Failed. Marking inode as bad.
NTFS-fs error (device hda1): ntfs_fill_super(): Failed to load essential metadata.


Obviously, this is a Windows partition. We can't boot to it: Disk read error. Replace system disk? Abort, Retry, Fail?

Or whatever the error message is that you get when you try to boot with a non-bootable floppy in. There's not floppy in the floppy drive.

Any ideas? I may not be able to reply right away, as I won't have constant access to the troubled computer, but I'll do my best.

Thanks,
Natalie

[foamrotreturns]

I'm sorry to say, but those errors seem to indicate a completely crashed hard disk or utterly corrupted filesystem.

[jjmac]

Howdy,


Why does fdisk say the sector size for your hda1 partition is "2048". Thats 4X !!!. Something is wrong there.

I'd back your /etc/fstab and then rewrite the entry for hda1, stripping it down to a bare minimum. And then have a look at what the fdisk/cfdisk output is. You may find cfdisk a bit clearer to work with too.

Something simple like,,




/dev/hda1 /mnt/hda1 ntfs noauto,ro 0 0



to start with.

Those extra bits, such as ...



+ ls --color=auto -la /mnt/


seem to be a bit weird to me. I've never seen them before, and they aren't in "man mount" as legal options.

Have you tried to write to your ntfs partition on a previous occasion. Be warned, you can screw up a ntfs that way. Write support is dodgy due to the prorietry lock down on ntfs internals by MS.

What does ...

cfdisk /dev/hda

and ...

cfdisk -Pt /dev/hda

have to say on that.

Please give more details about what you have actually done, in the lead up to this. Have you mounted it successfully before, or is this the very first attempt etc.


Just found the other thread you mentioned ... where you say at the very start ...

>>
I currently running Knoppix from a CD to recover some files from my hd. I usaly uses Windows, but it wont start up, and I need to backup some of my files.
>>

Which suggests that something happened before hand !

Can you describe what you were doing around that time, before you tried the Knoppix boot ?


It is possible to pass options to "fdisk" to force a "Head/Sector/Cylinder" geometry. And from there rewrite the table. But as i haven't actual had call to do that, it would be better to get an opinion on that from someone who has. It is described in the "man fdisk" man page though.

In the mean time though, just to backup your existing mbr/table in case any further damage is done i would suggest the following.

Take a good floppy ...




]# dd if=/dev/zero of=/dev/fd0 bs=1024 count=1440


That will zero out your floppy, then do ...




]# dd if=/dev/hda of=/dev/fd0 bs=512 count=1



That will put your existing mbr/table onto the floppy, as it currently is. And do take care to get the switches/parameters the right way round !


jm