Greetings drive guru's; I have a 3 drive hot swap cage in my machine for a couple years now, and no it is NOT setup as a raid of any kind.
It has had a triplet of 1T seagate drives in it since installing it. My main boot drive had a 10.04-4 LTS Ubuntu install on it, but the drive went read only a couple months back, so I swapped the top 2 and put wheezy on what is now /dev/sda. I eventually had copied off what I needed from the old drive so I removed it, leaving slot 2 empty while I ordered up 2 more drives from TigerDirect, but had to settle for the 2Tb version this time. Tonight I cut the blisterpack off the first of the 2Tb drives and slid it into slot 2. Wheezy, with "SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux" kernel running cannot connect to it, doing this from /var/log/messages: Apr 14 21:14:33 coyote kernel: [1098002.318613] ata2: hard resetting link Apr 14 21:14:39 coyote kernel: [1098008.240015] ata2: link is slow to respond, please be patient (ready=-19) Apr 14 21:14:43 coyote kernel: [1098012.328022] ata2: hard resetting link Apr 14 21:14:49 coyote kernel: [1098018.256019] ata2: link is slow to respond, please be patient (ready=-19) Apr 14 21:14:53 coyote kernel: [1098022.344027] ata2: hard resetting link Apr 14 21:14:59 coyote kernel: [1098028.264018] ata2: link is slow to respond, please be patient (ready=-19) Followed by quite a few megabytes of this: Apr 14 21:15:27 coyote kernel: [1098055.934065] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 21:15:27 coyote kernel: [1098055.934070] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 21:15:27 coyote kernel: [1098055.934074] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 21:15:27 coyote kernel: [1098055.934081] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Apr 14 21:15:27 coyote kernel: [1098055.935512] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 21:15:27 coyote kernel: [1098055.935515] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 21:15:27 coyote kernel: [1098055.935518] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 21:15:27 coyote kernel: [1098055.935522] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00 I got the impression that it was not even spinning up. So I plugged the old, read-only drive in to see if the slot was bad, but it signs on like this: Apr 14 21:35:05 coyote kernel: [1099234.688032] ata2: hard resetting link Apr 14 21:35:11 coyote kernel: [1099240.608030] ata2: link is slow to respond, please be patient (ready=-19) Apr 14 21:35:15 coyote kernel: [1099244.704026] ata2: hard resetting link Apr 14 21:35:16 coyote kernel: [1099245.588034] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Apr 14 21:35:16 coyote kernel: [1099245.596577] ata2.00: ATA-8: ST31000340AS, SD1A, max UDMA/133 Apr 14 21:35:16 coyote kernel: [1099245.596582] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) Apr 14 21:35:16 coyote kernel: [1099245.612502] ata2.00: configured for UDMA/133 Apr 14 21:35:16 coyote kernel: [1099245.612512] ata2: EH complete Apr 14 21:35:16 coyote kernel: [1099245.612633] scsi 1:0:0:0: Direct-Access ATA ST31000340AS SD1A PQ: 0 ANSI: 5 Apr 14 21:35:16 coyote kernel: [1099245.612851] sd 1:0:0:0: Attached scsi generic sg5 type 0 Apr 14 21:35:16 coyote kernel: [1099245.612895] sd 1:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Apr 14 21:35:16 coyote kernel: [1099245.612993] sd 1:0:0:0: [sde] Write Protect is off Apr 14 21:35:16 coyote kernel: [1099245.613034] sd 1:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 21:35:16 coyote kernel: [1099245.665063] sde: sde1 sde2 sde3 Apr 14 21:35:16 coyote kernel: [1099245.665558] sd 1:0:0:0: [sde] Attached SCSI disk Essentially normal except if I try to write to it, it will go read-only immediately. These 2 new drives are sata-3, 6Gb/sec drives. From the logs, the driver had set it down to 1.5Gbs in an attempt to talk to it, but obviously failed. The motherboard book only claims 3Gbs. Have I a duff drive, or, is either this kernel, or this Asus M2N-SLI Deluxe motherboard incapable of dealing with a 6Gb/sec, 2Tb drive with 4096 byte physical sectors? Or maybe a drive that needs a firmware update? All of those 1T's needed it before they settled down and Just Worked for several years. FWIW, the 1Tb drive as my main boot, is also a 4096 byte physical sector drive and seems to be ok AFTER I finally got an "aligned" partitioning scheme setup. Basically with a pair of drives this big, I am walking on brand new dirt here. Opinions, swags anybody? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201504142230.25345.ghesk...@wdtv.com
