Adding SATA drives

Ok, I got ahold of some laptop 60gb sata drives. I wanted to see what they would do so added them to the motherboard. on first boot without adjusting the BIOS I got an error not able to find boot device. Turned off something in Integrated setup and it booted but then no new drives in XP. So read the forum went back made some changes and it would start to boot and then lose the screen, monitor looked like it still had sync but nothing. So guys what the heck did I do wrong. I went back several times into the Bios and made changes and it would never fully boot. Also tried to remove my primary IDE drive and leave just one SATA drive on and boot to the XP CD and it did not see the drive. new to SATA so dont hurt me to bad...hahaha
Thanks in advance

So, are you now unable to boot to your original XP? Were you trying to install XP on the SATA drive or just add it?
If you can boot XP, and can't remember if you installed Intel INF's, you should do this as suggested by Kingfisher.
If not, click on the FAQ link in my sig and read #5(HDD's) for the proper Bios settings to enable all the SATA/IDE ports on this motherboard.
Then reboot to the Bios again and go to Advanced Features>>Boot Device Selection and make sure the drive with WinXP is in the list. It might be trying to boot off the old OS from the laptop drive you added. This would explain why it won't boot.
If "PATA Only" in the Bios won't work try "SATA Only"(even though your OS is on a PATA drive).
Normally adding a SATA drive on the 865/875 boards is just a matter of using the Bios settings from the FAQ thread, resetting Boot Device select if required, and formatting the new drive in XP.

Similar Messages

Problem adding SATA drive

Hi all
First time poster, long time lurker.
Hoping someone here can shed a bit of light on an unusual problem I am having.
Before I outline the problem I will say that my system is running beautifully, I've not got any problems with it in its current configuration, in fact it is the most stable set up I've owned so far. I am a happy MSI owner.
If I can get this issue sorted I'll be an extremely happy MSI owner. Now to the actual problem...
I have a pair of 36GB SCSI160 drives that I use for my system and apps drives and a 120GB ATA drive that I use for storage.
I've purchased a 120GB Seagate Barracuda SATA drive to add to my system as I've just about run out of space on the 120GB ATA drive, my storage drive.
I installed the new drive, set it up as a single Raid 0 volume using the SATA boot utility and checked it all under DOS, tested all OK.
The problem happens once I've booted into windows and enter my username and password.
I get a BSOD, IRQL_NOT_LESS_OR_EQUAL STOP 0x000000D1 Error which then does a memory dump, do a reboot and same thing.
Remove the SATA drive and system boots and works flawlessly, I'm typing this on it right now!
I can have the SATA drive connected to the system and NOT have a volume on it and the system works fine, naturally WINXP doesn't see the drive but it doesn't interfer with the operations at all. As soon as I put a volume on the drive... bam, BSOD next time I try to login after I boot up WinXP.
This indicates to me that the issue is a driver problem... I've tried the latest and still the same situation.
Any suggestions folks?

Quote
Originally posted by Wonkanoby
https://forum-en.msi.com/index.php?threadid=49947&sid=&hilight=scsi
things like this are all over the board though yours does not sound totally the same
Thanks for the link.
Very informative. Appears that there isn't an option for me at this time other than NOT using one or the other... I can have SCSI card and no onboard SATA OR I can have onboard SATA and no SCSI card.
Seems to me a BIOS revision is needed as it appears that this is not an uncommon scenario.
Thank you for your time Wonkanoby.

Adding first SATA drive - Questions

I'm going to be adding a SATA drive later today (Newegg and FedEx willing) and was just curious about a couple of things.
What I want to do is remove my old drive and add the SATA, install windows, and then install the old drive and transfer my files.
What (if any) setting do I have change in the bios on my K8N Platinum to get the SATA to work? When I add my old drive, what will be the default boot drive? How do I make it the SATA?
I'm up for any other thoughts you might have too.
Thanks
Aspire Turbo case
AMD Athlon 64 3000+
K8N Neo Platinum
ATI Radeon 9600XT
512mb Corsair Value Select 2.5cl
Western Digital 80GB EIDE
Windows XP SP2

