Normally I never have a problem with mounting my non-Linux partitions, but lately I've been having a problem and I'm not sure where I'm going wrong. I have a dual boot system. This is my fstab: ------------------------------------ /dev/hda6 / reiserfs acl,user_xattr 1 1 /dev/hda7 /media/storage2 reiserfs acl,user_xattr 1 2 /dev/hda1 /windows/C ntfs ro,defaults 0 0 /dev/hda2 /windows/D vfat defaults 0 0 /dev/hda5 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/hdb1 /home auto acl 0 0 /dev/hdb2 /media/storage auto acl 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid none /subdomain subdomainfs noauto 0 0 -------------------------------------- All the mount points are created etc, and permissions on the mount points are set to 777 before mounting (I set them to 777 in my quest to figure out what's wrong). All my mounts work fine except for /dev/hda1 and /dev/hda2. - As $USER I cannot read /dev/hda1 (/windows/C) at all (only as root). - As $USER I cannot write to /dev/hda2 (/windows/D), although I do have read access. The mount points look like this after mounting (which makes sense given the behaviour I pointed out above): ------------------------ drwxrwxrwx 4 root root 96 2006-02-26 06:44 . drwxr-xr-x 25 root root 592 2006-02-25 17:58 .. dr-x------ 1 root root 4096 2006-02-25 12:00 C drwxr-xr-x 8 root root 16384 1970-01-01 01:00 D ------------------------ What I want is ReadOnly access (because it's ntfs) for all users to /dev/hda and ReadWrite access (because it's vfat) for all users to /dev/hda2. I've tried setting things up manually (editing the fstab myself)... and using the partitioner tool in YAST. The results are always the same.. no access to hda1 at all and RO access to hda2. Where am I going wrong? What can I do to fix this.. the right way? C.
On Sun, 2006-02-26 at 07:00 +0100, Clayton wrote:
Normally I never have a problem with mounting my non-Linux partitions, but lately I've been having a problem and I'm not sure where I'm going wrong.
I have a dual boot system. This is my fstab: ------------------------------------ /dev/hda6 / reiserfs acl,user_xattr 1 1 /dev/hda7 /media/storage2 reiserfs acl,user_xattr 1 2 /dev/hda1 /windows/C ntfs ro,defaults 0 0 /dev/hda2 /windows/D vfat defaults 0 0 /dev/hda5 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/hdb1 /home auto acl 0 0 /dev/hdb2 /media/storage auto acl 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid none /subdomain subdomainfs noauto 0 0 --------------------------------------
All the mount points are created etc, and permissions on the mount points are set to 777 before mounting (I set them to 777 in my quest to figure out what's wrong).
All my mounts work fine except for /dev/hda1 and /dev/hda2. - As $USER I cannot read /dev/hda1 (/windows/C) at all (only as root). - As $USER I cannot write to /dev/hda2 (/windows/D), although I do have read access.
The mount points look like this after mounting (which makes sense given the behaviour I pointed out above): ------------------------ drwxrwxrwx 4 root root 96 2006-02-26 06:44 . drwxr-xr-x 25 root root 592 2006-02-25 17:58 .. dr-x------ 1 root root 4096 2006-02-25 12:00 C drwxr-xr-x 8 root root 16384 1970-01-01 01:00 D ------------------------
What I want is ReadOnly access (because it's ntfs) for all users to /dev/hda and ReadWrite access (because it's vfat) for all users to /dev/hda2.
I've tried setting things up manually (editing the fstab myself)... and using the partitioner tool in YAST. The results are always the same.. no access to hda1 at all and RO access to hda2.
Where am I going wrong? What can I do to fix this.. the right way?
/dev/hda1 /mnt/ME vfat users,gid=users,umask=0002,iocharset=utf8 0 0 This is my entry in /etc/fstab for the fat32 partition on my main system. It allows for user read/write Mike@linux:/mnt> ls -l total 5 drwxr-xr-x 2 root root 48 2005-11-11 22:23 Dublin drwxr-xr-x 22 root root 592 2006-02-12 06:06 Linux drwxrwxr-x 13 root users 4096 1969-12-31 19:00 ME This is the attributes for for the mount points. I'm not sure of the syntax you need for automounting the ntfs as read only. The one system that I do have running ntfs and linux is a 9.3 and is out of service at the moment.
/dev/hda1 /mnt/ME vfat users,gid=users,umask=0002,iocharset=utf8 0 0
Hmmm was tied to the umask=002.... as in... I added users,gid=users and no change, but added umask=002 and it all started working. Hmmmm... I wonder why the YAST tools didn't set this up right on install? Oh well.. setting the umask gave the results I wanted. Thanks. C.
On 26/02/06, Clayton
/dev/hda1 /mnt/ME vfat users,gid=users,umask=0002,iocharset=utf8 0 0
Hmmm was tied to the umask=002.... as in... I added users,gid=users and no change, but added umask=002 and it all started working. Hmmmm... I wonder why the YAST tools didn't set this up right on install? Oh well.. setting the umask gave the results I wanted. Thanks.
C.
Clayton, you are not alone with this annoyance. Back in 9.1 I had a secondary hard drive formatted as FAT 32 and designated as mount point 'c'. It worked, read write permissions for everybody as it was meant to be a scratch disk. Then comes along 9.2, clean reinstall but it only root has read write access. Lo and behold, I get 9.3 and it all works agian as it should with no interference from me???? Huh??? Ok, so I figured that maybe there was an error somewhere in the SuSE scripts in 9.2 and that it had been put right for 9.3 So, what happens the other day when I install 10 onto another PC with a FAT32 formatted internal Zip drive? Back to 9.2 territory and only root can access it. It is my belief that it is the column that shows 'defaults' that is wrong. I shall try the lines that others have in my fstab file and see if it corrects things. -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
On Sun, 2006-02-26 at 12:00 +0100, Clayton wrote: Please leave some of the top of the message. It makes it easier to figure out if your responding to what I wrote or a quote from someone else.
/dev/hda1 /mnt/ME vfat users,gid=users,umask=0002,iocharset=utf8 0 0
Hmmm was tied to the umask=002.... as in... I added users,gid=users and no change, but added umask=002 and it all started working. Hmmmm... I wonder why the YAST tools didn't set this up right on install? Oh well.. setting the umask gave the results I wanted.
Setting it up right is a relative thing. I've never had SuSE set my ?fat based partitions as read\write outside of root. I've always had to edit fstab. Mike
Mike McMullin wrote:
On Sun, 2006-02-26 at 12:00 +0100, Clayton wrote:
Please leave some of the top of the message. It makes it easier to figure out if your responding to what I wrote or a quote from someone else.
Ha... some people hate too much quoting... others like loads of it :-) I'm a minimalist I guess <grin>
/dev/hda1 /mnt/ME vfat users,gid=users,umask=0002,iocharset=utf8 0 0 Hmmm was tied to the umask=002.... as in... I added users,gid=users and no change, but added umask=002 and it all started working. Hmmmm... I wonder why the YAST tools didn't set this up right on install? Oh well.. setting the umask gave the results I wanted.
Setting it up right is a relative thing. I've never had SuSE set my ?fat based partitions as read\write outside of root. I've always had to edit fstab.
Interesting. I had similar results as Kevan mentioned... it worked fine in 9.1, stopped working in 9.2 (I forget what I did back then to get it working) worked fine in 9.3 (no tinkering needed), worked fine in my first install of 10.0 (no tinkering.. had full rw access to a fat32 partition). Then I reinstalled 10.0 after a major drive failure... and no more fat32 rw access. To me, setting it up right is to allow rw access to partitions Linux can reliably rw to. I never pay much attention though to what is in my fstab since - at least in the last couple releases - it's always worked as expected. No matter in the long run... adding umask=002 worked. C.
participants (3)
-
Clayton
-
Kevanf1
-
Mike McMullin