linux (ubuntu) and ntfs (on seperate hard drive in same machine)

[BlkShdw88]

just wondering how to go about mounting a windows ntfs partition that is connected to the same computer on a seperate hard drive.. i tried mounting it but it just comes up witha red cross meaning i cant have access or sumthing.. i used the terminal to write.. sudo mount /dev/hda1 /mnt/winxp and it didnt work that well it just said it was mounted but i couldnt have access.. i dont think there is a ntfs driver for mounting?? i can access ntfs partitions across a network so is there any chance i can access it via smb? samba?

[horndude]

read only

[philg]

You can only use it read only as said before, your problem is probably permissions, and the ntfs partition can only be read by the user that mounted it. This can be fixed, just post the contents of /etc/fstab and I'll show you where to edit it

[BlkShdw88]

hey i cant go on linux until later on but all i want to do is be able to access my partition for reading files not for changing anything. i would like to be able to access my music and videos etc on my ntfs partition. but later i may post the /etc/fstab thing .. do u mean whats in the folder or there is a file called fstab? sorry i only just got ubuntu and im not too familiar with linux yet

[Greg]

fstab is a configuration/text file in the folder /etc. It should look something like this:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda5       none            swap    sw              0       0
/dev/hdd        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/hdc        /media/cdrom1   udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

[BlkShdw88]

sorry for late reply but im not sure what happend with my other hard drive but it wont boot now lol and it will take me a while before i reinstall linux on it or figure out what is going on (i don't urgently need linux) but i will remember what has been said here and thanks again .. if i have any troubles i will reply

[BlkShdw88]

ok ive reinstalled it and ive found the fstab file here is the contents:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hdb4 / ext3 defaults,errors=remount-ro 0 1
/dev/hdb2 /boot ext3 defaults 0 2
/dev/hda1 /media/hda1 ntfs defaults 0 0
/dev/hda5 /media/hda5 ntfs defaults 0 0
/dev/hda6 /media/hda6 ntfs defaults 0 0
/dev/hdb1 /media/hdb1 ntfs defaults 0 0
/dev/hdb5 none swap sw 0 0
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto 0 0


just so you know i found out i am able to mount the ntfs partition through Disks off the administration menu and can explore it through there but i cannot access it by just using the default file explorer thing. does this fstab file make it mounted at all times?

[philg]

Yes it does

In a terminal execute this code `ls -l /media` and `mount`. Post the output of both commands here

[BlkShdw88]

here is the output of ls -l /media command:

total 4
lrwxrwxrwx 1 root root 6 2006-01-21 21:55 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2006-01-21 21:55 cdrom0



here is the ouput of mount command:

/dev/hdb2 on / type ext3 (rw,errors=remount -ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid = 5, mode = 620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /lib/modules/2.6.12-10-386/volatile type tmpfs (rw,mode= 0755)
tmpfs on /dev type tmpfs (rw,size = 10M, mode = 0755)



what am i supposed to do to be able to mount it which file do i edit?

[philg]

The mount points don't exist for some reason, try these commands:

# mkdir /media/{hda1,hda5,hda6,hdb1}
# mount /media/hda1
# mount /media/hda5
# ...

Instead of manually mounting all the partitions after creating the mount points you could just reboot your system