Hi AdamE,
You don't need to touch
Quote
all you will need to change is the BOOT sequence (order).. you'll change it from:floppy - cdrom - hard drive 0 to floppy - cdrom - sata hd
There is no sata HD option here only HD.
If You want your OS on Sata as the C:\ drive , disconnect the ide temporarily as DrCool., advised.
When XP is installed:-
Switch of
Re-attach IDE
Boot Up
Enter Bios
Advanced options - Hard Disk Boot Order
You should see both your HDrives listed . Move the Sata so that it' on top (1st to Boot)
Job's Done
Board isn't quircky, it just lists IDE drives then Sata drives. Exactly the same procedure would be needed if for some reason you had HDrives on IDE 1 & Ide2 and wanted the HD on IDE2 to be the C:\ drive
good luck

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

Which 1TB (or bigger) SATA drive is the coolest/quietest/least power-hungry

I have a Power Mac G4 Dual 1.25 GHz MDD (it's this model here) which (as it's unmodified) runs very hot & noisy much of the time.
What doesn't help is that I have 3 hard drives installed. 2 of these (including the boot drive) are IDE (80 GB & 120 GB), and are attached to the cables at the front of the machine (am I right in thinking that this is the ATA-66 bus?). The third is a SATA drive (250 GB) connected to one of the sets of cables at the back of the machine (the ATA-100 bus?) via an IDE -> SATA adapter (not a PCI card).
This adapter took me many weeks of research to track down (& order online from the USA) as there didn't appear to be (at the time - a few years ago) anyone here in the UK that made or sold these adapters. (The opposite adapter - IDE drive to SATA cable - was freely available ironically, even in my local electronics shop). The physical size of the adapter means that I can't sit one of the other drives in the empty drive bay at the back of the machine.
A few months ago, as I was almost out of hard drive space, I decided to get a new (SATA) drive to replace the existing 3 drives. As well as giving me lots of capacity, one drive is going to use less power than 3, give off much less heat than 3, and hopefully reduce the fan noise.
Incidentally, I've found many good articles on reducing heat/power consumption/noise in MDD Macs - see here, here, here, here & here.
At the time, 1TB was the largest size available. After much research, along with some forum postings - see here & here - I decided to go for the Samsung Spinpoint F1 drive, which is currently quite cheap - see here.
However, I recently discovered that Seagate now makes a 1.5 TB drive, which would obviously be preferable - see here & here although it is much more expensive - see here.
However, there are many reports of problems with the Seagate drive - see here, here & here.
What I'm wondering is if there are any drives that are bigger than 1TB apart from the Seagate?
If not, would people recommend that I chance going for the Seagate, and hope that I don't have the problems, or that I'll be able to flash the firmware at some future point to sort the problem if it occurs (I have Virtual PC 7.0.2 installed, running Windows 2000 Service Pack 4 - would this enable internal hard drives to have their firmware updated?) or should I just play safe and go for the Samsung, even though it's "only" 1TB?
The largest capacity money can buy is my primary concern, followed by low power usage, low heat output & low noise.
Many thanks.

Thanks for the info.
I don't really see the point in the expense of a PCI card when the IDE -> SATA adaptor works fine, and if I bought a PCI card, I'd then feel obliged to go through the hassle of selling the adaptor on eBay to try to recoup part of the cost of the PCI card.
I should have mentioned before that I want to format my new drive as a single partition, in Mac OS Extended (Journaled) format, and to boot from it. I only want the new drive in the Mac - I don't want any other drives in there. Apart from increased capacity & performance, and reduced power consumption, heat & noise - the main point of getting the new drive is so that there is only one drive in my Mac. Having more than one is a complete pain for me.
At the moment, despite having "Put the hard disk(s) to sleep when possible" unchecked in the Energy Saver pane of System Preferences, all 3 drives spin down very soon after they stop being accessed, which means an infuriating delay (& spinning beach ball) when they spin up again. One or more of them spinning up even interrupts music playing sometimes, and when I go to shut down the computer, if they are spun down but mounted on the desktop, they spin up again before they spin down as part of the shutdown procedure! Also, with more than one drive, I can't tell which drive a file/folder is on just by looking at it, if it's on the desktop.
As far as Other World Computing goes, they may ship to the UK, but by the time the international shipping charges are added, I very much doubt if the total cost of a new drive would work out cheaper than ordering from a UK supplier & getting free shipping.
Another potential problem I've discovered with the Seagate drive is actually a quote from the Other World Computing website that's reproduced in comment number 66 (on page 3) of the MacRumors Forums thread that I gave the link to in my initial post. Basically it says that if you format the Seagate drive as a single partition on a Mac, the performance isn't acceptable. It's apparently fine though if it's partitioned in 2 equal size volumes, or if you format it as an NTFS or FAT32 drive. Neither of these work-arounds are any use to me though.
Everything so far suggests that I should just go for the Samsung 1 TB drive, but I'm hesitant to do so until it's confirmed to me that there aren't any other drives out there that are bigger than 1 TB apart from the Seagate, and also, knowing my luck, the day after I buy the Samsung, Western Digital or Hitachi or someone will bring out a flawless 1.5 TB drive for not a lot more money, and I'll be kicking myself for ending up with only 2 thirds of the capacity than I could have had...

