Mageia forum

HI all,

I have an issue with an external USB harddrive (1TB in size). Mageia3 (64bit) detects it, but when I open my Dolphin, I get the message "could not enter folder /run/media/.../825a68d4-aa21-4e17-a52b-2e017e6a1839". The contents of the harddrive are not displayed. The harddrive did work under Ubuntu, and is detected under Windows also.

Anyone know what the cause and the solution could be?

Many thanks, in advance!

Is the HDD encrypted ?

Please post the output of in a console(whilst hdd pluged in and switched on)

Code: Select all: lsusb

and

Code: Select all: cat /proc/mounts

Does seem to be seeing it if it has a mount point added.
however its handy to follow the messages log when you plug something in that's causing problems.

To do that in a root console type

Code: Select all: su -

enter root password
then type

Code: Select all: journalctl -f

When you fist plug it in you should see something happening.

post output that's generated, will give me and others incite too

Pete.

Hiya,

The harddrive is not encrypted. To my knowledge, so I suppose not.

Command results:

bash: lsusb: command not found

cat /proc/mounts

rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=3036732k,nr_inodes=759183,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
/dev/sda1 / ext4 rw,noatime,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
tmpfs /tmp tmpfs rw 0 0
/dev/sda6 /home ext4 rw,noatime,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0

-- Logs begin at Sat, 2013-08-03 00:03:51 CEST. --
Oct 23 21:08:16 localhost userhelper[22684]: running '/usr/sbin/urpmi.update Tainted 32bit Backport...XX'
Oct 23 21:15:48 localhost dhclient[1745]: DHCPREQUEST on wlan0 to 192.168.0.1 port 67
Oct 23 21:15:48 localhost dhclient[1745]: DHCPACK from 192.168.0.1
Oct 23 21:15:48 localhost NET[23000]: /sbin/dhclient-script : updated /etc/resolv.conf
Oct 23 21:15:48 localhost dhclient[1745]: bound to 192.168.0.233 -- renewal in 1400 seconds.
Oct 23 21:19:37 localhost kcheckpass[23151]: pam_tcb(kscreensaver:auth): Authentication passed for ...500)
Oct 23 21:21:56 localhost su[23284]: pam_tcb(su:auth): Authentication passed for root from XX(uid=500)
Oct 23 21:21:56 localhost su[23284]: (to root) XX on /dev/pts/1
Oct 23 21:21:56 localhost su[23284]: pam_tcb(su:session): Session opened for root by XX(uid=500)

External harddrive doesn't appear in the log from journalctl. Did you run journalctl as root, and did you plug the drive only after journalctl -f was running?

I ran it as root, but the harddrive was already plugged in.

When logged in as root and plugging in the HD after, I get this:

Oct 23 21:21:56 localhost su[23284]: pam_tcb(su:auth): Authentication passed for root from XX(uid=500)
Oct 23 21:21:56 localhost su[23284]: (to root) XX on /dev/pts/1
Oct 23 21:21:56 localhost su[23284]: pam_tcb(su:session): Session opened for root by XX(uid=500)
Oct 23 21:39:08 localhost dhclient[1745]: DHCPACK from 192.168.0.1
Oct 23 21:39:08 localhost NET[24077]: /sbin/dhclient-script : updated /etc/resolv.conf
Oct 23 21:39:08 localhost dhclient[1745]: bound to 192.168.0.233 -- renewal in 1547 seconds.
Oct 23 21:45:34 localhost su[24385]: pam_tcb(su:auth): Authentication passed for root from XX(uid=500)
Oct 23 21:45:34 localhost su[24385]: (to root) erik on /dev/pts/2
Oct 23 21:45:34 localhost su[24385]: pam_tcb(su:session): Session opened for root by XX(uid=500)
Oct 23 21:46:06 localhost kernel: usb 2-3: new high-speed USB device number 3 using xhci_hcd
Oct 23 21:46:06 localhost kernel: usb 2-3: New USB device found, idVendor=059f, idProduct=102a
Oct 23 21:46:06 localhost kernel: usb 2-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
Oct 23 21:46:06 localhost kernel: usb 2-3: Product: LaCie Device
Oct 23 21:46:06 localhost kernel: usb 2-3: Manufacturer: LaCie
Oct 23 21:46:06 localhost kernel: usb 2-3: SerialNumber: 92DB4FFFFFFF
Oct 23 21:46:06 localhost mtp-probe[24462]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000...2-3"
Oct 23 21:46:06 localhost mtp-probe[24462]: bus: 2, device: 3 was not an MTP device
Oct 23 21:46:06 localhost kernel: Initializing USB Mass Storage driver...
Oct 23 21:46:06 localhost kernel: scsi6 : usb-storage 2-3:1.0
Oct 23 21:46:06 localhost kernel: usbcore: registered new interface driver usb-storage
Oct 23 21:46:06 localhost kernel: USB Mass Storage support registered.
Oct 23 21:46:07 localhost kernel: scsi 6:0:0:0: Direct-Access ST310005 28AS P...2 CCS
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] Write Protect is off
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] Mode Sense: 28 00 00 00
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] No Caching mode page present
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] No Caching mode page present
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Oct 23 21:46:07 localhost kernel: sdb: sdb1
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] No Caching mode page present
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Oct 23 21:46:07 localhost kernel: sd 6:0:0:0: [sdb] Attached SCSI disk

