hard drive mounting problem in Hardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I am having problems mounting my external hard drive correctly, there are several issues:
1. If I don't have an entry in fstab the external mounts with no problem (in terms of permissions) but it creates a new folder in /media every time. The order is /media/disk then I reboot and the next time it mounts to /media/disk-1 then /media/disk-2 etc...The old folders are left in /media so after 10 restarts I effectively have 18 empty folders (two partitions on external, one booting to /media/BACKUP then it goes to /media/BACKUP_ then /media/BACKUP__ etc...then the disk partition). Also, the empty folders have big red X's on them which I assume means something with permissions.
2. I have tried several fstab entries:
a. /dev/sdb6 /media/disk vfat utf8,umask=
When I go to places and click the 243 gig partition I get a "permission denied" which from my understanding comes from the umask=007
b. /dev/sdb6 /media/disk vfat defaults,umask=0 0 0
Same thing, in places there is my 250 GB media but when I click on it it comes up with an error saying "Cannout mount volume. You are not privileged to mount this volume."
c./dev/sdb6 /media/disk vfat defaults,umask=000 0 0
This is by far the weirdest one of them all. I have that twice but the second entry is /dev/sdb5 /media/BACKUP vfat defaults,umask=000 0 0
The BACKUP (second entry) is fine, on boot it mounts and I have privileges to read and write to the partition.
The disk partition does not mount on boot. When I go to places and click the 243 GB Media it fails to mount and complains about privileges. The two entries are identical other than dev and mount point. I can mount in terminal with sudo mount command but before Hardy install I had no problem having the drive mount on boot with full privileges.
Thanks for the hard work!
I can confirm this. Every time I reboot a new direcory is created on /media. I think this is a very bad regression. Please fix this before release hardy