Mac Pro Compatibility With Older SATA Drives And DVI Connectors

I soon plan to replace my 5 year old G5 with a new Mac Pro and need two questions answered so that I will know what options i have for the transfer of older data and apps. The Apple web site for the Mac Pro includes the following paragraph which gives me reason for concern:
Your Mac Pro includes four drive bays, allowing you to configure it with
up to 8 terabytes of storage using 7200-rpm Serial ATA 3Gb/s drives, up
to 2 terabytes of storage using high-performance solid-state drives, or
any combination of each type of drive. Configure each drive bay
separately.
Does the phrase "using 7200-rpm Serial ATA 3Gb/s drives" mean that the Mac Pro will ONLY work with 3Gb/s drives or that it performs best with 3Gb/s drives?
I currently have two internal SATA 250/300 GB Maxtors (Maxtor 7Y250M0 and Maxtor 6B300S0... both are 7200 RPM but I don't know the data transfer speed). Ideally I would get a Mac Pro with a single 1 TB drive, move one or both of these older SATA drives to the new computer, one temporarily and the other permanently in order to transfer data and Apps to the new machine. If this is not possible then the new machine will need to wait until after I get a new larger FW external drive to use as a data transfer medium (I had planned to do that anyhow). I need to do some advance planning for this so I need to know what to expect in advance. I noticed this possible wording ambiguity on Apple's description of the Mac Pro long ago, but now I need to find out the answer for sure. Apple, you need to be more specific with your words.
Can anybody answer this question for me?
My second question regards display connectors. Does the standard (no bucks added) display card include a standard DVI connector or only the newer Mini-DVI connectors. I think I see a standard DVI connector in the low res picture of the back of the Mac Pro but am unsure. My 5 year old Apple display bit the dust a year ago and I had to replace it with an HP 2009m display (mumble grumble) which does use a standard DVI connector. A new Apple display is too rich for my blood so I plan to continue using the HP display for now and need to find out if I will need a display adapter to go with it.
Many thanks to anyone who can answer these questions authoritatively.
For anyone who asks why I still run 10.3.9 on my G5, I can only answer response speed. New OS versions always act like a lead anchor on a machine with their added overhead and Tiger really does feel like a ball and chain tied to me... it just does not reaspond as fast as I do. I look forward to the speed of a new machine.
Phil Rogers
--

Does the phrase "using 7200-rpm Serial ATA 3Gb/s drives" mean that the Mac Pro will ONLY work with 3Gb/s drives or that it performs best with 3Gb/s drives?
Any commercial sATA drive will do just fine. 7200 RPM is not a requirement.
WD "Green" drives have caused user complaints about "long delay until ready" when installed inside a Mac Pro, but are fine for backups.
You are making the leap from PowerPC to Intel Mac. Eventually, you should re-initialize your old drives to GUID partition table for best responsiveness.
Migrating your System will not be possible. Use the pre-installed System or Install a new System on a GUID-partitioned drive with the release DVD in the box.
Migrating your Applications is a Bad Idea. You should plan on re-installing all your third-party Applications from their release discs.

New internal SATA Drive can't access internet or e-mail

I'm re-posting this since it never got resolved, but I've paraphrased to try keep it more concise:
I recently added an internal 500GB SATA drive (and PCI card) to my G4 (partitioned 100GB for apps and remainder for storage). The old HD is running OS X 10.2.8, and I initialized the new HD with a fresh version of 10.3. I set up my Network settings exactly as they are on the old HD (at least I'm 99% sure), but I'm unable to access the Internet and set up e-mail from the new HD. In fact, the new HD doesn't seem to recognize any of my peripherals (DVD burner, printer, cable modem, etc.).
At first I got an error claiming an IP address couldn't be found. So I changed the TCP/IP Config from DHCP to manual DHCP just to see if the status changed, which it did: "Built-in Ethernet is currently active and has the IP address [IP]. You are connected to the internet via Built-in Ethernet"; but it still didn't work.
And when I tried to set up e-mail, I got this error:
"The POP server “mail.[ISP].net” is not responding. Check your network connection and that you entered the correct information in the “Incoming Mail Server” field. If it still doesn’t respond, the server might be temporarily unavailable. If you continue, you may not be able to receive any email."
FYI - the IP address is in the 192.168.0.0 through 192.168.255.255 range, and both e-mail and internet access work fine on the original (10.2.8) drive.
I know I'm doing something wrong, but can someone help me figure out what? Should I have installed 10.2.8 on the new HD first, and then upgraded it to 10.3?
New HD: 500GB Maxtor MaXLine Pro 500 SATA II 3.0 Gb HD (16MB buffer, 7200 RPM)
New PCI Card: OWC Serial ATA 2-Channel PCI/PCI-X Controller

Resolved this issue by other means.

5 SATA Drives on a MSI 7125 MB in Non-RAID

Hello Everyone,
I have been running 4 SATA drives, 3-250 GB Seagates and a Plextor DVD, on my MB for awhile now. I went to install Vista this weekend and added another drive so that I can functioning with XP until Vista is ready to use. My question is how do I enable the SATA ports 5-8? I don't want to run RAID, I just want access to the extra ports. I will be multi-booting and plan on moving one of my non-booting drive the the upper SATA ports so that I can continue to boot to multiple drives including the DVD.
I would prefer not to run the RAID drivers if I can avoid that.
Thank you...

Quote from: charles05663 on 06-February-07, 02:31:05
Thank syar2003...
If I was to mod the bios, where would I find one?
On the ISO cd I have made for 7125 .
The W7125NMM.1D0 has this option unblocked . You don't have to mod anything - just update to that bios version
See:
Topic: Bios Collection. *Updated 01.21.07*
In cmos setup - look under "Integrated Pheriferals" enter the option "OnBoard SIL3114 Mode" and under it change RAID (mode) to SATA (mode)
Save .
Now you can add single disk to port 5-8 SIL ports.
And for drivers you'll need this :
Win2000/XP ,32bits
http://www.siliconimage.com/docs/3114_x86_win32_base_logo_1205.zip
Vista ,32bits
http://www.siliconimage.com/docs/3114_x86_13100_logo.zip
Vista ,64bits
http://www.siliconimage.com/docs/3114_x64_1.2.8.0_logo.zip

How many IDE drives & CDrom can be installed with SATA drives??

How many IDE drives & CDrom can be installed with SATA drives??
i have 2 IDE hard disks & 2 CDROM drives: can install SATA hard disk added to these drives or do i have to remove some???
& if it can be added, can i install 2 SATA drives???
THX in advance

The 3 versions of this board that are available are:
875P Neo-FISR (PCB 2.0)
875P Neo-LSR (PCB 1.0)
875P Neo-FIS2R (PCB 1.0)
All of these boards will have the following ports provider by the chipsets ICH5R south bridge.
2 x SATA (Supporting 2 SATA HDD drives)
2 x PATA (Supporting 4 IDE devices)
All 6 of these can be used at the same time (provided you are using win XP or 2K) you just need to make sure yor BIOS is set right.
->INTEGRATED PERIPHERALS
->ON-CHIP IDE CONFIG
ATA CONFIG: S-ATA ONLY or P-ATA ONLY
S-ATA/P-ATA KEEP ENABLED: YES
OPERATE MODE:
If you set to "legacy mode" S-ATA are set to channel 1 and 2 and P-ATA to channel 3 and 4. If you set to "native mode" P-ATA are channel 1 and 2 and S-ATA 3 and 4. You can only use the raid functionfon SATA in native mode.
If you have the 875P Neo-FIS2R (PCB 1.0) you will also have the following ports provided by the Promise PDC20378 PCI controller:
2 x SATA (Supporting 2 SATA HDD drives)
1 x PATA (Supporting 1 Master IDE HDD drive)
The PATA port is limited to 1 Master HDD by the lite BIOS. This can in theory be upgraded to the full BIOS supporting a master and a slave, but this may obviously void your warranty.
So the answer to your origional question is:
2 x SATA HDDs and 4 x IDE HDD/CDROM if you have 875P Neo-FISR (PCB 2.0) or 875P Neo-LSR (PCB 1.0)
or
4 x SATA HDDs, 1 x IDE HDD (2 if you modify the BIOS) and 4 x IDE HDD/CDROM if you have 875P Neo-FIS2R (PCB 1.0)

Seagate 160 SATA Drive & Neo-FIS2R mobo

Everyone, I need your help for a newbie.
I have installed a Seagate 160mb SATA drive as my primary bootable drive on a Neo-FIS2R mobo. I have successfully moved my partitions etc from the previous drive (80GB Seagate IDE drive).
The system boots fine, Windows XP sees the drive but everytime Windows XP starts, it pops up messages saying New Hardware found and tries to install the SATA drive under the IDE ATA/ATAPI Controllers section in Device Manager.
Under this section in Device Manager, I see 2 IDE Channels defined with yellow circles and exclamation marks inside the yellow circles.
I have 1 IDE drive attached as well and maybe later another IDE drive will be added.
What settings do I need in my BIOS? Are there drivers required to be installed in Windows XP?
Thanks for your help. This is driving my crazy!

In bios under Integrated Peripherals, On Chip ATA Operating Mode set
Native Mode
ATA Configuration - PATA only
SATA Keep enabled - yes
PATA Keep enabled - yes
PATA channel selection - both
This should let you boot from the SATA and see the PATA.

Sata drive problems

right my dilema is this i have buit a new system and everything works fine, finished it off by buying a couple of maxtor sata drives, a 200gig for storage and a 120gig for boot/os.
maxblast3 i cannot get to run from cd or floppy but it runs fine from windows so i am able to see the drives and format them etc.
saturday i spent best part on 12 hours trying to install windows xp on the 120 and everytime i was defeated, and finally got off with it, so cracked a bottle open
ok then install process was
boot form cd
xp cd in drive
mobo sata drivers in floppy ready
press any key to boot from cd
wait abit
F6 to install extra drivers, done that ok
cd activity copying files over ready to install
your pc will reboot in 15 seconds
boots up fine, don't press key to boot from cd
bang my problem begins
the screen reads like this " press any key to boot from cd........error loading operating system"
anyone else suffered this and managed to get around it ? this happens "everytime"
so the next thing was to try the 200gig even though it was not recognised as 200gig (137) and install xp so i done exactly the same as above and everything went fine xp installed no problem. however i don't want xp on this drive as i do not want to partition it and it is too much messing round to get windows to recognise its true size.
the 200gig is a diamondmax +10 ncq 7200rpm sata/150 it has no molex and no jumper place on it.
the 120 is a diamondmax +9 7200rpm sata/150 now this drive has a molex plug and a jumper place like an ordinary drive, it also has a sata power point and sata connection point. it look exactly like an ide drive with ide plug pulled off and sata point put on it i thought sata's did not need jumpers ?
another thing i have noticed....in your system tray you have an icon like a little grey box with a green arrow above it that you use to safely remove hardware like usb stuff etc my drive shows up in there ?
http://img.photobucket.com/albums/v...orbog/sata1.jpg
anyone got a sata 120 gig as a boot drive ? what make do you have ?
my pc spec is
msi k8n neo2 mobo
1 gig dual channel ram
amd 64bit 3200 winchester cpu
antec neopoer 480w psu
plenty cooloing
msi 6600gt 128mb graphic card
using ide drive at the mo
hope this makes sense, thanks for any advice
forgot to add the 120 works fine as generic storage drive just can't get an o/s onto it.

Quote from: BWA on 14-February-05, 11:18:17
Just threw that into the discussion to see if it would lead anywhere. I'm using Hitachi sata drives and they are the same as the IDE drive with an added chip foir the sata (think that is why they still have the old style power connection along with the sata connection)
my system's based on the same mobo (k8n neo4) with only one Hitachi80GB sataII hdd... and i have the same trouble like 'gravies': i'd get windows to start install (with help of drivers off floppy; by F6) but when it reboots to actually set up the system it hangs... not recognizing the boot files written on my SATAdrive = or the drive itself...
Did you somebody resolve this problem?
It's driving me crazy already 4 looong days... (first i also had faulty floppy../
thx,
s

Urgent - No 64bit Promise SATA driver (not RAID)

I'd already installed XP64 on an old PATA drive without problems, so today I decided to use the new VIA SATA drive to dual-boot it off my SATA drive, along with my main XP32 installation. Unfortunately, although it found the VIA driver at F6 and got to the GUI install it locked solid at Devices. Worse than that it's totally screwed all the boot files so I now can't get to anything on either the SATA or PATA drives, and blue screen on any attempt to boot either drive. That's 4 OS installs gone.
I moved the SATA over to the Promise controller thinking I'd seen 64bit Promise drivers for weeks, but it seems these are only RAID drivers and are called "Promise FastTrak 378 (tm) Controller". Needless to say they don't find a single SATA drive. What I need would be the driver called "Promise SATA378 (tm) Controller" but I can't find it. Have Promise really released a RAID driver but no single SATA driver for the same controller???
If I don't find it I guess I'm looking at 4 days spent formatting and reinstalling.

Hi Jocko
OK, I'll try explain (and remember!)
First I installed XP32 on the lone SATA drive. No problem as it was the only drive.
Then I added an old PATA drive, which BIOS and Windows Setup always sees as Disk 0 and the SATA as Disk 1.
I then installed XP32 onto the PATA drive. No problem, I think it was because Windows saw it as Disk 0 as it put the MBR in the right place.
I then put Server64 and XP64 on the PATA drive to test them (leaving by day-to-day install safe on the SATA drive. Again, no problems, it updated the MBR correctly to let me multiboot between the 3 OSes on the PATA drive.
I then tried to add an install of XP64 to the SATA drive, but because I left the PATA drive connected, Windows setup updated the MBR of the PATA drive instead. On subsequent reboot it failed because it was pointing to the wrong drive (I think). So I had half an install on the SATA drive, and a boot.ini on the PATA which pointed to a non-existent half installation. Even with BIOS listing the SATA drive as the boot device, each time the PC restarted it tried to carry on the installation and of course failed.
That's when I had to refer to my book on Recovery Console...
So it seems that if multiple drives are installed, it will update the MBR on the lowest ID drive, which is not necessarily the drive the installation is actually going on to! I think!

[Athlon64] CAN'T SEE SINGLE SATA DRIVE / K8T NEO no Promise controller

I have a K8t NEO -the cheapskate version with no PROMISE SATA controller or on-board Firewire
I have been running on XP SP2 on 2 IDE drives, everything is ok. I added a SINGLE SATA drive and turned the VIA SATA controller on in BIOS. I did the MSI Live Update and have the latest VIA SATA driver, latest chipset, latest BIOS, latest EVERYTHING. At boot, the VIA SATA controller reports my Hitachi SATA as Channel 0 Primary" in the SATA devices table. Going into the SATA RAID menu it tells me "You can't make RAID with just one drive" which is true, of course. But the point is the controller SEES the drive.
I've run MSI Live Update and have the latest BIOS, latest SATA XP driver, latest EVERYTHING.
Windows XP doesn't see the SATA drive.
In XP I see a VIA RAID CONTROLLER in Hardware / Device Manager which is DISABLED. When I right-click then click ENABLE on the VIA RAID CONTROLLER the machine reboots immediately. I tried safe mode, same thing. I tried BIOS settings of "No PNP O/S Installed" and "Yes PNP O/S Installed" and reset the NVRAM. No change.
I think there must be an IRQ conflict.... I have a sound card (on-board sound is turned OFF in BIOS) and AGP video card, and that's it- no WiFi NIC or anything else to eat up IRQ resources. I use the Realtek on-board ethernet.
I tried my Windows 98 partition and that booted, detected the new hardware (VIA SATA) and I installed the driver from the MSI CD and Win 98 is happy with the SATA drive..... it sees the drive just fine.
How do I make Windows XP see the SATA drive?

Have you tried starting XP with CD and entering recovery, log on as admin and see if SATA drive is there? Remember to "F6" with a floppy drive of SATA drivers for
-XP-... I'm assuming you already have as you said all is uptodate. When the boot BIOS for the VIA SATA apprears and you press "TAB" I believe it is, you can mess with the SATA functions. Sorry if does not apply to your compy or you've already done all this.... BTW you CAN run a RAID array with one HDD, at least thats what I did on my Promise controller.
In my Device Manager under Disk drives it looks like this (notes bracketed are noting position):
Promise 1+0 Stripe/RAID0 SCSI Disk Device (Bus Number 0, Target ID 1, LUN 0 (G:\ 1-160GB IDE Seagate/notice ONE drive)
Promise 2+0 Stripe/RAID0 SCSI Disk Device (Bus Number 0, Target ID 0, LUN 0) (F:\ 2x200 SATA)
ST3160023A (Location 1 (1) VIA IDE D:\)
VIA SATA RAID 0 SCSI Disk Device (Bus Number 0, Target ID 0, LUN 0) (E:\ 2x120 SATA)
WDC WD800JB-00CRA1 (Location 0 (0) VIA IDE C:\)
Under the boards BIOS, is the SATA drive listed under the BOOT table??? In my system it lists the above 5 partitions (7 HDD's total), floppy, 2 CD/DVD drives, etc...
Oh also in Device Manager IS the VIA SATA controller appearing in the "SCSI and RAID controllers" tab??? I have set mine to just SATA before and of course now it says "VIA SATA RAID Controller"... for you it should read "VIA SATA Controller". Remember there are 2 different drivers for the SATA controller, one for SATA and one for SATA RAID. Look on your floppy disk or if you saved out the updated driver. I made a new floppy with the latest XP drivers. When booting from WINXP CD, and promted for "F6" and press it, later it will show you TWO different drivers after reading the floppy disk for XP. You obviously want the non RAID driver... hope that helps somewhat... g'luck

Adding Internal Drives to G5

I need more space on my G5.
Currently I have the original 80G Hard drive that came with it, and an added 200G internal drive. I work with video and am constantly having to delete old projects in order to make room for new ones.
As I understand it, the G5 will only allow for 2 internal drives. One being the start up drive (which should hold all applications/Library/Ect.) and then another "scratch" drive for actual projects (i.e. video/audio capture). Am I correct?
I am a novice still trying to understand what/what not to put where. All I know is that I work with hours of video and am in desparate need of more space. So any suggestions/advice you may have will be greatly appreciated.
G5 Mac OS X (10.3.9) 1.6 Ghz Power PC 1.25 G Memory

Trade up ;-(
You are working with a G5 1.6 single cpu. No PCI-X, and PCI bus has a bug that limits disk writes to 75MB/sec with any PCI card interface (SATA, SCSI etc).
I would forget the 80GB for work and put it aside for now, and invest in 500GB drive. Would be nice to build an external SATA RAID.
There are some internal dual and triple drive bracket kits that run off SATA controllers as well - you ought to have ample room for one (or two).
But I always thought that working with video it was very helpful to have dual cpu or better.
Any investment in SATA drive would help now and later, but I would look at G5 2.3 Dual Core or something too.
A boot drive, media drive, scratch can be a drive or drives set up in RAID. Even a FW800 and FW400 for backup, archive, capture etc.
Some drives like Seagate 7200.10 750GB would be nice, but you need to upgrade to 10.4.6+. Also, my guess is that you would notice things run better with 2-4GB RAM. Definitely more than 1.25, probably double that.

Adding Hard Drives to Tower

Hi Group,
Well I finally took the plunge and purchased my Mac Pro Tower for our recording studio
www.VisionRecordingStudios.com
I got so fed up with Windows XP and the unstable of that operating system thta I needed a more stable platform. Now my entire life is PC FREE!!!!
Anyway, I had a question about adding additional hard drive to the mac. I had recently added an internal hard drive to my PC and I would like to take that drive out, format it and install it as a secondary drive in the tower. Is this possible?
It a western digital black...here is the link
http://www.wdc.com/en/products/products.asp?driveid=733
just a standard SATA drive. I would assume it would work in the tower correct? I didn't purchased additional drives when I bought the tower due to the cost and I was hoping to re-use these form the PC.
Any advice would be greatly appreciated.
Thank you

Well that's great news!! I have 2 internal 500 gig hard drives I can erase and install in the mac as my back ups for my recording studio. GOD I am so happy I am finally moving to mac in our studio.
in 2009 I have gotten rid of my office pc and purchased an I-mac and sold my laptop and got a macbook pro. I love them both!! Absolute no issues with them and they are about as plug and play as you get. The last investment was in our studio. I was using a year old dell with XP pro and it was nothing but a nightmare. Loosing usb ports, crashing during sessions, you name it and it happened.
I know I will never buy another PC product again!!
Thanks for your help with my hard drive question

Adding SATA drives

Similar Messages

Maybe you are looking for