COMRESET errorno -19 for GPT tabled 2 TB eSata HD

[knoobie]

Binary package hint: usplash

Hello.

System is HP with AMD 5000+, 4GB RAM, 400GB internal SATA HD, 1 TB eSata HD, 2 TB eSata HD.

I have tested this with both 64 bit Kubuntu 9.10 and 64 bitUbuntu 9.10 using the 2.6.31-14 and -15 generic kernels.

Problem:

I have an eSata attached external HD 2 TB in size. It is partitioned using GPT and not MBR. It has a single 1.9 TB ntfs-3g partition.

If I leave the drive enabled during boot, I first get a COMRESET errrorno -16 followed by three COMRESET failed, error -19. It also adds about 2 minutes to the time to get to the logon screen.
Then the drive is not mountable during the duration of the session.

However, if I have the drive powered off during boot, then turn it on after logging in, the drive mounts without errors.

I also have another 1 TB eSata drive attached to the same controller (SII 3114) that has had no issues. The only difference (besides size) is that the 1TB drive uses an MBR style partition table, whereas the 2TB uses a GPT partition table.

A successful connection shows the 2TB drive (from lshw)
           *-disk:1
                description: ATA Disk
                product: WD My Book
                vendor: Western Digital
                physical id: 1
                bus info: scsi@2:0.0.0
                logical name: /dev/sdj
                version: 1015
                serial: WU2Q10040000
                size: 1863GiB (2TB)
                capabilities: gpt-1.00 partitioned partitioned:gpt
                configuration: ansiversion=5 guid=08f1e97b-afa0-41f0-ad1a-7add2a2eb116
              *-volume:0
                   description: Windows reserved partition
                   physical id: 1
                   bus info: scsi@2:0.0.0,1
                   logical name: /dev/sdj1
                   serial: 70a3180a-3a76-49c6-b4e1-ef5d6df38c77
                   capacity: 127MiB
                   capabilities: nofs
                   configuration: name=Microsoft reserved partition
              *-volume:1
                   description: Windows NTFS volume
                   physical id: 2
                   bus info: scsi@2:0.0.0,2
                   logical name: /dev/sdj2
                   version: 3.1
                   serial: c672fdf0-165a-9b43-b633-df5f2a00372f
                   size: 1862GiB
                   capacity: 1862GiB
                   capabilities: ntfs initialized
                   configuration: clustersize=4096 created=2008-10-14 23:43:58 filesystem=ntfs label=esata2t name=Basic data partition state=clean

Errors shown (from kern.log)
sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 4:0:0:0: [sr0] Sense Key : Not Ready [current]
sr 4:0:0:0: [sr0] Add. Sense: Incompatible medium installed
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
Buffer I/O error on device sr0, logical block 1
Buffer I/O error on device sr0, logical block 2
Buffer I/O error on device sr0, logical block 3
Buffer I/O error on device sr0, logical block 4
Buffer I/O error on device sr0, logical block 5
Buffer I/O error on device sr0, logical block 6
Buffer I/O error on device sr0, logical block 7

sr 4:0:0:0: [sr0] Device not ready
sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 4:0:0:0: [sr0] Sense Key : Not Ready [current]
sr 4:0:0:0: [sr0] Add. Sense: Incompatible medium installed
end_request: I/O error, dev sr0, sector 0
< above block repeats 14 times>

ata3: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
ata3: SError: { PHYRdyChg CommWake }
ata3: hard resetting link
ata3: link is slow to respond, please be patient (ready=-19)
ata3: COMRESET failed (errno=-16)
ata3: hard resetting link
ata3: link is slow to respond, please be patient (ready=-19)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3.00: ATA-6: WD My Book 1105, 1015, max UDMA/133
ata3.00: 3907017568 sectors, multi 0: LBA48
ata3.00: configured for UDMA/100
ata3: EH complete
...
 ata3: COMRESET failed (errno=-19)
 ata3: reset failed (errno=-19), retrying in 10 secs
<above repeats 3 time>

ata3: reset failed, giving up

usplash.conf - default - not an issue

uname -a
Linux marty-pc 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:53:52 UTC 2009 x86_64 GNU/Linux

ProblemType: Bug
Architecture: amd64
Date: Wed Dec 2 14:52:42 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: HP-Pavilion GN567AA-ABA s3220n
NonfreeKernelModules: nvidia
Package: usplash 0.5.49
ProcCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=756488c5-fe6a-472c-be5e-a546975f76d7 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: usplash
Uname: Linux 2.6.31-15-generic x86_64
UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1366
 yres=768
XsessionErrors:
 (gimp-2.6:2341): Gtk-CRITICAL **: gtk_box_reorder_child: assertion `GTK_IS_WIDGET (child)' failed
 (npviewer.bin:4808): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
 (npviewer.bin:5237): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
dmi.bios.date: 06/18/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.18
dmi.board.name: Acacia
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.18:bd06/18/2008:svnHP-Pavilion:pnGN567AA-ABAs3220n:pvr:rvnASUSTekComputerINC.:rnAcacia:rvr1.00:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GN567AA-ABA s3220n
dmi.sys.vendor: HP-Pavilion

[knoobie (g63marty)]

Bug incorrectly filed against package usplash. Should be linux kernel.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.