this problem still exists in gutsy the worst thing is, that i cannot unplug my eSATA HD safely. if i umount the partition and unplug it, the system hangs for about one minute and there are various error messages in dmesg: Dec 31 03:52:39 x2 kernel: [34550.804000] ata2: timeout waiting for ADMA IDLE, stat=0x400 Dec 31 03:52:39 x2 kernel: [34550.804000] ata2: timeout waiting for ADMA LEGACY, stat=0x400 Dec 31 03:52:39 x2 kernel: [34550.804000] res c0/00:00:00:00:00/00:00:00:00:00/40 Emask 0x12 (ATA bus error) Dec 31 03:52:39 x2 kernel: [34550.804000] ata2: hard resetting port Dec 31 03:52:52 x2 kernel: [34563.652000] ata2: SATA link down (SStatus 0 SControl 300) Dec 31 03:52:52 x2 kernel: [34563.652000] ata2: failed to recover some devices, retrying in 5 secs Dec 31 03:52:57 x2 kernel: [34568.656000] ata2: hard resetting port Dec 31 03:52:57 x2 kernel: [34569.380000] ata2: SATA link down (SStatus 0 SControl 300) Dec 31 03:52:57 x2 kernel: [34569.380000] ata2.00: limiting speed to UDMA/133:PIO3 Dec 31 03:52:57 x2 kernel: [34569.380000] ata2: failed to recover some devices, retrying in 5 secs Dec 31 03:53:02 x2 kernel: [34574.384000] ata2: hard resetting port Dec 31 03:53:03 x2 kernel: [34575.108000] ata2: SATA link down (SStatus 0 SControl 300) Dec 31 03:53:03 x2 kernel: [34575.108000] ata2.00: disabled Dec 31 03:53:04 x2 kernel: [34575.612000] sd 2:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Dec 31 03:53:04 x2 kernel: [34575.612000] sd 2:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor] Dec 31 03:53:04 x2 kernel: [34575.612000] Descriptor sense data with sense descriptors (in hex): Dec 31 03:53:04 x2 kernel: [34575.612000] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 31 03:53:04 x2 kernel: [34575.612000] 00 00 00 00 Dec 31 03:53:04 x2 kernel: [34575.612000] sd 2:0:0:0: [sdc] Add. Sense: Scsi parity error Dec 31 03:53:04 x2 kernel: [34575.612000] end_request: I/O error, dev sdc, sector 0 Dec 31 03:53:04 x2 kernel: [34575.612000] ata2: EH complete Dec 31 03:53:04 x2 kernel: [34575.612000] ata2.00: detaching (SCSI 2:0:0:0) Dec 31 03:53:04 x2 kernel: [34575.612000] sd 2:0:0:0: [sdc] Synchronizing SCSI cache Dec 31 03:53:04 x2 kernel: [34575.616000] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK Dec 31 03:53:04 x2 kernel: [34575.616000] sd 2:0:0:0: [sdc] Stopping disk Dec 31 03:53:04 x2 kernel: [34575.616000] sd 2:0:0:0: [sdc] START_STOP FAILED Dec 31 03:53:04 x2 kernel: [34575.616000] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
after this the devices is not listed anymore when executing "fdisk -l". is there a way to "eject" the device (/dev/sdc in my case) manually, so the kernel doesn't try to access it anymore? removing it with "hal-device -r <udi>" doesn't work completly: "fdisk -l" still shows the device and the error described above still occours. -- poor handling of eSATA drives https://bugs.launchpad.net/bugs/139748 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
