Why can't I mount /dev/sda1 and access its files anymore in Dolphin?

Hi,

I don’t know why but I can’t seem to mount /dev/sda1 (my Sabayon Linux partition) anymore in Dolphin and view its files. Yes my user account has admin privileges and I can mount my external drive fine and access its files. I can also mount /dev/sda1 from the command-line with

sudo mount /dev/sda1 /mnt

but I can’t seem to mount it and access its files in Dolphin anymore. The exact error I keep getting whenever I try to mount /dev/sda1 in Dolphin is:

An error occurred while accessing ‘/home/makerpm’, the system responded: You are not authorized to perform this operation: Not authorized to perform operation

The kdesu dialog to ask for my admin password pops up for like a blink of an eye before it disappears, after attempting to mount /dev/sda1 in Dolphin. My username is fusion809 (and yes I am sure I am logged in as this account as running echo $USER from a new Konsole tab returns fusion809), /home/makerpm is the home folder of the makerpm user I use for building Atom packages locally by following the Fedora Wiki guide on building RPMs. This error seems to have started when I ran (as root):


mount /dev/sda1 /mnt
chroot /mnt /bin/bash

and ran

equo update && equo upgrade

in the chroot to keep my Sabayon installation on /dev/sda1 up-to-date. After this I unmounted /dev/sda1 from the command-line to make it accessible to Dolphin and since then I have been experiencing this issue.

Thanks for your time,
Brenton

There’s too much here that is left for guessing.

For example, I don’t know what it means to say that your account has admin privileges.

Yes, some distros use membership of the “wheel” group for that. But opensuse doesn’t. Have you changed “polkit” settings so that some group membership gives special rights?

Also, is there an entry in “/etc/fstab” for this file system? If there is, what does it say?

I meant that the User Manager (from System Settings) says I’m an administrator, that and I have sudo privileges. Here is a screenshot to show what I mean by User Manager.
http://imgur.com/9cBfyDe.pngHere is my /etc/fstab file:


UUID=b580137e-7ecc-4af6-9a38-e64a64760147 swap swap defaults 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 / btrfs defaults 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /boot/grub2/i386-pc btrfs subvol=boot/grub2/i386-pc 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /boot/grub2/x86_64-efi btrfs subvol=boot/grub2/x86_64-efi 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /opt btrfs subvol=opt 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /srv btrfs subvol=srv 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /tmp btrfs subvol=tmp 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /usr/local btrfs subvol=usr/local 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/crash btrfs subvol=var/crash 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/lib/libvirt/images btrfs subvol=var/lib/libvirt/images 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/lib/mailman btrfs subvol=var/lib/mailman 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/lib/mariadb btrfs subvol=var/lib/mariadb 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/lib/mysql btrfs subvol=var/lib/mysql 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/lib/named btrfs subvol=var/lib/named 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/lib/pgsql btrfs subvol=var/lib/pgsql 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/log btrfs subvol=var/log 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/opt btrfs subvol=var/opt 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/spool btrfs subvol=var/spool 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /var/tmp btrfs subvol=var/tmp 0 0
UUID=0f4760e7-fd18-4a70-a398-0989a55c46c1 /.snapshots btrfs subvol=.snapshots 0 0
UUID=752942f3-8eb3-49e0-98c6-19530af17c7c /home                xfs        defaults              1 2

the way I usually determine UUIDs for my various partitions is to mount them in dolphin and then look at their /run/media/fusion809/ file path (e.g., one of my external drive partitions is at /run/media/fusion809/5fc20d24-4af4-4e5b-882b-f76dc533aca6/ so that gives me a UUID of 5fc20d24-4af4-4e5b-882b-f76dc533aca6), and I can’t do that for my internal partition (as if I could I wouldn’t be asking this question to begin with). If you have another way of determining my /dev/sda1 partition’s UUID please tell me if you need it in order to help me with this issue.

Partition UUIDs can be found in /dev/disk/by-uuid.

Yeah it has a list of UUIDs, but how do I determine which belongs to which partition?

Nvm I determined it using gparted. It gave a UUID for my /dev/sda1 drive of 81c7ac71-d58f-48f4-9cc0-c5ca1ae5e60d.

ls -l /dev/disk/by-uuid | grep sda1

Thanks returned the same result UUID=81c7ac71-d58f-48f4-9cc0-c5ca1ae5e60d for sda1

sudo blkid in a terminal will give you the id of all drives and partitions

user manager might say administrator but there are no admin accounts on openSUSE there is only one **root
**why not use polkit to do what you want
create a file

kdesu kate /etc/polkit-1/rules.d/10-udisks2.rules

paste this content and save the file

// See the polkit(8) man page for more information
// about configuring polkit.

// Allow udisks2 to mount devices without authentication
// for users in the "storage" group.
polkit.addRule(function(action, subject) {
    if ((action.id == "org.freedesktop.udisks2.filesystem-mount-system" ||
         action.id == "org.freedesktop.udisks2.filesystem-mount") &&
    subject.isInGroup("users")) {
        return polkit.Result.YES;
    }
});

I suggest you don’t use the general users group but create a new group called **storage **and adding yourself to it, now you’ll be able to mount all partitions without the need for root password, and you won’t have to mess with disk ID’s or mount points

Thanks I_A, you truly are a Wise Penguin :stuck_out_tongue: as this worked perfectly, this problem is resolved.

I do not know what you did with the directory I pointed you to, but in my place:

henk@boven:~> ls -l /dev/disk/by-uuid/
totaal 0
lrwxrwxrwx 1 root root 10 26 feb 09:38 38ccaf9f-8c5e-4533-97a8-5b5b21a42411 -> ../../sda1
lrwxrwxrwx 1 root root 10 26 feb 09:38 67aabbdc-41c8-4c4c-a965-4ff46768c4cf -> ../../sda5
lrwxrwxrwx 1 root root 10 26 feb 09:38 9865fe09-eafd-4d98-a71c-571d130d973f -> ../../sda3
lrwxrwxrwx 1 root root 10 26 feb 09:38 c041d002-125b-4ab6-a642-169c1a1f86fa -> ../../sda6
lrwxrwxrwx 1 root root 10 26 feb 09:38 e5968513-8374-4ca1-b41c-4ade10442a5d -> ../../sda2
henk@boven:~> 

they are symlinks to sda1, etc. Isn’t that what you wanted to know??

And in case you doubt what hardware is behind sda1, etc., use

ls -l /dev/disk/by-id/

In general, when we provide some hint here, a little bit of adventurous exploration by you is expected. :wink: