[SOLVED] Problem with external USB drive started yesterday

My system freezes for about 65 seconds at the login screen. After 65 seconds, I can login and everything is normal afterwards.
I discovered that I can eliminate the freeze by disconnecting the external USB drive from the PC. Here are the error messages from kernel.log when the drive is connected:
Oct 15 23:10:14 localhost kernel: [ 17.035091] usb 1-1.3: device descriptor read/64, error -110
Oct 15 23:10:29 localhost kernel: [ 32.155955] usb 1-1.3: device descriptor read/64, error -110
Oct 15 23:10:29 localhost kernel: [ 32.325394] usb 1-1.3: new high speed USB device number 4 using ehci_hcd
Oct 15 23:10:31 localhost kernel: [ 34.045126] MediaState is connected
There is supposed to be a kernel boot option (irqpoll) to prevent this from occurring. However, that option seems to no longer work for kernels after 2.6.39. If I try using it with Arch, the system will not boot, saying all the CPU's failed.
I also don't understand why this just started happening yesterday, as the USB drive has been connected to the PC longer than I've been using Arch. Also, my kernel has not been updated since I installed Arch on Oct 8.
Does anyone know another fix or workaround for this problem?
Thanks,
Tim
Last edited by ratcheer (2011-10-17 01:30:08)

Problem solved
I feel stupid, but I also feel better. I turned off the PC, disconnected the power from the USB drive for about 15 seconds, reconnected the power, rebooted, removed the irqpoll kernel option, and Ubuntu started, perfectly. I need to learn that the USB drive just goes freaky sometimes and remember to do this. But, this is only the second time I've had to do this in months of use.
Tim

Similar Messages

FSCK and reboot issues with external USB drive

I'm having an issue with an external USB hard drive I'm using. I've always had issues with this drive cause my reboot to "freeze" when it's mounted. Basically the system message with be sent out, but it doesn't actually proceed with the reboot. No switch to init 6 or anything, but the shutdown process is still active. I can continue to use the computer as usual, but I can't cancel the existing shutdown or try to enter init level 6 by hand. So I just got around this by unmounting the drive before I shutdown. However, lately when I try to unmount the drive I get an error saying that the drive is in use and I should check to see what processes are using it by runing lsof or fuser.
Yesterday I tried copying dsome files from the drive but there wasn't and activity on the drive. cp didn't report any errors though, it just sat there and did nothing. I tried running fsck on the drive, but didn't get much farther. I'll see some activity on the drive for about a second, then all activity stops and fsck just sits there. When I try to kill fsck, it won't. Even with a kill -9.
I'm really confused as to what is going on. Has anyone else had this problem? Anyone have any ideas what could be causing all this or what I can do to stop this? Thanks in advance!
David
[email protected]

Press the reset button on the device. It is located between the USB and power ports. Make sure to take-out the external USB drive before you reset the device. Or you can also restore the defaults by accessing the Administration tab > Factory Defaults sub-tab in the router’s web-based setup page. Check out this link for the set up; http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=32cffead811249aea7e9fc6730bf59ad_KB25681_EN_v1.xml...

[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.

IMAC won't start with external USB drive

I've been running Leopard for a few weeks now and decided to connect an external USB hard drive to use with Time Machine, it did the backup fine and seems to be working fine... however, every time I start my imac in the morning I get a gray screen that just hangs. I have to unplug the USB drive then reboot again.. that salves the problem.. but is annoying to have to do that each time.. I also noticed today that my ipod when plugger in via USB will not mount on the desktop.. I have to unplug the USB hard drive then plug the ipod in again.. that solves the problem..
Anyone have this same issue..??? It seems to be USB related or Time Machine related.. maybe both..
Cheers
D.

The Disks are formatted with Ntfs as i am using Bootcamp with Windows 7. So repairing disks would not work in Mac OSX, and is not needed as the disks are ok. I would be a strange coincidence that both disks would be corrupted at the same Time.
I have tried three different other USB disks in the meantime and the Macbook could Boot up everytime with no problem. I found the answer in another forum. The controllers (USB to SATA) in the enclosures of the disks are not compatible with my Macbook, they are rather cheap WD disks and a lot of other users reported the same problem. ist might be possible to upgrade the firmware, but i will rather look for some other disks and try them first before i buy.

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)

Post-Install Problem with External Firewire drive

I just installed Tiger 10.4.3 and the computer would not reboot. It would stop prior to the Starting Mac OS X progress bar and gray out letting me know that the computer needs to restart.
I finally got it to boot successfully by unplugging or turning orr my external Maxtor Firewire drive. The external drive was plugged during the install process (mistake?)
Via Software upgrade, I upgraded to 10.4.6 in the hopes that this would solve the issue. No luck and when turning the drive on, it immediately goes right to the gray screen and lets me know it will need to reboot.
Is this a known problem with a known solution? Did I FUBAR my drive somehow? Any suggestions for righting to ship?
Thanks!
Rob P

OK, last one before dinner. I found the panic log. here is what it says:
Description: Panic (system crashes) log
Size: 12.39 KB
Last Modified: 5/25/06 6:39 PM
Location: /Library/Logs/panic.log
Recent Contents: ...
panic(cpu 0): 0x400 - Inst access
Latest stack backtrace for cpu 0:
Backtrace:
0x000857F4 0x00085C24 0x000287B4 0x0008F6A8 0x000927B8
Proceeding back via exception chain:
Exception state (sv=0x24051780)
PC=0x00000020; MSR=0x40009030; DAR=0x11F23B98; DSISR=0x40000000; LR=0x16FE0DEC; R1=0x1227BB90; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x16FE0C58 0x16FE08DC 0x16FE043C 0x0021FFAC 0x0021FDA8 0x002206F8 0x00220D54 0x002111D0
0x00211194
Kernel loadable modules in backtrace (with dependencies):
com.maxtor.iokit.IOFireWireMxBt(2.0d1)@0x16fdf000
dependency: com.apple.iokit.IOFireWireFamily(1.4.0)@0x233d3000
Exception state (sv=0x22F58A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC
Does this help anyone???
Rob P

Aperture 2.1.1 Vault problem with external usb disk

I have just updated to 2.1.1 and now Aperture freezes every time I connect my usb external disk and try to create or update a vault. I have to force quit Aperture and remove the disk before I can use Aperture again. The only way I can create a vault is to create it on my internal disk then manually copy to the external usb. Another topic here suggested the problem is with network disks but I have a very similar problem with a local usb disk. I have tried two different disks with the same results. All my software and os is up to date.
Does anyone else have this problem?

I have a similar problem, and have a not totally satisfactory fix for my issue.
I have my photos stored on an external FW drive.
Originally I also stored my vault on the same drive.
When I started Aperture with this config then Aperture would not pass the loading screen. I would have to kill the process to quit.
If I started Aperture with the FW drive disconnected then it would launch, but I would then attach eth FW drive and have to Manage referenced files.
What has worked for me:
I have removed the vault from the FW drive and Aperture now boots quickly as 2.1 did.
I have to create the vault on the internal HD and copy to the external.

Aperture 3 problems with external hard-drives

Because of an external drive failure I had to move my Aperture Library 350+gb to another external hard-drive (iMac only has 500 gb internal drive). It is working; however, about 2500 photos are referenced, the rest are managed masters. No problem apparently with masters. But cannot reconnect with referenced files because the external drive is now deceased and cannot be dismounted. (Please continue reading before firing off an answer telling me to repair the database with Opt Command at start up. That did not solve my problem.)
I know how to individually reconnect files which were located on a (now) offline (permanently) volume. But is there no easier way to get Aperture to recognize that a drive no longer exists and a new drive has taken its place? (Yes. I have read about using SQLite Database Browser to change the UUID of the drive to the new drive. But this seems bizarre that a high end program like Aperture 3 requires users to tweak the database to get Aperture to recognize a new drive.) I have installed the most recent Aperture update. There was one today I believe. No help.
Thanks for your input.

paulfresh wrote:
it also appears to be mavericks... I don't have any software programs installed for both my OWC and lacie drives and they still wont eject properly under Mavericks
No, it doesn't appear to be Mavericks. All good here on the five Macs in my studios and all attached drives. But blame Apple if it makes you feel better.
http://www.theregister.co.uk/2013/11/05/western_digital_fesses_up_to_mavericks_d ata_loss_mess/
Cheers
Pete

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.

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.

Problem with the usb drives

After re-instal of the Lion my Macbook pro does not see any of the external hard drives, usb, phones etc. What can be the problem?

Several thoughts ... when you're having interface problems, do an SMC reset instead of a PRAM reset, as often USB/Firewire operations issues are power-related:
1. From the Apple menu, choose Shut Down (or if the computer is not responding, hold the power button until it turns off).
2. Unplug all cables from the computer, including the power cord and any display cables.
3. Wait at least 15 seconds.
4. Plug the power cord back in, making sure the power button is not being pressed at the time. Then reconnect your keyboard and mouse to the computer.
5. Press the power button on the back to start up your computer.
Are there any driver or firmware upgrades for either of the drives? If you haven't, you might check on the manufacturers web site.
Also, does the firewire drive also support USB? Have you tired it on USB, for comparison?

Problem with External Hard drive connection with PowerBook

I recently bought a Seagate FreeAgent/Go 500gig portable drive (2009) that only has a USB hookup. It does not register or operate on my PowerBook (G4 2005) but works fine on my wife's MacBook (2008). It appears from other discussion boards that it may be the case that not enough power is going through the USB port to the external hard drive. If this is correct is there a recommended solution so I can use the Seagate on both computers? Is there a way to get more power through the USB port?
I'd hate to have to go out and buy another external hard drive with an external power source because it would defeat the purpose of being portable if I have to have separate outlets for both the powerbook and the external hard drive (not to mention more cords). Any suggestions would be greatly appreciated.

Are you sure an additional USB to power or "Y" cable didn't come in the box, ****123? Most USB powered drives seem to come either with a "Y" cable, or an additional USB to power cable, these days.
In fact the "Seagate Freeagent "Go" Quick Start guide (see http://www.seagate.com/staticfiles/support/freeagent/fago_mac_qsgr3.pdf ) actually shows one as necessary for using over USB (though this is the model with FW as well).
Seagate's own troubleshooting document concerning this issue can be found at http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=213059&NewLan g=en
Cheers
Rod

Problem with External Hard Drive

Hi,
I'm having trouble with my External Hard Drive, a 300GB Iomega USB. Everytime i use it with my iMac G4 it disconnects by itself and i get the "Device Removal" message after 20 minutes or so. This occurs even though the Mac hasn't moved, the Hard Drive and its wire wasn't moved and even when I'm not doing anything on my Mac. This occurrs in all three of the USB ports even though other devices plugged into them work fine.
It's a problem with your External Hard Drive and/or its wire i hear you say. However, the External works fine when plugged into my Windows Laptop.
Any help would be much apreciated as all my music, movies and work are on my External.
Thanks in advance,
K

Hi there:
You may have to use a Mac disk utility on the external USB hard disk drive, since the error
you see is likely caused by some defect. And the symptom is in how the drive fails to mount.
Perhaps a tool like Disk Utility could see what kind of errors, but not fix them; if this is the
case, a more specific tool such as DiskWarrior (for the Mac OS your machine has) may help.
Depending on the level this problem exists, the drive may be repairable through use of one
of the disk utility type of tools; or it may need to be erased, reformatted, etc. So, if there is
some kind of error in the directory or other portion, DiskWarrior could probably fix it and not
interfere with the data on the drive... Or, that's the hoped-for outcome.
And that direction is likely one to pursue. For the sake of discussion, you - do - have extra
USB cords, just in case you have one that does not like Macs? A diabolical PC infiltrator?!
Good luck & happy computing!

Problems with external USB HDDs (MSI P67A-C45)

Hello! Help me, please.
I'm using number of external HDDs (3,5'' -- with power supply each). Most of them are plugged into the motherboard USB 2.0 via a powered USB hub. Some of them are plugged directly to the motherboard. I'm facing three major problems with them. Please, consult me.
1) I cannot access those of HDDs, which are plug via the hub. Windows just do not see them. If I plug the hub into a laptop, it works.
2) Only factory-made external HDDs are working, being plugged directly into USB 2.0. Those of them, which I made myself (using HDD and a box, obviously) are not working with USB 2.0, BUT ONLY WITH USB 3.0. I do not understand, whats the problem with USB 2.0 then... Devices like mouse, printers, scanners are working...
3) If HDDs are plugged and switched on during booting up, the loader gets stuck on "B4" phase. It can be completely stuck or only for 5 minutes and then go on booting. My question is: whats the problem? How can I fix this?
Please, take into the account that all this system was working perfectly fine a week ago, when I had another motherboard and CPU. I'm using these disks for several yeas. I just had a reason for the MB+CPU upgrade and this upgrade leads to such problems... Please, help me.

if they are all fitted with a seperate power source then yes it matters not
many usb drives have 2 usb connectors
one for data and power
the second is just for more power from a second connection
http://www.google.co.uk/imgres?imgurl=http://ecx.images-amazon.com/images/I/41yBRjqo6sL._SS500_.jpg&imgrefurl=http://forum.xda-developers.com/showthread.php%3Ft%3D408693&h=500&w=500&sz=21&tbnid=Qv6dCMoxqLa8cM:&tbnh=130&tbnw=130&prev=/images%3Fq%3Dusb%2Bsplitter&zoom=1&q=usb+splitter&hl=en&usg=__QYH3uaKOuQVopk73OYWaBzBEAsM=&sa=X&ei=nuZDTbSnJsPKhAfBgdnRAQ&sqi=2&ved=0CDcQ9QEwAg
end looks like this

MacBook freezing and crashing/running slow, problem with external hard drive

I've been having some issues for the past couple months with my laptop randomly freezing, usually when I have a lot happening. I've ended up having to hard-restart it several times because it will just hang and I can't get into the menu at all to force quit things. In the past couple days, it's now started crashing completely, although restarting okay. This last time, though, it crashed while I was trying to empty the trash and since then it's been crazy slow and not very responsive.I tried running disk utility and ccleaner, and although they repaired some stuff they didn't fix the problem.
I think iTunes might be the issue. I was trying to move my music library when this last thing started. I have it all on an external hard drive, and I was trying to move it from one folder to another. I tried repairing the external hard drive with disk utility to see if that was the issue, but now my files have all vanished and the external appears blank.
I also recently installed BootCamp, if that makes a difference.
I'm mostly just really unsure what to do. I don't want to do anything to the external because I need to recover the stuff that was on it, but I also need my laptop to be usable.

Thanks for the response. I tried booting in recovery mode and running disk utility again and that seemed to help. It's still hanging when I plug in the external hard drive but otherwise seems to be working okay. My main issue now is the invisible files. I tried booting in Windows, planning to install Recuva to try and get the files back. However, they show up fine there. This is a relief but I'm not totally sure what is happening. I'm guessing the disk has somehow mounted incorrectly on the mac portion but I'm not sure how to fix that. I'm about to restart on the other partition and see what's going on there.

[SOLVED] Problem with external USB drive started yesterday

Similar Messages

Maybe you are looking for