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

Similar Messages

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

  • PM8M-V Sata drive problem

    Hi
    I've been searching high and low for a solution to the problem with the pm8m-v MB where it does not give any options in the BIOS to enable the SATA drives. I've also read several posts in this forum about this matter and was unable to find a solution.
    https://forum-en.msi.com/index.php?topic=99290.0
    https://forum-en.msi.com/index.php?topic=93394.0
    Has there been any updates from MSI to resolve this problem?
    I know that my SATA drives work as they register in the RAID utility on statup, but I do not want to install as RAID and the BIOS does not offer any option to change this.

    Quote from: Jack t.N. on 21-October-09, 23:31:36
    The mainboard's controller does not support SATA-II hard drives.  Please read the hard drive manual and find out how to force the drive into SATA-I compatibility mode (usually this is done via jumper settings).
    sir there are no jumper setting in this motherboard , and i have checked the manual there is no option to go to SATA-I compatibility mode , is there any solution ?

  • K8T800 Neo-V V1.0 - SATA Drive Problem

    Hi everyone,
    I'm becoming a little frustrated with my computer at the moment because it's being very tempremental with regards to detecting my Western Digital 500GB Sata drive. Most of the time it doesn't recognise it, but earlier on today (or rather yesterday now) it did show up on my XP O/S which I am currently running on a small IDE drive.
    I normally use my WD 500GB drive as my main drive, and a 200GB Maxtor IDE drive as a storage drive however, my SATA drive suddenly developed a problem with VISTA which kept me from viewing my desktop. After resetting the bios to the default setting I installed XP Pro onto a smal IDE drive so that I could update the bios drivers for my mainboard. However, I have the most recent drivers for everything, but my SATA drive STILL won't show up. It takes a long time for the mainboard to boot after searching for IDE drives (which I assume is searching for SATA drives) and then it boots XP from the IDE Drive 
    My question is, how the hell can I get my XP installation to recognise my SATA drive again. I managed it once, but ever since then it's vanished. I have jumpered my SATA drive to run in 150mb p/s but did no luck. Also changed my 'On-Chip SATA-IDE Controller' setting in bios to SATA but still no luck 
    Can somebody PLEASE point me in the right direction? I'm usually able to sort simple things like this out - but this one has me at the end of my teather 
    I'm also running bios version 5.10 (Which is VERY different to the previous version that I've been used to)
    Many thanks in advance,
    Adam

    Quote from: TechnoRocker on 04-June-09, 01:13:33
    I intend to, but I don't have a cable spare. You only provided one with the mainboard and so I will have to go out and purchase another cable. We'll see what happens and I'll report back soon.
    What bios version is best and most stable?
    Quote
    What bios version is best and most stable?
    Which works for you.
    What was your BIOS version and what's current version installed?
    Also ID your mainboard, look here for details ==> https://forum-en.msi.com/index.php?topic=113146.0
    or paste mainboard serial number
    Quote
    I intend to, but I don't have a cable spare.
    Well find it from somewhere.
    Also some moments are not clear to me:
    * Does this HDD worked before fine in your machine?
    * What was your final action before issue to come?
    * When the HDD is "missing" in your OS, does the BIOS detect it?
    * Do you flashed your BIOS before issue to come or not? If yes provide info about your old version and current BIOS installed.

  • K8N nForce 4 (CK804) and SATA drive problems

    Hi,
    I have a K8N Neo MB with a 4 port sata and RAID. It seems that it is not stable with sata drives at all.
    I had at first 2 120G SEAGATE drives. I kept getting random hangups from windows AND linux. I thought it was a problem with one of the drives to I booted with one of them at a time and worked a bit... it seemed the problem went away.
    but later, after a week or so, it seems everything comes back again. same problems with freezes and hangups.
    when windows for example freezes, and i press reset. at the boot screen, the POST would hang up at the step which detects the SATA drives. it would stay like this foreever.
    I would have to totally shut down power for a few seconds and boot again.
    I tried working with pata drives and its totally great and stable. no problems. if i install a sata drive with the pata, i get the same hangup problems.
    i bought another seagate 80gb sata drive just to make sure that the older 120gb were not a problem. it worked for me fine a t first, but started to do exactly the same afterwards
    i tried to access the drive from linux in order to trace the access pattern of the drive and get a sense of what was going wrong. Here is the syslog from the kernel messages.
    any help with that issue is highly appreciated. thanks
    Mar  8 22:01:15 ubuntu kernel: [  715.201288] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:01:15 ubuntu kernel: [  715.201297] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:01:15 ubuntu kernel: [  715.201300] ata1: status=0xd0 { Busy }
    Mar  8 22:01:15 ubuntu kernel: [  715.201308] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:01:15 ubuntu kernel: [  715.201310] sda: Current: sense key: Aborted Command
    Mar  8 22:01:15 ubuntu kernel: [  715.201313]     Additional sense: Scsi parity error
    Mar  8 22:01:15 ubuntu kernel: [  715.201318] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:01:15 ubuntu kernel: [  715.201322] Buffer I/O error on device sda5, logical block 0
    Mar  8 22:01:45 ubuntu kernel: [  731.858112] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:01:45 ubuntu kernel: [  731.858121] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:01:45 ubuntu kernel: [  731.858124] ata1: status=0xd0 { Busy }
    Mar  8 22:01:45 ubuntu kernel: [  731.858132] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:01:45 ubuntu kernel: [  731.858135] sda: Current: sense key: Aborted Command
    Mar  8 22:01:45 ubuntu kernel: [  731.858137]     Additional sense: Scsi parity error
    Mar  8 22:01:45 ubuntu kernel: [  731.858143] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:01:45 ubuntu kernel: [  731.858147] Buffer I/O error on device sda5, logical block 0
    Mar  8 22:02:15 ubuntu kernel: [  748.515491] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:02:15 ubuntu kernel: [  748.515501] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:02:15 ubuntu kernel: [  748.515504] ata1: status=0xd0 { Busy }
    Mar  8 22:02:15 ubuntu kernel: [  748.515511] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:02:15 ubuntu kernel: [  748.515514] sda: Current: sense key: Aborted Command
    Mar  8 22:02:15 ubuntu kernel: [  748.515516]     Additional sense: Scsi parity error
    Mar  8 22:02:15 ubuntu kernel: [  748.515523] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:02:15 ubuntu kernel: [  748.515526] Buffer I/O error on device sda5, logical block 0
    Mar  8 22:02:15 ubuntu kernel: [  750.227687] Losing some ticks... checking if CPU frequency changed.
    Mar  8 22:02:45 ubuntu kernel: [  765.554638] ata1: command 0x25 timeout, stat 0xd0 host_stat 0x1
    Mar  8 22:02:45 ubuntu kernel: [  765.554651] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
    Mar  8 22:02:45 ubuntu kernel: [  765.554654] ata1: status=0xd0 { Busy }
    Mar  8 22:02:45 ubuntu kernel: [  765.554666] sd 0:0:0:0: SCSI error: return code = 0x8000002
    Mar  8 22:02:45 ubuntu kernel: [  765.554669] sda: Current: sense key: Aborted Command
    Mar  8 22:02:45 ubuntu kernel: [  765.554672]     Additional sense: Scsi parity error
    Mar  8 22:02:45 ubuntu kernel: [  765.554681] end_request: I/O error, dev sda, sector 39086208
    Mar  8 22:02:45 ubuntu kernel: [  765.554686] Buffer I/O error on device sda5, logical block 0

    the answer for this problem is very simple.. I was having EXACTLY THE SAME PROBLEM as you... I changed 3 hds sata 200gb because I wasnt finding out the cause... so I found this link:
    http://www.msi.com.tw/program/service/faq/faq/esc_faq_answer.php?L_kind=1&Q_LIST=1141&NA=637
    The problem is the NCQ technology... just disabled it and everything will be fine... i did this here and now is everything PERFECT! lol
    regards!

  • Second SATA drive problem

    So i work in the video business. I am constantly popping hard drives in and out safely. Anti static bags etc. etc. Anyways i just popped a SATA drive in and it mounts but will not show the files? I went ti disk utility but it says it does not need repair and is verified. It also shows there are 54 files and 19 folders. Thing is i know that there are 54 files and 19 folders but when i double click the Hard drive icon on the desktop it shows none of the files or folders. Any help would be greatly appreciated.

    Hi
    Spotlight is the tool you use for searching your Mac. The very first time you run it, it goes through your HD making a note of every word in every file (indexing). This means that, say you type the word 'Word' into Spotlight, it will find every instance of that word (whether in title of document, or contents of document).
    Steve

  • Mac Mini slow when accessing hd - NVidia MCP79 SATA Driver Problem?

    I bought a Mac Mini (Early 2009) a while ago. Unfortunately i have a problem concerning speed and responseability which i couldnt solve even with a lot of googleing.
    I noticed that problem first time when i tried to play a video file from hd. The video does not play as smooth as it should. It stutters from time to time. It is like a short interruption. The picture freezes for half a second and replays the lost frames very fast after that. These freezes do not occure periodically. It seems to appear randomly. The wierd thing is that the cpu usage is very low and there is enough free ram and disk space.
    So i think its not a ressource problem. I noticed that these freezes do not only affect video playback. The whole system is kind of unresponsive. And thats the the case if there is some sort of hd or dvd access. When i try to copy a huge file these freezes are increasing rapidly. The more hd access the more the system is unresponsive and cannot be used anymore.
    All these effects reminded me of a faulty dma/udma setting on windows machines. So i tried to check the transfer mode for my macs hd controler. But i didnt find any place where to check that. And i dont really think it is running in pio mode because that would result in a high cpu usage.
    I played around a little bit to understand whats going on. So this is what i found out:
    When i play a video from the hd its stuttering. It increases if i copy a file from or to the hd. Copying a file from the dvd-rom increases the effect as well. It is not influenced by a copy from AND to an external usb hd. And the whole effects do not appear under Windows Vista no matter how much i acces the hd.
    So i come to the conclusion that there must be something wrong with the SATA controler driver which is a NVidia MCP79. Unfortunately i have no idea what i can do to solve this problem. And i didnt find any advice or something in the internet.
    So i would appreciate any suggestions.

    Ok, I think I was jumping to conclusion. Disabling journaling didnt remove the problem. It just seemed so because my problem is much less distinct with Leopard. Bad luck I guess.
    kmac1036, to answer your questions. For sure I dont have warranty anymore. Maybee I should have posted that I upgraded my Mac to 3 GB RAM. Furthermore I replaced the original Hitachi HD with a Western Digital 500 GB model.
    Somehow that may be connected to my problem. I've read that many people have problems with the WD HD and those beachballing issues with SN. (I do so too)
    But my performance problem when accessing the HD did also exist with the Hitachi. In fact the Mini was extremly slow with the original 1 GB RAM. I think putting some additional memory into the machine helped because it reduced hd accesses.
    Ok, I am not an expert. But if I had to guess I would say the following seems to happen. There may be an operation in the hd driver that takes longer than it should. Because of that it maintains cpu cycles and prevents the kernel to continue scheduling. That would explain why the freezes are not connected to a high cpu usage and why the systems seems to catch up things after the freeze very fast.

  • MacBook Pro mid 2009 HDD to a Kingston SSD SATA drive - Problems

    Hi
    I own a MacBook Pro Mid 2009 and I'm running OSX Mavericks with Windows 8.1 Pro Bootcamp.  I wanted to upgrade to an SSD drive and after reading the great reviews on Amazon, I purchased a Kingston 240GB SSD 2.5" V300 SATA 3.
    Many of the buyers had installed the SSD drive on Macbook Pro, including "mid 2009' models without any real problems but I've just spent the best part of 3 hours trying to install the drive but so far, it has not worked and the problem seems to be that, although the Acronis True Image software that comes with the drive to 'clone' the source drive and install it onto the destination drive (new SSD drive), I get a message which states, "WARNING:  After migration, the O/S will not be able to boot from the destination disk in the BIOS - If you want to boot from the destination disk after migration, you need to enable UEFI booting in your system and then restart".
    During one of my first attempts to install the SSD drive, I removed the original HDD from the MBP and installed it in the supplied 2.5" caddy and and connected it to the MBP via the USB cable supplied then installed the new Kingston SSD SATA3 drive in the MBP, powered up and then rebooted.  The Acronis bootable software launched and after choosing 'clone disk', cose source and destination drives, I got a message saying:  "The selected disk will be migrated as is (disks layout will remain GPT)".  "After operation completion, operating systems will not boot from the destination disk in the BIOS".
    My system has the latest available Boot ROM Version (MBP.00AC.B03 and the SMC Version is 1.47f2 and as far as I am aware, Apple computers have no BIOS that you can access like on Windows computers and instead use EFI instead.
    Both drives had Extended Journaled GUID Partitions on them and what baffles me is that other buyers of these Kingston SSD SATA3 drives appear to have managed to install the SSD drive, but I've had to give up.
    I would really like to get the SSD drive working but so far I've failed.  Any advice would be appreciated and I'll try it out before reluctantly returning the drive for refund.

    Hi
    Thanks for your reply.
    Yes the Acronis software is Windows but I read through a lot of reviews on the Kingston SSD SATA 3 drives Amazon and from what I can gather, after removing the original drives and installing that in the 2.5" caddy and then installing the new SD drive in the Macbook, those buyers then used the software to boot from and clone the source drive to the new drive.
    I'm not sure if I mentioned it in my first post, but I did use the Disk Utility in Mac OSX and erased, formatted and partitioned the drive and then pushed CMD + R at start up but I was not able to install a copy of the OS because the drive was not recognised.
    I think I also used the disk utility in Windows and then tried again in OSX but no luck.  I'm no expert but as stated above, the issue seems to be that the SSD drive is not booable in the BIOS (or Mac equivalent).
    The SSD drive is SATA 3 and I'm sure that the SATA ports are SATA 1 on my MBP and maybe that the problem Perhaps someone can confirm this. 

  • Replaced failed HDD Sat. L455-5000 with new Western Digital 320 SATA drive-problems with recovery

    Original HDD died.  Replaced it with new WD 320 SATA from Best Buy-nice drive-good reviews.  Used Recovery Center DVD's I had burned earlier.  Three with Toshiba Recovery  2 with Windows Recovery Envrinoment and DRivers/Apps.
    Toshiba REcovery only asked for first 3.  Computer restart after Recovery Install(First Three Disks) gives error message:
    File: \windows\system32\DRIVERS\LPCFilter.sys 
    Status:  0xc0000428
    WIndows Cannot Verify Digital Driver Signature.
    Windows Boot Manager "screen" always comes up and Windows fails to start.  
    1.Asking for a windows installation disk-thought this was given in Toshiba Recovery DVD's I burned.
    2. Chosse language settings-click next
    3. CLick " repair your computer."
    I thought the Toshiba Recovery Disks were supposed to install everything for me.  I don't have a sparate windows system disk.  Never burned one
    Any help woud be great.
    Thanks,
    Charles

    Time for some good news.
    I received and installed an OEM WD 250 (Toshiba) replacement drive.  After loading the recovery disks this morning-it worked perfectly-just like "out of the box."  
    It was the HDD failure after all.  No software gliches at all.  Windows update of course is attempting to re-load about 500 updates. LOL.  I also learned to spread them out in groups of 10-20 long ago as well.  This will take some time; but the laptop is running fine. 
    So I learned some great lessons.  1)-stick with OEM replacement hardware-computers are "locked in time" to a definite hardware configuration that works well at that time in history.  2) If I had not used my own "decision" tree to problem solve-I'd still have a dead computer.  3) I was correct to order an external drive enclosure to test the bad drive after I was unable to do so with the laptop.  4)I made the right choices to contact the Western Digital Drive support to find out the new drive really might also be the problem.  5) It was also great to be able to get such amazing help on this forum too-what a great resource for Toshiba owners. 6)Finally-I was able to "chat" with the Toshiba Rep. online to confirm the OEM part number of the WD drive they had used-and ordered -cheaper- from Amazon.com.
    7) After 2 weeks of my own time(and great online resources) and $80.00-I fixed my laptop myself.  Never had to mail it anywhere.
    8) I also ended up with a great external backup drive-that I was always too lazy-and cheap-to order for myself  before.  LOL.
    9) Now what about the Toshiba OEM Graphics card that the "Windows Experience Survey' always says I need to replace?  Nope -not going there -yet.
    Thanks for all the help-
    Sincerely,
    Charles

  • SATA Driver problems

    Hello everyone,
    I'm having a problem attempting to install Windows XP.  I have 2 Maxtor 250GB using SATA 3 and 4.  Created the RAID array via F10 (mirrored). I hit F6 during the beginning of the setup to provide the additional drivers for Nvidia Raid Class Driver and the Nvidia NForce Storage Controller, and then proceed with the setup.  Now, it gets as far as "Setup is starting Windows" whereupon it is SUPPOSED to proceed to the EULA and then the screen for choosing the partition etc...but it just reboots....
    Now, if I attempt the install WITHOUT specifying additional drivers, XP setup can detect the 2 drives, and I can install...but after installation it is horribly unstable...any attempt to view drive contents results in machine_error BSOD's...
    I have tried getting the drivers directly from MSI's site (since the date and sizes are different than the ones provided with the mobo) but get the same result.
    Oh, and flashed BIOS to 1.12
    I would appreciate any suggestions.
    Thanks.

    Well, it appears I found the problem.  Thanks for the suggestions though.  I was reading through every post that had something even CLOSE to my problem, and one person suggested switching out the CD-ROM drive.  I tried an older crappy drive I had laying around, and despite the fact that it took an incredibly long time to install windows, it ACTUALLY WORKED.  How the heck could the CD-ROM drive be causing this much of a problem?  I guess I don't really care since it's actually running now, but I'm pretty curious.  The only thing I could think of is that the nvRAID appears to somehow join the IDE and SATA chains into one for raiding purposes, so perhaps certain CD drives cause problems when trying to intermingle with arrays.  However, I put the drive that doesn't work back in and it works fine now that windows is installed.  Anyone have any theories?
    I'd just like to say here for all the people searching for a similar solution:  IF YOUR COMPUTER IS HANGING OR REBOOTING AT THE "SETUP IS STARTING WINDOWS..." PHASE, SWITCH OUT YOUR CD ROM *FIRST*.  I tried every other possible solution first, flashing the bios, new RAID drivers, different types of RAID arrays, and even different XP CDs.  Hopefully this post will save at least one person some time
    These benchmarks sound about right?  (4 WD 7200x8 250Gb SATA in RAID 0 - 931Gb):
    Burst transfer: 234.9 MB/s
    Average read: 141.0 MB/s
    Random access: 13.6ms
    CPU utilization: 11%

  • MOVED: sata drive problems

    This topic has been moved to AMD64 nVidia Based board.
    https://forum-en.msi.com/index.php?topic=73353.0

    Quote
    Originally posted by JER101
    Quote
    Originally posted by dacull
    I don't think so, people with many different types of motherboard have reported the problem, apparently..
    according to
    http://www.blep.net/hl2stutter/
    It occurs on both Intel and AMD CPUs of all speeds.
    I studied that link and can't any reference to disk controllers, yet many are admament that  the problem is poor sound caching which requires sounds to be loaded (from disk!). How the disk controller functions during intensive system use as typified by 3d games could be at the heart of the problem. Other games with large datebases also  stutter, such as Microsoft Train sim.
    I'm not saying you are not onto something .. ive had very similar problems with a supposedly top of the range dell laptop with a bad HD interface, everytime it accessed the disk, everyhing would stop momentarily, there is no reason that should be the case and just shows that it is not releasing its interrupt quickly enough.
    The reason I pointed the link out is that you were hinting it was the nvidia sata implementation but i think thats only for AMD (atleast now) yet the link implies that intel systems are affected also.
    The sooner the cause is discovered the better.. I get it , its not too bad though. installing the new nvidia separate sound drivers helped alot.

  • 2008 - How to make the SATA drives run full speed with Bootcamp and XP ?

    Has anyone found a way - after all this time - of repairing a 2006 install of Windows XP SP2 - or in someway fixing the rather slow SATA drive problems?
    I have not upgraded to 10.5 - but would if the new Bootcamp somehow (via new drivers??) fixed the problem!
    My machine is now 2 years old ( 2.66 4 core ) and I finally need XP's full speed for a project - but most of the posts I've seen are fro 2006 and expired.
    Help!
    -Glen

    And again, my objective to is get 'full speed' from the SATA drives while running XP.
    -Glen

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

  • 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

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

