Problems with second hard drive

I bought my PowerMac G5 new in 2005 and about two years after I got it, I installed a second internal hard drive. I didn't have any problems with the drive until about six months ago (which was when I moved, but I'm not sure if that has anything to do with it). Around that point, I started hearing a single, loud click followed by a slight winding down noise. Then, my computer would almost completely freeze. After a few moments, I would hear a bunch of soft clicks and my computer would go back to normal. I figured that it was a problem with one of the hard drives, but I wasn't sure what to do.
Later on, the problem got more severe, lasting more like 30 seconds. When my second drive unmounted during one of these episodes, I shut my computer down, opened the case, took both plugs out of the second hard drive, put them back in, and started up my computer again. After that, my computer was running great again. But, a few weeks later, the symptoms started up again.
So, I've gone through the same cable un-plug and re-plug process whenever the drive unmounts. Sometimes it helps and sometimes it doesn't seem to help at all. Altogether, I think that the second drive has unmounted about five or six times. I haven't had this problem at all with the original hard drive and I haven't noticed any other problems with my computer. (Well, okay, there's the rare occasion when, instead of going to sleep, it turns the screen black and puts the fans on full blast.)
Could the drive itself be going bad and it has nothing to do with the cables? I have a utility installed that always monitors the SMART status and it hasn't reported any problems. Are there any other troubleshooting steps I should take? Any advice would be appreciated. Thanks!

Before I bought DiskWarrior, I thought I'd try some troubleshooting with the software I have on hand. But while I was doing that, the problem got worse. Now, I'm having major problems just getting the computer to boot. I'll give you the rundown on what's happened. It goes through a few boneheaded twists and turns and goes on at great length, but I thought I'd relate it all in the hopes that someone can see a likely pattern.
My first thought was the Apple hardware test, which I had thought was on the Mac OS 10.5 install DVD. So naturally, I didn't see the hardware test listed under Utilities. But while I had it up, I used Disk Utility to do repairs on both hard drives (checking both the disk and permissions). It found no problems on the 2nd hard drive, but found a few errors with "leaves" on the booting drive. It also found a bunch of issues with the permissions, but I don't think it was anything out of the ordinary.
Just for the heck of it, I asked it to run the repairs again. Not long into that, I got what I think is a kernel panic (overlaid message saying I needed to restart my computer in a few languages). It also sped up the fans.
I pushed the power button to shut it down, then started it up again. I heard the startup chime, then nothing but a black screen and the ol' hyperactive fans. I went through that several times before I was finally able to boot from the DVD again. Then, I changed the startup disk back to my usual boot volume and restarted. I had to go through the black screen and insane fans several more times before I could boot normally.
Next, I thought I'd try OnyX to see what it could do. Which might not be much, but I had it repair the disks again and also had it run the daily, weekly, and monthly maintenance scripts.
I checked into the black screen & hyperactive fans booting problem elsewhere in the forums, and saw that it was recommended to run the Apple hardware test and also found the correct procedure for doing so, which was to insert the PowerMac G5 install disc (not the Mac OS X upgrade DVD) and press Option when booting. I loaded the disc, restarted, and held down the Option key, but before I could get anything to actually load, I had several more sessions with the black screen of fans.
Regarding that boot problem, I've sometimes seen the red light inside the case turn on almost immediately after I turn on the computer. Other times, it will not light up by itself. But, when I hold the power button in to shut it down, the red light briefly turns on before the unit shuts down. I've also noticed that the light on the Caps Lock button is coming on and staying on when I'm trying to start the computer.
So, after several tries, I checked my G5 User's Guide and it said to disconnect any external devices before trying the hardware test. I had a USB thumb drive plugged in and a FireWire drive hooked up for Time Machine backups, so I took both of them out. Once again, I tried starting up with Option held down and this time, it worked. The fans started running at full blast after I selected the hardware test, which I hoped was normal. So, I asked it to run the extended test and it found no problems. I restarted my computer without reconnecting anything and, at least for now, it's working normally.
Any new thoughts?

Similar Messages

  • [SOLVED] Problem with second SATA drive

    My laptop has two hard drive bays, and just recently I added a second SATA drive (moved it from my old laptop) to the extra bay.
    Now, anytime the second hard drive /dev/sdb has any heavy disk activity, it appears to cause a shutdown of the SATA port for the first drive (/dev/sda)!  Though the second drive is still fine, and I can still write to it until the system crashes from the root drive (on /dev/sda) being shutdown.
    If I don't mount and use the second drive, the first drive works just fine, and I can pound it with traffic without issue.
    I can reproduce this problem by copying large amounts of data to drive 2.
    This is when I get in my dmesg when the first SATA drive shuts down:
    [ 3013.249525] ata1.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x6 frozen
    [ 3013.249532] ata1.00: failed command: READ FPDMA QUEUED
    [ 3013.249539] ata1.00: cmd 60/08:00:78:b8:ba/00:00:24:00:00/40 tag 0 ncq 4096 in
    [ 3013.249539] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
    [ 3013.249543] ata1.00: status: { DRDY }
    [ 3013.249545] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249559] ata1.00: cmd 61/08:08:b8:60:7b/00:00:29:00:00/40 tag 1 ncq 4096 out
    [ 3013.249559] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249562] ata1.00: status: { DRDY }
    [ 3013.249564] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249568] ata1.00: cmd 61/08:10:c0:60:7b/00:00:29:00:00/40 tag 2 ncq 4096 out
    [ 3013.249568] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249570] ata1.00: status: { DRDY }
    [ 3013.249572] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249576] ata1.00: cmd 61/08:18:c8:60:7b/00:00:29:00:00/40 tag 3 ncq 4096 out
    [ 3013.249576] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249578] ata1.00: status: { DRDY }
    [ 3013.249580] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249585] ata1.00: cmd 61/08:20:48:12:d7/00:00:18:00:00/40 tag 4 ncq 4096 out
    [ 3013.249585] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249587] ata1.00: status: { DRDY }
    [ 3013.249589] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249593] ata1.00: cmd 61/08:28:28:63:38/00:00:19:00:00/40 tag 5 ncq 4096 out
    [ 3013.249593] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249595] ata1.00: status: { DRDY }
    [ 3013.249597] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249601] ata1.00: cmd 61/08:30:28:6f:38/00:00:19:00:00/40 tag 6 ncq 4096 out
    [ 3013.249601] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249603] ata1.00: status: { DRDY }
    [ 3013.249605] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249609] ata1.00: cmd 61/08:38:28:98:ae/00:00:25:00:00/40 tag 7 ncq 4096 out
    [ 3013.249609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249611] ata1.00: status: { DRDY }
    [ 3013.249613] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249617] ata1.00: cmd 61/08:40:d8:79:3b/00:00:25:00:00/40 tag 8 ncq 4096 out
    [ 3013.249617] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249619] ata1.00: status: { DRDY }
    [ 3013.249621] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249625] ata1.00: cmd 61/08:48:08:98:b6/00:00:18:00:00/40 tag 9 ncq 4096 out
    [ 3013.249625] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249627] ata1.00: status: { DRDY }
    [ 3013.249629] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 3013.249633] ata1.00: cmd 61/08:50:10:98:36/00:00:19:00:00/40 tag 10 ncq 4096 out
    [ 3013.249633] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3013.249636] ata1.00: status: { DRDY }
    [ 3013.249640] ata1: hard resetting link
    [ 3013.575549] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 3013.576784] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [ 3013.578334] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [ 3013.578588] ata1.00: configured for UDMA/133
    [ 3013.592223] ata1.00: device reported invalid CHS sector 0
    [ 3013.592233] ata1.00: device reported invalid CHS sector 0
    [ 3013.592238] ata1.00: device reported invalid CHS sector 0
    [ 3013.592242] ata1.00: device reported invalid CHS sector 0
    [ 3013.592246] ata1.00: device reported invalid CHS sector 0
    [ 3013.592250] ata1.00: device reported invalid CHS sector 0
    [ 3013.592254] ata1.00: device reported invalid CHS sector 0
    [ 3013.592258] ata1.00: device reported invalid CHS sector 0
    [ 3013.592263] ata1.00: device reported invalid CHS sector 0
    [ 3013.592267] ata1.00: device reported invalid CHS sector 0
    [ 3013.592271] ata1.00: device reported invalid CHS sector 0
    [ 3013.592302] sd 0:0:0:0: [sda]
    [ 3013.592306] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592310] sd 0:0:0:0: [sda]
    [ 3013.592313] Sense Key : 0xb [current] [descriptor]
    [ 3013.592320] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592323] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592342] 00 00 00 00
    [ 3013.592351] sd 0:0:0:0: [sda]
    [ 3013.592353] ASC=0x0 ASCQ=0x0
    [ 3013.592358] sd 0:0:0:0: [sda] CDB:
    [ 3013.592361] cdb[0]=0x28: 28 00 24 ba b8 78 00 00 08 00
    [ 3013.592376] end_request: I/O error, dev sda, sector 616216696
    [ 3013.592414] sd 0:0:0:0: [sda]
    [ 3013.592417] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592421] sd 0:0:0:0: [sda]
    [ 3013.592423] Sense Key : 0xb [current] [descriptor]
    [ 3013.592428] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592431] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592449] 00 00 00 00
    [ 3013.592458] sd 0:0:0:0: [sda]
    [ 3013.592460] ASC=0x0 ASCQ=0x0
    [ 3013.592465] sd 0:0:0:0: [sda] CDB:
    [ 3013.592467] cdb[0]=0x2a: 2a 00 29 7b 60 b8 00 00 08 00
    [ 3013.592482] end_request: I/O error, dev sda, sector 695951544
    [ 3013.592505] sd 0:0:0:0: [sda]
    [ 3013.592508] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592512] sd 0:0:0:0: [sda]
    [ 3013.592514] Sense Key : 0xb [current] [descriptor]
    [ 3013.592519] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592522] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592540] 00 00 00 00
    [ 3013.592549] sd 0:0:0:0: [sda]
    [ 3013.592551] ASC=0x0 ASCQ=0x0
    [ 3013.592556] sd 0:0:0:0: [sda] CDB:
    [ 3013.592558] cdb[0]=0x2a: 2a 00 29 7b 60 c0 00 00 08 00
    [ 3013.592572] end_request: I/O error, dev sda, sector 695951552
    [ 3013.592583] sd 0:0:0:0: [sda]
    [ 3013.592586] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592589] sd 0:0:0:0: [sda]
    [ 3013.592592] Sense Key : 0xb [current] [descriptor]
    [ 3013.592597] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592599] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592618] 00 00 00 00
    [ 3013.592626] sd 0:0:0:0: [sda]
    [ 3013.592628] ASC=0x0 ASCQ=0x0
    [ 3013.592632] sd 0:0:0:0: [sda] CDB:
    [ 3013.592635] cdb[0]=0x2a: 2a 00 29 7b 60 c8 00 00 08 00
    [ 3013.592649] end_request: I/O error, dev sda, sector 695951560
    [ 3013.592665] sd 0:0:0:0: [sda]
    [ 3013.592668] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592671] sd 0:0:0:0: [sda]
    [ 3013.592673] Sense Key : 0xb [current] [descriptor]
    [ 3013.592678] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592684] Aborting journal on device dm-0-8.
    [ 3013.592701] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
    [ 3013.592687] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592723] 00 00 00 00
    [ 3013.592729] sd 0:0:0:0: [sda]
    [ 3013.592730] ASC=0x0 ASCQ=0x0
    [ 3013.592733] sd 0:0:0:0: [sda] CDB:
    [ 3013.592735] cdb[0]=0x2a: 2a 00 18 d7 12 48 00 00 08 00
    [ 3013.592744] end_request: I/O error, dev sda, sector 416748104
    [ 3013.592752] Buffer I/O error on device dm-0, logical block 266057
    [ 3013.592760] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902184 (offset 258048 size 4096 starting block 266057)
    [ 3013.592766] sd 0:0:0:0: [sda]
    [ 3013.592768] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592771] sd 0:0:0:0: [sda]
    [ 3013.592772] Sense Key : 0xb [current] [descriptor]
    [ 3013.592776] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592778] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592790] 00 00 00 00
    [ 3013.592795] sd 0:0:0:0: [sda]
    [ 3013.592797] ASC=0x0 ASCQ=0x0
    [ 3013.592800] sd 0:0:0:0: [sda] CDB:
    [ 3013.592801] cdb[0]=0x2a: 2a 00 19 38 63 28 00 00 08 00
    [ 3013.592811] end_request: I/O error, dev sda, sector 423125800
    [ 3013.592817] Buffer I/O error on device dm-0, logical block 1063269
    [ 3013.592822] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5898577 (offset 970752 size 4096 starting block 1063269)
    [ 3013.592842] sd 0:0:0:0: [sda]
    [ 3013.592845] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592849] sd 0:0:0:0: [sda]
    [ 3013.592851] Sense Key : 0xb [current] [descriptor]
    [ 3013.592856] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592859] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592877] 00 00 00 00
    [ 3013.592885] sd 0:0:0:0: [sda]
    [ 3013.592887] ASC=0x0 ASCQ=0x0
    [ 3013.592892] sd 0:0:0:0: [sda] CDB:
    [ 3013.592894] cdb[0]=0x2a: 2a 00 19 38 6f 28 00 00 08 00
    [ 3013.592908] end_request: I/O error, dev sda, sector 423128872
    [ 3013.592915] Buffer I/O error on device dm-0, logical block 1063653
    [ 3013.592922] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902187 (offset 1171456 size 4096 starting block 1063653)
    [ 3013.592931] sd 0:0:0:0: [sda]
    [ 3013.592934] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.592937] sd 0:0:0:0: [sda]
    [ 3013.592940] Sense Key : 0xb [current] [descriptor]
    [ 3013.592945] Descriptor sense data with sense descriptors (in hex):
    [ 3013.592947] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.592966] 00 00 00 00
    [ 3013.592974] sd 0:0:0:0: [sda]
    [ 3013.592976] ASC=0x0 ASCQ=0x0
    [ 3013.592980] sd 0:0:0:0: [sda] CDB:
    [ 3013.592983] cdb[0]=0x2a: 2a 00 25 ae 98 28 00 00 08 00
    [ 3013.592997] end_request: I/O error, dev sda, sector 632199208
    [ 3013.593006] Buffer I/O error on device dm-0, logical block 27197445
    [ 3013.593018] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 6425165 (offset 151552 size 4096 starting block 27197445)
    [ 3013.593028] sd 0:0:0:0: [sda]
    [ 3013.593031] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.593034] sd 0:0:0:0: [sda]
    [ 3013.593037] Sense Key : 0xb [current] [descriptor]
    [ 3013.593042] Descriptor sense data with sense descriptors (in hex):
    [ 3013.593045] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.593063] 00 00 00 00
    [ 3013.593071] sd 0:0:0:0: [sda]
    [ 3013.593073] ASC=0x0 ASCQ=0x0
    [ 3013.593078] sd 0:0:0:0: [sda] CDB:
    [ 3013.593085] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
    [ 3013.593089] cdb[0]=0x2a: 2a 00 25 3b 79 d8 00 00 08 00
    [ 3013.593104] end_request: I/O error, dev sda, sector 624654808
    [ 3013.593111] Buffer I/O error on device dm-0, logical block 26254395
    [ 3013.593115] lost page write due to I/O error on dm-0
    [ 3013.593126] sd 0:0:0:0: [sda]
    [ 3013.593129] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.593132] sd 0:0:0:0: [sda]
    [ 3013.593135] Sense Key : 0xb [current] [descriptor]
    [ 3013.593140] Descriptor sense data with sense descriptors (in hex):
    [ 3013.593142] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.593161] 00 00 00 00
    [ 3013.593169] sd 0:0:0:0: [sda]
    [ 3013.593171] ASC=0x0 ASCQ=0x0
    [ 3013.593175] sd 0:0:0:0: [sda] CDB:
    [ 3013.593178] cdb[0]=0x2a: 2a 00 18 b6 98 08 00 00 08 00
    [ 3013.593192] end_request: I/O error, dev sda, sector 414619656
    [ 3013.593198] Buffer I/O error on device dm-0, logical block 1
    [ 3013.593201] lost page write due to I/O error on dm-0
    [ 3013.593211] sd 0:0:0:0: [sda]
    [ 3013.593213] Result: hostbyte=0x00 driverbyte=0x08
    [ 3013.593217] sd 0:0:0:0: [sda]
    [ 3013.593219] Sense Key : 0xb [current] [descriptor]
    [ 3013.593224] Descriptor sense data with sense descriptors (in hex):
    [ 3013.593227] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3013.593245] 00 00 00 00
    [ 3013.593253] sd 0:0:0:0: [sda]
    [ 3013.593256] ASC=0x0 ASCQ=0x0
    [ 3013.593260] sd 0:0:0:0: [sda] CDB:
    [ 3013.593262] cdb[0]=0x2a: 2a 00 19 36 98 10 00 00 08 00
    [ 3013.593277] end_request: I/O error, dev sda, sector 423008272
    [ 3013.593283] Buffer I/O error on device dm-0, logical block 1048578
    [ 3013.593286] lost page write due to I/O error on dm-0
    [ 3013.593298] ata1: EH complete
    [ 3013.595707] EXT4-fs error (device dm-0) in ext4_dirty_inode:4603: Journal has aborted
    [ 3013.596581] EXT4-fs error (device dm-0): ext4_journal_start_sb:370: Detected aborted journal
    [ 3013.596591] EXT4-fs (dm-0): Remounting filesystem read-only
    [ 3020.421558] journal commit I/O error
    [ 3020.421570] journal commit I/O error
    [ 3020.421574] journal commit I/O error
    [ 3020.421578] journal commit I/O error
    [ 3020.421581] journal commit I/O error
    [ 3147.052191] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
    [ 3147.052197] ata1.00: failed command: READ FPDMA QUEUED
    [ 3147.052209] ata1.00: cmd 60/50:00:d0:48:99/00:00:1c:00:00/40 tag 0 ncq 40960 in
    [ 3147.052209] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
    [ 3147.052212] ata1.00: status: { DRDY }
    [ 3147.052213] ata1.00: failed command: READ FPDMA QUEUED
    [ 3147.052218] ata1.00: cmd 60/18:08:28:49:99/00:00:1c:00:00/40 tag 1 ncq 12288 in
    [ 3147.052218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3147.052220] ata1.00: status: { DRDY }
    [ 3147.052221] ata1.00: failed command: READ FPDMA QUEUED
    [ 3147.052226] ata1.00: cmd 60/88:10:48:49:99/00:00:1c:00:00/40 tag 2 ncq 69632 in
    [ 3147.052226] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3147.052228] ata1.00: status: { DRDY }
    [ 3147.052229] ata1.00: failed command: READ FPDMA QUEUED
    [ 3147.052234] ata1.00: cmd 60/20:18:00:a4:ba/00:00:24:00:00/40 tag 3 ncq 16384 in
    [ 3147.052234] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 3147.052236] ata1.00: status: { DRDY }
    [ 3147.052239] ata1: hard resetting link
    [ 3147.378368] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 3148.066853] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded
    [ 3148.069139] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [ 3148.069393] ata1.00: configured for UDMA/133
    [ 3148.080059] ata1.00: device reported invalid CHS sector 0
    [ 3148.080066] ata1.00: device reported invalid CHS sector 0
    [ 3148.080071] ata1.00: device reported invalid CHS sector 0
    [ 3148.080075] ata1.00: device reported invalid CHS sector 0
    [ 3148.080112] sd 0:0:0:0: [sda]
    [ 3148.080114] Result: hostbyte=0x00 driverbyte=0x08
    [ 3148.080117] sd 0:0:0:0: [sda]
    [ 3148.080118] Sense Key : 0xb [current] [descriptor]
    [ 3148.080123] Descriptor sense data with sense descriptors (in hex):
    [ 3148.080125] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3148.080136] 00 00 00 00
    [ 3148.080140] sd 0:0:0:0: [sda]
    [ 3148.080142] ASC=0x0 ASCQ=0x0
    [ 3148.080145] sd 0:0:0:0: [sda] CDB:
    [ 3148.080146] cdb[0]=0x28: 28 00 1c 99 48 d0 00 00 50 00
    [ 3148.080156] end_request: I/O error, dev sda, sector 479807696
    [ 3148.080170] sd 0:0:0:0: [sda]
    [ 3148.080171] Result: hostbyte=0x00 driverbyte=0x08
    [ 3148.080173] sd 0:0:0:0: [sda]
    [ 3148.080175] Sense Key : 0xb [current] [descriptor]
    [ 3148.080178] Descriptor sense data with sense descriptors (in hex):
    [ 3148.080180] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3148.080190] 00 00 00 00
    [ 3148.080195] sd 0:0:0:0: [sda]
    [ 3148.080196] ASC=0x0 ASCQ=0x0
    [ 3148.080199] sd 0:0:0:0: [sda] CDB:
    [ 3148.080200] cdb[0]=0x28: 28 00 1c 99 49 28 00 00 18 00
    [ 3148.080209] end_request: I/O error, dev sda, sector 479807784
    [ 3148.080216] sd 0:0:0:0: [sda]
    [ 3148.080218] Result: hostbyte=0x00 driverbyte=0x08
    [ 3148.080220] sd 0:0:0:0: [sda]
    [ 3148.080221] Sense Key : 0xb [current] [descriptor]
    [ 3148.080224] Descriptor sense data with sense descriptors (in hex):
    [ 3148.080225] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3148.080236] 00 00 00 00
    [ 3148.080241] sd 0:0:0:0: [sda]
    [ 3148.080242] ASC=0x0 ASCQ=0x0
    [ 3148.080245] sd 0:0:0:0: [sda] CDB:
    [ 3148.080246] cdb[0]=0x28: 28 00 1c 99 49 48 00 00 88 00
    [ 3148.080254] end_request: I/O error, dev sda, sector 479807816
    [ 3148.080267] sd 0:0:0:0: [sda]
    [ 3148.080268] Result: hostbyte=0x00 driverbyte=0x08
    [ 3148.080270] sd 0:0:0:0: [sda]
    [ 3148.080272] Sense Key : 0xb [current] [descriptor]
    [ 3148.080274] Descriptor sense data with sense descriptors (in hex):
    [ 3148.080276] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 3148.080287] 00 00 00 00
    [ 3148.080291] sd 0:0:0:0: [sda]
    [ 3148.080293] ASC=0x0 ASCQ=0x0
    [ 3148.080295] sd 0:0:0:0: [sda] CDB:
    [ 3148.080296] cdb[0]=0x28: 28 00 24 ba a4 00 00 00 20 00
    [ 3148.080305] end_request: I/O error, dev sda, sector 616211456
    [ 3148.080315] ata1: EH complete
    I have experimented, and found that if I turn off NCQ on the kernel command line in my bootloader (libata.force=noncq), that it takes longer before the problem occurs.  Though, if I write enough to the second drive, it does still happen after a while, just greatly reduced its chances of happening.
    Is it possible that the old drive (sdb) is causing the problem?  I noticed that it is much noisier than I remember when the drive head moves around.
    Another curiosity while I was trying to duplicate the problem:
      - I start a large file copy from sda -> sdb
      - At the same time in another terminal, I do "find / -print"
      - When I hear the drive 2 head moving, it pauses the output of the "find" command.
    Every time I hear the head move, I see the find output pause.  Its almost like the drive seek on drive 2 causes the whole Sata controller to pause while the head moves.  Very odd!
    Anyone have any ideas?   I think the next thing I will try is borrow a drive from another machine, and do the big write to it to see if I get the same results.
    If it is of any help, here is some more info on the laptop:
    lspci:
    00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
    00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
    00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
    00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
    00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
    00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
    00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
    00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
    01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
    01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1)
    07:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)
    0d:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5e)
    13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
    13:00.1 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
    19:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
    cat /proc/interrupts:
    CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
    0: 50 0 0 0 0 0 0 0 IO-APIC-edge timer
    1: 958 0 0 0 0 0 0 0 IO-APIC-edge i8042
    8: 1 0 0 0 0 0 0 0 IO-APIC-edge rtc0
    9: 1675 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi
    12: 12257 0 0 0 0 0 0 0 IO-APIC-edge i8042
    16: 24769 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1, mmc0, nvidia
    17: 142 0 0 0 0 0 0 0 IO-APIC-fasteoi snd_hda_intel
    19: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi rts_pstor
    23: 1937 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb4
    41: 1 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    42: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    43: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    44: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    45: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    46: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    47: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    48: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
    49: 19406 0 0 0 0 0 0 0 PCI-MSI-edge iwlwifi
    50: 36099 0 0 0 0 0 0 0 PCI-MSI-edge ahci
    51: 14 0 0 0 0 0 0 0 PCI-MSI-edge mei
    52: 386378 0 0 0 0 0 0 0 PCI-MSI-edge snd_hda_intel
    53: 56803 0 0 0 0 0 0 0 PCI-MSI-edge eth0
    NMI: 34 5 19 5 18 4 13 4 Non-maskable interrupts
    LOC: 77964 17705 161241 14302 187823 16150 56845 12750 Local timer interrupts
    SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
    PMI: 34 5 19 5 18 4 13 4 Performance monitoring interrupts
    IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts
    RTR: 7 0 0 0 0 0 0 0 APIC ICR read retries
    RES: 13721 7023 304 110 175 110 213 123 Rescheduling interrupts
    CAL: 6941 7677 2774 7670 5804 7568 7655 7673 Function call interrupts
    TLB: 366 545 268 179 310 272 212 166 TLB shootdowns
    TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
    THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
    MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
    MCP: 29 29 29 29 29 29 29 29 Machine check polls
    ERR: 0
    MIS: 0
    smartctl --all /dev/sda
    smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
    Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
    === START OF INFORMATION SECTION ===
    Device Model: ST9500423AS
    Serial Number: 5WS354LM
    LU WWN Device Id: 5 000c50 044bb741b
    Firmware Version: 0005DEM1
    User Capacity: 500,107,862,016 bytes [500 GB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Device is: Not in smartctl database [for details use: -P showall]
    ATA Version is: 8
    ATA Standard is: ATA-8-ACS revision 4
    Local Time is: Thu Sep 13 15:26:14 2012 CDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 0) seconds.
    Offline data collection
    capabilities: (0x73) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 105) minutes.
    Conveyance self-test routine
    recommended polling time: ( 3) minutes.
    SCT capabilities: (0x303f) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail Always - 54715920
    3 Spin_Up_Time 0x0003 098 098 085 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1114
    5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 069 060 030 Pre-fail Always - 10214892
    9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2030
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 559
    184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
    187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
    188 Command_Timeout 0x0032 100 098 000 Old_age Always - 8590065667
    189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 053 049 045 Old_age Always - 47 (Min/Max 47/51)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 17
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 871
    193 Load_Cycle_Count 0x0032 039 039 000 Old_age Always - 122293
    194 Temperature_Celsius 0x0022 047 051 000 Old_age Always - 47 (0 17 0 0 0)
    195 Hardware_ECC_Recovered 0x001a 113 099 000 Old_age Always - 54715920
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67229123085518
    241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1947733828
    242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2798982459
    254 Free_Fall_Sensor 0x0032 001 001 000 Old_age Always - 899
    SMART Error Log Version: 1
    ATA Error Count: 8 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 8 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    a1 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
    a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
    Error 7 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    04 71 09 a9 00 80 e0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
    a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
    Error 6 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
    a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
    Error 5 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    04 71 09 a9 00 80 e0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
    a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
    2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
    Error 4 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
    2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
    61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
    61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed without error 00% 6 -
    # 2 Short offline Aborted by host 90% 1 -
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    smartctl --all /dev/sdb
    smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
    Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
    === START OF INFORMATION SECTION ===
    Model Family: SAMSUNG SpinPoint M6
    Device Model: SAMSUNG HM320JI
    Serial Number: S16LJF0QB02815
    LU WWN Device Id: 5 0f0000 001202815
    Firmware Version: 2SS00_01
    User Capacity: 320,072,933,376 bytes [320 GB]
    Sector Size: 512 bytes logical/physical
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 7
    ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
    Local Time is: Thu Sep 13 15:27:10 2012 CDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 110) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 110) minutes.
    SCT capabilities: (0x003f) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
    3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2562
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 810
    5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000e 252 252 051 Old_age Always - 0
    8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
    9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 4842
    10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 440
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 154
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 71
    194 Temperature_Celsius 0x0022 073 073 000 Old_age Always - 55 (Min/Max 17/55)
    195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1
    196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0012 252 252 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
    200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0
    201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0
    223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 534
    225 Load_Cycle_Count 0x0032 077 077 000 Old_age Always - 236803
    SMART Error Log Version: 1
    No Errors Logged
    SMART Self-test log structure revision number 1
    No self-tests have been logged. [To run self-tests, use: smartctl -t]
    Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
    SMART Selective self-test log data structure revision number 0
    Note: revision number not 1 implies that no selective self-test has ever been run
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Last edited by johni (2012-09-16 00:46:54)

    It appears my drive one really is failing.  It was the first drive and not the second making the loud head seek sound.  I borrowed another drive from a friend, and copied my drive one to it.   No problems with the new drive in place.

  • Problems installing second hard drive and second DVD recorder

    I have tried about every combination of tricks to install a second hard drive.  I want to add a 250GB, WD IDE hard drive to my 3000J 115 7387A32 on the IDE channel.  I have set up the bios then added the drive and the reverse but cannot get computer to boot in either case.  It locks on the first screen where is says hit Enter to.... Enter makes the text go away, but nothing after. I am trying to install it as a single drive on the secondary IDE channel. 
    I know the HD is good as I removed it from another computer.  It does have Win XP on it.  I will format it using Vista IF I can get it installed.
    Basically, I am having the same problems within stalling the second DVD, which is SATA.

    Your initial hard drive should be jumpered as Master. When you install a second hard drive it must be jumpered Slave. There should be a diagram on the case of the HD showing the jumper locations.
    Power Macintosh G3 and G4: IDE Master and Slave Support and Configuration
    http://docs.info.apple.com/article.html?artnum=24342
    Power Mac G4: Installing Internal Storage Devices
    http://support.apple.com/kb/HT1815
     Cheers, Tom

  • Problems installing second hard drive in HP Pavilion M7-1015dx laptop.

    I just bought a new HP Pavilion M7-1015dx. I have successfully installed an SSD drive as the primary hard drive and now I want to use the 1tb hard drive that the computer came with as data and install it in the second hard drive bay. I have a cable that I used from my old HP DV7 when I had a second hard drive but I am having issues with my M7-1015dx laptop.
    When I plug the sata cable into the second connector on the laptop and attach my hard drive (I have tried several hard drives) and go to power the laptop on, the power light just blinks a few times. Now I know there is something wrong for I just purchased the laptop two days ago... I got the idea to try the cable that I used to plug into the second connect to check and see if I plugged it into the first and I got the same issue, power light blinking. So I am wondering if it is the cable... is this possible? Are there different rated sata cables? I also tried the cable the came with my new laptop to make sure that it just wasn't the second port - I tried plugging it in to the second port with a hard drive attached and the laptop this time turned on but asked for a bootable disk because it requires boot disk to be in the 1st hard drive bay connection which I knew. I just want to give all the information so that I can get this fixed.
    Please help me

    Hey Brother-Brad, 
    I'm sorry you're running into issues installing a second hard drive. Your issue may not be the cable. Do you have a working hard drive installed currently with Window on it? 
    If so, 
    1. In Windows, Click the Start button.
    2. Type 'hard disk'
    3. Click on 'Create and format hard disk partitions' (aka Disk Management)
    4. Look at Disk 0 listed at the bottom in the middle. Does it say Basic or Dynamic?
    5. If it says Basic, right-click it and select Convert to Dynamic.
    Hard drives must be set as Dynamic for dual hard drives to be recognized.
    Let me know the results when you get a chance

  • InDesign CS2 has problems with multiple hard drives

    I have a mac pro that has two external hard drives attached to it. One is connected through usb and the other firewire. When ever I try to open an inDesign file on the hard drive that mounted second I get an error message. However I the hard drive that mounted first works just fine.
    The error message is: "Cannot open the document xxx. You may not have permission or the document may be open already. For multi-user access, close the file and then lock it using the File > Get Info command in the Finder."
    Any help would be greatly appreciated.

    I've not had any such problem. It's been a while since I used CS2, but I definitely used it on computers with more than one disk attached. I don't think I had a mix of FireWire and USB drives though.
    Dave

  • Dual Booting with second hard drive

    Okay so I just ordered an enclosure to replace my optical drive with my old HDD. I have already put an SSD where the old HDD was and I could really use some more storage space for video projects. Also, I want to dual boot Ubuntu on this machine. I am wondering what the best way to go about that would be for performance. Should I make a scond partition on the SSD or use the HDD that I am putting in the optical drive bay for Ubuntu? And how can I use the extra HDD space to store data from both operating systems? Any help is greatly appreciated.

    It seems that I have run into a problem. After doing a little more reading, it looks like mavericks will not allow me to dual boot. Also, a clarification to an earlier post I do NOT want to run virtual machine. Could I get around this problem by doing what you, LowLuster, suggested at first. Putting Ubuntu on the second drive by replacing the disk drive and installing that way, then putting bot drives into the machine? Also, the hard drive I am putting in place of the disk drive is 750Gb. I do not need 750Gb of space for Ubuntu. Is there a way to use the rest of that hard drive as storage for Mac OS?

  • Error code 36 (problems with external hard drive)

    I have just upgraded to Yosemite and am now having major problem with my external western digital hard drive.  I cannot create new folders and when I hit command N I get error code 36.  I also cannot move files from one folder to the next.  When I try to move them I get the error message: "The operation cannot be completed because a file of that name already exists" and that simply isn't true.  None of the files' names exist in the other folder.

    Ok, It appears to be the fault of Western Digital.  I ejected the hard drive and then plugged it back in and it said that the drive was broken but I could still read the files and it told me to save the files on another disk and reformat.  So it was just a coincidence that I upgraded to Yosemite at the same time that my external hard drive broke.

  • Backup problems with external hard drive

    I bought a WD passport external hard drive and copied my itunes library onto a file there. I re-set the location of the library on itunes to the drive on the external hard drive. So far I have not deleted anything from my computer hard drive. However, when I am in itunes and click onto a song, nothing comes out of my speakers. Everything looks normal, as if the track is playing, but nothing is happening. I tried buying a new track off of itunes online, downloaded it, and installed it on my ipod; it plays fine, on my ipod, but will not play on the computer. Something is obviously wrong, but I can't figure out what has happened. Any help out there?
    Thanks!
    Delany

    It sounds to me like your iMac is on it's last legs....at least the internal hard drive. If you can't make a new Time Machine backup I would advise you replace your iMac as soon as possible.
    Assuming your three-week old backup is sound you should have no problems moving everything over to a new Mac. I would recommend you use the Setup Assistant that appears when you start up the new Mac (and note: It only appears the first time you start the new Mac; you can move everything over later on via Migration Assistant, but you may see issues with accounts if you opt for that route).
    I don't think you need the Genius Desk for Setup Assistant. You only have to power up the new iMac, answer a few questions....select "....From Another Disk..." When it asks how you want to move everything over....connect up your Iomega external drive...and wait for it to finish. (Could take several hours depending on the amount of data you're moving).
    A couple of notes:
    1.  If your Iomega is a Firewire drive you'll need a Firewire to Thunderbolt adapter to connect it to your new iMac.
    2.  If you need to load CDs or DVDs remember the new iMacs don't contain an optical drive. You would need to get an Apple SuperDrive or third part external burner if you need that functionality.
    I'm puzzled by the comment made in Seventy One's post questioning the reliability of the new iMacs. I upgraded from a 24" early 2008 model to a 27" model and everything works flawlessly. I hardly ever see the beachball anymore.

  • Problem with upgrading hard drive in 2009 Macbook Pro with Snow Leopard

    Current drive is 320gb with fresh install of OS SL updated with some other programs installed.  New drive is Seagate Momentus 750, same brand and model as the old, just bigger.
    I install the new drive, boot off the OS SL CD and go into disk utility.  Partition and format with GUID and Journaled. Install starts and ultimately fails every time.
    Tried to clone the 320 by putting it in the macbook, use the 750 via usb/sata.  Drive restores, but it is unreliable in loading and stability.  When it gets to the grey screen, it alternately flickers the Apple, Folder and NO sign.  Sometimes it loads, sometimes it just keeps spinning.  When it does load, it's slow and programs that take more power crash.
    Brought it to Apple.  They said it was a problem in the SMART section, so I got a new drive under warranty.  This is the THIRD drive i've gotten from Seagate.  Still doesn't work.
    I've countlessly repaired and verified the drive.  Helps to load sometimes, but not all the time. 
    If I put the 320 back in, everything works great.
    Thanks.
    -Ben

    Is there a quality external enclosure to put the large drive in, one that has its own power supply and not rely on the port power in the MacBook/Pro? If it is a viable drive and can actually run a bootable OS X version, I'd begin to wonder after all that.
    {I'd also looked up your computer in MacTracker to see what if any limits on hardware upgrade may exist. Nothing said of direct interest to the HDD. Also in everymac.com, so there should be no surprises. Yet to have those problems is troublesome and a surprise. New drives can fail. Maybe in batches?}
    And a clone of a working system for backup could be made with a utility such as CarbonCopy cloner or superduper, etc then tested as a bootable clone, with the hard disk drive tested thoroughly before use. It also is odd that a drive of that size would act up, I see drives of even larger size offered online by reputible resellers and Mac specialist companies who have been around awhile, such as OWC. I just looked to see if there was a ceiling on support of larger size HDD capacities, and 750GB is not the largest. Maybe the series you chose could be among a troublesome batch or brand.
    http://eshop.macsales.com/MyOWC/Upgrades.cfm?model=302 has a variety of stuff, including RAM, HDD, SSD, etc. And their staff has people who know what they sell. Well, some of them do. I had called them on a topic several years ago and they didn't really have an answer (I was given an OWC dual HDD external drive & it had issues, but had never been used. It still is sitting as-new, w/o support; now obsolete.)
    I'd try a different brand and put it into an enclosure that has its own power supply, ports for USB2.0/3.0 and FW400/800, and so on. Perhaps even an OWC line item, not that I've had any valid experience with them here in AK. And ask their people about their products, get names, finger prints, mug shots...! LOL
    Good luck & happy computing!

  • Permission problems with external hard drive

    Hello there, I'm writting you from Paris but my french is just not good enough to really explain my problem. I'm no computer expert so i might not use the right name for stuff but i will try to be as clear as possible.
    I have a macbook pro 13" from early 2012 and I'm currently running Mountain lion.
    At home i use an internet modem that has an internal hard drive of 250gb. and it also gives you the possibility to conect other usb hard drives on it so you can access them through wifi.
    I currently have to usb hd of 1tb each, one i use it for Time Machine and so far it works fine and i haven't had a problem with it, all back ups have been done ok. In the other one i have all my films and tv shows and stuff like that and it is in this one that i have the problem. In certen files and folders i'm not able to do anything with them, i tried to rename them but it says i don't have the permission to do it, i tried to delet another one and it said pretty much the same thing, some other time i tried to move the file to a diferent folder it it would ask me for my password and after type it and press enter it would just not move them, no error messager or anything it just didn't do it. Most of the times i have a messager saying stuff about permission or things like i can't read the file. The thing i can't understand is that as soon as i plug the HD on my mac it works fine i can rename and change stuff, I noticed that some of the files and folders have a little lock on the corner, but they aren't the ones i tried to move or rename before and i tried already unlocking all of them but eventhough i manage to unlock them when i plug the HD back to the modem it keeps the same, can't rename or move, not even to the trash.
    Can anyone help me out here? I'll be really thankful
    Cheers!

    Drive was shot and could not rescue the information

  • Permissions problem with External Hard drive.

    Hi,
    I've been using my external hard drive for almost a year now and out of the blue last night I ran into a interesting problem. For some reason I couldn't transfer any files to a thumb drive and shortly after I realized I didn't have Read and write permissions for any files on my mac, and everything required my password to get to. I went into disk utility and repaired the permissions and the list went on forever. Upon completion of that nothing was resolved.
    SO! I popped in my Snow leopard disk and did a repair of the permissions and system through there hoping that would fix it. I than booted up the main drive and got stabbed in the face with a HUGE error message upon the apple loading screen with a "MISSING DRIVER" "KERNAL ERROR" "CORRUPT FILE" etc.
    I went back and did a restore from my external harddrive hoping that would work, and it did. I can access my time machine backups from my external harddrive but cannot do so through my own control.
    What should I do? Should I reformat my external harddrive? Which would suck because I'm a paranoid freak and if something would happen during the reformatting I will lose literally over a year of work that is crucial.
    error message upon opening my backup
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201061.png
    error message upon trying to backup
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201-1.png
    icon of backup drive
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201062.png
    Can anyone shed some light?

    nomhak wrote:
    I went back and did a restore from my external harddrive hoping that would work, and it did. I can access my time machine backups from my external harddrive but cannot do so through my own control.
    What is that, a "clone?" What do you mean by "cannot do so through my own control."?
    What should I do? Should I reformat my external harddrive? Which would suck because I'm a paranoid freak and if something would happen during the reformatting I will lose literally over a year of work that is crucial.
    Again, what's on that drive? Do you have a clone and TM backups on the same external? If so, are they in the same partition?
    error message upon trying to backup
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201-1.png
    This one says you need to repair or reformat the disk; that means your backups are corrupted.
    Try to do a +*Repair Disk+* (not permissions) on it.
    If there are errors that Disk Utility can't fix, or the +*Repair Disk+* option is grayed out (meaning OSX has already determined that it can't fix it), post back.

  • Problem with External Hard Drive - Firewire

    I have a problem with a *300GB Venus DS3 Hard Disk* / USB 2.0 - Firewire 400 (not sure if 400).
    I have a +Mac G4 (1GHz Power PC G4 / 1GB DDR SDRAM)+ running +Mac OS 10.3.9.+
    I connect Venus hard disk through USB cable and no problem. But when I want to connect it via Firewire it doesn´t appear in the desktop.
    If I go to *System Profile* it says that there is a device connected to the FireWire port but i can´t see it in the desktop and if a open *Disk Utility*, there is no other hard disk besides the internal, so I can´t mount the Venus DS3 Hard Drive.
    I looked in the internet and found this page -> http://american-media.com/support/downloadDDDS2316CBK.html
    I was about to download the *Firmware Update* but i read this:
    AMS is not held responsible for any damage caused by misusage of this utility! Use at your own risk and be aware that your warranty might be void! DO NOT CHANGE
    ANY SETTINGS WITHOUT CONSULTING TECHSUPPORT. Do not distribute or post these files on the internet!
    I searched in Internet and found that many persons had issues connecting Hard Drives using Firewire port and read some tips (like unplugging all the usb firewire devices unless mouse and keyboard, disconnect AC cable, wait 15 minutes, ...) but couldn´t fix the problem.
    I also wrote several emails to the manufacturer of Venus hard drives (American-Media) but so far no answer.
    I would really appreciate it if someone could tell me how to connect the Venus DS3 to a Mac G4 (OS 10.3.9) via FireWire.
    Thank you very much

    I suspect the problem is in the size of the drive. You say the drive was formatted for Mac and Windows. How did you do that? With older Macs, there is a 128 gB limit on drive size.
    Here is a link to a third party disk utility that claims it gets around the size limit:
    http://www.SpeedTools2.com/
    Another possibility is to connect the drive to a Windows machine and re-format it into 3 volumes, each less than 128 gB. The Mac should be able to see the partitions.
    Sidebar comments:
    • The way I read the information on the AMS web page that you cited, you do not need a driver. And that is consistent with my experience with firewire enclosures.
    • Inside the AMS enclosure, the drive is a standard ATA/IDE drive. That you can use the drive with a USB connection is proof the drive itself is working.
    • The "bridge" is a key component in FW conectivity. (That is a piece of circuitry that sits between the IDE drive and the FW connection. It is inside the enclosure.) It appears your enclosure has the Oxford 911 chipset on the bridge. That is good.

  • Is it a hardware or software problem with my hard drive?

    A few days ago, I was burning a dvd on my Powerbook G4. It was taking a few minutes and I left. When I came back the dvd burn had completed but my screen was filled with a lot of text and codes. It was also frozen, all I could do was force the machine to quit. It said I had a corrupt stack and system failure. When I tried to restart, the computer failed to find a start-up disk. Using an option key hold down on start and the OS 10.4 installation disk I was able to get started. When ran disk first aid, the internal drive had file structure problems with bit maps and trees not large enough(??), or something like that. So I asked disk first aid to repair the hard drive. It whirred, and after a bit it said the hard drive was repaired. When I restarted from the repaired drive, things seemed ok, but not for long. Again everything froze up. I repeated the option start-up and disk repair. Again the utility found problems and repaired them. Same story when I restarted.
    So next time I installed the OS 10.4 on an external fire drive and used it as the start-up disk. This seemed to work fine. After checking to make sure all my data from the failing drive was backed up to another drive (I have two ext fire-wire drives connected), I thought I would erase the affected drive and reinstall the OS. I did that, and then updated the OS to 10.4.8.
    My problem now is that whenever the computer seems to be using the internal drive, whether booted from it or not, eventually something will freeze-up. Also, I am sure this drive was s.m.a.r.t. enabled, but now it says it is not smart supported. What's happening here? I do not have a hardware test in my utilities and I do not know if I have a physical problem with the drive or a file structure problem that recurrs for some reason. What is my next move??

    Thanks for the Seagate info eww. My pb is a 800 MHz so I'll stick to finding a 120Gig HD. After my last posting, I wanted to make sure this hd was faulty and so I was running the computer booted up from the suspect drive. Things were fine for a while and after I had left the computer running and was away, when I came back, the screen was black and unresponsive to any prompt. I then went through 15 restarts trying to get booted up. I tried everything to get booted from the DVD drive and the OS install disk but it would go to the first screen where you select the drive to boot from and I would only get that ticking watch cursor and could go no further. Finally, I tried the restart with the command-S key route and got a disk os3 I/O error and a hfs early jnl init failed to open. I typed in fsck -fy and it seemed to run a disk repair similar to disk first aid. After a restart, I got to the finder screen but it ran very slow with that spinning pinwheel. I reset the pram again this time it said diskoS3, major 14, minor 2, HD appears OK. It then ran a little better until I was finally able to get to preferences and select the ext hd to boot from.
    So now I'm able to get back online to this forum and check on the postings. And again everything seems to work fine from the ext HD. So does that confirm that my int drive is "screaming Replace me!!"
    It must appear as though I am a glutten for punishment but I just like sorting these things out. Thanks for your help.

  • Problems with External Hard drive, will not mount and errors in disk utilit

    i have a powerbook g4 aluminum. i have an external hard drive for it. a simple tech 100gig portable drive, almost brand new. i dont know what happened to it, but one day i was starting my computer up with it attached. it wounldnt fully start up, said "waiting for local disks" so i uplugged the external hard drive. now it wont mount and will only show up in the disk utility of my friends macbook. i tried to verify and repair, and this is the message i got.
    Verify and Repair disk “UNTITLED”
    ** /dev/disk1s1
    could not read boot block (Input/output error)
    Error: The underlying task reported failure on exit
    1 non HFS volume checked
    1 volume could not be repaired because of an error
    Im in mexico writing a book and so i really need help on this one guys.

    Hi, hjbugs, and welcome to Apple Discussions. Disconnecting the drive while your Powerbook was accessing it probably caused your problem. It may be repairable using DiskWarrior or TechTool Pro, but if you don't have access to one of those and aren't going to buy one, reformatting the drive with Disk Utility may be the only other way to make it usable again. If it contains data you need to recover first (i.e., data that isn't also stored on your internal HD or other storage media), download the free demo version of one of the data recovery utilities mentioned in this thread and use it to see what is recoverable. If the files you need are recoverable, buy the full version of one of the utilities and recover them.

  • Having problems with External Hard Drives on my Laptop

    Ever since using linux i've always had the same problem. Whenever i connect a hard-drive, it keeps disconnecting/ spitting input-ouptut errors.
    I thought it was because of the hard-drive failing, which turned out to be the problem with my last two, but i'm using another one (Seagate MomentusXT 500GB) and i'm getting the same problem.
    I had just reformatted this hard drive from NTFS to Ext4 using Gparted, so maybe that's the problem? I'm really kind of lost.
    I mount my HDD like this:
    sudo mount /dev/sdd1 /mnt/usb
    and unmount like this:
    sudo umount /mnt/usb
    It connects initially, and i'm able to put stuff onto it. I was able to put a whole TV series on it successfully, but when i tried copying my music onto it it failed and alot of the music didn't copy, giving me these errors:
    ile system
    cp: cannot create directory ‘/mnt/usb/music/Clawfinger’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Cake’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/The Glitch Mob - Discography’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Bastille - Bad Blood (The Extended Cut)’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/ARCTIC MONKEYS - DISCOGRAPHY (2005-13) [CHANNEL NEO]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/NIRVANA DISCOGRAPHY @320Kbps CbR Mp3 [TuGAZx]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/The Doors - STUDIO DISCOGRAPHY’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Tiesto - Red Lights (2014.Dance)’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Tiesto - A Town Called Paradise (Deluxe Edition) 2014 320kbps CBR MP3 [VX]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Daft Punk - Discography - 1994-2013’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Pink_Floyd_Greatest_Hits’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Calvin Harris - Discography - 2007-2013’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Weezer [Discography]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/MGMT’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Blackmill’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Avicii - Discography’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Zedd’: Read-only file system
    cp: preserving times for ‘/mnt/usb/music’: Read-only file system
    I can then unmount and mount the HDD again, and try again, but i keep getting the same problem.
    Here's my dmesg:
    [22951.444217] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [22966.616452] usb 1-1: device descriptor read/64, error -110
    [22981.892003] usb 1-1: device descriptor read/64, error -110
    [22982.155518] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [22997.327767] usb 1-1: device descriptor read/64, error -110
    [23012.603571] usb 1-1: device descriptor read/64, error -110
    [23012.867002] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [23017.881048] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23017.881078] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23023.098593] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23023.302055] usb 1-1: device not accepting address 19, error -62
    [23023.462289] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [23028.476297] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23028.476314] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23033.693797] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23033.897336] usb 1-1: device not accepting address 19, error -62
    [23033.897435] usb 1-1: USB disconnect, device number 19
    [23033.903973] sd 10:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x01 driverbyte=0x00
    [23033.903976] sd 10:0:0:0: [sdd] CDB:
    [23033.903977] cdb[0]=0x2a: 2a 00 03 90 e5 10 00 00 f0 00
    [23033.903982] blk_update_request: I/O error, dev sdd, sector 59827472
    [23033.903985] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478464)
    [23033.903987] buffer_io_error: 4990 callbacks suppressed
    [23033.903988] Buffer I/O error on device sdd1, logical block 7478178
    [23033.903990] Buffer I/O error on device sdd1, logical block 7478179
    [23033.903991] Buffer I/O error on device sdd1, logical block 7478180
    [23033.903992] Buffer I/O error on device sdd1, logical block 7478181
    [23033.903993] Buffer I/O error on device sdd1, logical block 7478182
    [23033.903994] Buffer I/O error on device sdd1, logical block 7478183
    [23033.903995] Buffer I/O error on device sdd1, logical block 7478184
    [23033.903996] Buffer I/O error on device sdd1, logical block 7478185
    [23033.903997] Buffer I/O error on device sdd1, logical block 7478186
    [23033.903998] Buffer I/O error on device sdd1, logical block 7478187
    [23033.904015] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478524)
    [23033.904027] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478554)
    [23033.904050] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478584)
    [23033.904066] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478614)
    [23033.904080] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478644)
    [23033.904095] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478674)
    [23033.904110] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478704)
    [23033.904124] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478734)
    [23033.904139] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478764)
    [23033.905630] sd 10:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x01 driverbyte=0x00
    [23033.905632] sd 10:0:0:0: [sdd] CDB:
    [23033.905633] cdb[0]=0x2a: 2a 00 03 90 e6 00 00 00 f0 00
    [23033.905639] blk_update_request: I/O error, dev sdd, sector 59827712
    [23033.906165] Aborting journal on device sdd1-8.
    [23033.906176] JBD2: Error -5 detected when updating journal superblock for sdd1-8.
    [23033.906270] EXT4-fs (sdd1): Delayed block allocation failed for inode 16777761 at logical offset 0 with max blocks 2048 with error 30
    [23033.906272] EXT4-fs (sdd1): This should not happen!! Data will be lost
    [23033.906276] EXT4-fs error (device sdd1) in ext4_writepages:2395: Journal has aborted
    [23033.906793] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.906801] EXT4-fs error (device sdd1): ext4_journal_check_start:56: Detected aborted journal
    [23033.906802] EXT4-fs (sdd1): Remounting filesystem read-only
    [23033.906803] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.906808] EXT4-fs (sdd1): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 16777762; err -30
    [23033.907641] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907644] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907690] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907692] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907736] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907738] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907771] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907773] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907805] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907845] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907886] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907919] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907947] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23034.490498] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880225074480
    [23034.490502] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802250744c8
    [23220.391199] usb 1-1: new high-speed USB device number 54 using xhci_hcd
    [23235.563509] usb 1-1: device descriptor read/64, error -110
    [23250.839126] usb 1-1: device descriptor read/64, error -110
    [23251.102653] usb 1-1: new high-speed USB device number 55 using xhci_hcd
    [23266.274917] usb 1-1: device descriptor read/64, error -110
    [23281.550616] usb 1-1: device descriptor read/64, error -110
    [23281.814174] usb 1-1: new high-speed USB device number 56 using xhci_hcd
    [23286.831502] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23286.831579] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23292.049048] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23292.252556] usb 1-1: device not accepting address 56, error -62
    [23292.412732] usb 1-1: new high-speed USB device number 57 using xhci_hcd
    [23297.426714] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23297.426728] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23302.644273] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23302.847753] usb 1-1: device not accepting address 57, error -62
    [23302.847781] usb usb1-port1: unable to enumerate USB device
    Anyone know how to fix this?

    There is a whole lot of bad going on there.
    There are problems both drive errors and USB errors.  I don't believe it.
    I have a hunch the drive is starving for power. 
    USB devices are supposed to function all the way down to 4.25V.  Not all do.
    USB ports are supposed to be able to deliver 4.25V at the end of the cable at 500mA.  Not all do.
    USB 2.0 devices are not supposed to draw more than 100mA unless they negotiate for more.  Some violate that.
    USB 2.0 devices are never supposed to draw more than 500mA. Some violate that.  Especially disk drives.
    My guess is that your drive is drawing excess current and the voltage drop through the port and cable are dropping you below 4.25; or at least below the voltage that your drive goes "Tango Uniform"[1].   Does your drive have the option for external power?  If so try it.  Following up on wtx's comment;  USB 3.0 is capable of delivering more power.   Also, some drives have used a cable that violates just about every aspect of the USB specification:  A "Y" cable that plugs into two host ports to provide more power to the guest.  I despise this solution with every fiber of my electrical engineering existence; never-the-less, you might try one.
    edit:  [1] Teats Up.
    Last edited by ewaller (2015-04-04 17:02:04)

