Second SATA HD formatting...

well i managed to update my bios successfully, again no hitches,
but the ram is still only showing up as 2 x 256 instead of 2 x 512,
even when run solo.
i cant install XP SP2 yet either because the machine is primarily for running ProTools, which isnt compatible with it yet.
might i be wise to send back the ram while i still can?
and i need advice on how to get my second SATA drive working!
i left it out til i got everything up and running with the boot drive and now want to get it going for use as my audio drive; ive hooked it up, it appears as working fine in device manager, but i cant seem to format it!
partitionmagic wont do it either. in fact, it wont do anything! i put a 40gb partition on my boot drive when installing winxp, intending to set the other 40gb of that drive up later to store games and random files on, and now i cant seem to set up even that second partition, thus my 80gb drive is only operational as 40gb! and my second 160GB drive cant be brought to life at all!
egadz the hassle!
please help!

Hi.
In the many times I am in Dublin, I've never been called a leg end.
The external drive, if its SATA, the drivers are already on C:> drive, so you should be able to see and format it, IDE just as any IDE.
The Rambiz, best run memtest86 and see if Ram is compatable with rig, and itself.
Then in Bios, change Memclock mode to limit, then memclock value to 333 or 400, some mem works at DDR333 only, try that and see if it finds the other stick. You might try Dimm3 for 2nd stick, sometimes Dimm2 is flakey with certain Ram.
Ram that gives Memtest errors at 400, often is OK at 333. You may have a flakey stick, if all errors in MT are above 512, you will know stick 2 is not compatable with stick 1, try them seperately, if 1 still gives errors RMA it.
It should run at 200 : ie 200x2 = 400   : 157 x 2 =333.
Never mind the million, a guiness will do.
Cheers
jocko

