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.

Similar Messages

Solaris 10 Install problem with SATA drives

Hi, I'm trying to install solaris 10 on a x86 system with 2 SATA drives running in a on board SATA controler (not RAID).
During install the setup fails to detect the disks, to install Windows XP I have to provide disk drivers during the setup procedure by pressing F6 and providing the drivers, alas I cannot seem to find either a way to provide SATA controler drivers to solaris, nor a suitable driver for solaris .
Any help would be extremely apreciated.

I had the same SATA problem on builds 69 and 72 of Solaris10, but the Release version recognises and installs readily on SATA drives on three mainboards that I use. They are Tyan s2875 with dual opteron cpus, Asus k8N-E with a 754 pin athlon64 cpu, and Gigabyte GA-K8NS-939 with a939 pin athlon64.
My Mandrake Linux10 says it sees the SATA drives, but never installed on them.
FreeBSD 5.3 Release for AMD64 sees the SATA and installs with no problems.
Hope this gives you some encouragement to persist

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.

RS480M2-IL Problems with SATA Drives.

I work at an Official AMD Service Center and we build Custom AMD64 Systems. The IDE Boot Delay was removed from the latest BIOS update. Thanks to this, SATA drives are having problems booting up. SATA Drives are taking too long to spool up, so the system moves on to the next Device on the bootup priority list. (One customer was booting up from a external USB 2.0 Drive or CD-Rom Drive (Not bootable media). If we disable everything but the Hard Drive from the selection, sometimes we get a Stop after Post Error We build systems with the SATA drives due to them supposedly being faster. Should we switch to IDE drives for the boot drives, or is there a fix for this problem. Please let me know and send an email to [email protected] . Thank You.
-Richard D. Orr-
Sales Retail Rep /Bench Tech Representative
CyberSmart Computers, Pensacola, FL

I'm experiancing the same problem with this board. I purchased back in february and tired a SATA drive then and it was slower then molassas in the snow. I thought is was a windows issue. I bought the board for Linux and loaded Fedora 3 and Fedora 4-64 on a PATA drive and have had it running almost flawlessly ever since. The main problem has been the reboot freeze that is reported all over the web.
I put a SATA drive back into this system as a dual boot, loaded Win2k and once again slooooooow. Download all the latest drivers, tried again, same thing.
Today it freezes on the boot screen, still loades my Linux no problem and runs Folding@Home 24/7 no problem.
Ok, Flash bios from CD built on WinXP - No problem goes well.
Reboot problem seems better but now it won't reboot from linux, have to hit reset
Voltage controls for fans no longer available Still no controls for raising frontside bus
Still won't recognize the drive. Put drive in K7NF Delta, Boots fine (complains about drivers but expected). Drive is OK feew.
Rebooted Linux from PATA and system is fine.
Brand new MSI X850XT sits in box unopened

Another "Problem With SATA Drive" thread...

Hey guys, how ya doin'?
Ok, I have a K8N Neo Platinum I got a couple days ago along with all my other parts to buld myself a new system. I got a 120GB Western Digital SATA hard drive. The WD1200JD. I got everything together and plugged in my HD, I turned it on and the HD started making really loud stuttering noises and wouldn't POST or let me get into BIOS. It just stuck at the logo screen. So I unplugged the HD and then it let me into BIOS. I changed the boot order, and made sure that SATA was enabled. The I plugged the drive back in, and it still wouldn't go past the logo screen. Then I messed around a little bit more with boot order and finally got it to POST. I went to install windows XP on it, and the "To install SATA drivers hit F6" screen came up and I hit F6 and nothing happened. It went past that, and got to setup but when I tried to format the drive, it said there was no drive present. I inspected all my BIOS settings and everything seemed to be fine. I think I got a borked Hard Drive.
Any ideas?. Thanks.

Quote
Originally posted by Calculusaurus
Quote
Originally posted by ninjastyle
You shouldn't need to install any drivers or press F6 if you're only using one SATA drive. I really wish MSI would be more clear about this because I get tired of telling people the same thing!!
No need for any floppy disc drive, pressing F6 or installing drivers if using a single SATA drive.
I agree, MSI needs to spell it in bold letters in the manual for its K8N users. It's just to ambiguous for the user to not know this. :(
I think the confusion comes from other chipsets where you DO need to install plain SATA drivers at the F6 prompt even if you use just one SATA drive.

Problems with SATA drive

Hi,
I have been using the 865PE Neo2 board fine for about 6 months, although yesterday my OS (XP) hung. When I rebooted, I got the following message:
'Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM'
I tried to repair the OS by booting from the XP disk, pressing F6 and adding the 'Promise 376/378 Driver' (is this the correct driver? i have lost the original floppy which came with the board!). When I then press 'R' to repair, I am given the following message:
'Setup did not find any hard disk drives installed in your computer'.
I have run the hard drive diagnostics from maxtor which all passed.
Any help would be much appreciated. My system is as follows:
MSI 865PE Neo2
Maxtor DiamondMax Plus 9 160GB HD
1GB RAM
Thanks,
Gavin

Quote
On-Chip ATA(s) Op Mode: Legacy Mode
Change to Native Mode.
Other settings are OK. If you can't boot, change SATA only to PATA only. You may have to enter the bios again after saving these changes to get the boot drive reselected.

Problem installing SATA driver

Did a clean install of my system today and ran into many problems >.<
I used maxblast bootable CD to partition my 300gb maxtor drive.
Used the floppies to setup XP pro and pressed f6 at start.
Only have 1 drive Drive and it is plugged into the 1st SATA port, so I used the nvidia disk that came with my MB and chose the bottom option from the menu of 2 choices ( nvidia nforce storage controller )
Windows setup then recognised the correct partitions maxblast had created and allowed me to install XP onto my choosen one.
Once this was installed everything seemed to be working fine.
Installed SP2 and all windows updates.
Then I decided to try the nvidia unified driver from the nvidia website ( didn't install anything from the MSI supplied disk )
That seemed to totally kill my PC on reboot, it can up with some startup screen I had never seen before, all black with a small rectangle with a windows logo in it. It hung on this screen after a while.
Upon next reboot it would just bluescreen before getting fully into windows.
So I though ho-hum, time to try again.
Did everything the same, and at the point just after using nvidia disk during installation for the 2nd time & putting the XP CD in the drive ( the part where it says setup is copying files ) My PC would bluescreen really fast and reboot with a message ntldr is missing.
I tried this over and over always getting the same results, I also tried installing both the options from the floppy with the same result.
The only way I could set it up was without hitting F6 and letting windows get on with it. Trouble is, once it gets to the partition part it only see's my HD as 120gb or something similar, and doesnt see the partitions I created in maxblast.
Once in XP I'm able to reclaim the rest of the HD space though.
Then I just used all the drivers from the CD included with the MB, and all seems to work well apart from I was getting a message saying my USB stick drive could operate faster with USB 2 ports - Got the same message in all the ports, but it seemed to dissapear after I uninstalled a entry in device manager that was a yellow ? next to USB device.
Is there something I'm doing wrong in the setup using the floppy disk? - perhaps the floppy is dodgy?
It would be good to get it working like that, as I wouldn't have to wait ages while I format and partition the drive within XP, maxblast does it almost instantly.
Also would be really good to know what drivers to install after XP has just been installed and updated.
Should I use the CD that comes with MB, or try the nvidias again?
Latest version bios used (1.4) with the raid options disabled and no overclocking at all.

Still no luck being able to install those drivers during install.
I even tried the method in the sticky thread where I enabled RAID on the channel the drive was in and pressed F10 at boot > hit right arrow key etc.
System would bluescreen at the moment the welcome to setup section appears where you choose partition to install on etc.
In the end I disabled raid in bios again and didn't use the drivers floppy ( I'd also used the latest from that unified driver download as also mentioned in the sticky )
Using the slipstreamed sp2 installer windows actually recognised the full size of the drive now on the setup section ( the screen it would bluescreen at with the SATA drivers installed from floppy )
I got the nforce maxwell and realtek drivers installed from the CD that came with MB and all is fine, so I'll count my blessings and leave it as is....for now
I do wonder why it wont allow me those drivers though, I checked my HD with powermax uility and it seemed fine, but something must be dodgy somewhere. I just hope it doesn't rear it's ugly head while I'm in the middle of doing some work or anything.

Problem of SATA burner blu-ray drive vs IDE ribbon in the mac. Would all I need is a SATA to IDE/IDE adaptor?

I purchased an MCE blu-ray burner a while back in 2010 and am only now installing it, and am running into the problem of SATA drive vs IDE ribbon in the mac.
Would all I need is a SATA to IDE/IDE adaptor? Are there any details I need to know?

that one will definetly not work, notice how theres no place for you to hook your power connector in there? going IDE to SATA is something I am yet to find an adaptor that really works well yet( that being said i only tried once.) that being said, you can definetly use somethign like the thing i link to below assuming you have a free HDD bay. you can use it to bring one of your HDD sata ports AND power, up to your optical drive bay. That way, theres no convertion, only a quick little extention. They come in varying lengths from 3", (prob too short), to 8" (the one i linked to, might just barely be long enough, maybe still too short) to 20", more than long enough.
Good luck
http://www.ebay.com/itm/22-Pin-Male-22-Pin-Female-SATA-Extender-Cable-8-Inch-/27 0651981600?pt=LH_DefaultDomain_0&hash=item3f041d7f20#ht_500wt_1039

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

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

K8N sata driver disk problems while installing win xp

I've seen quite a few people have this problem. I hit f6, after all is said and done, it asks me to insert the disk labled NVIDIA RAID DRIVER (SCSI) into drive A: press enter when ready.
It reads the two files it asked for earlier fine, so why, when I press enter, does it insist that the disk isn't in there and I still need to put the same disk in there??
I've seen other posts where people make other driver boot disks and they work, so what exactly do I need to do, or where exactly do I need to go, or what exact files do I need to make this happen??
my one sata drive is plugged into sata 1.

If you are using only 1 sata drive you could install xp without the F6 option and install the default xp drivers for your sata drive. There is not a lot of difference regarding performance. Otherwise create your own sata drivers floppy(instructions in the sticky) and work from there.

Boot up problem ; My G31TM - P35 with Windows 7 OS cannot see my SATA drive

I recently bought a new g31tm-p35 motherboard with Intel Core 2 Duo Processor. I also bought a Seagate 500 g harddrive (SATA) and installed my old IDE harddrive. I loaded Windows 7 (32) Pro OS. My problem is that when I boot up my PC, it does not always see my SATA harddrive (drive D) where my OS is loaded on. It sees my old harddrive (c) but there is no OS loaded on that drive. It then gives me a "missing BOOTMGR" error. Can anyone help?

Try another SATA data cable and ensure it's fully seated and no sharp kinks in it, ensure SATA power cable is fully seated or try a different SATA power plug from the PSU. I had a similar problem not long ago and it was due to a PSU power problem for SATA that required a new PSU to fix it.

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

Please Help: problems with 2nd internal SATA drive on G5

Hello everyone,
I was transferring and deleting very large files from my main drive, a 2nd 250GB SATA internal drive, and an external 250GB FW800 drive recently (about 50GB worth of data transfered), and decided to run disk warrior and repair my permissions/verify disk in disk utilities once completed.
Everything seemed fine until I verified my 2nd internal drive upon which I received the following error: "First Aid Failed" citing "Invalid node structure" and that the volume needs to be repaired. I attempted to Repair disk, though the process stops and I get the same error "Volume could not be repaired because of an error."
This 2nd SATA drive only holds data (I'm a musician so it only holds sample data for streaming in Logic) but it contains allot of information (185GB used of 233GB) which according to my math comes out to about 80% used. This should be acceptable amount, correct? The drive also has Journaling enabled, though I'm not sure if its relevant or not.
What should I do? The drive itself seems to be working fine, but why would disk utility have a problem reading/repairing it if its indeed fine. Should I be worried? The drive is probably no more than 2 years old, so it cant be drive failure yet, can it?
Thanks in advance for any help you can provide!
Update: I tried to graph the problem drive again in diskwarrior, and this time an error occurred! This obviously did not happen the first time I used diskwarrior to graph and build a new directory, so something must have happened recently. What could have happened? What should I do?
Message was edited by: Jonathan Timpe

This 2nd SATA drive only holds data (I'm a musician
so it only holds sample data for streaming in Logic)
but it contains allot of information (185GB used of
233GB) which according to my math comes out to about
80% used. This should be acceptable amount, correct?
Yes, that's fine.
The drive also has Journaling enabled, though I'm not
sure if its relevant or not.
Hmm, I think I once had a drive with a directory problem that couldn't be fixed with DiskWarrior without journaling being (temporarily) disabled. After disabling journaling, I used DiskWarrior to Rebuild the drive's directory, then I reenabled journaling.
What should I do? The drive itself seems to be
working fine, but why would disk utility have a
problem reading/repairing it if its indeed fine.
Should I be worried? The drive is probably no more
than 2 years old, so it cant be drive failure yet,
can it?
I'm afraid it could be, I've had drives fail at any time between half a year after purchase up to 3 or more years after. Though often one hears the drive "die", or notices very slow performance due to bad blocks being weeded out, and the S.M.A.R.T. status - visible in Disk Utility (only for internal drives) in the bottom right, when you select a drive (not volume) is an indicator of a harddisk's health as well (though not the most complete, see this hint, or S.M.A.R.T. Guard).
Update: I tried to graph the problem drive again in
diskwarrior, and this time an error occurred! This
obviously did not happen the first time I used
diskwarrior to graph and build a new directory, so
something must have happened recently.
Did you try to repair anything with Disk Utility in the meantime?
What could
have happened? What should I do?
So did the Repair with DiskWarrior not finish? What kind of error was it?
In my experience, DiskWarrior mostly fixed any directory trouble. For more serious cases, see this thread.

[SOLVED] Very strange P43 Neo-F + sata drive problem in vista...

Well I'd been running Windows 7 flawlessly apart from a few non-related motherboard problems, so I decided to install Vista.
Basically my main OS drive (sata) is always detected, but then occasionally (more often than not) my secondary sata drives will simply not be listed in device manager once the system is booted up. Now, I've seen this problem before, and it was sorted by right clicking 'my computer' going to 'manage' and setting the drives up to be detected. But this simply isn't the case here.They don't appear anywhere!
It sometimes sorts itself out once I click 'Scan for hardware changes' in device manager and they magically appear as if ive just plugged in a USB device, which is fine I guess...but each time it swaps the damn drive letters around! So having media library's in Winamp, etc or putting a shortcut toolbar to my music on the taskbar is all but pointless!
All of my hardware apart from Bluetooth has drivers installed for it, and nothing seems to be conflicting at all. Does anyone have any idea why this is
happening? because in all my years of computing I've never seen something as strange as this...
As far as I know I have the latest Intel INF drivers installed (9.0.0.1011)
This is the board: http://www.ebuyer.com/product/148024

I can't see how it'd be PSU because Win7 was just fine...but here it is...
PSU: OCZ XStream 600W PSU
100~240Vac 10-5A 50/60Hz
+3.3V(36A), +5V(30A), +12V1(18A), +12V2(18A), +12V3(18A), +12V4(18A)
Specs:
Dual Core E5200 2.5GHz
4GB Corsair RAM + 2GB OCZ RAM
nVidia GeForce 9600 GT
MSI P43 Neo-F
Not detected (at Vista startup) drives:
Hitachi HDP725050GLA360
ST3320620AS
(they show up perfectly fine in DOS, but I remember only the drive below appeared during Vista setup drive options...)
Detected Primary OS drive:
WDC WD800JD-00LUA0
My drives in BIOS are set to IDE mode (which has always been fine for me in the past). I set it to AHCI Mode to check if it boots but it just sticks on the same screen (flashing underscore). I'm sure it's driver related but I'm totally out of options now...you'd think installing the ones provided on the MSI site would get it working... :/
Another thing is under 'Storage Controllers' in device manager, there is only an IDE Controller. I'm sure there should be a SATA one there, too?

Problem adding SATA drive

Similar Messages

Maybe you are looking for