Sumayya Shahzad
2010-07-02 10:47:00 UTC
Hi All,
I am facing some problems with mounting one of my NTFS partition.
Distribution being used is Finnix 93.0.
Here are the details of the problem. I typed *fdisk -l* and here is the part
of it's output related to this question of mine
.
.
/dev/sda5 2989 5600 20971520 7 HPFS/NTFS
/dev/sda6 5600 8211 20971520 7 HPFS/NTFS
/dev/sda7 8211 10822 20971520 7 HPFS/NTFS
.
.
Now, when i mounted */dev/sda6* as
ntfs-3g /dev/sda6 /home/Partition
following error poped up:
ntfs-3g: Failed to access volume '/dev/sda6': No such file or a directory
Then, the ouput of ntfs-3g --help is printed telling me how to use ntfs-3g.
Also the exit code was equal to 11.
I then tried *ntfsfix /dev/sda6* and got following output:
Failed to determine whether /dev/sda6 is mounted; No such file or directory
Mounting volume.... Error opening partition device: No such file or directory
Failed to startup volume: No such file or directory
FAILED
Attempting to correct errors...Error opening partition device: No such
file or directory
FAILED
Failed to startup volume: No such file or directoryVolume is corrupt.
You should run chkdsk
We cannot run *"chkdsk" as we cannot boot from Windows at this point of time
neither can we install Windows again.
*
I then, restarted my computer and tried to mount the partition again. Exit
code this time was equal to 0 which means that mounting went successful this
time.
But that's not the end of problem. I am having same problem again and again
when I mount a partition which does not appear after one or two restarts and
some time I also encounter a new exit code i.e. *21*
I have used ntfs-3g on Debian too but never faced such a problem.
In short, mounting a NTFS partition fails via ntfs-3g with an Exit Code=11.
On restart the drive is mounted successfully with an Exit Code=0 but some
times on restart the system returns an Exit Code=21.
Any idea what possibly may be going wrong? where exactly can be the problem?
and how to solve it?
Thanks a lot.
Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.colobox.com/pipermail/finnix/attachments/20100702/9a7a5d2d/attachment.htm>
I am facing some problems with mounting one of my NTFS partition.
Distribution being used is Finnix 93.0.
Here are the details of the problem. I typed *fdisk -l* and here is the part
of it's output related to this question of mine
.
.
/dev/sda5 2989 5600 20971520 7 HPFS/NTFS
/dev/sda6 5600 8211 20971520 7 HPFS/NTFS
/dev/sda7 8211 10822 20971520 7 HPFS/NTFS
.
.
Now, when i mounted */dev/sda6* as
ntfs-3g /dev/sda6 /home/Partition
following error poped up:
ntfs-3g: Failed to access volume '/dev/sda6': No such file or a directory
Then, the ouput of ntfs-3g --help is printed telling me how to use ntfs-3g.
Also the exit code was equal to 11.
I then tried *ntfsfix /dev/sda6* and got following output:
Failed to determine whether /dev/sda6 is mounted; No such file or directory
Mounting volume.... Error opening partition device: No such file or directory
Failed to startup volume: No such file or directory
FAILED
Attempting to correct errors...Error opening partition device: No such
file or directory
FAILED
Failed to startup volume: No such file or directoryVolume is corrupt.
You should run chkdsk
We cannot run *"chkdsk" as we cannot boot from Windows at this point of time
neither can we install Windows again.
*
I then, restarted my computer and tried to mount the partition again. Exit
code this time was equal to 0 which means that mounting went successful this
time.
But that's not the end of problem. I am having same problem again and again
when I mount a partition which does not appear after one or two restarts and
some time I also encounter a new exit code i.e. *21*
I have used ntfs-3g on Debian too but never faced such a problem.
In short, mounting a NTFS partition fails via ntfs-3g with an Exit Code=11.
On restart the drive is mounted successfully with an Exit Code=0 but some
times on restart the system returns an Exit Code=21.
Any idea what possibly may be going wrong? where exactly can be the problem?
and how to solve it?
Thanks a lot.
Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.colobox.com/pipermail/finnix/attachments/20100702/9a7a5d2d/attachment.htm>