Maybe you are looking for

  • Stock on a particulare date

    Hi, i am developing a STOCk-in-transit report, wherein , i need to display stock on a date entered by the user on selection screen. The stock includes all stock type (unrestricted, quality and blocked stock). How do we calculate the stock on a partic

  • Can't see my bill...since October!!

    I have called countless times to support. First they say I don't have a login...ummm how did I log in then. It shows my name and lets me pay my bill but I dont' have a login... In their records, the name is right the address is right etc. On the webs

  • Can't Edit a form after converting it to reader extended

    I am struggling with an issue when creating a form. I create the form in Word, convert and edit in Acrobat Pro, then save a version as "reader extended" so that our users can fill it out. However, there were some errors in the form after I saved it a

  • I want to check XI setting in my existing sever

    Hi Guru's I want to check XI setting in my existing sever , as i m new in xi. I want to know abt SLD , adaptor and alert setting etc plz  help me Thanks in advance Edited by: sandeep gautam on Dec 26, 2007 7:47 AM

  • Unable to connect to internet via the proxy - Proxy set up OEM 12c

    Windows server 2008 64 bit OEM 12.1 I have to get agent software for Windows server 2003, and as far as I know the only way is through self update in OEM, is this the only way? But when I input my Oracle support credentials I get an error : Unable to