ATA Bus Speed?

Hey all,
Just a quick question:
Does anyone know whether the HDD bus on the Mini is ATA/100 or ATA/133?
Not really all that big of an impact on things, I know. I'm just curious, that's all.
-Mark

Thanks Dave!

Similar Messages

ATA bus error

Hello,
I have some problems with hard drive on my laptop. Sometimes everything freezes for few seconds (usually during start-up, but sometimes after I login) and I get some errors. After that, everything seems to be working fine.
Part of dmesg with errors:
[ 10.019887] ata1.00: cmd 60/00:10:10:da:59/01:00:0f:00:00/40 tag 2 ncq 131072 in
res 41/84:00:f2:da:59/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.019968] ata1.00: status: { DRDY ERR }
[ 10.019992] ata1.00: error: { ICRC ABRT }
[ 10.020017] ata1: hard resetting link
[ 10.339913] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 10.443163] ata1.00: configured for UDMA/133
[ 10.443191] ata1: EH complete
[ 10.516832] ata1.00: exception Emask 0x0 SAct 0x7000 SErr 0x0 action 0x6
[ 10.516877] ata1.00: irq_stat 0x40000008
[ 10.516902] ata1.00: failed command: READ FPDMA QUEUED
[ 10.516935] ata1.00: cmd 60/e8:60:e8:16:3b/00:00:0f:00:00/40 tag 12 ncq 118784 in
res 41/84:e8:8c:17:3b/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.517017] ata1.00: status: { DRDY ERR }
[ 10.517041] ata1.00: error: { ICRC ABRT }
[ 10.517067] ata1: hard resetting link
[ 10.836973] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 10.964972] ata1.00: configured for UDMA/133
[ 10.965002] ata1: EH complete
[ 10.984003] ata1: limiting SATA link speed to 3.0 Gbps
[ 10.984015] ata1.00: exception Emask 0x0 SAct 0x60020000 SErr 0x0 action 0x6
[ 10.984106] ata1.00: irq_stat 0x40000008
[ 10.984157] ata1.00: failed command: READ FPDMA QUEUED
[ 10.984225] ata1.00: cmd 60/20:e8:40:6e:b0/00:00:13:00:00/40 tag 29 ncq 16384 in
res 41/84:20:46:6e:b0/00:00:13:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.984397] ata1.00: status: { DRDY ERR }
[ 10.984445] ata1.00: error: { ICRC ABRT }
[ 10.984497] ata1: hard resetting link
[ 11.304016] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 11.409308] ata1.00: configured for UDMA/133
[ 11.409343] ata1: EH complete
[ 11.441025] vboxpci: IOMMU not found (not registered)
[ 11.543239] bbswitch: version 0.8
[ 11.543246] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 11.543252] bbswitch: Found discrete VGA device 0000:03:00.0: \_SB_.PCI0.RP05.PEGP
[ 11.543262] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 11.543355] bbswitch: detected an Optimus _DSM function
[ 11.543372] pci 0000:03:00.0: enabling device (0006 -> 0007)
[ 11.543434] bbswitch: Succesfully loaded. Discrete card 0000:03:00.0 is on
[ 11.545169] bbswitch: disabling discrete graphics
[ 11.545181] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 13.327790] r8169 0000:01:00.0 enp1s0: link up
[ 20.651344] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x6
[ 20.651349] ata1.00: irq_stat 0x40000008
[ 20.651353] ata1.00: failed command: READ FPDMA QUEUED
[ 20.651359] ata1.00: cmd 60/08:c8:98:86:ae/00:00:10:00:00/40 tag 25 ncq 4096 in
res 41/84:08:98:86:ae/00:00:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 20.651361] ata1.00: status: { DRDY ERR }
[ 20.651363] ata1.00: error: { ICRC ABRT }
[ 20.651367] ata1: hard resetting link
[ 20.971293] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 21.080441] ata1.00: configured for UDMA/133
[ 21.080467] ata1: EH complete
[ 21.121498] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[ 21.121503] ata1.00: irq_stat 0x40000008
[ 21.121507] ata1.00: failed command: READ FPDMA QUEUED
[ 21.121513] ata1.00: cmd 60/00:e8:00:f4:69/01:00:0f:00:00/40 tag 29 ncq 131072 in
res 41/84:00:ee:f4:69/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 21.121515] ata1.00: status: { DRDY ERR }
[ 21.121517] ata1.00: error: { ICRC ABRT }
[ 21.121521] ata1: hard resetting link
[ 21.441483] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 21.546775] ata1.00: configured for UDMA/133
[ 21.546795] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 21.546798] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 21.546801] sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0
[ 21.546802] sd 0:0:0:0: [sda] CDB:
[ 21.546804] cdb[0]=0x28: 28 00 0f 69 f4 00 00 01 00 00
[ 21.546812] blk_update_request: I/O error, dev sda, sector 258601984
[ 21.546829] ata1: EH complete
[ 21.606131] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x6
[ 21.606139] ata1.00: irq_stat 0x40000008
[ 21.606145] ata1.00: failed command: READ FPDMA QUEUED
[ 21.606155] ata1.00: cmd 60/88:48:00:d8:36/00:00:0f:00:00/40 tag 9 ncq 69632 in
res 41/84:88:04:d8:36/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 21.606160] ata1.00: status: { DRDY ERR }
[ 21.606163] ata1.00: error: { ICRC ABRT }
[ 21.606170] ata1: hard resetting link
[ 21.924963] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 22.035385] ata1.00: configured for UDMA/133
[ 22.035408] ata1: EH complete
[ 22.111984] ata1: limiting SATA link speed to 1.5 Gbps
[ 22.111991] ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6
[ 22.111994] ata1.00: irq_stat 0x40000008
[ 22.111997] ata1.00: failed command: READ FPDMA QUEUED
[ 22.112003] ata1.00: cmd 60/90:c0:48:39:32/00:00:0f:00:00/40 tag 24 ncq 73728 in
res 41/84:90:8a:39:32/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 22.112005] ata1.00: status: { DRDY ERR }
[ 22.112007] ata1.00: error: { ICRC ABRT }
[ 22.112011] ata1: hard resetting link
[ 22.431783] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 22.535011] ata1.00: configured for UDMA/133
[ 22.535038] ata1: EH complete
[ 22.618877] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x0 action 0x6
[ 22.618886] ata1.00: irq_stat 0x40000008
[ 22.618891] ata1.00: failed command: READ FPDMA QUEUED
[ 22.618901] ata1.00: cmd 60/00:08:08:2c:32/01:00:0f:00:00/40 tag 1 ncq 131072 in
res 41/84:00:70:2c:32/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 22.618906] ata1.00: status: { DRDY ERR }
[ 22.618909] ata1.00: error: { ICRC ABRT }
[ 22.618920] ata1: hard resetting link
[ 22.938608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 23.023643] ata1.00: configured for UDMA/133
[ 23.023682] ata1: EH complete
[ 53.428943] ata1.00: exception Emask 0x1 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[ 53.428953] ata1.00: irq_stat 0x40000008
[ 53.428960] ata1.00: failed command: READ FPDMA QUEUED
[ 53.428971] ata1.00: cmd 60/00:00:00:e8:31/01:00:10:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
[ 53.428976] ata1.00: status: { DRDY }
[ 53.428981] ata1.00: failed command: READ FPDMA QUEUED
[ 53.428990] ata1.00: cmd 60/08:08:20:fe:e9/00:00:0f:00:00/40 tag 1 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.428994] ata1.00: status: { DRDY }
[ 53.428998] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429006] ata1.00: cmd 60/08:10:28:fe:e9/00:00:0f:00:00/40 tag 2 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429010] ata1.00: status: { DRDY }
[ 53.429014] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429022] ata1.00: cmd 60/08:18:30:fe:e9/00:00:0f:00:00/40 tag 3 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429026] ata1.00: status: { DRDY }
[ 53.429029] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429037] ata1.00: cmd 60/08:20:38:fe:e9/00:00:0f:00:00/40 tag 4 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429042] ata1.00: status: { DRDY }
[ 53.429045] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429053] ata1.00: cmd 60/08:28:40:fe:e9/00:00:0f:00:00/40 tag 5 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429057] ata1.00: status: { DRDY }
[ 53.429061] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429069] ata1.00: cmd 60/08:30:48:fe:e9/00:00:0f:00:00/40 tag 6 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429073] ata1.00: status: { DRDY }
[ 53.429076] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429084] ata1.00: cmd 60/08:38:50:fe:e9/00:00:0f:00:00/40 tag 7 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429089] ata1.00: status: { DRDY }
[ 53.429092] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429100] ata1.00: cmd 60/08:40:58:fe:e9/00:00:0f:00:00/40 tag 8 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429104] ata1.00: status: { DRDY }
[ 53.429108] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429116] ata1.00: cmd 60/08:48:60:fe:e9/00:00:0f:00:00/40 tag 9 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429120] ata1.00: status: { DRDY }
[ 53.429124] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429132] ata1.00: cmd 60/08:50:68:fe:e9/00:00:0f:00:00/40 tag 10 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429136] ata1.00: status: { DRDY }
[ 53.429139] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429148] ata1.00: cmd 60/08:58:70:fe:e9/00:00:0f:00:00/40 tag 11 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429152] ata1.00: status: { DRDY }
[ 53.429155] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429163] ata1.00: cmd 60/08:60:78:fe:e9/00:00:0f:00:00/40 tag 12 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429168] ata1.00: status: { DRDY }
[ 53.429171] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429179] ata1.00: cmd 60/08:68:80:fe:e9/00:00:0f:00:00/40 tag 13 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429183] ata1.00: status: { DRDY }
[ 53.429187] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429195] ata1.00: cmd 60/08:70:18:e8:a9/00:00:16:00:00/40 tag 14 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429199] ata1.00: status: { DRDY }
[ 53.429203] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429211] ata1.00: cmd 60/08:78:90:fe:e9/00:00:0f:00:00/40 tag 15 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429215] ata1.00: status: { DRDY }
[ 53.429218] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429226] ata1.00: cmd 60/08:80:98:fe:e9/00:00:0f:00:00/40 tag 16 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429230] ata1.00: status: { DRDY }
[ 53.429234] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429242] ata1.00: cmd 60/08:88:a0:fe:e9/00:00:0f:00:00/40 tag 17 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429246] ata1.00: status: { DRDY }
[ 53.429250] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429258] ata1.00: cmd 60/08:90:a8:fe:e9/00:00:0f:00:00/40 tag 18 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429262] ata1.00: status: { DRDY }
[ 53.429265] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429273] ata1.00: cmd 60/08:98:b0:fe:e9/00:00:0f:00:00/40 tag 19 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429277] ata1.00: status: { DRDY }
[ 53.429281] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429289] ata1.00: cmd 60/08:a0:b8:fe:e9/00:00:0f:00:00/40 tag 20 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429293] ata1.00: status: { DRDY }
[ 53.429297] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429305] ata1.00: cmd 60/08:a8:c0:fe:e9/00:00:0f:00:00/40 tag 21 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429309] ata1.00: status: { DRDY }
[ 53.429312] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429320] ata1.00: cmd 60/08:b0:c8:fe:e9/00:00:0f:00:00/40 tag 22 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429325] ata1.00: status: { DRDY }
[ 53.429328] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429336] ata1.00: cmd 60/08:b8:d0:fe:e9/00:00:0f:00:00/40 tag 23 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429340] ata1.00: status: { DRDY }
[ 53.429344] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429352] ata1.00: cmd 60/08:c0:d8:fe:e9/00:00:0f:00:00/40 tag 24 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429356] ata1.00: status: { DRDY }
[ 53.429360] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429367] ata1.00: cmd 60/08:c8:e0:fe:e9/00:00:0f:00:00/40 tag 25 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429372] ata1.00: status: { DRDY }
[ 53.429375] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429383] ata1.00: cmd 60/08:d0:e8:fe:e9/00:00:0f:00:00/40 tag 26 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429387] ata1.00: status: { DRDY }
[ 53.429391] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429399] ata1.00: cmd 60/08:d8:f0:fe:e9/00:00:0f:00:00/40 tag 27 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429403] ata1.00: status: { DRDY }
[ 53.429407] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429414] ata1.00: cmd 60/08:e0:f8:fe:e9/00:00:0f:00:00/40 tag 28 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429419] ata1.00: status: { DRDY }
[ 53.429422] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429430] ata1.00: cmd 60/08:e8:00:ff:e9/00:00:0f:00:00/40 tag 29 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429435] ata1.00: status: { DRDY }
[ 53.429438] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429446] ata1.00: cmd 60/08:f0:88:fe:e9/00:00:0f:00:00/40 tag 30 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429450] ata1.00: status: { DRDY }
[ 53.429458] ata1: hard resetting link
[ 53.749173] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 53.836070] ata1.00: configured for UDMA/133
[ 53.836079] ata1.00: device reported invalid CHS sector 0
[ 53.836116] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836119] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836121] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836123] sd 0:0:0:0: [sda] CDB:
[ 53.836125] cdb[0]=0x28: 28 00 0f e9 fe 20 00 00 08 00
[ 53.836133] blk_update_request: I/O error, dev sda, sector 266993184
[ 53.836148] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836151] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836153] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836154] sd 0:0:0:0: [sda] CDB:
[ 53.836155] cdb[0]=0x28: 28 00 0f e9 fe 28 00 00 08 00
[ 53.836162] blk_update_request: I/O error, dev sda, sector 266993192
[ 53.836167] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836169] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836171] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836173] sd 0:0:0:0: [sda] CDB:
[ 53.836174] cdb[0]=0x28: 28 00 0f e9 fe 30 00 00 08 00
[ 53.836180] blk_update_request: I/O error, dev sda, sector 266993200
[ 53.836185] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836187] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836189] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836190] sd 0:0:0:0: [sda] CDB:
[ 53.836191] cdb[0]=0x28: 28 00 0f e9 fe 38 00 00 08 00
[ 53.836198] blk_update_request: I/O error, dev sda, sector 266993208
[ 53.836202] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836204] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836206] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836208] sd 0:0:0:0: [sda] CDB:
[ 53.836209] cdb[0]=0x28: 28 00 0f e9 fe 40 00 00 08 00
[ 53.836215] blk_update_request: I/O error, dev sda, sector 266993216
[ 53.836220] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836222] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836224] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836225] sd 0:0:0:0: [sda] CDB:
[ 53.836226] cdb[0]=0x28: 28 00 0f e9 fe 48 00 00 08 00
[ 53.836232] blk_update_request: I/O error, dev sda, sector 266993224
[ 53.836237] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836239] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836241] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836242] sd 0:0:0:0: [sda] CDB:
[ 53.836243] cdb[0]=0x28: 28 00 0f e9 fe 50 00 00 08 00
[ 53.836249] blk_update_request: I/O error, dev sda, sector 266993232
[ 53.836253] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836255] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836257] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836259] sd 0:0:0:0: [sda] CDB:
[ 53.836260] cdb[0]=0x28: 28 00 0f e9 fe 58 00 00 08 00
[ 53.836266] blk_update_request: I/O error, dev sda, sector 266993240
[ 53.836270] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836272] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836274] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836276] sd 0:0:0:0: [sda] CDB:
[ 53.836277] cdb[0]=0x28: 28 00 0f e9 fe 60 00 00 08 00
[ 53.836283] blk_update_request: I/O error, dev sda, sector 266993248
[ 53.836287] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836289] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836291] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836293] sd 0:0:0:0: [sda] CDB:
[ 53.836294] cdb[0]=0x28: 28 00 0f e9 fe 68 00 00 08 00
[ 53.836300] blk_update_request: I/O error, dev sda, sector 266993256
[ 53.836354] ata1: EH complete
[ 53.922776] ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6
[ 53.922827] ata1.00: irq_stat 0x40000008
[ 53.922855] ata1.00: failed command: READ FPDMA QUEUED
[ 53.922891] ata1.00: cmd 60/00:28:38:3f:04/01:00:10:00:00/40 tag 5 ncq 131072 in
res 41/84:00:5a:3f:04/00:01:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 53.922981] ata1.00: status: { DRDY ERR }
[ 53.923007] ata1.00: error: { ICRC ABRT }
[ 53.923037] ata1: hard resetting link
[ 54.242882] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 54.357940] ata1.00: configured for UDMA/133
[ 54.357967] ata1: EH complete
[ 54.413337] ata1.00: limiting speed to UDMA/100:PIO4
[ 54.413343] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6
[ 54.413387] ata1.00: irq_stat 0x40000008
[ 54.413412] ata1.00: failed command: READ FPDMA QUEUED
[ 54.413445] ata1.00: cmd 60/20:40:c0:04:b1/00:00:16:00:00/40 tag 8 ncq 16384 in
res 41/84:20:d4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 54.413527] ata1.00: status: { DRDY ERR }
[ 54.413551] ata1.00: error: { ICRC ABRT }
[ 54.413578] ata1: hard resetting link
[ 54.733264] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 54.835393] ata1.00: configured for UDMA/100
[ 54.835419] ata1: EH complete
[ 54.883575] ata1.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x6
[ 54.883618] ata1.00: irq_stat 0x40000008
[ 54.883643] ata1.00: failed command: READ FPDMA QUEUED
[ 54.883675] ata1.00: cmd 60/08:18:e0:04:b1/00:00:16:00:00/40 tag 3 ncq 4096 in
res 41/84:08:e4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 54.883756] ata1.00: status: { DRDY ERR }
[ 54.883779] ata1.00: error: { ICRC ABRT }
[ 54.883805] ata1: hard resetting link
[ 55.203636] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 55.301754] ata1.00: configured for UDMA/100
[ 55.301780] ata1: EH complete
[ 55.357428] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[ 55.357474] ata1.00: irq_stat 0x40000008
[ 55.357500] ata1.00: failed command: READ FPDMA QUEUED
[ 55.357532] ata1.00: cmd 60/f0:90:e0:34:a5/00:00:0e:00:00/40 tag 18 ncq 122880 in
res 41/84:f0:ea:34:a5/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 55.357613] ata1.00: status: { DRDY ERR }
[ 55.357636] ata1.00: error: { ICRC ABRT }
[ 55.357661] ata1: hard resetting link
[ 55.677344] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 55.779200] ata1.00: configured for UDMA/100
[ 55.779228] ata1: EH complete
[ 55.954538] ata1.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x6
[ 55.954585] ata1.00: irq_stat 0x40000008
[ 55.954610] ata1.00: failed command: READ FPDMA QUEUED
[ 55.954643] ata1.00: cmd 60/00:90:00:eb:a4/01:00:0e:00:00/40 tag 18 ncq 131072 in
res 41/84:00:10:eb:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 55.954725] ata1.00: status: { DRDY ERR }
[ 55.954748] ata1.00: error: { ICRC ABRT }
[ 55.954774] ata1: hard resetting link
[ 56.274496] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.367864] ata1.00: configured for UDMA/100
[ 56.367921] ata1: EH complete
[ 56.448401] ata1.00: limiting speed to UDMA/33:PIO4
[ 56.448412] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6
[ 56.448483] ata1.00: irq_stat 0x40000008
[ 56.448524] ata1.00: failed command: READ FPDMA QUEUED
[ 56.448578] ata1.00: cmd 60/00:10:58:ec:a4/01:00:0e:00:00/40 tag 2 ncq 131072 in
res 41/84:00:fe:ec:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 56.448715] ata1.00: status: { DRDY ERR }
[ 56.448753] ata1.00: error: { ICRC ABRT }
[ 56.448798] ata1: hard resetting link
[ 56.768215] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.856253] ata1.00: configured for UDMA/33
[ 56.856297] ata1: EH complete
[ 56.898690] ata1.00: exception Emask 0x0 SAct 0x60 SErr 0x0 action 0x6
[ 56.898770] ata1.00: irq_stat 0x40000008
[ 56.898816] ata1.00: failed command: READ FPDMA QUEUED
[ 56.898876] ata1.00: cmd 60/00:30:c8:ee:a4/01:00:0e:00:00/40 tag 6 ncq 131072 in
res 41/84:00:e8:ee:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 56.899029] ata1.00: status: { DRDY ERR }
[ 56.899072] ata1.00: error: { ICRC ABRT }
[ 56.899121] ata1: hard resetting link
[ 57.218560] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 57.311513] ata1.00: configured for UDMA/33
[ 57.311542] ata1: EH complete
[ 57.355664] ata1.00: exception Emask 0x0 SAct 0x500 SErr 0x0 action 0x6
[ 57.355754] ata1.00: irq_stat 0x40000008
[ 57.355806] ata1.00: failed command: READ FPDMA QUEUED
[ 57.355873] ata1.00: cmd 60/58:50:00:ec:a4/00:00:0e:00:00/40 tag 10 ncq 45056 in
res 41/84:58:1a:ec:a4/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 57.356044] ata1.00: status: { DRDY ERR }
[ 57.356091] ata1.00: error: { ICRC ABRT }
[ 57.356145] ata1: hard resetting link
[ 57.675608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 57.766781] ata1.00: configured for UDMA/33
[ 57.766816] ata1: EH complete
[ 57.806077] ata1.00: exception Emask 0x0 SAct 0x3000 SErr 0x0 action 0x6
[ 57.806134] ata1.00: irq_stat 0x40000008
[ 57.806164] ata1.00: failed command: READ FPDMA QUEUED
[ 57.806203] ata1.00: cmd 60/00:68:70:24:a5/01:00:0e:00:00/40 tag 13 ncq 131072 in
res 41/84:00:f2:24:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 57.806302] ata1.00: status: { DRDY ERR }
[ 57.806330] ata1.00: error: { ICRC ABRT }
[ 57.806362] ata1: hard resetting link
[ 58.125961] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 58.211103] ata1.00: configured for UDMA/33
[ 58.211156] ata1: EH complete
[ 58.249769] ata1.00: exception Emask 0x0 SAct 0x18000 SErr 0x0 action 0x6
[ 58.249854] ata1.00: irq_stat 0x40000008
[ 58.249901] ata1.00: failed command: READ FPDMA QUEUED
[ 58.249962] ata1.00: cmd 60/00:80:20:27:a5/01:00:0e:00:00/40 tag 16 ncq 131072 in
res 41/84:00:a2:27:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 58.255626] ata1.00: status: { DRDY ERR }
[ 58.258790] ata1.00: error: { ICRC ABRT }
[ 58.261924] ata1: hard resetting link
[ 58.579657] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 58.666164] ata1.00: configured for UDMA/33
[ 58.666199] ata1: EH complete
[ 58.716707] ata1.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x6
[ 58.718539] ata1.00: irq_stat 0x40000008
[ 58.720328] ata1.00: failed command: READ FPDMA QUEUED
[ 58.722121] ata1.00: cmd 60/00:d0:68:92:5c/01:00:0f:00:00/40 tag 26 ncq 131072 in
res 41/84:00:76:92:5c/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 58.725736] ata1.00: status: { DRDY ERR }
[ 58.727553] ata1.00: error: { ICRC ABRT }
[ 58.728965] ata1: hard resetting link
[ 59.046670] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 59.132488] ata1.00: configured for UDMA/33
[ 59.132515] ata1: EH complete
[ 59.180459] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[ 59.181979] ata1.00: irq_stat 0x40000008
[ 59.182990] ata1.00: failed command: READ FPDMA QUEUED
[ 59.183943] ata1.00: cmd 60/f8:e8:68:93:5c/00:00:0f:00:00/40 tag 29 ncq 126976 in
res 41/84:f8:6a:93:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 59.185831] ata1.00: status: { DRDY ERR }
[ 59.186778] ata1.00: error: { ICRC ABRT }
[ 59.187715] ata1: hard resetting link
[ 59.507035] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 59.610051] ata1.00: configured for UDMA/33
[ 59.610080] ata1: EH complete
[ 59.661766] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[ 59.663154] ata1.00: irq_stat 0x40000008
[ 59.664089] ata1.00: failed command: READ FPDMA QUEUED
[ 59.665027] ata1.00: cmd 60/98:38:60:94:5c/00:00:0f:00:00/40 tag 7 ncq 77824 in
res 41/84:98:64:94:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 59.666916] ata1.00: status: { DRDY ERR }
[ 59.669774] ata1.00: error: { ICRC ABRT }
[ 59.672954] ata1: hard resetting link
[ 59.990695] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 60.087554] ata1.00: configured for UDMA/33
[ 60.087600] ata1: EH complete
[ 60.217903] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[ 60.219413] ata1.00: irq_stat 0x40000008
[ 60.220456] ata1.00: failed command: READ FPDMA QUEUED
[ 60.221440] ata1.00: cmd 60/20:38:00:1b:3e/00:00:0f:00:00/40 tag 7 ncq 16384 in
res 41/84:20:18:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 60.223332] ata1.00: status: { DRDY ERR }
[ 60.224269] ata1.00: error: { ICRC ABRT }
[ 60.225206] ata1: hard resetting link
[ 60.544531] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 60.653686] ata1.00: configured for UDMA/33
[ 60.653713] ata1: EH complete
[ 60.701540] ata1.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x6
[ 60.703016] ata1.00: irq_stat 0x40000008
[ 60.704106] ata1.00: failed command: READ FPDMA QUEUED
[ 60.705056] ata1.00: cmd 60/88:50:78:1b:3e/00:00:0f:00:00/40 tag 10 ncq 69632 in
res 41/84:88:78:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 60.706949] ata1.00: status: { DRDY ERR }
[ 60.707884] ata1.00: error: { ICRC ABRT }
[ 60.708824] ata1: hard resetting link
[ 61.028237] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.142293] ata1.00: configured for UDMA/33
[ 61.142319] ata1: EH complete
[ 61.195399] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6
[ 61.197750] ata1.00: irq_stat 0x40000008
[ 61.200089] ata1.00: failed command: READ FPDMA QUEUED
[ 61.201690] ata1.00: cmd 60/20:78:10:39:38/00:00:0f:00:00/40 tag 15 ncq 16384 in
res 41/84:20:14:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 61.204897] ata1.00: status: { DRDY ERR }
[ 61.206484] ata1.00: error: { ICRC ABRT }
[ 61.208071] ata1: hard resetting link
[ 61.525313] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.630818] ata1.00: configured for UDMA/33
[ 61.630845] ata1: EH complete
[ 61.675724] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[ 61.677345] ata1.00: irq_stat 0x40000008
[ 61.678943] ata1.00: failed command: READ FPDMA QUEUED
[ 61.680539] ata1.00: cmd 60/50:90:30:39:38/00:00:0f:00:00/40 tag 18 ncq 40960 in
res 41/84:50:70:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 61.683756] ata1.00: status: { DRDY ERR }
[ 61.685369] ata1.00: error: { ICRC ABRT }
[ 61.686586] ata1: hard resetting link
[ 62.005676] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 62.108289] ata1.00: configured for UDMA/33
[ 62.108316] ata1: EH complete
[ 62.162783] ata1.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x6
[ 62.164411] ata1.00: irq_stat 0x40000008
[ 62.166015] ata1.00: failed command: READ FPDMA QUEUED
[ 62.167617] ata1.00: cmd 60/20:b0:d8:c3:3d/00:00:0f:00:00/40 tag 22 ncq 16384 in
res 41/84:20:d8:c3:3d/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 62.170837] ata1.00: status: { DRDY ERR }
[ 62.172433] ata1.00: error: { ICRC ABRT }
[ 62.173698] ata1: hard resetting link
[ 62.492749] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 62.607944] ata1.00: configured for UDMA/33
[ 62.607974] ata1: EH complete
Output of smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST1000LM014-SSHD-8GB
Serial Number: W3829AM6
LU WWN Device Id: 5 000c50 07be01372
Firmware Version: LVD3
User Capacity: 1,000,204,886,016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Sun May 10 11:12:02 2015 CEST
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
See vendor-specific Attribute list for marginal Attributes.
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: ( 150) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1081) SCT Status 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 117 099 006 Pre-fail Always - 158141600
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 429
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 4319585187
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1864
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 437
184 End-to-End_Error 0x0032 089 089 099 Old_age Always FAILING_NOW 11
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Min/Max 25/31)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 50
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6179
194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 19 0 0 0)
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
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 1779 hours (74 days + 3 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 10 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 b0 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 30 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 09:58:40.403 FLUSH CACHE EXT
61 00 08 ff ff ff 4f 00 09:58:40.403 WRITE FPDMA QUEUED
Error 12 occurred at disk power-on lifetime: 1722 hours (71 days + 18 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 30 50 3a c5 4e 00 00:01:28.045 READ FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 1537 hours (64 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:00:35.199 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:00:35.198 READ FPDMA QUEUED
60 00 08 10 10 2b 4f 00 00:00:35.188 READ FPDMA QUEUED
60 00 e0 20 e0 78 4f 00 00:00:35.187 READ FPDMA QUEUED
60 00 90 68 e1 78 4f 00 00:00:35.185 READ FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 1525 hours (63 days + 13 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 a0 ff ff ff 4f 00 00:00:15.374 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 80 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
60 00 68 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
Error 9 occurred at disk power-on lifetime: 1525 hours (63 days + 13 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 08 e0 9e 31 4f 00 00:00:15.146 READ FPDMA QUEUED
60 00 a8 ff ff ff 4f 00 00:00:15.073 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 98 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:00:15.068 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
Is this software bug or hard drive failure? Thanks in advance.

Thanks for your answers.
2ion wrote:
Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.
smartctl -v 1,hex48 -v 7,hex48 -a /dev/sda
should display OP's data in a usuable format.
In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you'll find people reporting that Seagate's own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad... Seagate is the horror. So, I'd say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.
OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive's cable? What was the situation before these errors showed up (maybe under Windows?)
smartctl -v 1,hex48 -v 7,hex48 -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST1000LM014-SSHD-8GB
Serial Number: W3829AM6
LU WWN Device Id: 5 000c50 07be01372
Firmware Version: LVD3
User Capacity: 1,000,204,886,016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon May 11 12:09:29 2015 CEST
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
See vendor-specific Attribute list for marginal Attributes.
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: ( 150) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1081) SCT Status 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 115 099 006 Pre-fail Always - 0x000005184840
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 433
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 0x0001017be679
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1880
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 441
184 End-to-End_Error 0x0032 089 089 099 Old_age Always FAILING_NOW 11
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 052 045 Old_age Always - 39 (Min/Max 37/39)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 50
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6282
194 Temperature_Celsius 0x0022 039 048 000 Old_age Always - 39 (0 19 0 0 0)
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
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 1779 hours (74 days + 3 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 10 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 b0 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 30 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 09:58:40.403 FLUSH CACHE EXT
61 00 08 ff ff ff 4f 00 09:58:40.403 WRITE FPDMA QUEUED
Error 12 occurred at disk power-on lifetime: 1722 hours (71 days + 18 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 30 50 3a c5 4e 00 00:01:28.045 READ FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 1537 hours (64 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:00:35.199 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:00:35.198 READ FPDMA QUEUED
60 00 08 10 10 2b 4f 00 00:00:35.188 READ FPDMA QUEUED
60 00 e0 20 e0 78 4f 00 00:00:35.187 READ FPDMA QUEUED
60 00 90 68 e1 78 4f 00 00:00:35.185 READ FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 1525 hours (63 days + 13 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 a0 ff ff ff 4f 00 00:00:15.374 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 80 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
60 00 68 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
Error 9 occurred at disk power-on lifetime: 1525 hours (63 days + 13 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
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 08 e0 9e 31 4f 00 00:00:15.146 READ FPDMA QUEUED
60 00 a8 ff ff ff 4f 00 00:00:15.073 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 98 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:00:15.068 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 1871 -
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.
These errors just appeared, not after upgrade and I didn't get them in the beginning. The situation before errors - everything worked exactly the same, I see no difference in performance, except that few seconds long freeze that sometimes happen. Can't tell about Windows, I have it pre-installed but never used it so I can't compare. I didn't check the cable, and I'd rather not do that - I don't want to mess with hardware, if I do something wrong I lose the warranty. If something is wrong then I'd rather have it checked and fixed by someone who knows how to do that (and for free, because I still have the warranty).

1 ATA bus + 2 HDD's + 2 OS's = ?best possible config?

As I still use some desktop audio composition applications in OS9 (NOT Classic), but use OSX chiefly for typical domestic use (web, mail, itunes), I would like to know the best possible means of optimising my G4 Digital Audio for VST hard disc recording with 2 HDD's hung off of the one ATA bus in the master and slave positions, without losing out on either OS9 or OSX system performance ?
At present I have the G4's OEM 40GB IBM internal HDD with both OS9 and OSX installed. Most of the data on the drive are mp3's, which I generally don't listen to too frequently on the computer (there's the iPod for that). I'm to receive a new 120GB Western Digital drive in the forthcoming few days which I'm eager to use in the best possible means.
I am assuming that my best means of proceeding would be to clone both OS's from the master 40GB IBM hdd to the new 120GB drive, copy all my audio app's to the 120GB drive, then switch the drives around on the bus, thus making the new 120GB drive my master while retaining the 40GB as a slave, acting mainly as a repository for my ipods content ?
Would it be advisable, upon formatting the new drive, to create two seperate partitions, one of which for OS9 and the other for OSX, for optimum system performance ? Should I first format the drive in OS9 or does it matter if I format it in OSX first ?
Will the fact that I have cloned over my OS's to the new 120GB drive affect my OSX applications in any way, in so much as my iTunes will still recognise where all the content is (if the content remains on the "original" master [now slave] 40GB drive), Safari's bookmarked pages will be retained, my email account will still be accesible from mail etc.
Or, would the simplest solution be that I shift everything (both OS's, all app's, data) off of the 40GB master drive to the slaved 120GB, and then switch the drives master/slave positions ? Would I then be able to delete both OS's from the original IBM 40GB drive, thus freeing up more hard disc, and proceed with the 120GB Western digital as my master system and main data drive.
Or (are ye still with me?) should I simply leave the OS9 system on the 40GB IBM, clone OSX to the new WD120GB drive, copy all my OSX related data (i.e. mp3's) to the WD, swop the drives master and slave positions, so that on booting into either OS9 or OSX I will always only ever be using either the master or the slave on that bus, thus making the best use of its limitations ?
If anybody has some idea of what it is I'm getting at then please feel free to share what advice you have (bar advising me to buy a new computer - I'll wait for the new Conroe'd Macs to appear before upgrading my computer hardware, thanks very much).
G4 Digital Audio 533Mhz Mac OS X (10.3.9) OS9.2.2

Hi, Brian!
You can simply initialize (format) the new WD drive using Disk Utility while booted to OS X on your IBM startup drive. Insure you check the Disk Utility box there to install the OS 9 drivers, which I'd recommend for any and all drives you have now or might get in the future, whether you're planning to run OS 9 on them or not. It doesn't take up any user-accesible space and not having the drivers should you need them is a problem that requires reformatting the drive and erasing everything on it in the process. You don't have to use OS 9 Disk Utility for anything beforehand.
As for master versus slave on a two-drive setup from a single ribbon cable, the Mac could care less which is which. It only cares that you have one of each. It doesn't care which drive is connected to which connector on the ribbon cable, either. You can boot and run equally well from a master or from a slave. The drives auto-negotiate, meaning that the controller recognizes the different drive speeds independently. Neither drive gets priority over the other for access to the bus. A slower drive configured as master will not limit the speed of data transfer on a faster slave drive. The drives will each be limited by their individual capabilities and by the overall "speed" of the drive bus, which in your case is capped at 66.7 MB/s maximum throughput.
If your IBM is a 5400 RPM drive, I'd put the OS's on the WD (regardless of its configuration as master or slave, which makes no difference), using the IBM as a backup drive.
If you're one who doesn't shy from partitioning, you could split the WD into two partitions, using one for OS X and the other for OS 9. You could later split the IBM as well, using different partitions for backups/clones and for data storage or a scratch disk. If you partition into multiple volumes, think through the sizes of the individual volumes you'll create. The most common problem folks run into is creating too many volumes and/or volumes that are later too small to be used effectively, wasting disk space. Safely changing partition sizes after-the-fact generally means erasing the entire drive to redo them. There are software utilities which will do this on-the-fly, but they all strongly advise backing up beforehand, which might say something about the risk in using them. Moreover, if you have to back up everything first, you may as well erase the drive and repartition from scratch...
Cloning makes an exact duplicate of a volume. Thus, if you clone your startup volume, you can boot to it and it will operate exactly the same as the original volume. The only apparent difference you'll see is that the startup volume you're running will be the one that appears on the top right corner of your desktop, instead of the original one. The clone copies everything over exactly as it was on the original, less some completely irrelevant temporary system files.
If you want to relocate your iTunes Music Folder (and all your iTunes music) from it's default location in Home/Music/iTunes/iTunes Music to another volume, you should perhaps do it after you've completed and tested the drive setups, cloning, etc. We can help you out with this if you'd like. It's easy to do, but involves a few setup steps to get it to operate correctly. I'd leave it alone for now until you're up and running from the new drive. At that point it will be easy to do.
Bottom line? I'd install the WD, partition it into two volumes, clone the IBM volume to one of the new volumes, copy the OS 9 Folder from the newly-cloned volume to the empty new volume, test startup and run from each of the new volumes to be satisfied that the cloning was successful, then trash the OS 9 folder from the new volume that has OS X on it. At that point you can either retain the IBM volume for backup or erase it and use it for whatever you desire (to include storing your music there).
If you need a cloning utility, I'd recommend Super Duper, which is extremely easy to understand and use. It's shareware, but allows for free use to do do full volume clones, which you are going to do here. Another good utility is CarbonCopyCloner (CCC), which is also fairly simple to use and allows for free use to do your clone. If you decide to keep and continue to use either one, CCC is less expensive, but SuperDuper has some additional, easy-to-use options that are enabled if you decide to purchase it.
Gary
1GHz DP G4 Quicksilver 2002, 400MHz B&W rev.2 G3, Mac SE30 Mac OS X (10.4.5) 5G iPod, Epson 2200 & R300 & LW Select 360 Printers, Epson 3200 Scanner

Burning errors from slower ATA bus?

I've been digitizing old videotapes and have gotten into a comfortable routine. The process is iMovie to iDVD to .img file to .cdr file to disk. After burning I store the .cdr files on my #3 hard drive.
The other day I tried burning a DVD from the .cdr file on that #3 hard drive, which is on the slower ATA 66 bus, and encountered repeated failures during the verification phase.
Burning the same file from the regular HD on the ATA 100 bus was successful.
Is it possible that the slower bus speed is the culprit? In the past that HD has given me some other problems, but the files copy from HD to HD just fine.

alphaniner wrote:Don't worry about the Radeon error for now. The other errors related to your drive bus are probably the problem. Normally I'd recommend checking cables and connections. But I've never seen a "SError:" line with so many 'details' and you have such errors on two ports, so it may be more complicated than that. Have you searched for info on Linux support of the controller?
Thanks for the response.
I searched for the things you wrote. By "drive bus" and "controller" do you mean the bus driver and device controller from this diagram?
http://www.linuxforu.com/wp-content/upl … 1/ldd1.jpg
Additionally, I found the following forum post while searching: http://ubuntuforums.org/showthread.php?t=2038227
Does that mean I should try reconnecting my drives to different ports on my motherboard?
Last edited by Commie Pinko (2013-12-17 22:39:41)

Failing HD's or is problem the main ATA bus

OK i'll try to give all the facts and keep this post as short as possable
I have G4 sawtooth? dual 1 gig with 3 hard drives, the 80 gig seagate that came with the G4 connected to the main ATA bus and about a year ago i added a 120 gig Maxtor as slave along with another Maxtor drive 80 gig i added as slave to the CD/DVD drive. Up to a couple of weeks ago no problems.
I leave my computer on at all times.
Both drives connected to main ata bus both drives running Tiger10.4.7
and the third OS 9.2.2
the problem started if i needed to restart for any reason, upon booting back up 1 or the other did not show up, checked all the connections, even using a new ata cable.... no change, just a restart would cause one or the other not to appear never to the the 3rd drive.
The problem keep happining more freqently, getting to the point that both drives would not appear, so it only booted off the OS 9 drive.
Ran disk utility on both drives
Checking the slave drive with 4 partitions never indicated any problems,
A few weeks ago the Master drive{Seagate) gave me 2 errors, "could not unmount drive" same thing using Techtool, i could not verify permmisions, "no valid packages found"
The drive still operated fine.
Now yesterday both drives would not show up and would only boot off the OS 9 drive.
Spent most of the night trying anything i could think of
One last thing struck me, I coneccted the OS 9 drive as master and pluged it into the main ata bus, you guessed it that drive did not boot,
after that i connected the other two drives to ata bus that the CD?DVD drive was connected to and upon starting up both drives are up and running fine so far (still got the same error messesages off the same drive as before).
So what am i dealing with here, i think there is a problem with the main ata bus.
So as of now im up and running with only 2 drives,
the third drive and the CD?DVD pluged into the main bus do not show up.
Well i think i covered everything, now anybody got any ideas on what's happining with the main ata bus, can't take it out to fix it, my only source of income is disability so paying someone is out of the question!
What to do?
Thanks for reading this now i await to hear from you.
sknoxx
Sawtooth G4 desktop duel 1gig Mac OS X (10.4.7)

is this what i need
I need a ide pci controler card with an ata133 interface
can i keep the drives i have internal
i m going to buy another HD 250 gig, now that will have to be external
right?
will the sawtooth model give me all 250 gigs
will the drive transfer data quicker than the iniernal drives
how many drives can be connected
i already have a pci usb card so i don't want usb or firewire
does it have to be mac only or will a pc card work as well
im in Hawaii so i would rather buy it here to avoid shipping costs
is this what i need?
this is at compusa for $40
Overview for
StarTech.com Dual Channel Serial ATA PCI Controller Card
(Based on manufacturer's information)Make the jump to Serial ATA performance with a two-port Serial ATA controller card from StarTech.com. The PCISATA provides your system with two independent Serial ATA ports for connecting internal Serial ATA devices like hard drives, CD-ROMs, CD-RWs and DVD drives.
Cutting-edge Serial ATA connectivity at the fraction of the cost of a new motherboard, the PCISATA2 is compatible with both Windows® and Linux® operating system environments and is backed by our lifetime warranty and FREE lifetime tech support.
Features
Compliant with PCI Specification V2.2
Compliant with Serial ATA Specification V1.0
High-speed data transfer rates of up to 150 MBytes/sec
Two independent Serial ATA channels support one Serial ATA device on each channel
Controller Type: SATA
Slot Type: PCI
Port Connectors:
2 x SATA Female
are any of rhese what i need?
EIDE ULTRA ATA-133/100 PRO CONTROLLER FOR MAC
Price Range: $55.87-79.99
Manufacturer: SIIG Inc. Part number: SCMP4A12
Information on EIDE ULTRA ATA-133/100 PRO CONTROLLER FOR MAC
Full specs
User opinions
Manufacturer info
Compare with most popular
Full specs
General
Device Type
Plug-in card
Type:Interface Type
PCI
Localization
English:N/a
Expansion / Connectivity
Expansion Slot(s) Total
1 PCI
Port(s) Total (Free) / Connector Type:Port(s) Total (Free) / Connector Type Port(s) Total (Free) / Connector Type
2 2 for PC connection Storage ATA-133 40 pin IDC Male 2 Internal Installed
Expansion Bay(s) Total
None
Expansion / Port(s) Required
Slot(s) Required
1 PCI
Port(s) / Connector(s) Required
None
Bay(s) Required
None
Software / System Requirements
Operating system
Apple MacOS X, Apple MacOS 8.6, Apple MacOS 9.x
Storage Controller
Storage Controller Supported Device Type:Supported Device Type
CD drive, Hard drive
Storage Controller:RAID Level
N/A
Data Transfer Rate
133 MBps
Storage Controller:Controller Interface Type
ATA-133
Max Storage Devices Qty
4
Controller Interface Type:Channel Qty
2
Miscellaneous
Package type
Retail
Warranty
Service / Support Details
Limited warranty Parts and labor 5 years Bring-in
Power
Power device type
None
sknoxx
Message was edited by: Steve Knox

G60-519WM motherboard bus speed, CPU support list

I was given this laptop in 12/2010. It of course has the celeron 900 in it with an 800 MHz fsb. My question is what bus speeds does the mobo support and where can I find a list of supported CPUs. The only semi-reliable info I found suggested upgrading the cpu with a t9600 that has a 1066 MHz fsb.

Hi:
Below is the link to the Maintenance & Service Guide for your notebook.
http://h10032.www1.hp.com/ctg/Manual/c02985882.pdf
Supported processors are listed in Chapter 1, starting on page 1-1.
Paul

WHY IS S.M.A.R.T STATUS SUPPORTED ON ATA BUS BUT NOT ON SCSI?

I have 4 internal HD's on a G4 733 S-Drive (Digital Audio) running X.4.4
and my question is:
Why is S.M.A.R.T STATUS supported on the ATA bus but not on the SCSI bus?
Is there something wrong with my computer if only 2 of the 4 internal HD's read "Verified" and the other two state "SMART STATUS NOT SUPPORTED"?
The only reason I noticed this is because I decided to clone my main HD running X.4.2 (supported) to a larger 7200 rpm HD connected to the SCSI. My Main HD is in position one on the ATA Bus. All four internal hard drives are currently running well although the SCSI bus was a bit slower upon startup only. So I updated the cloned HD to X.4.4 and then loaded iLife '06 to the cloned drive just to make sure all runs as expected. Which it did.
I ran apple's DU on all four internal HD's and all of them showed the green writing with No red lettering. But can someone please help me interpret the following from apple's DU on each HD which reads follows:
Disk Description : IBM-IC35L060AVER07-0 Total Capacity : 57.3 GB (61,492,838,400 Bytes)
Connection Bus : ATA Write Status : Read/Write
Connection Type : Internal S.M.A.R.T. Status : Verified
Connection ID : Device 0
Disk Description : WDC WD1200JB-00HUA0 Total Capacity : 111.8 GB (120,034,123,776 Bytes)
Connection Bus : ATA Write Status : Read/Write
Connection Type : Internal S.M.A.R.T. Status : Verified
Connection ID : Device 1
Disk Description : ATA WDC WD1200JB-00G Media Total Capacity : 111.8 GB (120,034,123,776 Bytes)
Connection Bus : SCSI Write Status : Read/Write
Connection Type : External S.M.A.R.T. Status : Not Supported
Connection ID : SCSI Target ID 0, Logical Unit 0
Disk Description : ATA Maxtor 6Y120P0 Media Total Capacity : 114.5 GB (122,942,324,736 Bytes)
Connection Bus : SCSI Write Status : Read/Write
Connection Type : External S.M.A.R.T. Status : Not Supported
Connection ID : SCSI Target ID 2, Logical Unit 0
Thanks in Advance.
SDMacuser

Hi, SD!
I haven't found anything specific on this, but I have always been under the impression that S.M.A.R.T. simply doesn't work with SCSI or externals. In my own experience, if I switch a drive from FW to my IDE bus, it reports. If I switch from the IDE bus to FW, the drive's S.M.A.R.T isn't supported.
Other than being unable to actually run and verify S.M.A.R.T. on your SCSI or external drives, I really don't think that you need be concerned with the "not supported" message, which simply is telling you that the particular drive or bus can't run S.M.A.R.T. (man! I hate typing all those "periods"...).
It also isn't supported on some old hard drives, even if they're connected to the IDE bus (like those 6-10 giggers I scrounge from ancient PCs that my friends and relatives junk when they finally switch and get new Macs...)
Regards,
Gary
1GH DP G4 Quicksilver 2002, 400MH B&W rev.2 G3, Mac SE30 Mac OS X (10.4.2) 5G iPod, Epson 2200 & R300 & LW Select 360 Printers, Epson 3200 Scanner
1GH DP G4 Quicksilver 2002, 400MH B&W rev.2 G3, Mac SE30 Mac OS X (10.4.2) 5G iPod, Epson 2200 & R300 & LW Select 360 Printers, Epson 3200 Scanner

How can I determine Bus Speed

Hi all
Dumb question #2.
The beast is a G4 MDD with dual 450MHz chips and the model number is M5183 and the machine number as per System Profiler is 406. Serial number is SG03402HK5W
Got all that.
I need to determine Bus Speed so I can buy the proper Ram Cards for this machine. It was supplies from the eBay seller with PC133 chips in there and surprisingly enough it runs 9.2.1 just fine.
How can I determine whether my machine is a 100MHz or 133MHz.
I suspect my Machine is not an MMD but a Gigabit Ethernet with dual 450 processors. Is this correct?
John Fenn

You can find all the G4 specs here to identify your machine and get the RAM specs and bus speed.
-Douggo
G4 Dual 867 MDD Mac OS X (10.4.3) 1.25GB RAM; 3 HDD's; Pioneer 106D; 20" Cinema Display; 30GB iPod Photo

Changing the system bus speed?

Hello,
I have an overclocked 700MHz (now 900MHz) eMac, with a 100MHz system bus speed, and I am wondering, is the only way of messing with the processor speed overclocking it? And if you CAN change the bus speed, will it make the eMac feel any faster? Since the processor is at 900MHz, I would like the bus speed to be around 750-850MHz. Is that even possible? I've tried googling this kinda thing, but all I get is how to overclock it. (I got that part already, I just want to know if I can change the system bus speed too.)
Regards.....
Your fellow eMac User,
Matthew Knice

I'm thinking that, with two months of viewing, it either isn't possible or offeres too much risk of turning the computer into an expensive doorstop.
The Beige G3's bus speed was controlled by jumpers, relatively easy to tweak. Newer Macs tend to be hardwired

Can't fully boot OS 9 when OS X 10.4 drive is connected to ATA bus

A friend has a g4 733 quicksilver running os 9.2.2. He bought a new 80gb drive and I installed it along with OS X 10.4. Updated and installed various applications (mainly audio apps).
Then tried to boot back into OS 9 and at the very end of the startup progress (when the extensions are loading at the bottom of the screen) I get a message - something like "error 10" or "illegal instruction" or "bus error" (it changes).
I'm able to start OS 9 holding down shift with extensions off, but no combination of checked or unchecked extensions seemed to fix the problem (in fact, un-checking all extensions in extension manager still reproduced the problem; how is that different than booting with shift?).
The only solution I've found is to completely disconnecting the new hard drive with 10.4 from the ATA bus. BTW... When I boot OS 9 with extensions off, I can see the OS X drive. Also, OS X can see the OS 9 drive. And I tried master/slave and CS jumper settings on the hard drives.
Anyone have any ideas or suggestions?
Thanks!!

Hi, bcometa -
When a machine is started (in OS 9) with Shift held down, not only are extensions disabled (selectively - there's a couple or so that are intentionally not disabled), but control panels and things in the Startup Items folder in System Folder are prevented from loading.
The problem causer may be a control panel, or it may be something in the Startup Items folder - or both. It would be something that would attempt to interact with an additional drive, and fails in the attempt. Things in this category can include 3rd-party software, such as: a disk utility like Silverlining or Norton; a security app such as virus software; or most anything else designed to scan or check drives for something.
Sometimes resetting PRAM can help, by forcing the Mac to acknowledge and register a change in hardware configuration during startup.
in fact, un-checking all extensions in extension manager still reproduced the problem; how is that different than booting with shift?
In addition to disabling extensions (selectively, as I mentioned earlier; Text Encoding Converter is one that is not disabled, as I recall), booting with Shift held down in OS 9 also:
• prevents the loading of control panels;
• prevents the loading of certain items which are located outside the Extensions folder, loose in the System Folder;
• prevents the loading of items in the Startup Items folder;
• prevents Disk First Aid's intrusive checking of the drive after an 'improper' shutdown.

Is my HDD an ATA and is on ATA bus 0 ???

My powerbook is 1,67 GHZ and 80 Go and won't boot , the optical drive is broken , so i use target disk mode to reinstall it . But it shut down when i press the "T" button to enter TDM. And if i don't press "T"
According to Apple ,I must be sure that my hard driver is an ata and on ATA bus 0 because "it's normal for a computer to shut down while entering in Target Mode if it hasn't detect any ATA hard drive on a ATA Bus 0
What is ATA Bus 0, the only thing i know is that my Hard is an ATA/IDE
What to do for solve this problem ???

There is another reason you may not be able to enter target disk mode, which is if you have a firmware password on your system. See this Apple note: http://support.apple.com/kb/ht1352
My 1.67Ghz Powerbook has the internal hard drive as defined By Apple, ie, there's no option to change the ATA bus designation, and it can enter target disk mode.

Disk utility reports failing hard drive with error code STF/8/3:2 ATA BUS 0

My imac G5 (running Tiger) suddenly decided not to boot past the grey apple screen with the spinning wheel. I ran the disk utility and received error code STF/8/3:2 ATA BUS 0 MASTER on the mass storage test. I tried to run repair and only received a message "fatal hard drive error etc... back up, recover asap... I could not access the disk so I connected my new MacBook Pro by firewire in target disk mode. My HD shows up however, "nothing" shows up under when my "user" file. All I care about saving is my iphoto library. Everything else is trivial. Can someone Please help me? Is there any way I will be able to save this file?
Message was edited by: Elizabeth Burson

Welcome to Discussions - you can try DiskWarrior and see if it can retrieve some of your data. You can also take it in to Apple with an external fire wire drive you have purchased elsewhere (cheaper) and see if they can transfer the data. You can then install the external into your computer.

Bus Speed on LimeBook

This Lime iBook is slowing down more and more as I add stuff to it. I'm wondering how much bus speed has to do with it, accessing and all that. I perform all the regular maintenance and use macJanitor also. Is it just a consequence of older technology and slow processor speeds? Mine is the SE with 466 mhz CPU.

RichardIf you are using more and more of your Hard Disk space the system is limited on the amount of virtual memory it can use. It is advisable to leave at least 10% of your hard disk free. I assume you are using Mac OS 9 (this was what would have been supplied with your Lime iBook originally. The hard disk could also do with de-fragmenting now and again under OS 9. (Although you shouldn't do this if you do have OS X installed.) You can tell the bus speed of a mac by looking in the System Profiler. The Processor speed is also a good hint. Your processor is 466. 466/66.67 = 7. This is the multiplier (usually an integer). If you go to the Control Panel and Energy Saver there is an option check box which can reduce the multiplier to 5.5 ... 5.5x 66.67 = 366MHz - this saves battery power - only available on the 466 iBooks and Powerbooks. Many of the overclocking mods for Macs involve changing the multipier - but this involves serious hardcore soldering so it's not an option unless Apple builds in the option.
To get your iBook to go fast I recommend you:
Up your RAM to the maximum (576Mb)
Upgrade the Hard Disk or purchase a Firewire External Drive.
My other tip would be to not buy brand new software - it invariably requires more processing power (as it is aimed at today's machines). Look out for the same (geniune) software but older versions on eBay.

MOVED: [Opteron] AGP Bus Speed is 0x

This topic has been moved to Server/workstation.
[Opteron] AGP Bus Speed is 0x

This topic has been moved to Server/workstation.
[Opteron] AGP Bus Speed is 0x

ERROR CODE 2STF/8/3: S-ATA BUS O-Master

I was running Pro ToolsLE on my iMac G5 and then all operations stopped or froze, I forced quit, lost what I was working on when it stopped. Then I tried to restart after deleating the pro tools prefs file and the gray screen with apple symbol and indicator comes up and doesn't continue to boot up.
I ran Tech tools from the install disc and the ERROR CODE 2STF/8/3: S-ATA BUS O-Master comes up. After researching further I think the Hard Drive has Failed!!
Can this be true? I have not used the computer that much. I will be calling Apple Care. Has anyone else experienced this, and is my iMac G5 not as reliable as I thought?

Welcome to Discussions - hard drives can fail at any point, the amount of use is no indication of longevity. My iMac G5 is a Rev A, and (fingers crossed) the original drive is still working flawlessly. In every batch there are some that will fail prematurely and others that will last long past their fail date. Please do call Apple Care and see what they say.
See if there's any way you can put your computer in Target Disk Mode and get your data off the drive before it goes in for repair.
Miriam

ATA Bus Speed?

Similar Messages

Maybe you are looking for