[SOLVED] Error mounting: mount exited with exit code 13

[pavan_85]

Hi all,
I have a dual boot windows xp and ubuntu linux(9.10) on my PC.
When i am trying to load windows xp from GRUB, it is showing my safemode windows options.
but when i tried it with all those options, the systems is getting started allover again.

Linux has no problems loading. So i tried to look through the NTFS file systems of windows xp. but all i was getting is this.

"Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details."

Can u suggest me how to rectify this problem.

Thanks,
Pavan

[devils casper]

Post the output of fdisk -l command here.

sudo fdisk -l

* Its small L in fdisk -l.

[D-cat]

also:

Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important!

If you can't get into safe mode with command prompt, try booting from the CD into the recovery console.

[bugrit]

I have a problem that looks very similar to pavan_85's:

Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read vcn 0x0: Input/output error
Failed to mount '/dev/sdb1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

I followed your request to "fdisk -l" with the following results:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x037d037d

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2040 16382488+ 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 2040 7152 41065920 7 HPFS/NTFS
Partition 2 does not end on cylinder boundary.
/dev/sda3 7153 19457 98839882 5 Extended
/dev/sda5 7153 7407 2048256 82 Linux swap / Solaris
/dev/sda6 7408 7434 216846 83 Linux
/dev/sda7 7435 9987 20506941 83 Linux
/dev/sda8 9988 19457 76067743+ 83 Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa4c6a4c6

Device Boot Start End Blocks Id System
/dev/sdb1 1 60801 488384001 7 HPFS/NTFS

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
16 heads, 63 sectors/track, 969021 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xcdb28f24

Device Boot Start End Blocks Id System
/dev/sdc1 1 20318 10240240+ 7 HPFS/NTFS
/dev/sdc2 20319 28668 4208400 7 HPFS/NTFS
/dev/sdc3 28669 498842 236967696 7 HPFS/NTFS
/dev/sdc4 498843 969018 236968704 7 HPFS/NTFS

Disk /dev/sdd: 500.1 GB, 500107862016 bytes
16 heads, 63 sectors/track, 969021 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x66986698

Device Boot Start End Blocks Id System
/dev/sdd1 1 969018 488385040+ 7 HPFS/NTFS

It might be worth mentioning that the three 500GiB drives are all WD SATA units and that sdc and sdd were, for a while, configured as a (nVidia software) RAID 0 pair under windoze. After I changed my mind about using RAID, I had no problems using the drives as separate units under windoze. All I did was disable RAID in the BIOS and then reformat the drives individually. However, after I switched to Linux, I couldn't get the two drives to cohabit in Ubuntu, until I used dmraid to clear the drives' metadata. I doubt that any of that has anything to do with sdb's current problems but I feel a bit uneasy about it.

I can't run "chkdsk D: /f " because windoze refuses to boot when sdb is connected and that also applies to Safe Mode. XP gets as far as letting me log on and then it hangs forever, with no sign of life. I tried hot-plugging the drive after start up but windoze would have none of it and promptly rebooted the machine.

In Ubuntu, I have commented out fstab's entry for sdb because it was slowing down boot while the system tried to mount sdb, before failing and offering the option to ignore/proceed or try to fix things manually. On that last point, I have tried swapping around the power and data connectors on my drives but the problem always follows the same physical unit.

Advice, anyone?

Edit:
I forgot to mention that sdb was pretty full - only 14GiB free - when it went on the blink. Isn't that always the way, though!

[pavan_85]

here is my fdisk -l command result:

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd48fd48f

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2611 20972826 7 HPFS/NTFS
/dev/sda2 2861 9728 55167210 f W95 Ext'd (LBA)
/dev/sda3 2612 2860 2000092+ 82 Linux swap / Solaris
/dev/sda5 2861 5101 18000801 83 Linux
/dev/sda6 5102 7833 21944758+ 7 HPFS/NTFS
/dev/sda7 7834 9728 15221556 7 HPFS/NTFS


Further, i have one doubt: if i perform chdsk /f on recovery console, will i have any problem with ubuntu???? like will it work normally or i have to perform some grub re-installation kind of thing????

[bugrit]

I have tried ntfsfix, with the following unsuccessful results:

bugrit@lucid:~$ sudo ntfsfix /dev/sdb1
Mounting volume... Failed to read vcn 0x0: Input/output error.
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Failed to read vcn 0x0: Input/output error.
Remount failed: Input/output error.

I'm beginning to wonder whether I should be looking at some form of data recovery. What Linux or other tools do people recommend for recovering data from "troubled" NTFS partitions?

[hatebreed]

do you have any norton tools? I've found that they work very well and can get into them from dos via 98 disk or freedos.

[hatebreed]

this is a tool for windows that you might want to check out. Freeware Data Recovery and yes it is free.

[bugrit]

do you have any norton tools? I've found that they work very well and can get into them from dos via 98 disk or freedos.

I haven't used Norton for many years and I'm afraid that I have no low-level tools available at the moment. All my rarely-used kind of stuff was on the inaccessible drive and it's why I was rather hoping that there would be some Linux software that could do the job.

Edit:
Our posts crossed but thank you for the link. I'll let you know how I get on.

Another edit:
Unfortunately, their NTFS Partition tool is designed for XP and it requires that boot and the faulty drive are both mounted before it can do its thing. Unlike Ubuntu, XP refuses to boot whenever my faulty drive is connected.

[D-cat]

Well, do you have enough space on a good drive to absorb the data from the fritzed out one? Linux does have tools like dd_rescue (if the drive has physical bad sectors) or photorec, which will recover common data file types from a damaged partition, but both require that you place the disk image or recovered files (respectively) in a location on a different drive.