From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonas Schwertfeger Date: Fri, 02 Apr 2010 13:09:02 +0000 Subject: Re: System hangs when using USB 3.0 HD with on Ubuntu Message-Id: List-Id: References: <4BB37454.8070808@interlog.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Kay Sievers Cc: Alan Stern , Douglas Gilbert , David Zeuthen , linux-hotplug-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Sarah Sharp , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, USB Storage List , Matthew Dharm , linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Lennart Poettering Actually, you hit the nail on the head Kay. I moved the hdparm rule out of the way and voil=E0, the drive mounts. I then manually ran hdparm on the device: sudo hdparm --verbose /dev/sdb /dev/sdb: outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00 SG_IO: ATA_16 status=3D0x0, host_status=3D0x7, driver_status=3D0x0 SG_IO: bad response (not CHECK_CONDITION) outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 a1 00 SG_IO: ATA_16 status=3D0x0, host_status=3D0x7, driver_status=3D0x0 SG_IO: bad response (not CHECK_CONDITION) HDIO_DRIVE_CMD(identify) failed: Invalid exchange readonly =3D 0 (off) readahead =3D 256 (on) geometry =3D 36365/64/32, sectors =3D 0, start =3D 0 Does the command sent by hdparm look familiar? Exactly, it is the third ATA command (IDENTIFY DEVICE) we discovered earlier and caused the drive to stall. Does anyone know why the drive would not be able to cope with this command? And also, why does it not choke on it in USB 2.0 mode but only in USB 3.0? -Jonas