[SOLVED] thunar stopped to mount USB storages (Debian squeeze)
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
But I somewhat think that symptom is different. Even though I start thunar manually, nothing changes...
Does anybody know how to make things work?
Happy Penguins!
Have you tried mounting the usb manually from a command line? something like this:
Code:
sudo mount /dev/sda1 /media/usbdisk
Do you get an error message when you do this? (the dev may not be sda1 and your mount point may not be /media/usbdisk. Just change the command to fit your particular setup). Also is your usb storage device include in the fstab file?
cheers,
jdk
I have checked hal policies (compared to lenny one), but I do not think I am on the right track.
When thunar is evoked as a daemon.
Code:
>thunar-volman: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_90c_1000_AA20000000015580.
thunar-volman: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_90c_1000_AA20000000015580_if0.
thunar-volman: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_90c_1000_AA20000000015580_scsi_host_scsi_device_lun0.
The message above pops out when an USB stick is connected.
Happy Penguins!
Last edited by kaz2100; 05-05-2009 at 05:50 AM.
Reason: typo
I have checked hal policies (compared to lenny one), but I do not think I am on the right track.
When thunar is evoked as a daemon.
Code:
>thunar-volman: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_90c_1000_AA20000000015580.
thunar-volman: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_90c_1000_AA20000000015580_if0.
thunar-volman: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_90c_1000_AA20000000015580_scsi_host_scsi_device_lun0.
The message above pops out when an USB stick is connected.
Happy Penguins!
Sorry, I guess I don't know what thunar is. I thought it was a file manager. Anyway, I don't use it so maybe somebody who does can help.
Srak ni,
jdk
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Rep:
I don't know if this is the issue or not, but I think your issues with mounting the usb drive have to do with a different labelling system for devices in Squeeze. Hard drives used to be labelled "hdx" (with x being a corresponding letter such as "a" or "b"), and usb drives were sdx (again with "x" being a corresponding letter to the usb-drive, the first being "a", the second "b", and so on). Now, it seems both usb and hard drives are all labelled with "sdx", and generally hard drives take the first few letters. So, in your case, there may have been an issue with thunar referencing an outdated fstab file that had the wrong device locations for your usb-sticks/usb-drives.
The two bottom entries that are commented out are old entries that worked with Lenny, but not with Squeeze. "sda" now refers to my first hard drive (rather than hda, which it used to be), whereas "sdb" now refers to my second hard drive. If you only have one hard drive, then the usb-stick would become "sdb" (I think). Since I have two hard drives, the usb sticks become "sdc" (with "a" and "b" representing the two hard drives). For the two usb-sticks that I have, I set up two different mount-points (usb, and usb2) each coming from sdc1 and sdc2.
[later edit]
It turns out that the device for the second usb is /dev/sdd1, rather than /dev/sdc2. I just tested this, and it works.
Last edited by mark_alfred; 08-04-2011 at 10:16 PM.
Hard drives used to be labelled "hdx" (with x being a corresponding letter such as "a" or "b"), and usb drives were sdx (again with "x" being a corresponding letter to the usb-drive, the first being "a", the second "b", and so on). Now, it seems both usb and hard drives are all labelled with "sdx", and generally hard drives take the first few letters.
I may be wrong but it is my understanding that on older kernels, USB and SATA connected drives use the sdx notation (does the s stand for scsi?) and PATA connected drives used hdx notation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.