HDD and CD/DVD not accessible

I was told elsewhere in these fora that I don’t need to mount a drive which I can see on the left of Dolphin.

WHEN I try accessing it I am given the following error:

An error occured while accessing 'maxtor3240', the system
responded: org.freedesktop.Hal.Device.PermissionDeniedByPolicy:
org.freedesktop.hal.Storage.mount-fixed auth_admin_keep_always
<-- (action, result)Can anyone help?

I am the only user and the one setting-up the system (only yesterday; V11.1 and KDE)

I am also having a problem accessing the CD and DVD - they don’t even show-up in the left pane.

Can anyone help me access these? Thanks

http://i247.photobucket.com/albums/gg132/nlp239/opensuse/snapshot01.png

> I was told elsewhere in these fora that I don’t need to mount a drive
> which I can see on the left of Dolphin.

didn’t that person who answered you said he thought that was the case…

> WHEN I try accessing it I am given the following error:
>
>
> Code:
> --------------------
> An error occured while accessing ‘maxtor3240’, the system
> responded: org.freedesktop.Hal.Device.PermissionDeniedByPolicy:
> org.freedesktop.hal.Storage.mount-fixed auth_admin_keep_always
> ← (action, result)Can anyone help?
> --------------------

could be a permissions issue…that is, maybe your user does not have
permission to access that drive…

is it a Linux file system, or other? well, my GUESS is you have to
launch an instance of Dolphin as the root user, then right click on
that drive, select properties and (as root) give your user self
read/write permission (well…it depends on if you want both read and
write permission and if it is mounted for both read and write)…

there is probably a HowTo on permissions somewhere on the wiki…you
can also change ownership and permission from a command line…and you
may need to visit fstab and set it to mount both read and write…

see (in a terminal) man mount

> I am also having a problem accessing the CD and DVD - they don’t even
> show-up in the left pane.

if there is nothing in the drive there is nothing to access…

put in a disk and see what happens then…something SHOULD happen in
less than 15 to 30 seconds…if it does not, post again…

someone should have given you a few new guy reading hints…did they?

you might search the HowTos on permissions and/or look though the
forum search results for “permissions” at:
http://forums.opensuse.org/search.php?searchid=900455

and/on “access DVD” (without the quotes) at:
http://forums.opensuse.org/search.php?searchid=900405


The Real Elvis

Sorry wrong word. Should have said “Might be the case”

could be a permissions issue…that is, maybe your user does not have
permission to access that drive…

How can this possibly be if I am the one and only user loging-in as the Admin!!

is it a Linux file system, or other?

Yes, ext3

well, my GUESS is you have to
launch an instance of Dolphin as the root user, then right click on
that drive, select properties and (as root) give your user self
read/write permission (well…it depends on if you want both read and
write permission and if it is mounted for both read and write)…

The only thing available on right click is “Hide Maxtor 3027” and I get the same error message.

Any ideas?

> Any ideas?

perplexing…

sign in as a regular user, open a terminal, become root and type in
these lines (one at a time) and hit enter…then post the results back
to here

cat /proc/partitions
fdisk -l
cat /etc/fstab
df --print-type
uname -a

>> could be a permissions issue…
> How can this possibly be if I am the one and only user loging-in as
> Admin!!

are you saying you logged into KDE (or Gnome or other GUI environment)
as root?

NEVER do that, EVER…


nom de plume

First of all, thanks for replying.

What I’m saying is I am the only user therefore I have access to root.

Here’s the result of what you asked me to do

jcsullivan@linux-s3cg:~> cat /proc/partitions
major minor  #blocks  name

  8     0   10022040 sda
  8     1     771088 sda1
  8     2    5245222 sda2
  8     3    4000185 sda3
  8    16    3320352 sdb
  8    17    3317391 sdb1
jcsullivan@linux-s3cg:~> fdisk -l

Program 'fdisk' is present in package 'util-linux', which is installed on your system.

Absolute path to 'fdisk' is '/sbin/fdisk', so it might be intended to be run only by user with superuser privileges (eg. root).

