Fat32 Usb Stick

i have tried to mount a usb stick which is formatted to fat32, yet it said read-only file system. it mounted to start with but after trying to copy a file over to it, it said read-only, i was confused as i know fat32 should be compatible. so, i unmounted it (su to root, then umount /dev/sdb1). i then mounted it to a home directory, i did

mount -t vfat /dev/sdb1 /home/ross/usb_stick

this worked, but still, i got read only. i then su to root in a console again and did a manual command to copy

cp /home/file/i/want/to/copy /home/ross/usb_stick

and still, read only file system.

why on earth is this, it's fat32!!!!!!

please help. i would say im usually ok at mounting, but this has me stumped.

thanks.

seems like similar problems to your networked files: missing user rights to access mount point.
add user to
storage group

i then mounted it to a home directory, i did

mount -t vfat /dev/sdb1 /home/ross/usb_stick[/b]

as root?
then obviously root took over mount point.

adding user to relevant groups should resolve such problems (that is why these exist), even though only root has rights to mount a device. In KDE/Gnome this should be sufficient.

seems like similar problems to your networked files: missing user rights to access mount point.
add user to
storage group
as root?
then obviously root took over mount point.

adding user to relevant groups should resolve such problems (that is why these exist), even though only root has rights to mount a device. In KDE/Gnome this should be sufficient.
[/b]

ok will give this a shot tomorrow.

do i just go yast>security and users>group management and create a new group called storage, and add my user and root?

difference between network and this though, on network i can write to it at least...
this is odd though, since i have written to usb fat32 disks before without any problems :blink:

thanks,

Ross.

edit: think i also tried chmod 777 to mount point but i think that failed too, still got read only file system. i even did cp file in console (logged in as su!) and still no such luck. :huh:

storage group is default linux group
dev are created dynamically, no point of setting user rights on it.

you can create static mount point add this to fstab with owner set for specific user/group
remember though that with dynamic mount point each USB port require separate entry in fstab

storage group is default linux group
dev are created dynamically, no point of setting user rights on it.

you can create static mount point add this to fstab with owner set for specific user/group
remember though that with dynamic mount point each USB port require separate entry in fstab
[/b]

how would one go about setting this up in fstab? the only problem i can think of is that not drives i will put in wil be the same file system, so fstab may get confused...? i will take a look later at groups later, never really looked into this so will be very interesting to learn a little more - i'm always willing to learn things new which i know directly affect me

if i get some troubles i'll post back, most likely tomorrow, as that's when i'll get to the usb stick again.

thanks again broch, you have helped me on countless times already

Ross.

this is not difficult.
example:
#usb file system (required)
none on /proc/bus/usb type usbfs (rw)
#listed devices below
/dev/sdb1 /media/usb auto noauto,user,exec 0 0
/dev/sdc1 /media/usb1 auto noauto,user,exec 0 0
/dev/sdd1 /media/usb2 auto noauto,user,exec 0 0

and so on
as in the case of zip you should not try to mount whole device but only partition (so in the case of USB: sdb1, sdc1, sdd1 and so on)


check device name created for each USB port (connect device and run mount command) e.g mount

$ mount
........
/dev/sdb1 on /media/usb type vfat (rw,nosuid,nodev,noatime,flush,uid=1000,utf8,short name=lower)


the whole information listed above is generated automatically (udev rules), so that is why you don't need to specify fs

- create for each device mount point

- do not specify file system

that is all

create separate mount points for each USB port if you want to connect more than one USB device at the same time. Otherwise one USB point is enough.

hope this will help

this is not difficult.
example:
#usb file system (required)
none on /proc/bus/usb type usbfs (rw)
#listed devices below
/dev/sdb1 /media/usb auto noauto,user,exec 0 0
/dev/sdc1 /media/usb1 auto noauto,user,exec 0 0
/dev/sdd1 /media/usb2 auto noauto,user,exec 0 0

and so on
as in the case of zip you should not try to mount whole device but only partition (so in the case of USB: sdb1, sdc1, sdd1 and so on)
check device name created for each USB port (connect device and run mount command) e.g mount

$ mount
........
/dev/sdb1 on /media/usb type vfat (rw,nosuid,nodev,noatime,flush,uid=1000,utf8,short name=lower)
the whole information listed above is generated automatically (udev rules), so that is why you don't need to specify fs

- create for each device mount point

- do not specify file system

that is all

create separate mount points for each USB port if you want to connect more than one USB device at the same time. Otherwise one USB point is enough.

hope this will help
[/b]

thank you broch will let you know how things go

This is a drive by comment:
Need to be a bit careful if you mount something in fstab and then disconnect it by hand. On the next boot Suse will expect it to be connected and if it's not Suse will not boot to GUI

Passing thought

Swerdna

that is why there is "noauto" bit

device is not expected to be mounted at boot time

what about using yast partitioner tool to create a mount point? is there not a way to say noauto in there, so it doesn't expect it at boot?

also, broch, in the group there was no 'storage' group to be found :huh: there were many many others as standard, (3 of which my user was ticked for), but i could find any related to storage. hmmmm :huh:

thanks for any further advice anyone.