hardy problem with mounting uuid partitions

Asked by ajmal_82

sorry but UUID of management in hardy creating problems.i tried to edit fstab and here is its output
cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda7
UUID=268bde23-9222-4680-86d4-ccad2705eec6 / ext2 relatime,errors=remount-ro 0 1
# /dev/sda6
UUID=921f462a-5816-4040-97ef-850e469c4687 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
#/dev/sda1 /media/UBERCITIZEN -auto vfat -ro w 0 0
#/dev/sda5 /media/SABOTAGE -auto vfat -ro w 0 0
#/dev/sda9 /media/HUMMING -auto vfat -ro w 0 0
#/dev/sda8 /media/COPPERHEAD -auto vfat -ro w 0 0

as you can see i tried auto and previously i typed -t in place of auto.but nothing works because there are new uuid system,
just got information on net how to find uuid it is using command:sudo blkid.
see o/p:
 blkid
/dev/sda1: UUID="94FA-B6F5" TYPE="vfat" LABEL="UBERCITIZEN"
/dev/sda5: LABEL="SABOTAGE" UUID="60ED-C3F5" TYPE="vfat"
/dev/sda6: TYPE="swap" UUID="921f462a-5816-4040-97ef-850e469c4687"
/dev/sda7: UUID="268bde23-9222-4680-86d4-ccad2705eec6" TYPE="ext2"
/dev/sda8: LABEL="COPPERHEAD" UUID="481C-0DE8" TYPE="vfat"
/dev/sda9: LABEL="HUMMING" UUID="481C-0EDB" TYPE="vfat"

now please suggest me what to do.i tried twice installing hardy but in both cases it doesnt auto mount fat partitions.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Pramod Dematagoda (pmdematagoda) said :
#1

You don't have to use the UUID in order to specify the drives/partitionsm but in the case of fstab, the line should look like this:-
/dev/sda1 /media/UBERCITIZEN vfat defaults 0 0

You cannot use a mount command as a line in fstab, it is slightly different. Also, if you want to check if the FAT partitions will mount correctly without restarting the PC, then execute:-
sudo mount -a
if all the FAT partitions aren't mounted with that command, then the corresponding fstab entry maybe incorrect.

Revision history for this message
ajmal_82 (ajmal-82) said :
#2

thank you,but i installed on my friends pc the same problem occured.he doesnt even have internet connection,and gparted is not installed by default so how do i know what are missing entries in fstab(local volumes that are not mounted) also if there are external drives missing in fstab.command please.i think the above solution is correct but what about this.

Revision history for this message
Pramod Dematagoda (pmdematagoda) said :
#3

Post the outputs of:-
cat /etc/mtab
and
sudo fdisk -l

If you see any partitions/drives given by fdisk that are missing in mtab, then that is what you are looking for.

Revision history for this message
ajmal_82 (ajmal-82) said :
#4

hotrod@hotrod-desktop:~/crclient$ cat /etc/mtab
/dev/sda7 / ext2 rw,relatime,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
/sys /sys sysfs rw,noexec,nosuid,nodev 0 0
varrun /var/run tmpfs rw,noexec,nosuid,nodev,mode=0755 0 0
varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
udev /dev tmpfs rw,mode=0755 0 0
devshm /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
lrm /lib/modules/2.6.24-16-generic/volatile tmpfs rw 0 0
securityfs /sys/kernel/security securityfs rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
gvfs-fuse-daemon /home/hotrod/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=hotrod 0 0
/dev/sda5 /media/SABOTAGE vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0
/dev/sda9 /media/HUMMING vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0
/dev/sda8 /media/COPPERHEAD vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0
/dev/sda1 /media/UBERCITIZEN vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0

hotrod@hotrod-desktop:~/crclient$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda7
UUID=268bde23-9222-4680-86d4-ccad2705eec6 / ext2 relatime,errors=remount-ro 0 1
# /dev/sda6
UUID=921f462a-5816-4040-97ef-850e469c4687 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
#/dev/sda1 /media/UBERCITIZEN vfat defaults 0 0
#/dev/sda5 /media/SABOTAGE vfat defaults 0 0
#/dev/sda9 /media/COPPERHEAD vfat defaults 0 0
#/dev/sda8 /media/HUMMING vfat defaults 0 0
*********
have you seen the difference it actually doesn't mount after reboot.
 i think root only can execute mount -a,so does this save permanent changes to fstab and it will mount all partitions on next boot without my changing again settings.i saved the above settings in fstab.
also how would i know that it got error or it succesfully mounted partitions after executing "mount -a".dmesg doesnt give me proper information.

Revision history for this message
Pramod Dematagoda (pmdematagoda) said :
#5

Actually if that is your fstab file then it is quite obvious as to why they aren't mounted at boot:-
#/dev/sda1 /media/UBERCITIZEN vfat defaults 0 0
#/dev/sda5 /media/SABOTAGE vfat defaults 0 0
#/dev/sda9 /media/COPPERHEAD vfat defaults 0 0
#/dev/sda8 /media/HUMMING vfat defaults 0 0
those lines above maybe the ones you are looking for but you(or something else) has deactivated them by commenting them out by adding a #. Just remove the # from beginning of the lines and see if that fixes it.

Revision history for this message
ajmal_82 (ajmal-82) said :
#6

sorry but its not solved the problem,but if u can answer this:
on my friends pc i see drives now mounting without read/write permissions,also i see in main menu>>places>>as
external drives>>winc,wind etc how to make it appear as local fat partitions not external.
also when i mounted them as winc,wind,wine etc( mount points as /media/winc).so now they dont even show the xp label i gave.how to make it display drives as drive label not 26gig drive.he has four,26 gig partitions so its confusing.
    i wonder how dapper drake mounted all partitions without intevention from user.

Revision history for this message
Pramod Dematagoda (pmdematagoda) said :
#7

If you manually mount them without using gnome-mount then that is the reason you don't see the labels, the labels are seen if you mount the drives through HAL which is through gnome-mount.

About the read/write problem, what are the fstab entries for those drives/partitions?

Revision history for this message
ajmal_82 (ajmal-82) said :
#8

/dev/sda3 /media/wind vfat umask=0000 0 0
The above line is used to mount windows d drive.,This is one of the entry in the fstab of my friends pc.and there are .i didnt understand about gnome-mount,HAL mounting.any external resource to find what is gnome-mount" type of mounting.also will this continue when ever i reinstall the hardy os.anyway to make it through HAL aka gnome-mount.

Revision history for this message
Pramod Dematagoda (pmdematagoda) said :
#9

The entry is rather strange:-
/dev/sda3 /media/wind vfat umask=0000 0 0
the umask option seems to be the problem there, just replace that with defaults and see if that fixes it.

Revision history for this message
ajmal_82 (ajmal-82) said :
#10

your going back to same thing i told u check above post:
 /dev/sda8 /media/wind vfat defaults 0 0.........doesnt mount partitions in read and write mode it mounts as read-only mode.can we chat to clarify in irc?.
umask works with that entry of umask=0000 i have both read/write permission.
defaults doesnt give me write access.also its unclear about
1)gnome-mount function your referred as HAL mounting
2)changing places>>external drives to places>>winc,wind etc(local drives with labels if possible)

Revision history for this message
Pramod Dematagoda (pmdematagoda) said :
#11

Ok, then try using this line:-
/dev/sda3 /media/wind vfat uid=1000 0 0

Can you help with this problem?

Provide an answer of your own, or ask ajmal_82 for more information if necessary.

To post a message you must log in.