bash: fdisk: command not found
jcsullivan@linux-s3cg:~> cat /etc/fstab
/dev/disk/by-id/ata-WDC_WD102AA_WD-WMA0M1945275-part1 swap                 swap      defaults              0 0
/dev/disk/by-id/ata-WDC_WD102AA_WD-WMA0M1945275-part2 /                    ext3      acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD102AA_WD-WMA0M1945275-part3 /home                ext3      acl,user_xattr        1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
jcsullivan@linux-s3cg:~> df --print-type
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/sda2     ext3     5162828   3395576   1504992  70% /
udev         tmpfs      252932       180    252752   1% /dev
/dev/sda3     ext3     3937252     90824   3646420   3% /home
jcsullivan@linux-s3cg:~> uname -a
Linux linux-s3cg 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386GNU/Linux
jcsullivan@linux-s3cg:~>

I took the fdisk command as an l not an i nor a 1 (one)

Thanks

> jcsullivan@linux-s3cg:~> fdisk -l
>
> Program ‘fdisk’ is present in package ‘util-linux’, which is installed on your system.
>
> Absolute path to ‘fdisk’ is ‘/sbin/fdisk’, so it might be intended to be run only by user with superuser privileges (eg. root).
>
> bash: fdisk: command not found
<snip>
>
> I took the fdisk command as an l not an i nor a 1 (one)

you guessed correctly, it is a lower case L…

however, you didn’t follow my previous instructions which were: “sign
in as a regular user, open a terminal, become root and type in these
lines”

i know that for several reasons, one is that a regular user can’t run
fdisk (which is why i told you to become root)…

if you do not understand how to “become root” ask. read:
http://en.opensuse.org/SDB:Login_as_root#Execute_a_command_as_root_during_a_terminal_session
*

for now, do it this way:
-type su - <that is an su, one space, and then a single dash]
-press Enter
-enter the root password when challenged [note: you will NOT be able
to see what you are typing as you enter the root password]
-type fdisk -l <that is a lower case letter L]

then, post the results back here…


nom de plume
*

It isn’t that I don’t try to follow instructions so please accept my apologies.

I am the only user on the system so does that mean I need to create a new user?

I’ve just booted the system afresh and waited for the first screen which wait for my input. That screen is a choice between Opensuse, Failsafe Opensuse and Floppy.

I chose the first and pressed enter and waited for the next input screen which in my case is a text screen with linux-s3cg login:
Entering “su -” and the password tells me “Login incorrect”.

Just to test, and very carefully I typed “root” and my password and I was allowed in with “linux-s3cg ~ #” whereupon I immediately did an “exit” (don’t get the wrong idea that’s ALL I know.

So, where does that leave me? I have no su but I do root. Do I do the fdisk command using root, at that particualr screen.

I’m really confused.
Thanks

> I’m really confused.

you are not nearly as confused as i am…why? because:

when you select OpenSUSE (that first choice) on the first boot screen,
the next thing you should see is a graphical user interface
(GUI)…you, know kinda like Windows[tm]…with buttons and a pretty
backround…like that screen shot you posted showing Dolphin…(by the
way, how did you get that screen shot, by booting using the SECOND
option “Failsafe Opensuse”)

THAT pretty GUI is what should come up when you select OpenSUSE!
since it does not, you have not quite completed the initial install…

i’ll get back to that in a moment…but first i wanna tell you that
you actually HAVE two different ‘people’ on your computer…

you have a NORMAL USER named jcsullivan who has the user permissions
needed to read and write files in jcsullivan’s /home directory…ONLY!
yes, he (you) can also launch some programs (like Firefox) but cannot
preform ‘system administrator’ duties like (for example) shut down the
firewall, or change the firewall so a cracker can come in and steal
jcsullivan’s bank password…

the ‘person’ who has the power to make system wide changes is name
root (or superuser)…

until Ubuntu (and then openSUSE) started trying to help Windows[tm]
folks transition to Linux there was always required a password for
each user (even if only one) and a DIFFERENT password for root…then,
somebody decided that was tooo complicated so they wrote the install
script to allow both the installing user (which is YOU: jcsullivan)
AND root to have the same password…so, even though there is only one
of you on the computer you have TWO jobs: one is to be user with the
name of “jcsullivan” , and the other is to be the system
administrator, with the name of “root”…

jcsullivan can wipe out ALL of his own files…just delete all of
them, and the basic operating system will still function perfectly (if
it did so before) because jcsullivan canNOT delete or change system
files or settings…

however, if you log in as root you can delete the entire contents of
the machine with little trouble…

with me so far?

