You are not logged in.
Hi,
I own several usb keys and usb HDD. All of them are usually mounted with udiskie. However, recently, one of my HDDs stopped to be mounted automatically.
I checked the permissions in /dev and I saw that:
brw-rw---- 1 root disk 8, 0 11 févr. 08:37 sda
brw-rw---- 1 root disk 8, 1 11 févr. 08:37 sda1
brw-rw---- 1 root disk 8, 2 11 févr. 08:37 sda2
brw-rw---- 1 root disk 8, 5 11 févr. 08:37 sda5
brw-rw---- 1 root disk 8, 16 11 févr. 14:59 sdb
brw-rw---- 1 root disk 8, 17 11 févr. 14:59 sdb1
brw-rw---- 1 root disk 8, 32 11 févr. 15:23 sdc
brw------- 1 root root 8, 33 11 févr. 15:23 sdc1
brw------- 1 root root 8, 34 11 févr. 15:23 sdc2
sdc1 and sdc2 represents the two partitions of the problematic disk. sdb is a working usb key and sda are for the internal hard drive.
Does anybody have an idea of what's going on? if these permissions are really the root of the problem...
Many thanks.
Offline
Hi
Say what changed in your system between the working automounting udiskie and the not working one.
Post what dmesg says after you plugged in the HDD.
And post the output of a manual mount command for the disk as user, then as root if the first one doesn't work.
Try also the udisks command line in a console to mount the disk through udisks as a user then as root.
Offline
Are those NTFS partitions? Are you using NTFS-3g?
Does your kernel version ( uname -a) ) match the installed version ( pacman -Qi linux )
They can be different for a variety of reasons -- the most common reason is if you were to update the kernel (which replaces the old kernel modules with the new kernel modules) without rebooting. In this case the old kernel is still running and cannot find its modules. At the reboot, you start the new kernel.
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
Online
Hi,
thanks for your help.
2 partitions, one is ntfs (with ntfs-3g) the other is ext4. I guess it's not related to the partition format.
It's not related to a missing reboot after a kernel upgrade.
I have no clue about the changes I made. I plug it only from time to time, and sometimes this disk is mounted on other computers (windows...).
root can mount it without problem (#mount /dev/sdc1 /mnt for instance), write on it, unmount it...
relevant part of the dmesg output after plug in the disk:
[33064.732211] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[33065.792762] usb-storage 2-2:1.0: USB Mass Storage device detected
[33065.793459] scsi6 : usb-storage 2-2:1.0
[33065.793907] usbcore: registered new interface driver usb-storage
[33066.795405] scsi 6:0:0:0: Direct-Access WD My Book 1170 1042 PQ: 0 ANSI: 6
[33066.795798] scsi 6:0:0:1: Enclosure WD SES Device 1042 PQ: 0 ANSI: 6
[33066.797199] sd 6:0:0:0: [sdb] Spinning up disk...
[33066.959299] scsi 6:0:0:1: Failed to get diagnostic page 0x8000002
[33066.959307] scsi 6:0:0:1: Failed to bind enclosure -19
[33066.959330] ses 6:0:0:1: Attached Enclosure device
[33067.797993] .......ready
[33074.170803] sd 6:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[33074.171275] sd 6:0:0:0: [sdb] Write Protect is off
[33074.171292] sd 6:0:0:0: [sdb] Mode Sense: 53 00 10 08
[33074.171601] sd 6:0:0:0: [sdb] No Caching mode page found
[33074.171606] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[33074.172013] sd 6:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[33074.172591] sd 6:0:0:0: [sdb] No Caching mode page found
[33074.172595] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[33074.194550] sdb: sdb1 sdb2
[33074.195306] sd 6:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[33074.195886] sd 6:0:0:0: [sdb] No Caching mode page found
[33074.195890] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[33074.195894] sd 6:0:0:0: [sdb] Attached SCSI disk
If I do # udisks --mount /dev/sdc
it says that Mount failed: Error mounting: mount: bad filetype, wrong option, wrong superblock on /dev/sdc
I got this extra output in dmesg
[33110.332792] usb 2-2: Disable of device-initiated U1 failed.
[33115.332139] usb 2-2: Disable of device-initiated U2 failed.
[33115.439614] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[33115.453167] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880124d9e480
[33115.453175] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880124d9e4c0
Offline
There is an inconsistency in your infos:
the dmesg messages say sdb1, sdb2 for the partitions on the disk, and your commands use sdc1.
The udisks command line should use the partition device, just as the mount command:
# udisks --mount /dev/sdc1
This one should work now.
Can you try the 'mount' and 'usdisks --mount' commands as a user, and post the output.
Offline
I changed the names to be consistant with the first message and I forgot to replace in the output.
While my problem was reproducible, after the following upgrade:
[PACMAN] Running 'pacman --color auto -S -u'
[PACMAN] starting full system upgrade
[PACMAN] upgraded linux-api-headers (3.12.4-1 -> 3.13.2-1)
[ALPM] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[ALPM-SCRIPTLET] Generating locales...
[ALPM-SCRIPTLET] en_US.UTF-8
[ALPM-SCRIPTLET] fr_FR.UTF-8
[ALPM-SCRIPTLET] Generation complete.
[PACMAN] upgraded glibc (2.18-12 -> 2.19-1)
[PACMAN] upgraded binutils (2.24-1 -> 2.24-2)
[PACMAN] upgraded cython (0.20-2 -> 0.20.1-1)
[PACMAN] upgraded cython2 (0.20-2 -> 0.20.1-1)
[PACMAN] upgraded gcc-libs (4.8.2-7 -> 4.8.2-8)
[PACMAN] upgraded elfutils (0.157-1 -> 0.158-1)
[PACMAN] upgraded evolution-data-server (3.10.3-1 -> 3.10.4-1)
[PACMAN] upgraded gcc (4.8.2-7 -> 4.8.2-8)
[PACMAN] upgraded gcc-fortran (4.8.2-7 -> 4.8.2-8)
[PACMAN] upgraded gstreamer (1.2.2-1 -> 1.2.3-1)
[PACMAN] upgraded gst-plugins-base-libs (1.2.2-1 -> 1.2.3-1)
[PACMAN] upgraded openjpeg (1.5.1-1 -> 1.5.1-2)
[PACMAN] upgraded gst-plugins-bad (1.2.2-3 -> 1.2.3-1)
[PACMAN] upgraded gst-plugins-base (1.2.2-1 -> 1.2.3-1)
[PACMAN] upgraded gst-plugins-good (1.2.2-2 -> 1.2.3-1)
[PACMAN] upgraded kdelibs (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdegraphics-mobipocket (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded nepomuk-core (4.12.1-2 -> 4.12.2-1)
[PACMAN] upgraded kactivities (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdebase-katepart (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded oxygen-icons (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdebase-runtime (4.12.1-3 -> 4.12.2-1)
[PACMAN] upgraded kdebase-kwrite (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdebase-lib (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdeedu-marble (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdegraphics-kolourpaint (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded libkipi (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdegraphics-ksnapshot (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded libkexiv2 (4.12.1-2 -> 4.12.2-1)
[PACMAN] upgraded kdegraphics-okular (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded kdesdk-kate (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded libdivecomputer (0.4.1-1 -> 0.4.2-1)
[PACMAN] upgraded libksane (4.12.1-1 -> 4.12.2-1)
[PACMAN] upgraded libreoffice-fr (4.1.4-1 -> 4.1.5-1)
[PACMAN] upgraded libreoffice-common (4.1.4-3 -> 4.1.5-1)
[PACMAN] upgraded libreoffice-base (4.1.4-3 -> 4.1.5-1)
[PACMAN] upgraded libreoffice-calc (4.1.4-3 -> 4.1.5-1)
[PACMAN] upgraded libreoffice-writer (4.1.4-3 -> 4.1.5-1)
[PACMAN] upgraded postfix (2.11.0-1 -> 2.11.0-2)
[PACMAN] upgraded python-numpy (1.8.0-1 -> 1.8.0-2)
[PACMAN] upgraded python2-numpy (1.8.0-1 -> 1.8.0-2)
[PACMAN] upgraded s-nail (14.5.2-3 -> 14.5.2-4)
[PACMAN] upgraded systemd (208-10 -> 208-11)
[PACMAN] upgraded systemd-sysvcompat (208-10 -> 208-11)
[PACMAN] upgraded valgrind (3.9.0-1 -> 3.9.0-2)
[PACMAN] upgraded xf86-video-intel (2.99.909-2 -> 2.99.910-1)
[PACMAN] upgraded youtube-dl (2014.02.08.2-1 -> 2014.02.10-1)
Exited with code 0
I will repost if the problem reappears.
Offline