LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   problems with usbstick (https://www.linuxquestions.org/questions/linux-hardware-18/problems-with-usbstick-607173/)

CrashedAgain 12-16-2007 04:37 PM

problems with usbstick
 
I cannot get two of my 3 boxes to read my usb stick.
System 1 is a desktop with a Debian (originally Kanotix) system installed. It detects and tries to read the stick, selecting "open in a new window" in the kio dialog box results in a new "system:/media/sda1" window appearing then there is an error message:
Code:

A security policy in place prevents this sender from sending this message to this recipient,
 see message bus configuration file (rejected message had interface
"org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")

I don't understand this message, it seems like it is saying it wants to send a message but can't because of a security policy which makes no sense, kind of like saying i've got a secret and i can't tell you nyaa nyaa.
Dmesg tail after plugging in the stick:
Code:

Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
  Vendor: SanDisk  Model: U3 Titanium      Rev: 2.19
  Type:  Direct-Access                      ANSI SCSI revision: 02
SCSI device sda: 1994385 512-byte hdwr sectors (1021 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 1994385 512-byte hdwr sectors (1021 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: Attached scsi removable disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
  Vendor: SanDisk  Model: U3 Titanium      Rev: 2.19
  Type:  CD-ROM                            ANSI SCSI revision: 02
sr0: scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray
sr 0:0:0:1: Attached scsi CD-ROM sr0
sr 0:0:0:1: Attached scsi generic sg1 type 5
usb-storage: device scan complete
cdrom: This disc doesn't have any tracks I recognize!
EFS: 1.0a - http://aeschi.ch.eu.org/efs/
FAT: invalid media value (0x01)
VFS: Can't find a valid FAT filesystem on dev sda.
usb 1-2: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
  Vendor: SanDisk  Model: U3 Titanium      Rev: 2.19
  Type:  Direct-Access                      ANSI SCSI revision: 02
SCSI device sda: 1994385 512-byte hdwr sectors (1021 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 1994385 512-byte hdwr sectors (1021 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
 sda: sda1
sd 1:0:0:0: Attached scsi removable disk sda
sd 1:0:0:0: Attached scsi generic sg0 type 0
  Vendor: SanDisk  Model: U3 Titanium      Rev: 2.19
  Type:  CD-ROM                            ANSI SCSI revision: 02
sr0: scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray
sr 1:0:0:1: Attached scsi CD-ROM sr0
sr 1:0:0:1: Attached scsi generic sg1 type 5
usb-storage: device scan complete
cdrom: This disc doesn't have any tracks I recognize!

The second box is a laptop with Debian Etch installed. It partially recognises the stick, opens up a windows "system:/media/scd0" which contains some windows autorun files "autorun.inf,LaunchPad.zip and launchpad.exe". It then tries to open the rest of the stick in a new windows "system:/media/sda1" but fails with the following erro message:
Code:

mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
dmesg reports:
Code:

SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
  Vendor: SanDisk  Model: U3 Titanium      Rev: 2.19
  Type:  Direct-Access                      ANSI SCSI revision: 02
  Vendor: SanDisk  Model: U3 Titanium      Rev: 2.19
  Type:  CD-ROM                            ANSI SCSI revision: 02
usb-storage: device scan complete
SCSI device sda: 1994385 512-byte hdwr sectors (1021 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 1994385 512-byte hdwr sectors (1021 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: Attached scsi removable disk sda
sr0: scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray
sr 0:0:0:1: Attached scsi CD-ROM sr0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 0:0:0:1: Attached scsi generic sg1 type 5
cdrom: This disc doesn't have any tracks I recognize!
cdrom: This disc doesn't have any tracks I recognize!
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
cdrom: This disc doesn't have any tracks I recognize!
cdrom: This disc doesn't have any tracks I recognize!
cdrom: This disc doesn't have any tracks I recognize!
cdrom: This disc doesn't have any tracks I recognize!
FAT: Unrecognized mount option "flush" or missing value
crashedagain@Laptop:~$


Can anyone help?

michaelk 12-16-2007 08:11 PM

Your USB stick is a U3 device which appears as two devices. A cdrom which contains the encryption stuff (launchpad) which only works in windows and a regular USB storage device which in your case sda1 that can be mounted just like any other device as long as you do not password protect the files. I have the same device and it automounts fine in CentOS. The dmesg output looks like the device is being recognized correctly but it is possible that hal has problems with trying to automount the device.

You can remove the cdrom part via the link below.
http://www.u3.com/uninstall/

CrashedAgain 12-16-2007 09:30 PM

My third computer (also Debian Etch system) also automounts the stick but in two separate mounts; system/media/scd0 mounts the U3 stuff & system?media/sb1 mounts the data partitions.
If it's the U3 program that is giving me problems, why not just reformat the stick with a single fs instead of using their uninstall program which is a windows program?

michaelk 12-17-2007 06:57 AM

From the information I've read you can not just reformat due to the additional hardware present in these type of drives.

CrashedAgain 12-17-2007 05:04 PM

I've Googled all over the place & it looks like you MUST use their removal program...which is windows XP/2000 & up only. The only win system I've got is ME, so I guess I'll have to go visit somebody.

BillyCrook 12-17-2007 10:53 PM

I had a similar problem:

Every time I plugged in a usb storage device, I got this window:

Code:

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ ◻                                            X ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃                                                ┃
┃    Cannot mount volume.                      ┃
┃    Error org.Freedesktop.Hal.PermissionDenied ┃
┃                                                ┃
Details ▼                                      ┃
┃  Permission denied: Not in active session    ┃
┃                                                ┃
┃                                ┏━━━━━━━━┓      ┃
┃                                ┃ ↩ OK  ┃      ┃
┃                                ┗━━━━━━━━┛      ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

I know they *used to* just pop up and show me their files, but i figured this was AutoFS, and never worried about it. Well now all I get is this ambiguous error message. I googled it, and found out it was because I had disabled the ConsoleKit service. To correct this error, go to a shell, and type sudo /sbin/chkconfig --level 345 ConsoleKit on and press enter. This will set ConsoleKit to start up automatically on boot. Next either reboot, or type sudo /etc/init.d/ConsoleKit start to start the service. Then log out and back in.

Hope this helps someone.


All times are GMT -5. The time now is 09:34 AM.