Guten Morgen, vorab, es sind 4 exakt gleiche Computer, einen habe ich installiert und konfiguriert, die anderen habe ich mit dd geklont. Das ging soweit auch, dauerte halt lange... Verschiedene USB Sticks werden am Compute der installiert wurde nicht erkannt! Sobald ich einen USB Stick einstecke, bekomme ich folgende Fehler: Bei einem anderen Stick kommt der gleiche Fehler, außer die sache mit dem ntfs... es wird aber auch nichts gemountet bzw. geöffnet. May 29 16:29:45 kernel: usb 5-1: new high speed USB device using ehci_hcd and address 8 May 29 16:29:45 kernel: scsi6 : SCSI emulation for USB Mass Storage devices May 29 16:29:45 kernel: usb-storage: device found at 8 May 29 16:29:45 kernel: usb-storage: waiting for device to settle before scanning May 29 16:29:50 kernel: Vendor: OTi Model: Flash Disk Rev: 2.00 May 29 16:29:50 kernel: Type: Direct-Access ANSI SCSI revision: 02 May 29 16:29:50 kernel: sdb: Unit Not Ready, sense: May 29 16:29:50 kernel: : Current: sense key: Unit Attention May 29 16:29:50 kernel: Additional sense: Not ready to ready change, medium may have changed May 29 16:29:50 kernel: sdb : READ CAPACITY failed. May 29 16:29:50 kernel: sdb : status=1, message=00, host=0, driver=08 May 29 16:29:50 kernel: sd: Current: sense key: Unit Attention May 29 16:29:50 kernel: Additional sense: Not ready to ready change, medium may have changed May 29 16:29:50 kernel: sdb: test WP failed, assume Write Enabled May 29 16:29:50 kernel: sdb: assuming drive cache: write through May 29 16:29:50 kernel: sdb: Unit Not Ready, sense: May 29 16:29:50 kernel: : Current: sense key: Unit Attention May 29 16:29:50 kernel: Additional sense: Not ready to ready change, medium may have changed May 29 16:29:50 kernel: sdb : READ CAPACITY failed. May 29 16:29:50 kernel: sdb : status=1, message=00, host=0, driver=08 May 29 16:29:50 kernel: sd: Current: sense key: Unit Attention May 29 16:29:50 kernel: Additional sense: Not ready to ready change, medium may have changed May 29 16:29:50 kernel: sdb: test WP failed, assume Write Enabled May 29 16:29:50 kernel: sdb: assuming drive cache: write through May 29 16:29:50 kernel: sdb: Unit Not Ready, sense: May 29 16:29:50 kernel: : Current: sense key: Unit Attention May 29 16:29:50 kernel: Additional sense: Not ready to ready change, medium may have changed May 29 16:29:50 kernel: sdb : READ CAPACITY failed. May 29 16:29:50 kernel: sdb : status=1, message=00, host=0, driver=08 May 29 16:29:50 kernel: sd: Current: sense key: Unit Attention May 29 16:29:50 kernel: Additional sense: Not ready to ready change, medium may have changed May 29 16:29:50 kernel: sdb: test WP failed, assume Write Enabled May 29 16:29:50 kernel: sdb: assuming drive cache: write through May 29 16:29:50 kernel: sdb:end_request: I/O error, dev sdb, sector 0 May 29 16:29:50 kernel: Buffer I/O error on device sdb, logical block 0 May 29 16:29:50 kernel: Buffer I/O error on device sdb, logical block 0 May 29 16:29:50 kernel: Buffer I/O error on device sdb, logical block 0 May 29 16:29:50 kernel: unable to read partition table May 29 16:29:50 kernel: Attached scsi removable disk sdb at scsi6, channel 0, id 0, lun 0 May 29 16:29:50 kernel: Attached scsi generic sg1 at scsi6, channel 0, id 0, lun 0, type 0 May 29 16:29:50 kernel: usb-storage: device scan complete May 29 16:33:25 kernel: SCSI device sdb: 512000 512-byte hdwr sectors (262 MB) May 29 16:33:25 kernel: sdb: Write Protect is off May 29 16:33:25 kernel: sdb: Mode Sense: 03 00 00 00 May 29 16:33:25 kernel: sdb: assuming drive cache: write through May 29 16:33:25 kernel: SCSI device sdb: 512000 512-byte hdwr sectors (262 MB) May 29 16:33:25 kernel: sdb: Write Protect is off May 29 16:33:25 kernel: sdb: Mode Sense: 03 00 00 00 May 29 16:33:25 kernel: sdb: assuming drive cache: write through May 29 16:33:25 kernel: sdb: sdb1 May 29 16:38:58 udevd[2459]: get_netlink_msg: no ACTION in payload found, skip event 'umount' May 29 16:38:58 kernel: FAT: invalid media value (0x01) May 29 16:38:58 kernel: VFS: Can't find a valid FAT filesystem on dev sdb. May 29 16:39:07 kernel: NTFS driver 2.1.23 [Flags: R/W MODULE]. May 29 16:39:07 kernel: NTFS-fs warning (device sdb): is_boot_sector_ntfs(): Invalid boot sector checksum. May 29 16:39:07 udevd[2459]: get_netlink_msg: no ACTION in payload found, skip event 'umount' May 29 16:39:07 kernel: NTFS-fs error (device sdb): read_ntfs_boot_sector(): Primary boot sector is invalid. May 29 16:39:07 kernel: NTFS-fs error (device sdb): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. May 29 16:39:07 kernel: NTFS-fs error (device sdb): ntfs_fill_super(): Not an NTFS volume. Wenn ich jetzt genau diesen USB Stick in einen Computer der geklont wurde einstecke, mountet er automatisch und zeigt gleich ein Fenster im KDE an, so sollte es auch sein... Hier die Messages: May 30 07:50:58 kernel: usb 5-1: new high speed USB device using ehci_hcd and address 3 May 30 07:50:59 kernel: Initializing USB Mass Storage driver... May 30 07:50:59 kernel: scsi2 : SCSI emulation for USB Mass Storage devices May 30 07:50:59 kernel: usb-storage: device found at 3 May 30 07:50:59 kernel: usb-storage: waiting for device to settle before scanning May 30 07:50:59 kernel: usbcore: registered new driver usb-storage May 30 07:50:59 kernel: USB Mass Storage support registered. May 30 07:51:04 kernel: Vendor: OTi Model: Flash Disk Rev: 2.00 May 30 07:51:04 kernel: Type: Direct-Access ANSI SCSI revision: 02 May 30 07:51:04 kernel: sdb: Unit Not Ready, sense: May 30 07:51:04 kernel: : Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: sdb : READ CAPACITY failed. May 30 07:51:04 kernel: sdb : status=1, message=00, host=0, driver=08 May 30 07:51:04 kernel: sd: Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: sdb: test WP failed, assume Write Enabled May 30 07:51:04 kernel: sdb: assuming drive cache: write through May 30 07:51:04 kernel: sdb: Unit Not Ready, sense: May 30 07:51:04 kernel: : Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: sdb : READ CAPACITY failed. May 30 07:51:04 kernel: sdb : status=1, message=00, host=0, driver=08 May 30 07:51:04 kernel: sd: Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: sdb: test WP failed, assume Write Enabled May 30 07:51:04 kernel: sdb: assuming drive cache: write through May 30 07:51:04 kernel: sdb: Unit Not Ready, sense: May 30 07:51:04 kernel: : Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: sdb : READ CAPACITY failed. May 30 07:51:04 kernel: sdb : status=1, message=00, host=0, driver=08 May 30 07:51:04 kernel: sd: Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: sdb: test WP failed, assume Write Enabled May 30 07:51:04 kernel: sdb: assuming drive cache: write through May 30 07:51:04 kernel: sdb:end_request: I/O error, dev sdb, sector 0 May 30 07:51:04 kernel: Buffer I/O error on device sdb, logical block 0 May 30 07:51:04 kernel: Buffer I/O error on device sdb, logical block 0 May 30 07:51:04 kernel: Buffer I/O error on device sdb, logical block 0 May 30 07:51:04 kernel: unable to read partition table May 30 07:51:04 kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0 May 30 07:51:04 kernel: Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0, type 0 May 30 07:51:04 kernel: usb-storage: device scan complete May 30 07:51:04 kernel: sdb: Unit Not Ready, sense: May 30 07:51:04 kernel: : Current: sense key: Unit Attention May 30 07:51:04 kernel: Additional sense: Not ready to ready change, medium may have changed May 30 07:51:04 kernel: SCSI device sdb: 512000 512-byte hdwr sectors (262 MB) May 30 07:51:04 kernel: sdb: Write Protect is off May 30 07:51:04 kernel: sdb: Mode Sense: 03 00 00 00 May 30 07:51:04 kernel: sdb: assuming drive cache: write through May 30 07:51:04 kernel: SCSI device sdb: 512000 512-byte hdwr sectors (262 MB) May 30 07:51:04 kernel: sdb: Write Protect is off May 30 07:51:04 kernel: sdb: Mode Sense: 03 00 00 00 May 30 07:51:04 kernel: sdb: assuming drive cache: write through May 30 07:51:04 kernel: sdb: sdb1 May 30 07:51:04 hal-subfs-mount[6588]: SYMLINKS:: disk/by-id/usb-OTi_Flash_Disk_15E7436C79E60044 disk/by-path/usb-15E7436C79E60044:0:0:0 May 30 07:51:04 hal-subfs-mount[6588]: MOUNT_POINT:: /media/usbdisk May 30 07:51:04 hal-subfs-mount[6588]: MOUNTPOINT:: /media/usbdisk May 30 07:51:04 hal-subfs-mount[6588]: Collected mount options and Called(0) /bin/mount -t subfs -o fs=floppyfss,sync,procuid,nosuid,nodev,exec,utf8=true /dev/sdb1 "/media/usbdisk" May 30 07:51:04 udevd[2462]: get_netlink_msg: no ACTION in payload found, skip event 'mount' May 30 07:51:07 udevd[2462]: get_netlink_msg: no ACTION in payload found, skip event 'umount' May 30 07:51:07 udevd[2462]: get_netlink_msg: no ACTION in payload found, skip event 'mount' May 30 07:51:10 udevd[2462]: get_netlink_msg: no ACTION in payload found, skip event 'umount' Meine Vermutungen: - Der eine Computer hat ein Hardware Problem - Ein Dienst läuft nicht oder nicht richtig - OnlineUpdate?! Rechner stehen schon 2 Tage ca. evtl haben welche automatisch das OnlineUpdate durchlaufen... Mit lsusb wird alles richtig angezeigt... lshal gibt auf dem Computer der fehlerhaft läuft aus: lshal version 0.5.4 error: libhal_ctx_init: (null): (null) Bei den anderen Computern kommt eine endlos lange Liste, schein i.O. zu sein. Hat jemand eine Idee was es noch sein könnte? Vielen Dank und freundliche Grüße, Jan Vöhringer
Hallo Jan, es muss nicht unbedingt am PC liegen. Je nach Hersteller sind manche USB-Sticks sehr zickig; jedenfalls wurde dies hier schon mehrfach berichtet und entspricht auch meiner Erfahrung. Dagegen hilt im Grunde nur die Methode "trial and error": Neuere Sticks scheinen weniger anfällig zu sein. MfG Wolfgang Gruhn
On Tuesday 30 May 2006 08:22, Jan Voehringer wrote: [...]
lshal gibt auf dem Computer der fehlerhaft läuft aus: lshal version 0.5.4 error: libhal_ctx_init: (null): (null)
Liegt wohl daran, das HAL nicht läuft. Du solltest sicher sein, das der Dienst (hald) auch läuft, wenn du automatisches mounten (oder sinnvolle Ausgaben von lshal) willst. Danny
participants (3)
-
Danny Kukawka
-
Jan Voehringer
-
Wolfgang Gruhn