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

Similar Messages

[865PE/G Neo2 Series] Just got my first SATA drive.. need help booting up.. :(

Hey guys
I just got my very first SATA drive. it's a Hitachi 160GB 7k250!
anyway, I wanted to set this new drive (partion 1 to be exact) as my PRIMARY or what I like to call SYSTEM drive.. this is where i store only my windows core files and program files..
My previous setup is that I have 2 PATA drives (Primary master and Secondary Master) and 2 DVD drives (Primary Slave and Secondary Slave)..
Now with the introduction of this new SATA drive, well, i didnt know what to do..
I got as far as setting my BIOS to: (forgive me if the following isnt exact terms as in the bios)
ATA = PATA Channel only
keep SATA = YES
(and some settings i can't remember)
I was able to boot my computer up with the SATA HD partitions set at the next available drive letters.
Now here's the problem.. I currently have an Image of my C: (system) created with Acronis TrueImage 8, and i restored that to my SATA drive's FIRST partition...
The first partition is also formatted with the same file system NTFS and is set to primary..
From here, i honestly dont know what to do..
ofcourse I will have to set bios to boot the SATA drive first...
Also, since the System image (windows XP) is that of DRIVE C: I have to somehow set the SATA drive to be HD0 (first channel)... playing around in my bios I have accomplised to have set my SATA drive as IDE channel 1 = Primary.. funny thing is the rest of the drives moved down starting at IDE Channel 3 and 4..
Still i went on to boot up.. but i was unsuccessfull. I get a very quick blue screen (about 50 miliseconds) and then my computer shuts off and reboots..
I played around witht he settings and tried many things.. still get the quick BSOD and then reboot problem
GUys? What am i missing here?
I didnt know this SATA drive was gona get complicated.. i thought i'd be up and running by now.. :( ..
Please lend me some of your knowledge peoplez.. :D
tea

Hi Danny,
Thanks for your reply.
I have followed your instructions to the dot.. now im getting as far as the WindowsXP Boot Screen... after an unusually long loading time, i get that BSOD flash which i really cant make out since the darn thing reboots right away.. :(
I also tried
Native Mode
ATA Configuration - SATA only
(changing this to SATA, thinking you were mistaken since am booting sata up.. but what do i know ei?)
SATA Keep enabled - yes
PATA Keep enabled - yes
PATA channel selection - both
same results... a long boot screen loading time.. then a quick BSOD..
I alsto tried booting up in safemode.. the loading stops at agp440.sys and reboots after a long pause at that part.
So now I switched back to your recommended settings, but this time setting my old hard drive to boot (PATA).
To my surprise im back to where i started (despite maintaining your suggested settings) thus i am replying to this post again..
also, i noticed that with your suggested settings, my SATA drive is on IDE channel 1.. and the rest on IDE channel 3 and 4.. but here in windows my old hard drive is still drive C:.. I was expecting my SATA drive to be Drive C this time.. could this be the problem here?
I mean the windows Image I restored is setup to work on drive C (first drive), although I removed all the drive, could it be that my SATA drive is still not on drive C?
Please help. My brain's bleeding
Tea

800FSB Processor Question & SATA drives question.

1. Which is better the Heatsink Fan that comes with a Pentium 4 3.0Ghz 800FSB processor, or a Vantec Aeroflow TMD Heatsink Fan?
2. Is it better to stripe my two new 120 Gig SATA drives? Or is it better to just have them independent of each other? Why?

1. I didn't realize that the processor came with a HSF, so I bought a Vantec Aeroflow. Now I'm just trying to figure out if there is much of a difference between them. I either keep the Vantec and use it because it benefits me more, or I return it and get my money back because it doesn't benefit me any. Any suggestions?
2. It seems that striping (RAID 0) may be too risky in terms of possible data loss. I think I will just use each drive independently and reduce that risk.

Macbook Pro x SATA Drive question

If I were to purchase this exact drive from the link below:
http://www.amazon.com/Seagate-Barracuda-ST4000DX000-SATA-Drive/dp/B005WX3NEU/ref =sr_1_1?ie=UTF8&qid=1323734482&sr=8-1
Would it fit inside my MacBook Pro and would it be fully compatible with it as well (obviously)??
My MacBook Pro spechs are:
15-inch Early 2011 MacBook Pro
Processor: 2.3 GHz Intel Core i7
Memory: 4 GB 1333 MHz DDR3
Graphics: AMD Radeon HD 6750M 1024 MB
Software: Mac OS X Lion 10.7.4 (11E53) [But will be upgrading to Mountain Lion when released]
Please Help.

That's a 3.5" disk - your MacBook Pro can only use 2.5" HDs. Assuming you'd be installing it into your HD bay.
It also doesn't come in an enclosure - not a good thing.
Clinton

Added Hybrid SATA drive to ThinkCentre - does not recognize old IDE drive - Suggestions?

I added a 1TB Seagate Hybrid drive to my old ThinkCentre 808532U. I removed the jumper from the old IDE drive so it would be considered the secondary. I installed Windows 7 Professional 32 bit on the hybrid SATA. The old IDE had Windows XP. I want to use the old IDE drive as the secondary so I can access the data, pictures, etc. I do NOT want to boot XP. The system boots up fine with Windows 7. However, the system does not recognize the old IDE drive. I have gone into BIOS and changed the Parallel ATA to Secondary. The system still does not recognize the old IDE drive. Can someone provide recommendations? Thanks,Napp

I finally experimented enough that I found the solution! I tried putting all the IDE drives into Startup even though none showed any hardware assigned. I set Parallel ATA to Both. My machine would start up but not show the Logo screen or any screen for that matter. I put a Windows 7 install disk into the DVD ROM and got the Logo screen. I F1'd back into BIOS and suddenly two of the IDE entries in Startup were populated with the DVD drives. I set the order I wanted in Startup and saved the configuration. When Windows started it installed drivers for two devices. I looked into Computer and all the drives were listed!!!!!!!!!!! So now after several long nights I have my system configured properly for all the drives and all Windows 7 updates applied. I am waiting for delivery of a 256M graphics adapter and a gigabit ethernet adapter to see if I can increase performance. Time to sleep now..............

Swappable SATA Drive Question

I am searching for a way to have multiple (and fast) dedicated back ups (to be used sort of like removable media of old). I understand the concept of redundancy and while a RAID system gives me great capacity, and expandability, the result is still at a single location. I desire to be able to have a copy of critical documents off site (SDB), so am looking for a single bay SATA swappable that will allow me to 'swap' the drive(s) in the safe deposit box with the one(s) at home once weekly. I am considering the Wiebetech RTX-100H-Q. Does anyone have any experience with this concept, this drive or others that may serve this purpose? Are there any other considerations of which I need to be aware?
Thanks in advance!

That's a good idea. I do something similar, but using older, external complete drives - and I am not super regular.
A cheaper type of unit might be a Newertech:
http://eshop.macsales.com/item/Newer%20Technology/FWU2ESHDK/
No fan, but takes 2.5 and 3.5 inch drives.
Wiebetech has a good reputation; I haven't heard anything about this Newertech.

Adding a 3rd drive questions

1.) I have a mac pro with two 3Ghz processors and two 500GB harddrives. Does anyone know if adding a 3rd 500GB hard drive will make the mac run much hotter?
2.) I will use the 3rd drive just for backing up files, so it will not be accessed on a regular basis. In this case, should I still be concerned with finding a drive that is not too noisy? The drive only makes noise and spins when it is being accessed, right?
Thanks!!

On the other hand the Maxtor drives that you do
recommend have had one of the worst quality
reputations in the past. Since they've been
acquired by Seagate the quality of Maxtor drives has
improved.
Actually, what happened was once Seagate took over they had Maxtor stop making the Maxline III 7V300F0. The Seagate 7200.10 does not compare well to it so they removed the competition.
While the 7200.10 provides good sequential performance with large files it is unable to keep up with the Maxline models in small file duplication tests. It is too bad that Seagate did not integrate Maxtor technnology into Seagate products.
In addition, the Seagate 7200.10 320GB still has a write speed limitation of 47MB/sec. when mounted internally as a single drive inside Apple Mac Pro and PowerMac G5 models. I have a complaint posted on this at Seagate and they tell me no fix is available for the 320GB model.
Now when I buy a Maxtor 300GB at Frys it is just a rebranded 7200.10 hard drive with a 3 year warranty instead of a 5 year warranty that would have been provided had it been sold under the Seagate label.
Seagate bought Maxtor and instead of using the technology, dumped Maxtor hard drives. It will be very interesting to see what Seagate tries to pass off to Maxtor customers when they need warranty service in the future.

K8 Neo2 - Adding an SATA Drive - Some ???

Hey All...
I currently have the below HDD (in my sig) hooked up to SATA3. It is the only HDD I have right now.
I am getting a Raptor in the next few days, and want that puppy to be my main hdd, with the afore mentioned HDD as a secondary drive. So what I was planning on doing was attaching the Raptor to SATA3 and the Samsung to SATA4. Formatting and clean installing WinXP Pro (SP2) on the Raptor and reformatting the Samsung as a storage drive.
Is there anything I need to worry about? When I initially built my rig, I did not have to load RAID drivers, because I was only using the one drive. Now that I have two drives, will I have to? I am not doing any RAID arrays, but I am not sure if because there are two now, it will expect it.
Any thoughts/hints/tips/suggestions???

Quote
Originally posted by Recall
May I suggest that the best way of installing XP is to slipstream SP2. It makes for a much smoother install, plus it saves hassle with updates etc.
Thanks for the quick response, Recall. I am already on the Slipstream bandwagon. Last couple of installs have been from the genesis of AutoStreamer! That is one of the best programs ever made!!!

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.

[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 system won't boot past POST after I plugged in my new SATA drive. (SATA noob

I have a MSI K8n Neo 2 Platinum mobo with a Athlon64 +3500 and 1gig dual channel DDR 400. I currently have 2 drives set up a IDE primary (MAxtor 6Y120) and a IDE slave (Maxtor 6L080).
I recently purchased a Maxtor DiamondMax 10 6L300S0 300GB Serial ATA 7200RPM Hard Drive w/16MB Buffer.
It is my first SATA drive ever so non the less I am a newb. I want to use it as a non Raid media storage device while my primary IDE remains my boot OS drive.
I plugged the SATA in to the sata one port and powered it. I enabled the SATA in the bios with RAID disabled. When the system boots up it does the memory chech and lists all the IDE devices. Then it says "Detecting IDE drives..." and just hangs there. The new drive spins so it definatly has power but occasionaly it make occasional clicking sounds.
Once it actually booted up and windows detected it. I decided to reboot it just to play it safe but it never would get past post screen again. I can boot up the system normally when I unplug the SATA cable.
Please help I need to know if I am doing something wrong or I should RMA the drive. THANK YOU!

Got the same problem:
pata Maxtor Diamond Max =9 200 (40/160) Boot drive
AMD 64 x2 3800
Bios 1.2 090905 using MSi online auto update utility
2x 512 DDR double sided
X850 pro 128mb
PSU Sweetex 650w
Switched power supply
110/220 V switchable (220 V: 5 Amp/ 110V:10 Amp)
+ 3.3 V 28 Amp
+ 5 V 45 Amp
+ 12 V 25 Amp
-5 V 0.5 Amp
-12 V 0.8 Amp
- 5 Vsb 2 Amp PEAK 2.5
Max. 650 Watt
CE, FC
Boots perfectly with 1 pata, adda sata to sata 1 or 2 or 3 or 4
Boot stalls in bios at Raid setup. Tried enable raid with no drives enable , system booted twice, turned off overnight, then failed to start the next day. Will only restart with a cold reboot. Hot reboot produces a long BEEEEEP & power is on but nothing happens no post nothing.
SATA drive was taked from a working system (ECS 755a - AMD 64 3000 - PATA 200 / SATA 200), configured 40/160 40=OS Winxp 64 / 160 = data. System will not boot if this is the sole drive connected.

MSI NEO 4 Platinum with SATA Drive

I have recently built a new machine with the following specs but I am having problems with system stability in windows and was wondering whether it's because of the way I set up the hard drive.
Specs:
MSI K8N Neo 4 Platinum
AMD Athlon 64 3500 Winchester
Zalman CNPS7000B-Cu
1GB Corsair XMS PC3200 RAM
Sapphire X800 XT
Sound Blaster Audigy Player
Maxtor 80GB Serial ATA Hard Drive
Maxtor 40GB IDE Hard Drive
550W PSU
I plugged my SATA drive into slot 1 and booted from the maxblast 3 CD to partition and set up the hard drive. I then installed windows 98 and upgraded to windows 2000. My system seems to be slow and laggy, though it seems mostly fine in games. When I listen to music and browse a CD at the same time the sound stutters and lags. I am getting lots of slow down when doing lots of things on the computer but it shouldn't slow down as much as it is. I am also getting windows error messages.
Is there a different way I should have installed the hard drive. I can't boot from my windows 2000 disk in dos because it's only upgrade version. I read on the forum about adding the SATA drive to a raid array before installing windows but I don't understand what this means. Can you help?
The floppy drive also doesn't seem to work so I couldn't install SATA drivers at windows setup. How can I get it working because the lead seems to be connected correctly as it gives an error message on boot up with the purple stripe the other side of the floppy drive.

Quote
I can do it with a windows XP upgrade CD surely
yes
Quote
Me Yesterday, 12:55
If you have an XP upgrade CD follow the following steps.
1) Decide which HD you wish to install XP on.
If the Sata - Then turn of PC & unplug IDE Drive, this is a windows thing, as XP will see the Ide drive b4 the Sata & try to create the 1st drive as system drive. You can plug the ide back in when the install is complete.
2) Insert XP Cd. Enter Bios - Advanced bios change boot order so that CD is 1st device. or press f11 as pc posts, & select CD.
3) The PC should now boot from the XP CD.
You don't need to load any floppy drivers.
But XP will ask to see a qualifying product, put in your 2000 or 98 CD.
You should see a Hard drive Partition Setup screen - you can use this to delete any existing partition & format the drive (Don't use the quick format it's only quick cos it dont check for errors so slow & safe is best. See section How to partition and format your hard disk by using the Windows XP Setup program

Question installing SATA drive on Delta 2 Platinum mobo

I just got a brand spankin' new Raptor 74gb SATA drive I will be installing on my brand new MSI K7N2 Delta 2 Platinum mobo, and I have a few questions.
First off, I don't have any desire to run a RAID configuration but I want the SATA drive to be my boot drive. So my question is, do I still have to enable RAID in the bios? Or is just Enabling SATA enough?
Second, when I go to install WinXP, do I have to hit F6 and install any drivers?
The mobo did come with a floppy that reads
G72-NVSA020
Nforce3 SATA Raid Driver (For WinXP only)
If I do need drivers, does that floppy have the drivers I will need when installing windows? Or is there a place to download the latest ones I will need?
I am slipstreaming XP SP2 into my XP installation.
Also, I've read that I'm not supposed to have any PATA drives hooked up when installing windows which makes sense.
oh yeah...one more thing...i'm going to be using an AMD xp 3200+ 400mhz bus processor and all I have is three sticks of Crucial PC2100 DDR memory that I wanted to use since I already own it. Is this a bad idea?
thanks a bunch

Thanks for the quick response...I'll be building my system this weekend...I'm waiting for my PC Power & Cooling Silencer 470 ATX power supply that will arrive tomorrow. This bad boy should give plenty of juice (26a on 12v) to power my rig. It's good to know the pc2100 can be used to get the system up and running, but I'll be investing in some pc3200 shortly. I thought of a few more questions if you'd be kind enough to reply:
1) When I buy the PC3200, I plan on getting 2 sticks of 512 and running dual channel. I see you run Crucial ram. Are there any issues with Crucial ram running dual channel that you know of?
2) I have a SB live soundcard but plan on getting an Audigy 2 zs soon, should i just use the onboard sound for now? Is the onboard sound as good as an SB live?
3) Do you recommend using the MSI "LiveUpdate" feature to update bios and drivers, or should I just go with the Nvidia UDP v5.10 and update bios manually? Or maybe I don't even want to update the bios?
Thanks again
-Mike

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.

Question about using a SATA drive through an Epress34 card???

I have a basic question about OSX and how it treats a SATA drive hung from an Express34 SATA card. So OSX just treats any drive as a mounted drive as far as I know bbut what about when booting...
If, at boot up, I use the 'cmd C' option to select an external SATA dirve hanging off of an Express34 SATA card, will OSX see that drive as if it just were the internal drive in the MBP or is there some inherant difference between the real internal drive and any other SATA drive?
I guess the question is... does the cmd C option really just tell the OS to treat this drive as though it were the interal drive and boot from it (assuming the drive is bootable of course) or is ot doing something else.
If that is the case, why can't I use an external drive and install BootCamp on it, assumiong that I booted from this drive?
Is there a difference between an external SATA drive from an Express34 card and an external firewire drive?
TIA,
Peter

vedderfan94 wrote:
why?
*From the itunes store terms of service*:
+to purchase from an iTunes Store in a particular country, you must have both a residential address and a billing address in that particular country. Items on any particular country's iTunes Store are available only for distribution to customers who use a credit card, debit card, iTunes Gift Certificate, or iTunes Gift Card issued in and for that country.+
JGG

Adding first SATA drive - Questions

Similar Messages

Maybe you are looking for