ok…just to put mind at ease a little: when you got to that black
screen that just said “linux-s3cg login:” you were NOT logging into
Gnome, but rather into the basic operating system…SO it is perfectly
OKAY to become root in that non-GUI environment…

so, when you select the first opensuse option and get dumped at the
non-GUI prompt, when when it says “Login” it first wants to know the
name of the user, so type jcsullivan and press enter, then
type in your password and the “prompt” will change

from: linux-s3cg login:
to: jcsullivan@linux-s3cg:~>

showing that jcsullivan is using this terminal on the machine named
lunux-s3cg and is in his on home directory…see that “~” it is
shorthand for “home directory” and you will have signed in as YOU, a
regular, restricted access and power’s USER…

then, to “become root” you type

su -

which tells the system to Switch User [su] and without naming another
user, it is assumed that root wants to log in, and the system again
asks for “password”, and you must enter root’s password (yes, in your
case it is the same…but, someday you gonna learn how to change it
and make the two different, and very hard to guess the root password
(that keeps the bad guys out)

THEN, the prompt will change again,
from: jcsullivan@linux-s3cg:~>
to: linux-s3cg ~ #

when you see that “#” in a linux prompt you KNOW that root is signed
in, so BE CAREFUL cause you have ALL the power, to fix or destroy…

NOW, while you are signed in as root, type:

fdisk -l

press enter and send the output back to this thread…THEN, we will
try to get you a normal boot to a normal Gnome screen and get that
second hard drive sorted out for you…

while you are waiting for me (or hopefully someone else will drop in)
and continue this, do some reading about your new operating
system…you have a lot to learn…

patience…it is worth it…believe me.


nom de plume

Thank you yet again for all your help and patience.

Here’s the result of fdisk - small drives but I’m just testing the waters.

linux-s3cg:~ # fdisk -l

Disk /dev/sda: 10.2 GB, 10262568960 bytes
255 heads, 63 sectors/track, 1247 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0d2b3733

Device Boot Start End Blocks Id System
/dev/sda1 1 96 771088+ 82 Linux swap / Solaris
/dev/sda2 97 749 5245222+ 83 Linux
/dev/sda3 750 1247 4000185 83 Linux

Disk /dev/sdb: 3400 MB, 3400040448 bytes
255 heads, 63 sectors/track, 413 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0004d585

Device Boot Start End Blocks Id System
/dev/sdb1 1 413 3317391 83 Linux
linux-s3cg:~ #

And yes, so far as I can remember that screen image was using the Failsafe mode.

jc

First make sure that your system is up to date (YaST Online Update) to get all Bugfixes for hal.

If it still doesn’t work after that, then use this Workaround:

Add


<config version="0.1">
           <match action="org.freedesktop.hal.storage.mount-fixed">
             <match user="Your_Username">
               <return result="yes"/>
             </match>
           </match>
</config>

to /etc/PolicyKit/PolicyKit.conf and restart hal (not sure if necessary, but will do no harm).

Thank you for taking the time to help - yes all is up-to-date as of this morning (mine).

My question, before I actually make changes is:

  1. If this not happening to others than there must be something wrong with my system right?
  2. If I make this change, would it be permanent even if there was an update from V11.1
  3. Shouldn’t we find-out what is causing the problem to start with, since others do not seem to be facing the same issue.
  4. How do I restart hal if I needed to?

Thank you so much.

Search the internet via google for your error message to find out if others have this problem.

As I cannot foresee the future and the kind of updates which might be coming, I cannot answer this question.

See first comment, and filing a bug report in Bugzilla would be the proper way as it addresses the people who are in charge for the packages and know a lot more about debugging hal/udev/PolicyKit.

You don’t I just tested it.

> And yes, so far as I can remember that screen image was using the
> Failsafe mode.

ok, first things first…lets try to get that first option “openSUSE”
to boot to a GUI as it should (then, it will be easier to get you into
that second drive)…

so, now that you know both how to sign in as yourself and then become
root when necessary, carefully follow the instructions at
http://wiki.suselinuxsupport.de/wikka.php?wakka=HowToGetTheGuiBack

then, the next time you boot the top option you should see YOUR
(jcsullivan) Gnome environment come up…

and, by the way, that maxtor is not mounted…

are you on a laptop or desktop? is that second drive on a USB port, or
wired in to the motherboard? (i ask, because unless it was added after
installation i’m surprised that it is not automatically mounted)

> small drives but I’m just testing the waters.

understand…a smart way to start this learning curve climb
path…(lots to learn, but it will become more and more fun!)


nom de plume

This I’ve done and even tried it before. But to make sure I did it again today. Sorry, didn’t know you were going there.

Boot selection is NOT coming-up. It did before. Just the Login command prompt. At which point I followed the wiki instructions hoping I wasn’t by-passing something which is a required. I’ve cold-booted everytime to make sure and everything remains the same.
sax2 worked as did startx.

Startx takes me to the KDE and I’m OK with that until I try all this on another more modern machine even though it isn’t working ‘as it should’. What do you think?

Please note that I only went as far as startx since it worked. So please don’t get angry for NOT following ALL the steps. If I must, I will follow ALL the instructions.

and, by the way, that maxtor is not mounted…

are you on a laptop or desktop? is that second drive on a USB port, or
wired in to the motherboard? (i ask, because unless it was added after
installation i’m surprised that it is not automatically mounted)

It is a desktop and it is an internal drive. I don’t believe I added it later as I wanted to make sure OSuse did everything for me - but now I’m not sure - you’ve brought me into doubt.

So, if we’re OK with just using startx do we go ahead with Akoellh suggested way forward?

Thanks for your patience guys - it is appreciated.

> What do you think?

i think it is impossible for me to work with the limited set of
information you are giving …

like, what is the relationship of this other, more modern machine, for
instance? are you “breadboarding” on one computer and then (what?)
expecting exactly the same thing to happen on a newer machine, with a
different motherboard, different CPU, different graphic card, etc etc
etc etc…and perhaps some version of another operating system on it…

you might get a PERFECT default install on the first machine and a
BLACK SCREEN on the second (or vise versa)…

now, let me assume that one of those machines is completely devoid of
all data/files/photos etc that you wanna save, if that is the case i’d
suggest you START over on that machine by:

FIRST reading and following CAREFULLY all the great advice in this
thread: http://tinyurl.com/6jwtg9

there are NO short cuts that will save you more time than reading.

good luck, and have a lot of fun…


nom de plume

OK, so you’ve given-up on me without replying to the questions, don’t blame you I suppose.

“breadboarding”? Don’t know what the term means but wiki says it is something to do with solder-less boards. I’m sure you’ve meant it in another context.

A more modern machine simply means that if I get a more modern machine with better graphics and better drives I will have at least experienced and faced part of the learning curve.

You’ve spent a lot of time with me for which I am gratefull.

I have attempted to do just that but I am not allowed to.

All of this wasn’t meant to be easy but neither was it meant to be so difficult that I can’t get past the first base.

Any further help or ideas before I close this chapter?
THANKS

If you do it as root, you will be allowed to.

jcsullivan wrote:
> OK, so you’ve given-up on me

no, i gave up on your problem…i can’t help you more with this…and,
i can’t comment on what Akoellh is advising as he seems to be far
advanced from my knowledge of linux…or, maybe not…because, i have
NO idea about what he saying to do, or why…i THINK he answered your
how to access that drive question…but, without knowing that it is
not mounted…

i think…no, i already said: i think i’d start over by reading the
noob how to i’ve pointed you to several times…and now i add this
http://en.opensuse.org/Installation

and, do a careful NEW install…format and start over…get rid of the
crud which has been introduced…and, maybe this time (if your DVD is
good) all the system drives will be mounted…but, pay attention in
the in part were the install shows you the partitioning plan it will
use…gonna take some understanding of partitioning and mounting…

and now, i wish you luck with this note: millions are using
Linux…you can too…


MultiplePersonality

Well, I did just that. I no longer have the login screen, as can be seen below.

http://i247.photobucket.com/albums/gg132/nlp239/opensuse/Screenshot1.png

My file browser (note I’ve gone with gnome this time) is giving me all devices.

http://i247.photobucket.com/albums/gg132/nlp239/opensuse/Screenshot.png

Yet, and even though the Maxtor shows that it IS mounted I can’t access it (nor the dvd player).

http://i247.photobucket.com/albums/gg132/nlp239/opensuse/Screenshot-error.png

as it is owned by root

http://i247.photobucket.com/albums/gg132/nlp239/opensuse/Screenshot-maxtor3240Properties-1.png

Where do I go to login as root or change the access so I can write to the maxtor or play music.