Maybe you are looking for

  • Oracle.apps.fnd.cache.CacheException in login page

    Hi, i wrote one method in am and return that values to co and the following is the code in AM public String Status(String reqid){     String Status2=null; String Status;     while(Staus.equals("I")||Staus.equals("R")||Staus.equals("P"))       try{   

  • Drag and drop column header in a table

    Hi all, I need to drag the Column header in a table dynamically. When I drag the column out of the table, The table should be rearranged accordingly NOTE: The output is displayed in the form of XML(XSL). Pls help me solve the problem . Thanks in adva

  • Using a %% tag to write vb code in aspx file

    <p>Trying to create a pdf from an rpt. I used the wizard wich generated the code within the div tags. I authored the code inside the <%%> tags. I am following an article written by Edward Tanguay-How to create PDF files from ASP.NET pages. Can I refe

  • Iphone app organization???

    "And it's easier to organize all the apps on your iPhone or iPod touch, because now you can do it right in iTunes" Thats what it says, but when i plug my iphone in then sync it then I go to applications on itunes, I cant change my home or any other s

  • BT Homehub 2 dropping connection every few minutes

    Hi, my homehubs been working perfectly until today when it started dropping the connection every few minutes (ranging from 3 minutes up to 13). The broadband and phone lights go out then orange and then back to blue after about a minute. Having brows