Looks much better. Can you do an

Code: Select all: fdisk -l /dev/sdb

as root now that it's attached?

This yields:

Disk /dev/sdb: 7971 MB, 7971016704 bytes, 1946049 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x20202020

Device Boot Start End Blocks Id System
/dev/sdb1 63 1946047 7783940 b W95 FAT32

Do "ls -l" to check the owner and properties of the disk. Perhaps your user does not have access to it.

Personally I often run into these kind of issues since I use user "id" number for my disk rights instead of a user name. Then if I was clumsy enough not to use the same user ID for my user in a new installation or another distro I cannot access the disk!

Can you read the disk as root in a terminal? That is the easy way to check.

zeebra wrote:Do "ls -l" to check the owner and properties of the disk. Perhaps your user does not have access to it.

As it's a FAT32 partition it has no unix style permissions.

When mounted the mount point and all directories and files under it are given temporary read/write permissions of whomever mounted it.
These permissions are not and can not be written to the disc.

The only time I would expect to see this problem is if user A mounted the disc then user B tried to access it.

Ken-Bergen wrote:
zeebra wrote:Do "ls -l" to check the owner and properties of the disk. Perhaps your user does not have access to it.
As it's a FAT32 partition it has no unix style permissions.

When mounted the mount point and all directories and files under it are given temporary read/write permissions of whomever mounted it.
These permissions are not and can not be written to the disc.

The only time I would expect to see this problem is if user A mounted the disc then user B tried to access it.

The folder you mount it in does have Unix read/write permissions. I have had the same problem with Fat32 as well. Just because the run folder didn't have the correct user. But that might be my own fault as I have myself managed these disks to get them to only be accessed by the user ID.

Still worth checking though... Perhaps something is wrong.

In any case I would do in terminal as root user "export $(dbus-session)" then "dolphin" to run dolphin as root and check if you can access the disk.

OK, when I go in a terminal and try to access the drive there (as su), I have access. So it may be a Dolphin thing?

Entering "dolphin" yields:

Code: Select all: dolphin(11899)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/root/.kde4/socket-localhost/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly drkonqi(11900)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) [root@localhost Maori]# cd.. [root@localhost Art]# cd.. [root@localhost 825a68d4-aa21-4e17-a52b-2e017e6a1839]# dolphin dolphin(11947)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/root/.kde4/socket-localhost/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly drkonqi(11948)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) [root@localhost 825a68d4-aa21-4e17-a52b-2e017e6a1839]#

When I then type "export $(dbus-launch)", Dolphin does launch in the GUI, and I can access the drive. Seems a bit convoluted though, and apparently I would need to do this every time, as when I shut off the drive and turn it on again, the same problem pops up again too.. :s

If you use

Code: Select all: su -

you get a complete root environment able to run graphical programs such as dolphin.
Of course this has nothing to do with your original problem.

If you go into /run/media/{yourusername}/

type in ls -la to see what permissions the folders there have. The name of the folder should be a bunch of numbers and letters or "uuid" name. It should be owned by your user, not root or someone else.

Ps. Sorry "export $(dbus-launch)" is the correct command. I wrote it without the dollar sign.

Is it an option to re-format that harddrive perhaps? I've been trying Krusader instead of Dolphin, and that gives the same problem....

Even running "export $(dbus-launch)" does not always work, or sometimes only temporarily. And that means that this harddrive is a b*tch to use, so I tend to avoid having to do it. That shouldn't be so, I want my devices to work...

So if buying a new harddrive perhaps, what should I pay attention to? Not buying FAT32 drive, for instance? Would I have these issues with solid state drives?

Thanks.

You didn't answer about the question from zeebra on the permissions of the mountpoint.
Also, when the disk is mounted, please show the output of

Code: Select all: mount

Mageia forum

External harddrive detection

External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection

Re: External harddrive detection