Similar Messages

  • Second SATA Drive Read Only

    Need some help:
    I took my SATA Drive out of my Windows Computer (NTFS) 250GB, and put it into the second SATA bay of the G5. It had one jumper on the 3rd setting.
    The G5 found it and it can read fine, but it is read only. nothing i do can erase, format, etc. Disk info says owner:no, permissions:only read, can be formatted:no, SMART Status not supported, pretty much locked. It shows up as a 232.9 GB WDC WD2500JD-00FYB0.
    Any Suggestions on how to make writable/format? Is it a jumper issue?
    Thanks for your help out there!

    According to "http://docs.info.apple.com/article.html?artnum=75320"
    "Warning: NTFS formatted drives cannot be used in a Macintosh (except as read-only with Mac OS X 10.,3 as noted above). If you attempt to use a NTFS formatted disk, upon starting up the Mac OS will prompt you to format the drive. Do not format the drive, doing so will erase the contents of the drive. If you have an NTFS formatted disk, you must use another method to transfer the data from the PC to the Macintosh".
    Did you have this warning when you started up your G5 after installing the second drive ?
    If yes you may have to shut down the computer, disconnect the second NTFS SATA drive, restart and shut down, reconnect and restart to reformat.
    Just a suggestion.
    Good Luck
    Luc

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

  • My new macbook pro is giving me hardtime. even apple team is not being to solve it. they replace the motherboard first it didn't work. second time they formatted the computer and that also didn't work. every time my mac showing different problems.

    my new macbook pro is giving me hardtime. even apple team is not being to solve it. they replace the motherboard first it didn't work. second time they formatted the computer and that also didn't work. every time my mac showing different problems.
    At first my computer had issues. Once it go to sleep it will not back again. I dropped my laptop at apple store to fix it. After 10  days they returned my laptop saying they were no able to fix the problem so they replaced motherboard aiming if that might help. Acttually that didn't help.I had same issue again. I visited apple store again. This time they said they could fix, if I will allow them to format the harddrive. I said ok. They formatted it. It was working fine for few daysAfter few days compter is taking.even more than 15 min to shutdown. Now computer has another problem. It is being hang frequently like every 20'to.30 min.
    I don't know what to do? I still have one month left on first year warranty. I have requested couple times to apple associates either to fix or replace or refund. They are showing me rude behavior. They are not understanding my situation. I am a student. I need to do lot of home work. Since last three month my mac book and apple associates giving me hard time. Any suggestions are welcome.

    Contact Apple Customer Care - not Apple Care - Customer Support. Have your receipts handy and/or case numbers. Be patient, be calm, and tell your story just as you have here. I get the sense you are not in the US and don't have access to an Apple Store but are going to an independent shop. This makes using Customer Support all the more important. If phoning isn't viable, use registered mail.
    Since time is running short, be prepared to purchase AppleCare to exennd your warranty 2 more years. Yes, you shouldn't have to do this, but it gives you added protection and more opportunities over the next 2 years to claim a replacement computer if you don't get one immediately. After dealing with a similar unhappy situation with a Mac in the late 1990s I finally got a replacement computer and reimbursed for the AppleCare policy.

  • Jumper Settings for Second SATA-II drive Installed Into Dual 2.0Ghz G5

    I have installed a second SATA-II 500GB Maxtor drive into a brand new (purchased as re-furbished computer from Apple) dual 2.0Ghz PowerMac G5. The drive has four connector pins with a jumper slide over the last pin on the right. Before I power up the computer I want to verify the correct jumper settings. According to the Maxtor website, no jumpers are required since the "serial ATA host automatically determines the master and slave hard drive." And according to a MacSales tech (this is the vendor where I purchased the Maxtor drive) I should pull off the existing jumper. Can anyone verify if this is, in fact, the correct jumper setting (no jumpers on the connector pins) for this drive on this system?
    G5 dual 2.0 Ghz   Mac OS X (10.4.8)  

    Hello! From the Maxtor web site.
    "PLEASE NOTE: Unlike standard ATA drives, Serial ATA drives DO NOT require the use of jumpers to configure the drive. Please disregard any references to jumper settings and Master, Slave and Cable Select configurations in the Maxtor Installation Guide."
    I'd leave the jumper as is came when you got it. tom

  • Install second SATA Drive

    Hi,
    I currently have a PM G4 with two internal ATA drives installed and one SATA drive installed. I want to install a second SATA drive and have the extra power connection and SATA connection, but my question is where do I get side rails so I can install the secong SATA drive on top of the first similar to how the ATA drives are connected.
    Thanks,
    Bob

    you can if you take your optical drive out.
    go here for more info owc.

  • Second SATA Hard Drive Formatting

    Hi There,
    I have just fitted a second 1TB SATA HD to my Mac Pro, can anyone tell me how to format it in 'Disc Utility'
    Many thanks,
    Michael

    Hello Again,
    I've sorted this now, remembered what i did last time, Thanks.
    MP

  • Installing a second SATA hard drive - Problems booting

    Hi,
    I currently have one Maxtor 160GB SATA hard drive in my system with my operating system installed. I have another identical hard drive that I'm attempting to install now, into the second of five available SATA ports on my MSI P965 Neo motherboard.
    When I plug in the second hard drive, though, Windows will not boot. It gets to the Windows logo screen with the progress animation, but before even the animation can begin, it stops and the screen freezes. This does not fix itself with waiting.
    My boot priorities are set to: DVD-ROM, CD-RW, hard risk. The hard disk priorities are also as they should be to my knowledge - although it can be tricky because when ordering, both disks have the same name. I have tried with either one on top of the list, and you cannot remove a drive from the list alltogether.
    The SATA cable is in perfect condition. My BIOS is up-to-date.
    When I plug the hard drive in when the system is already running, Windows will detect it and files can be written/read flawlessly. As soon as I restart, however, I run into the same issue.
    The first HDD, with the OS on it, is in SATA 1, the second HDD is in SATA 4. Ports 3, 6, and 7 are unused.
    I'm out of ideas at this point, I don't see any other options that need to be changed.
    I'd appreciate any input you can offer - thanks in advance!

    I would debug this drive you are talking about which clears off all data and partitions information. Take out the good drive and leave in the dodgy one. Boot to a floppy with this dell win95 boot disc.
    http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R19775&formatcnt=1&libid=0&fileid=19601
    When at the A: prompt: type debug and enter, you get a (-) prompt and then enter the following script exactly:
    F 200 L1000 0 (enter)
    A CS:100       (enter)
    xxxx:0100 MOV AX,301  (enter)
    xxxx:0103 MOV BX,200  (enter)
    xxxx:0106 MOV CX,1     (enter)
    xxxx:0109 MOV DX,80   (enter)
    xxx:010C INT 13    (enter)
    xxxx:010E INT 20   (enter)
    xxxx:0110             (enter)
    g                        (enter)
    q                         (enter)
    restart your system.
    Now you can put back in your first drive as well, boot up into windows and use the disc manager to repartition and format.
    Old school! If you are still having problems I would replace the drive.

  • Can you a second Sata Hard Disk Drive in M Series?

    Hello,
    Can I install a second hard drive in M Series?
    In particular I would like to install a Seagate Barracuda SATA 1TB drive.
    I know it only has one bay, but I can house the disk in a separate case.
    Thank you
    Solved!
    Go to Solution.

    I believe it depends on the version of the m series you have.
    on the m72e series (small form factor); there is only one 3.5" sata bay.
    on the motherboard, there are 3 sata headers (cd drive/ hard drive + 1 other).
    the way i did it was to order a silverstone dual 2.5 => 3.5" drive adapter that screwed into the drive slot (you have to be careful; not all drive adapters have bottom screw mounts).
    This allowed me to put a 2.5" ssd and a 2.5" hard drive in the case.
    otherwise, it would be pretty tight/impossible to squeeze in 2 full size 3.5" hard drives in the m72e

  • Mounting a second SATA HDD in the Pavillion 500-304nd

    I have recently purchased the desktop mentioned in the subject line, along with a second 1TB SATA HDD to add to it. I did find the connections for a second drive but cannot find a place on the computer's frame to physically mount the drive. What's the secret here? Do I need an extra part to mount the HDD, and if so: where can I find one?
    This question was solved.
    View Solution.

    Hi,
    This HP posted document shows how to remove the existing hard drive but it doesn't show how to add a second hard drive since your PC is not provisioned for multiple hard drives.
    Review this thread.  Look at message #9.  There are many different ways to modify a PC as such but the solution was not provided by HP. If you think that this solution would work for your then ask the poster where to obtain the needed parts.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • Second Hard drive formatting some help please!

    Hi, I just installed a second SSD in place of my superdrive, a sandisk Extreme. Now however I cannot format the drive to use it... My enclosure for the superdrive has not arrived so I cannot use the OSX leopard disc to format the drive! any suggestions? The disk appears in the disk utility but gives an error message when trying to "erase" (format) the drive. If anyone knows hows to format the drive let me know! This is very frustrating because my system SSD is full! The following picture is the error I get:
    System:
    2011 MBP 13" 2.8 Ghz i7
    intel HD 3000
    16 Gb of G. Skill RAM
    SSD1: OCZ Vertex 3
    SSD2: Sandisk Extreme

    I'm always sadened when I see where someone hasn't been making backups that they can boot from (ie, clone) as part of their backup and maintenance strategy.
    Apple Disk Utility -> RESTORE tab, can also copy Source => Target
    CCC is nice if you want to copy/move your /Users/my_account to another drive
    (Also essentially you need to be able to boot off another drive to repair your system.)
    Replacing the system boot drive with new faster drive really helps. Having everything on one drive tends to bog down and be sluggish compared to having things spread out on multiple drives.
    /Users/my_account/Movies (or Pictures and other folders)
    - can be relocated to where you want.
    One of the best values in performance for boot drive has been the 640GB WD Caviar. Cost of disk drives have actually been going up, at least some vendors, lately.
    No one I know whould say you can't or shouldn't use a drive larger than 400GB, other than keeping the operating system on fast small lean and mean, and not load it up with a lot of media files and such.
    There was a 400GB WD drive that wasnt' compatible 4 yrs ago with G5s; Apple didn't update their hardware requirement to list larger drives when they came out later (currently, 2TB drives are being supported in most new systems today).

  • Converting seconds to minutes format

    Post Author: mwatson
    CA Forum: WebIntelligence Reporting
    How do you convert seconds to minutes in mm:ss format?

    Post Author: SKodidine
    CA Forum: WebIntelligence Reporting
    totext(truncate(/60),0,'','') & ":" & totext(remainder(,60),0,'','')

  • Convert seconds to HHMMSS format

    Hi All,
    Is there any function module to convert given no. of seconds,  to HH:MM:SS format . If seconds lessthan 86400, then we convert it in straight forwad way by usoung MOD formula. If sec >= 86400 then also i need get in format 24:MM:SS format.
    For example if sec = 86440, then after conversion format would be 24:00:40. Any FM to convert in this format. Please advise.
    Thanks
    Konda Reddy

    http://www.google.co.in/#hl=en&q=ConvertsecondstoHHMMSS%2B+SAP&meta=&aq=&fp=2cf627ce33d082a9

  • SATA harddisk - Format c: - Other partitions?

    I have 5 partitons (c: - g:) and Windows 2000 is installed on drive c. I want to format my c drive to reinstall Windows 2000 but I want to keep the other partitions and the data on them. I read that I need to press R on the first screen after I booted WIndows 2000 from CD, then K to get some sort of console where I can enter format c:. Because I have a SATA harddisk I need to install those "special" drivers with F6 as soon as Windows 2000 booted from my CD.
    Here's my question (maybe a stupid one but...). If I install these drivers and format my c: drive will the data on the other partitons remain unchanged? I don't want to loose my stuff on the other partitions and I'm not 100% sure if the reinstallation of the HD drivers will ruin my other partitions somehow.....
    Thanks for your help and I wish everyone a Happy New Year!
    Scipio

    It depends .
    If you have made extended partition with logical drives , removing the primary
    partition will result in a lost extended and all others , as data for the extended is also strored in the 1'st primarys mbr.
    If all partitions are primarys there is no danger deleting one partition as
    they all are indepentent of each other .
    Have a look at this article , how deleting primary and get extended back .
    http://support.microsoft.com/?kbid=249085
    Peronally , my impression is that a lot of users loose extended / logical partitions
    when altering/changing/deleting the system configuration of partitions .
    Doing partition deletions/modification on systems with extended / logical without backup of its data , and all data you want to preserve is plain stupidity .
    Stibe for the usage of four primary basic pr.HDD is the best and safest way to have your data .

  • Hundredth of a second ,how to format?

    How do I find the hudredth of a second, Timestamp is giving nano second and the SimpleDateFormat can format date to seconds or milliseconds, but I didn't find hundred of a second, I need to format date as hh:mm:ss:HH(HH is defined as hundredth of second in my requirements).
    thanks,
    Sujatha.

    Capital S is indicating millisecond in
    SimpleDateFormat, I checked the API.
    any more hints?If you are checking the API, there is a method relevant to your needs in the Timestamp class. It would have been much faster looking yourself than fishing for hints.

Maybe you are looking for

  • Iphone 5 stuck on connect to itunes after iOS 6.1 update

    I connected my iphone to itunes to download a few songs and the iOS 6.1 update.  I come back to the phone 15min later and itunes says the download was incomplete it is stuck on the connect to itunes screen.I try to restore the phone, but the device i

  • Infanite recovery mode

    when i plugged my iPod touch into the computer, it was not being detected by iTunes. so i restarted it. nothing. i then wiped it from the ipod. nothing, and now no music. i put it into manual recovery mode, and when then it detected the iPod. when i

  • Does the sound return after doing a system restore ?

    operating system windows 7 problem with sound

  • How to display 1st screen of movie file as a thumbnail image?

    Hi. I have a site that allows registered users to upload a video file. I would like to display the 1st screen shot from the video file as a thumbnail image for the file (like YouTube). Is there any way of automating this as part of the file upload or

  • FrameMaker 7.0 & Distiller 5.0 - Saving to PDF crashes application

    FrameMaker 7.0p579 Distiller 5.05 Windows XP SP2 Weve been unable to save FM files to PDF. I uninstalled FM, rebooted, reinstalled FM 7, and loaded patches 576, 578, 579. Now we receive this error message, after which the application just shuts down