USB mass storage not automounting anymore in Etch...
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.
Distribution: K/Ubuntu 18.04-14.04, Scientific Linux 6.3-6.4, Android-x86, Pretty much all distros at one point...
Posts: 1,802
Rep:
USB mass storage not automounting anymore in Etch...
I've developed aproblem in Debian etch with usb mass storage devices failing to automount anymore. Konqueror shows an error message relating to HAL (sorry, don't have the whole error message) saying that it can't deliver the message to the recipient due to security settings... Does anyone have an idea of what could be going on???
Even when I su to root, or kdesu to root, I get no ability to mount /dev/sda...
Is the usbfs broken perhaps???
By the way...
Also, I have to force CDs to burn... (but I believe this is unrelated)...
I'm starting to loose a little faith in Debian now (and yes, I understand that Etch is a TESTING distro, but I wanted the ability to play with XGL eventually).
Running Debian etch (kernel 2.6.16-2-686-smp). Initially on inserting a USB device, I just get:
Sep 8 13:01:54 athene kernel: usb 1-8: new high speed USB device using ehci_hcd and address 4
Sep 8 13:01:54 athene kernel: usb 1-8: configuration #1 chosen from 1 choice
Sep 8 13:02:57 athene kernel: usb 1-8: USB disconnect, address 4
Sep 8 13:03:02 athene kernel: usb 1-7: new high speed USB device using ehci_hcd and address 5
Sep 8 13:03:02 athene kernel: usb 1-7: configuration #1 chosen from 1 choice
Sep 8 13:03:33 athene kernel: usb 1-7: USB disconnect, address 5
Sep 8 13:03:39 athene kernel: usb 1-7: new high speed USB device using ehci_hcd and address 6
Sep 8 13:03:39 athene kernel: usb 1-7: configuration #1 chosen from 1 choice
If I then do 'modprobe usb-storage', I get:
Sep 8 14:05:01 athene kernel: Initializing USB Mass Storage driver...
Sep 8 14:05:01 athene kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Sep 8 14:05:01 athene kernel: usbcore: registered new driver usb-storage
Sep 8 14:05:01 athene kernel: USB Mass Storage support registered.
Sep 8 14:05:06 athene kernel: Vendor: Memorex Model: M-Flyer B Rev: PMAP
Sep 8 14:05:06 athene kernel: Type: Direct-Access ANSI SCSI revision: 00
Sep 8 14:05:06 athene kernel: SCSI device sdc: 4029440 512-byte hdwr sectors (2063 MB)
Sep 8 14:05:06 athene kernel: sdc: Write Protect is off
Sep 8 14:05:06 athene kernel: SCSI device sdc: 4029440 512-byte hdwr sectors (2063 MB)
Sep 8 14:05:06 athene kernel: sdc: Write Protect is off
Sep 8 14:05:06 athene kernel: sdc: sdc1
Sep 8 14:05:06 athene kernel: sd 6:0:0:0: Attached scsi removable disk sdc
However, 'mount -t ext3 /dev/sdc1 /media/usb/' (as root) gives
mount: special device /dev/sdc1 does not exist
(/dev/sdc doesn't work either).
Any suggestions? I had a look at the hal config suggestions, but wasn't sure what was meant by 'uncheck these lines' (& anyway I'm not really bothered if hal doesn't pick the device up automatically; I'm concerned that it doesn't seem to be visible manually either!).
If I rememebr correctly the two lines in the hal.conf file have the "#" symbol at the start, remove the "#" symbol and save the file (as root) When I done this I was able to manually mount the device from the command line.
I have not got any further with it at present as I have not had the time. Hopefully I am going to take my box to a meeting where hopefully there will be some more knowlegable linux type to help me with this and some other problems
If I rememebr correctly the two lines in the hal.conf file have the "#" symbol at the start, remove the "#" symbol and save the file (as root) When I done this I was able to manually mount the device from the command line.
Unfortunately my file doesn't have # at the start of either of these lines. I guess there must be another reason for / solution to my problem!
OK, it seems to be fixed now (after apt-get upgrade; something must have shown up in the last fortnight while I was away, I guess!). Just Works now - plug in, 'mount /media/usb' (correct entry has been put in /etc/fstab), works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.