Once agian: Problems with mounting ntfs
 

Hi

I realise that this question has been asked many time before and believe me I have read and tried the suggestions.

I am still having problems accessing ntfs partition on Slack 9.0

I trust that ntfs support is built in the kernel as I did not compile it myself. I only need read access to transfer my files.

Basic info:
Drvie 1: winxp 40gb
hda2 ntfs boots as drive C in win
hda5 fat boots as drive D in win [it is manufacturer's back up]

Drive 2: linux 120 gb


I have been able to mount partition D as
but have problems with

I have tried various methods ie:
and done
I have also tried other fstab settings ie
I am still not able to mount the partition.

I am sure I am missing something and after reading and searching all the posts here and elsewhere, I have not found out what.

Can you plz pint me in the right direction.

TIA
:)

What happens if you try it manually?
Putting the fstab aside for a second, try

[code]
mount -t ntfs /dev/hda2 /mnt/win noauto,user,users,uid=xxx
[/mount]

At least that way you should get a decent
error message ;)

Cheers,
Tink

Tnx for the help.

fstab:
/dev/hda2 /winxp ntfs noauto,users,exec,ro,umask=0222 0 0



# mount -t ntfs /dev/hda2 /mnt/winxp noauto,user,users,uid=xxx
Come up with standard mount man.

# mount -t ntfs /dev/hda2 /mnt/winxp
mount: mount point /mnt/winxp does not exist

# mount /winxp
mount: mount point /winxp does not exist

# mount /mnt/winxp
mount: can't find /mnt/winxp in etc/fstab or /etc/mtab

# mount /dev/hda2
mount: mount point /winxp does not exist

# mount -t ntfs /dev/hda2 /winxp
mount: mount point /winxp does not exist

# cfdisk /dev/hda
Pri/Log Free Space 8.23
hda5 Logical FAT16 [BACKUP] 2097.45
hda2 Boot Primary NTFS [^D] 37926.77


# ls /winxp
/bin/ls: /winxp: No such file or directory


Any ideas?
:confused:

Yes. Your mount point does not exist. Do mkdir /mnt/winxp and then try again.

Sorry my typing [copy] mistake [corrected].

It is currently:

fstab:
/dev/hda2 /winxp ntfs noauto,users,exec,ro,umask=0222 0 0


I had also tried it with /mnt/winxp and mkdir /mnt/winxp as per my first post.

:(

OK, then what's the error if it's not 'Mount point does not exist'?

The following mounts fine.
/dev/hda5 /fat-e vfat defaults,umask=000 0 0


But this does not
/dev/hda2 /winxp ntfs defaults,umask=000 0 0

Why is that? They both have the same settings.
/fat-e mounts but /winxp does not.

# mount /fat-e
already mounted

#mount /winxp
mount: mount point /winxp does not exist

I have tried dif settings as per above but not successfull yet.
I know it is a mounting problem but what is it?

:confused:

Grrrmbl. I thought you said the mount point exists? OK - apparently it does not. Have you tried mkdir /winxp and then mounting ? If it doesn't work, report the error and we'll take it from there.

Don't worry - we'll get the thing mounted (even if we have to use a shoehorn to do so).

Tnx

As per my first post. I initially had the entry as /mnt/winxp and then I created the mkdir /mnt/winxp and then tried to mount it but it did not work.

So I am not sure if the same process with /winxp and mkdir /winxp and mount /winxp would work.

How can I verify if Slack 9.0 bare.i is supporting ntfs?

Out of curiosity, hda has a weird partition set up. Could this be an element??

:confused:

ps. All the errors are mentioned in my second post in this thread.

If the problem is situated in the lack of FS support, you would get a different error. Nevertheless, to check for NTFS support, first do:

If that does not list NTFS, do

If that returns with "modprobe: Can't locate module ntfs", you don't have NTFS support.
If the modprobe works, do cat /proc/filesystems again to verify NTFS is now in there.

Also, to clear things up, what's the output from:

Before I forget, I am vey grateful for the help. :)

OK, I was posting from windos before but now I am in Slack.

Here is:
No 'ntfs' but 'nfs' ??

Next:
It simply takes me back to #

After that:
Wow ntfs is there now. :D



Finally,
I am in X and su in konsole.

Here is the complete fstab
:cry: :scratch:

Q: Would changes in fstab require reboot to be applied?

your entire problem is that you do not have a directory called winxp

you need to do (as root):

mkdir /winxp

and for your fstab the entry would be


/dev/hda2 /winxp defaults 0 0

You are right. I have messed up somewhere.

It was already mentioned in other threads and here by robartes :o

I had tried it before but I guess at the time, due to the changes to the fstab, I did not set the dir correctly or the fstab were not correct/matching at the time of changes and it did not mount.

I later removed the directories created and started all over again and that is where I ended up.


I now created mkdir /winxp and mount /winxp worked fine. I changed the fstab to auto from noauto and rebooted and it is all there and mounted.

Thank you all for the help.

It was my own mistake that caused the problem.
:newbie:

So your mount point does not exist after all! What have you been doing when you said you did a 'mkdir /winxp'? As said before, the problem is exactly what the mount command says: your mount point does not exist. Create it, and then try again.

UPDATE: OK, you've got it working now. Good. :)