You are not logged in.
Pages: 1
So I'm not entirely sure what just happened. My file manager recognizes that I have a 1.5TB HD plugged in called Elements, which is true. It recognized when I unplugged it and plugged it back in. However, whenever I try to use the file manager to access the drive, it says "Unable to mount location Not Authorized". This was perplexing, so I decided to view the device properties. These are it's current basic properties:
Name: 1.5TB Hard Disk: Elements
Type: unknown type (application/octet-stream)
Size: unknown
Location: computer:///
volume: unknown
Accessed: unknown
Modified: unknown
So in essence, my system is pretending to knows what it is, but it doesn't really, and can't mount it because I'm not authorized?
Last edited by Bewmstick (2011-06-17 04:01:14)
Offline
My user account is added to all the proper groups. I'm not sure if the HD is suppose to be listed in /media/ but it's not.
Offline
how are you trying to mount the drive?
can you post your /etc/fstab file?
and have you tried mounting the volume from the command line?
Hofstadter's Law:
It always takes longer than you expect, even when you take into account Hofstadter's Law.
Offline
It sounds as if you are using a desktop environment (which one) and a graphical file manager (which one)?
Assuming those to be true, you probably are not running console kit and or Dbus correctly.
How do you start your desktop environment (gdm, kdm, slim, from a command line)?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I'm trying to mount the drive by double clicking the icon in device browser on thunar. Also by double clicking the icon on the desktop. xfce4 is my desktop environment.
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/sdb1 /media/Elemental ntfs-3g defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=1c05c7f6-ded1-40f8-9159-f58583a0035d swap swap defaults 0 0
UUID=2b48ec1e-05b1-4d1f-8295-1d49bc45e14c /boot ext2 defaults 0 1
UUID=63047adf-30a0-47ee-b994-a31d5228d4d8 / ext4 defaults 0 1
UUID=ea5312f4-5f71-4d65-9b89-fc181114696e /home ext4 defaults 0 1
I have successfully formatted and mounted the drive in /media/Elemental, so I can access it now, but it's just weird that I have to manually mount it. Not sure what I messed up, but it mounted just fine before installing SLiM. Here's my daemons section in rc.conf
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond dbus slim)
Offline
Do you have thunar-volman installed?
Offline
Make sure consolekit is installed and follow these directions for setting up Slim for PolicyKit:
Offline
anonymous_user, you've solved the issue. It was entirely because of Slim not being setup for PolicyKit. Tyvm.
Offline
Glad you solved it. Can I get you to edit your original post and add [SOLVED] to the thread title?
Thanks.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Pages: 1