hal-storage-fixed-mount
Forum rules
Before you post please read this
Before you post please read this
hal-storage-fixed-mount
hal-storage-fixed-mount-all-options refused UID 1000 unable to access the drive.
Different guy, same problem
hal-storage-fixed-mount refused uid 1000
http://www.google.com/search?hl=en&q=hal-storage-fixed-mount+refused+uid+1000&btnG=Google+Search
Happens on a LOT of distros. Am using Mint 3 with KDE. Also happens on Kubuntu 710 (but not 704) and Freespire.
Put simply, I cannot access any of my drives except the Linux boot partition (and swap of course).
Here is my /etc/fstab
So! Somewhere online, I found a “solution;†instead of trying to directly access / mount them, I should sudo mkdir /media/DISK1, DISK2, etc etc etc etc etc etc for all of my drives. Ok, done.
Then I should add this to the etc/fstab file above, at the end:
You will see USB devices listed above, BTW. This happens with my USB drives, my IDE drives, my SCSI drives...
This worked until I rebooted. When I rebooted, I had the SAME PROBLEM. /etc/fstab was Unchanged, and to make it weirder, now my drives were sdk, sdl, sdm, etc. They just moved down the alphabet. I tried changing those trailing zeros above to various combinations of 0,1 and 1,1 and 1,2 and 2,2 and 2,1 and 2,0. Nothing fixes this.
http://www.google.com/search?hl=en&q=hal-storage-fixed-mount+refused+uid+1000&btnG=Google+Search
Happens on a LOT of distros. Am using Mint 3 with KDE. Also happens on Kubuntu 710 (but not 704) and Freespire.
Put simply, I cannot access any of my drives except the Linux boot partition (and swap of course).
Here is my /etc/fstab
Code: Select all
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# Entry for /dev/sdh2 :
UUID=4d1047df-5f28-4462-b155-44843ca0ae89 / ext3
defaults,errors=remount-ro 0 1
# Entry for /dev/sdh1 :
UUID=348455A984556DFC /media/sde1 ntfs-3g defaults,locale=en_US.UTF-8 0 0
# Entry for /dev/sdh5 :
UUID=d9631695-3162-40bf-9f41-7ca88b4f9788 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0So! Somewhere online, I found a “solution;†instead of trying to directly access / mount them, I should sudo mkdir /media/DISK1, DISK2, etc etc etc etc etc etc for all of my drives. Ok, done.
Then I should add this to the etc/fstab file above, at the end:
Code: Select all
/dev/sdh1 /media/DISK0 ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdi1 /media/DISK1 ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdj1 /media/DISK2 ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sde1 /media/USB1 ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdf1 /media/USB2 ntfs-3g defaults,locale=en_US.UTF-8 0 0You will see USB devices listed above, BTW. This happens with my USB drives, my IDE drives, my SCSI drives...
This worked until I rebooted. When I rebooted, I had the SAME PROBLEM. /etc/fstab was Unchanged, and to make it weirder, now my drives were sdk, sdl, sdm, etc. They just moved down the alphabet. I tried changing those trailing zeros above to various combinations of 0,1 and 1,1 and 1,2 and 2,2 and 2,1 and 2,0. Nothing fixes this.
Found more info
This is a very widely reported bug in anything *ubuntu based.
https://bugs.launchpad.net/ubuntu/+sour ... +bug/98751
https://bugs.launchpad.net/ubuntu/+sour ... bug/115768
PolicyKit wasn't ported to Debian and as I understand things, the next major rev of Ubuntu (and therefore it's HAL) shipped anyway.
The solution is to REMOVE this:
+ if (!invoked_by_uid || strcmp(invoked_by_uid, "0"))
+ if (!privilege || strcmp (privilege, "hal-storage-removable-mount"))
+ permission_denied_privilege (privilege, invoked_by_uid);
Which file? No idea. I haven't found anyone who could tell me.
https://bugs.launchpad.net/ubuntu/+sour ... +bug/98751
https://bugs.launchpad.net/ubuntu/+sour ... bug/115768
PolicyKit wasn't ported to Debian and as I understand things, the next major rev of Ubuntu (and therefore it's HAL) shipped anyway.
The solution is to REMOVE this:
+ if (!invoked_by_uid || strcmp(invoked_by_uid, "0"))
+ if (!privilege || strcmp (privilege, "hal-storage-removable-mount"))
+ permission_denied_privilege (privilege, invoked_by_uid);
Which file? No idea. I haven't found anyone who could tell me.
Unmountable media / hal-storage-removable-mount-all-options
Full disclosure and all details on the bug as I understand it.
This is a very widely reported bug in anything *ubuntu based.
Example of bug filed: https://bugs.launchpad.net/ubuntu/+sour ... +bug/98751
The actual reason the error happens:
PolicyKit wasn't ported to Debian and as I understand things, the next major rev of Ubuntu (and therefore it's HAL) shipped anyway. Bug therefore affects ALL *ubuntu based distributions.
Solution #1 that does not work
sudo mkdir /media/hdb5, then chmod it, then sudo mount /dev/hdb5 /media/hdb5
Reason this does not work:
Because on reboot, it all goes away!
Solution #1a that also does not work
Doing the above and also editing fstab to do this for you, as in adding
/dev/hdb5 /media/DISK0 ntfs-3g defaults,locale=en_US.UTF-8 0 0
Reason this does not work:
Because on reboot, not only does it not work, but your devices have moved one letter down the alphabet -- and hdb5 doesn't show anywhere!
Solution #2 that does not work
https://help.ubuntu.com/community/Autom ... Partitions
Reason this does not work:
Has good info, but no solution is listed for this infamous error.
Solution #3 that does not work
Use some sort of graphical file manager to check some sort of box. Example: checking a "user" box on a tab in Dolphin.
Reason this does not work:
The tab doesn't appear for devices that generate this error, OR it is greyed out.
There is ONE ACTUAL solution and TWO workarounds to this problem.
Actual solution #1:
PolicyKit must be added to all *ubuntu based distributions.
Workaround #1
/dev/YOURDRIVE /media/NAMEYOUWANTTOUSE ntfs-3g users,defaults,locale=en_US.UTF-8 0 0
By adding "users" you allow anyone with any permission level to read/write to all drives.
Workaround #2
REMOVE this:
+ if (!invoked_by_uid || strcmp(invoked_by_uid, "0"))
+ if (!privilege || strcmp (privilege, "hal-storage-removable-mount"))
+ permission_denied_privilege (privilege, invoked_by_uid);
Which file? No idea. I haven't found anyone who could tell me. If I knew, I'd recompile whatever file it was and submit it to someone in authority or offer it for download on my own website.
Problem with Workaround #1. Options on three drives are greyed out, and on one, a permissions tab is missing altogether!!?! This is an animated GIF to illustrate the problem:
http://vorck.com/images/mountproblem2.gif
Problem #2, generally with Linux not specifically Mint. This kludge of assigning devices that should be recognized as valid media to directories in mnt, and then chmoding and editing fstab... This is ridiculous. I'd like to be able to see media devices as media devices... not assign them to directories.
Thoughts?
This is a very widely reported bug in anything *ubuntu based.
Example of bug filed: https://bugs.launchpad.net/ubuntu/+sour ... +bug/98751
The actual reason the error happens:
PolicyKit wasn't ported to Debian and as I understand things, the next major rev of Ubuntu (and therefore it's HAL) shipped anyway. Bug therefore affects ALL *ubuntu based distributions.
Solution #1 that does not work
sudo mkdir /media/hdb5, then chmod it, then sudo mount /dev/hdb5 /media/hdb5
Reason this does not work:
Because on reboot, it all goes away!
Solution #1a that also does not work
Doing the above and also editing fstab to do this for you, as in adding
/dev/hdb5 /media/DISK0 ntfs-3g defaults,locale=en_US.UTF-8 0 0
Reason this does not work:
Because on reboot, not only does it not work, but your devices have moved one letter down the alphabet -- and hdb5 doesn't show anywhere!
Solution #2 that does not work
https://help.ubuntu.com/community/Autom ... Partitions
Reason this does not work:
Has good info, but no solution is listed for this infamous error.
Solution #3 that does not work
Use some sort of graphical file manager to check some sort of box. Example: checking a "user" box on a tab in Dolphin.
Reason this does not work:
The tab doesn't appear for devices that generate this error, OR it is greyed out.
There is ONE ACTUAL solution and TWO workarounds to this problem.
Actual solution #1:
PolicyKit must be added to all *ubuntu based distributions.
Workaround #1
/dev/YOURDRIVE /media/NAMEYOUWANTTOUSE ntfs-3g users,defaults,locale=en_US.UTF-8 0 0
By adding "users" you allow anyone with any permission level to read/write to all drives.
Workaround #2
REMOVE this:
+ if (!invoked_by_uid || strcmp(invoked_by_uid, "0"))
+ if (!privilege || strcmp (privilege, "hal-storage-removable-mount"))
+ permission_denied_privilege (privilege, invoked_by_uid);
Which file? No idea. I haven't found anyone who could tell me. If I knew, I'd recompile whatever file it was and submit it to someone in authority or offer it for download on my own website.
Problem with Workaround #1. Options on three drives are greyed out, and on one, a permissions tab is missing altogether!!?! This is an animated GIF to illustrate the problem:
http://vorck.com/images/mountproblem2.gif
Problem #2, generally with Linux not specifically Mint. This kludge of assigning devices that should be recognized as valid media to directories in mnt, and then chmoding and editing fstab... This is ridiculous. I'd like to be able to see media devices as media devices... not assign them to directories.
Thoughts?
Hello! This behavior is from start. Right from the moment the system starts, I get the error, and devices in question greyed out.
http://vorck.com/images/mountproblem2.gif
How the heck did you find out it's KDE?! Pretty good detective work so far.
Really appreciate the help and any insight you have.
FDV
http://vorck.com/images/mountproblem2.gif
How the heck did you find out it's KDE?! Pretty good detective work so far.
Really appreciate the help and any insight you have.
FDV
Am using Mint 3 with KDE.
That's how
But there was something else too, that I can't remember now.
I searched for strcmp in /etc in my gnome but nada...
strcmp is in the text to be removed you quote
You also find it /boot in abi.... and system.map but that's not it
You can use
Code: Select all
grep -r -i -o -s -I "searchstring" /etc/*Note that the -I is a major i not a minor L
As soon as I have the time to boot into Mint KDE I'll search for it

Don't fix it if it ain't broken, don't break it if you can't fix it

