Gateway LX6810-01 SATA Drive Bay Problems

I have been trying to install drives into the SATA bays but they are not showing up on the computer, is there something you have to do in the BIOS or something to turn them on before you use them? They do not show up in DIsk Managment or My Computer at all...
please let me know! I can be emailed at {removed per forum guidelines}

You may try posting this in the Computer portion of this forum.  There are TONS of gurus on here but many of them probably don't look under this category.
Nothing I post is an official statment of Best Buy or Geek Squad, it is only a helpful opinion!

Similar Messages

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

  • Single sata drive detection problem

    Ok here is my problem that I am pulling my hair out over.
    I purchased k7n2 delta ilsr and a sata 10000 WD raptor drive yesterday.
    I am trying to install the single drive in my system and the os will not detect the drive.
    This is the steps I have been taking to no avail.
    1.  On  boot up pressing ctrl f  to set up a stripe raid array (required even if there is only one drive)
    2. reboot and boot to western digital data lifeguard tools and format the drive.  (This program sees the drive just fine and says its functional.)
    3.  Reboot and set the bois to boot to os cd, reboot and run the w2000 cd and hit F6 when prompted.  Then it prompts me to install the promise 376/378 fastrack drivers which I do and it installs them.  then it leads me to the prompt to install the os and it says setup did not find any hard disk drives installed.
    I have tried many variations of this to no avail, what am I missing?

    I romoved the jumper in the jumper block with no change, the floppy drive installs the promise drivers fine, I d/l the larger file folders  for the promise drivers with no change.
    the drive is attached to sata1, I moved it to sata 2 with no change.
    The only thing I can think of is a bios setting I am missing, I cannot see the drive in the bios only when I boot to the wd utility.
    My other thought is according to the mobo manual it says to fdisk and format rather than using the data lifeguard utility I am using to format.  I do not have the files to boot to dos, fdisk and format the drive.  I made a msdos boot disk in xp and transfered format and fdisk to the floppy but the command in dos does not work.  format ???? to where there is no drive designation.

  • Sound Blaster X-Fi Platinum Drive Bay Problem/Remote Control Probl

    Yesterday I have received my X-Fi Platinum sound card.
    The sound card works fine.
    I see a red light in my dri've bay so I am assuming there is power.
    The problem is that when I plug in headphones it does not work.
    The remote control does not work either. Is there supposed to be a light when i press something on it's?
    Also people tell me to enable it in Entertainment Center Settings but it wont let me.
    When I open the program it pops up " Unable to find working IR device".
    Also when i get in the program it wont let me check the box that says " enable remote control". It is just grayed out and wont let me click.
    Can someone please help me.
    Thanks in advance.Message Edited by xkrnmikelx on 05-27-2006 0:50 PM

    Okay, I've got it running (almost):
    I did uninstall all Creative apps and drivers.
    After a reboot, I did run the Registry Cleaner of Tuneup (http://www.tune-up.com/)for several times.
    In addition, I did manually delete ALL creative entries in the registry with "regedit".
    I did also found some running tasks for my onboard RealTek soundcard, I thought they have been uninstalled already, did kill the tasks and deleted the related programms in the Windows folder (soundman.exe).
    After another reboot, I did run the installation from the CD again - the Entertainment Center is running.
    ONLY PROBLEM LEFT: All options are working, except in "Music". All options except the last one (Workplace) to browse folders, are crashing the Entertainment Center.
    When I select Artist, Album, Genre, the EC seems to look for files on my HD and shuts down after a while.
    Maybe my database/music folder is to large (+ 5000 titles, my complete CD collection as WMA files).
    I'm running a German OS, so I'm not 00% sure if the mentioned folders/options are correct translated.

  • Second Drive Bay Power Port Bad?

    I am trying to install a second drive into my PPC G5 but it is not recognized. I realized that the power cable setup for the second SATA drive bay is bad at the port. I plugged the power cable from the First Dive bay into the port on the motherboard for the second Drive Bays power and nothing. It wouldnt boot. I am pretty certain the port for the Second Drive Bay Power is bad on the motherboard. Is there anything I can do other than having this replaced?

    I assume you double checked the new drive as working on the known good power port. I have had a DOA from time to time. As the port for the bay comes out of the logic board I would also assume that it would not be worth replacing the logic board (unless you are handy yourself and could spot and fix a micro or a macro crack.
    The other possibility is to pull a copy of your machine's service manual and see how the drive power was routed. Which exact PowerMac model is yours? I have a quad and I am pretty sure the power connectors plug into the bottom end of the board. I guess what I am getting at is this. You will want to double check that the board's port itself is bad by testing the PS/s output at the mains. Maybe you will get lucky and find out that the PS is the culprit not hte board as some models of G5/s have PS recalls on them. I have late 2005 and know I have a service manual on mine somewhere on a drive. Other wise Google your board and see how the power is channeled.

  • Another WinXP Sata Raid Boot Problem

    Hi there, I've flipped though a bunch of posts but I haven't been able to find the issue I'm having, so I figured I'd post and cross my fingers.
    I'm running a K8 Neo4 Platinum board (updated the bios to 1.9) and I'm trying to get it to boot WinXP off a striped pair of Seagate Barracuda 7200.10 (400g).  With nothing else connected except a DVD drive, floppy drive, and the two HDs on ports 1 and 2 (set to striped array in the Riad setup), I booted up from the WinXP SP2 cd.
    Pressed F6, loaded the drivers (newest ones I could find at the msi site).  Setup detected an 800g hard disk no problem.  Created a small partition (50g) for the OS, formatted normally, and let Setup do it's thing.  Everything went fine with no errors, reg key, settings, not a hitch.
    And that's where the happiness ended.  Upon trying to boot from the drives, WinXP gets as far as loading Wup.sys and simply reboots itself.  Safe mode, last known all result in the same reboot.  I tried to repair the installation, fixboot, chkdsk, and that simply killed the installation wholesale.
    As a side note, I can install boot off a single SATA drive without problems.
    It feels like I'm forgetting something really simple, since XP was able to recognize and install without problems, but it just can't boot.  I've been fighting with this darn thing for a few days now, and I'm about ready to just give up and run them as single drives.  There is no data on there no reformatting or doing something funky is perfectly fine.  Anyone have any ideas?  Thanks in advance!

    Quote from: BOSSKILLER on 05-June-07, 01:32:35
    and...? any changes?
    get a copy of Memtest86 and test your memory for errors.
    another and most suspected thing is your PSU:
    "Antec 400W (3.3v/30 5v/28a 12v/14A)"
    get a decent PSU with 30A or more on +12V.
    Ah, I read the spec wrong.  The PSU is dual rails so 12v1 is 14a and 12v2 is 15a. Hopefully, since pretty much everything else is unplugged, that should be enough power to boot.
    I tried mem test, no errors after multiple passes.
    Also, when I tried the new nVidia drivers, it got me to where I am now.  Auto reboot when trying to start Windows.  The old MSI drivers gave me an undefined error or an "unmoutable device" error.  Both resulted in a bluescreen and immediate reboot.

  • Ejecting problem on my 2nd SATA Hard Drive Bay Caddy

    I am having an ejecting problem with my caddy secondary HD.
    Basically every time I close the lid, the secondary HD is ejected or, in case ejecting fails, I obtain an error message..very annoying situation.
    How can windows 7 avoid to eject it? Do you know a best practice to configure properly the 2nd SATA Hard Drive Bay Caddy??
    Thanks in advance!
    Fabio
    Solved!
    Go to Solution.

    Really sorry, I didn't explain properly: I was talking about Ejecting OS side (windows 7 eject my secondary HD when I close my laptop, consequence is that I don't see it anymore in Computer).
    ejecting is when you press here
    anyway Thanks!!

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

  • Possible to put two or more 3.5 SATA drives in optical bay of early 2008 mac pro?

    Hello! A question about expansion really. Here is my iexpansion plan. Wondering if you can see any possible problems?
    drive bay 1 - SSD - raid with drive 2
    drive bay 2 - SSD - raid with drive 1
    These will make the boot drive.
    Then...
    drive bay 3 - 3.5" sata - raid with drive 4
    drive bay 4 - 3.5" sata - raid with drive 3
    Two extra internal eSATA ports being extended out with wires to an empty PCI slot, leading to two external 3.5" drives in eSATA interfaced, self-powered enclosures.
    Optical Bay - Removing the two currently installed optical drives and replacing with two 3.5" SATA drives. In order to do this I'll need to get some form of ATAPI to SATA adapter as my early 2008 macpro uses the older interface.
    So my question is:
    Can you see any reason why this would not work and if you can point me towards an adapter that might work for holding/converting the interface of those two 3.5" drives in the optical bay? Will there be enough space for the adapter? I'll probably rig my own bracket for holding the drives there but any suggestions welcome!
    Will power become an issue? I'm also running a flashed PC graphics card which uses both of the additional power  ports (rather than just one). But other than that nothing extra.
    Many thanks for your time!

    Hi Hatter,
    Thanks for your reply. I'm not so worried about the SSDs as I am about the ability to put 2x3.5" SATA drives into the optical bay and have them fit (I do not want to pay a lot of money for any fancy pieces of metal such as the one you linked) when they necessary PATA-SATA adapter and power supply adapter if attached to them. Have you ever seen someone do this and what adatper did they use? I'm looking at this sort of thing:
    http://www.cooldrives.com/satoidecofor.html
    I can not put the SSDs in the Optical bay because the slower PATA interface would cut the speed so much it would not be worth it.
    Any tips on known reports of 2x 3.5" drives fitting in there would be great, and what adapter was used.
    Thanks!

  • W8.1/W7-64 dual boot, dual drive (SSD & SATA) GPT/MBR problems

    I'm posting in both the W8 and W7 forums because I'm not sure which is more appropriate.
    Setup:
    New Dell XPS8700 with Windows 8.1 installed on a 256GB SSD drive.  I upgraded to W8.1 Pro.
    2nd drive is a 2TB SATA.
    Goal:
    Keep W8.1 Pro on SSD.
    Install W7 Ultimate 64 (legal copy, installation disk) on SATA Drive.
    Select which one I want at boot.
    Main Issue
    Cannot easily choose which OS to log into.  See  Dual Boot Problems and Current State for details.
    Background: W7 Installation Probems
    1. I disabled Secure Boot in the BIOS and Fast Startup in Windows 8.1
    2. I created 3 partitions (D, E, F) on the SATA drive (a GPT drive)
    3. Used the Advanced Option in W8 to boot from the DVD (absurd),
    4. Windows 7 started setup from the DVD but at the initial screen (Language, Country), it hung. Hard. No keyboard, no mouse.  Had to turn off computer.
    5. Using F12, selected legacy boot from DVD.  Now the installation got beyond the first screen. I selected Custom Install.  When I tried to install to the E: partition, I got the message that W7 could not be installed on a GPT drive.  From
    a lot of research and reading, I'm guessing this is because I chose a legacy boot. But, please, note:  the only reason I did a legacy boot was because I could not get past the first screen with a "normal" CD/DVD boot,
    6. So, I went back into W8, deleted the volumes on the SATA drive, changed it to MBR, recreated the volumes.
    7. Using F12, again selected legacy boot from DVD and was able to install W7 on the E: partition, except that every reboot during the installation process got me back into W8, so I had to restart with the F12 option/legacy boot to finish W7 installation.
    8. Finally got W7 installed. Logged in. OK so far.
    Dual Boot Problems
    1. No boot menu.  Computer booted directly into W8.1. And, yes, Fast Startup in W8.1 still disabled. 
    2. Downloaded and installed EasyBCD.  Created boot menu for W8.1 and W7 with W8.1 the default.
    3. Reboot, select W8.  Fine, I'm into W8.1
    4. Reboot, select W7. All I get is one bar of hieroglyphics across top of screen.  Hard freeze.  Had to unplug computer.
    5. Do an F12 reboot and select legacy boot from the SATA drive.  Get a different boot menu  with Windows 7 on top and W8 Media version below.  Select W7.  It loads and I log in.
    6. Do an F12 reboot and select legacy boot from the SATA drive. This time, select W8.  Get an error that it can't find W8.
    Current State
    1. The default boot into W8 works fine.
    2. Can't get into W7 unless I do an F12 legacy boot from SATA at startup.
    3. If I do an F12 legacy boot from SATA, I can't get into W8.
    I do not want to rely on F12 for 2 reasons: first, I want W7 to be my default working enviroment. Please do not try to convince me that there is no good reason for that.  I want to do this, have legal, paid for copies of W7 (actually, I now have four.)
    Second, it will make installing W7 updates nightmarish since I'll have go go through the whole F12 thing for every reboot.
    I am assuming that the problem stems from the original GPT/MBR  split (with the SSD being GPT and the SATA being MBR) - although I could be wrong.  And, remember, the only reason I changed the SATA from GPT to MBR was because the W7 setup froze
    at the initial screen when I first tried to install W7 with a normal boot from DVD.
    Things I've tried:
    1. Via W8, got to a command prompt where I ran bootsect.exe /scanos.  The result was that it found NO Windows Installations. Obviously incorrect.
    2. Uninstalled EasyBCD from W8.
    3. Rebooted.  Same boot menu as before: W8.1 on top, Windows 7 below (as I had set things up in EasyBCD).
    2. Via W8 Command Prompt did a bcdboot c:\windows to try to get GUI boot menu.  Got the error message: failure when attemptng to copy boot files.
    What I want to do seems to me to be quite simple: run W8 from the SSD, run W7 from the SATA.  It's my understanding that I should be able to install W7 on a GPT drive and that would, I am hoping,
    solve the boot menu problem.  But see Installation Problems above: I couldn't do the default boot from the DVD and install W7 because it froze at the first screen.  Is there some other way to get past the freeze and install W7 to a GPT?
    I've been working on this for two weeks now, have read more articles, watched more YouTube videos than I care to list. Need Help Desperately.
    <textarea style="height:80px;width:444px;border:1px solid grey;padding:2px;"></textarea><select><option value="af">Afrikaans</option><option value="sq">Albanian</option><option value="ar">Arabic</option><option
    value="hy">Armenian</option><option value="az">Azerbaijani</option><option value="eu">Basque</option><option value="be">Belarusian</option><option value="bg">Bulgarian</option><option
    value="ca">Catalan</option><option value="zh-CN">Chinese (Simplified)</option><option value="zh-TW">Chinese (Traditional)</option><option value="hr">Croatian</option><option
    value="cs">Czech</option><option value="da">Danish</option><option selected="selected" value="auto">Detect language</option><option value="nl">Dutch</option><option
    value="en">English</option><option value="et">Estonian</option><option value="tl">Filipino</option><option value="fi">Finnish</option><option value="fr">French</option><option
    value="gl">Galician</option><option value="ka">Georgian</option><option value="de">German</option><option value="el">Greek</option><option value="ht">Haitian
    Creole</option><option value="iw">Hebrew</option><option value="hi">Hindi</option><option value="hu">Hungarian</option><option value="is">Icelandic</option><option
    value="id">Indonesian</option><option value="ga">Irish</option><option value="it">Italian</option><option value="ja">Japanese</option><option value="ko">Korean</option><option
    value="la">Latin</option><option value="lv">Latvian</option><option value="lt">Lithuanian</option><option value="mk">Macedonian</option><option value="ms">Malay</option><option
    value="mt">Maltese</option><option value="no">Norwegian</option><option value="fa">Persian</option><option value="pl">Polish</option><option value="pt">Portuguese</option><option
    value="ro">Romanian</option><option value="ru">Russian</option><option value="sr">Serbian</option><option value="sk">Slovak</option><option value="sl">Slovenian</option><option
    value="es">Spanish</option><option value="sw">Swahili</option><option value="sv">Swedish</option><option value="th">Thai</option><option value="tr">Turkish</option><option
    value="uk">Ukrainian</option><option value="ur">Urdu</option><option value="vi">Vietnamese</option><option value="cy">Welsh</option><option value="yi">Yiddish</option></select>⇄<select><option
    value="af">Afrikaans</option><option value="sq">Albanian</option><option value="ar">Arabic</option><option value="hy">Armenian</option><option value="az">Azerbaijani</option><option
    value="eu">Basque</option><option value="be">Belarusian</option><option value="bg">Bulgarian</option><option value="ca">Catalan</option><option value="zh-CN">Chinese
    (Simplified)</option><option value="zh-TW">Chinese (Traditional)</option><option value="hr">Croatian</option><option value="cs">Czech</option><option value="da">Danish</option><option
    value="nl">Dutch</option><option selected="selected" value="en">English</option><option value="et">Estonian</option><option value="tl">Filipino</option><option
    value="fi">Finnish</option><option value="fr">French</option><option value="gl">Galician</option><option value="ka">Georgian</option><option value="de">German</option><option
    value="el">Greek</option><option value="ht">Haitian Creole</option><option value="iw">Hebrew</option><option value="hi">Hindi</option><option value="hu">Hungarian</option><option
    value="is">Icelandic</option><option value="id">Indonesian</option><option value="ga">Irish</option><option value="it">Italian</option><option value="ja">Japanese</option><option
    value="ko">Korean</option><option value="la">Latin</option><option value="lv">Latvian</option><option value="lt">Lithuanian</option><option value="mk">Macedonian</option><option
    value="ms">Malay</option><option value="mt">Maltese</option><option value="no">Norwegian</option><option value="fa">Persian</option><option value="pl">Polish</option><option
    value="pt">Portuguese</option><option value="ro">Romanian</option><option value="ru">Russian</option><option value="sr">Serbian</option><option value="sk">Slovak</option><option
    value="sl">Slovenian</option><option value="es">Spanish</option><option value="sw">Swahili</option><option value="sv">Swedish</option><option value="th">Thai</option><option
    value="tr">Turkish</option><option value="uk">Ukrainian</option><option value="ur">Urdu</option><option value="vi">Vietnamese</option><option value="cy">Welsh</option><option
    value="yi">Yiddish</option></select>
    English (auto-detected) » English

    SOLUTION:
    The problem I described above stemmed from the fact that I had been unable to install W7 without using the legacy option. (The W7 installation would freeze at the first screen.)  That created the boot incompatibilities between W8.1 and W7because I had
    to use legacy for the latter but not for the former.
    It turned out that the USB ports were the basic problem.  The Windows 7 installation program doesn't recognize USB 3.0 ports. Unfortunately, the A08 BIOS in the XPS 8700 -Special Edition (as of late Dec. 2014) has only 3 options for enabling/disabling
    the USB ports: Front, Top, Back.  The back panel has a mix of USB 2.0 and 3.0 ports and I needed a 2.0 port for the mouse and keyboard to work.  However, disabling the Front and Top USB ports was sufficient. The W7 install no longer froze.
    So, from my W8 installation, I wiped out the SATA drive, changed it back to GPT, partitioned it, disabled the Front and Top USB ports in the BIOS and booted from the W7 DVD.  The installation went fine.  After installing the network driver, downloaded
    previously, and updating W7, I installed the USB 3.0 drivers and then re-enabled the Top and Front in the BIOS.
    So, now the EasyBCD boot options work just fine.  Both drives are GPT. No legacy options.
    <textarea style="height:80px;width:444px;border:1px solid grey;padding:2px;"></textarea><select><option value="af">Afrikaans</option><option value="sq">Albanian</option><option value="ar">Arabic</option><option
    value="hy">Armenian</option><option value="az">Azerbaijani</option><option value="eu">Basque</option><option value="be">Belarusian</option><option value="bg">Bulgarian</option><option
    value="ca">Catalan</option><option value="zh-CN">Chinese (Simplified)</option><option value="zh-TW">Chinese (Traditional)</option><option value="hr">Croatian</option><option
    value="cs">Czech</option><option value="da">Danish</option><option selected="selected" value="auto">Detect language</option><option value="nl">Dutch</option><option
    value="en">English</option><option value="et">Estonian</option><option value="tl">Filipino</option><option value="fi">Finnish</option><option value="fr">French</option><option
    value="gl">Galician</option><option value="ka">Georgian</option><option value="de">German</option><option value="el">Greek</option><option value="ht">Haitian
    Creole</option><option value="iw">Hebrew</option><option value="hi">Hindi</option><option value="hu">Hungarian</option><option value="is">Icelandic</option><option
    value="id">Indonesian</option><option value="ga">Irish</option><option value="it">Italian</option><option value="ja">Japanese</option><option value="ko">Korean</option><option
    value="la">Latin</option><option value="lv">Latvian</option><option value="lt">Lithuanian</option><option value="mk">Macedonian</option><option value="ms">Malay</option><option
    value="mt">Maltese</option><option value="no">Norwegian</option><option value="fa">Persian</option><option value="pl">Polish</option><option value="pt">Portuguese</option><option
    value="ro">Romanian</option><option value="ru">Russian</option><option value="sr">Serbian</option><option value="sk">Slovak</option><option value="sl">Slovenian</option><option
    value="es">Spanish</option><option value="sw">Swahili</option><option value="sv">Swedish</option><option value="th">Thai</option><option value="tr">Turkish</option><option
    value="uk">Ukrainian</option><option value="ur">Urdu</option><option value="vi">Vietnamese</option><option value="cy">Welsh</option><option value="yi">Yiddish</option></select>⇄<select><option
    value="af">Afrikaans</option><option value="sq">Albanian</option><option value="ar">Arabic</option><option value="hy">Armenian</option><option value="az">Azerbaijani</option><option
    value="eu">Basque</option><option value="be">Belarusian</option><option value="bg">Bulgarian</option><option value="ca">Catalan</option><option value="zh-CN">Chinese
    (Simplified)</option><option value="zh-TW">Chinese (Traditional)</option><option value="hr">Croatian</option><option value="cs">Czech</option><option value="da">Danish</option><option
    value="nl">Dutch</option><option selected="selected" value="en">English</option><option value="et">Estonian</option><option value="tl">Filipino</option><option
    value="fi">Finnish</option><option value="fr">French</option><option value="gl">Galician</option><option value="ka">Georgian</option><option value="de">German</option><option
    value="el">Greek</option><option value="ht">Haitian Creole</option><option value="iw">Hebrew</option><option value="hi">Hindi</option><option value="hu">Hungarian</option><option
    value="is">Icelandic</option><option value="id">Indonesian</option><option value="ga">Irish</option><option value="it">Italian</option><option value="ja">Japanese</option><option
    value="ko">Korean</option><option value="la">Latin</option><option value="lv">Latvian</option><option value="lt">Lithuanian</option><option value="mk">Macedonian</option><option
    value="ms">Malay</option><option value="mt">Maltese</option><option value="no">Norwegian</option><option value="fa">Persian</option><option value="pl">Polish</option><option
    value="pt">Portuguese</option><option value="ro">Romanian</option><option value="ru">Russian</option><option value="sr">Serbian</option><option value="sk">Slovak</option><option
    value="sl">Slovenian</option><option value="es">Spanish</option><option value="sw">Swahili</option><option value="sv">Swedish</option><option value="th">Thai</option><option
    value="tr">Turkish</option><option value="uk">Ukrainian</option><option value="ur">Urdu</option><option value="vi">Vietnamese</option><option value="cy">Welsh</option><option
    value="yi">Yiddish</option></select>
    English (auto-detected) » English
    <textarea style="height:80px;width:444px;border:1px solid grey;padding:2px;"></textarea><select><option value="af">Afrikaans</option><option value="sq">Albanian</option><option value="ar">Arabic</option><option
    value="hy">Armenian</option><option value="az">Azerbaijani</option><option value="eu">Basque</option><option value="be">Belarusian</option><option value="bg">Bulgarian</option><option
    value="ca">Catalan</option><option value="zh-CN">Chinese (Simplified)</option><option value="zh-TW">Chinese (Traditional)</option><option value="hr">Croatian</option><option
    value="cs">Czech</option><option value="da">Danish</option><option selected="selected" value="auto">Detect language</option><option value="nl">Dutch</option><option
    value="en">English</option><option value="et">Estonian</option><option value="tl">Filipino</option><option value="fi">Finnish</option><option value="fr">French</option><option
    value="gl">Galician</option><option value="ka">Georgian</option><option value="de">German</option><option value="el">Greek</option><option value="ht">Haitian
    Creole</option><option value="iw">Hebrew</option><option value="hi">Hindi</option><option value="hu">Hungarian</option><option value="is">Icelandic</option><option
    value="id">Indonesian</option><option value="ga">Irish</option><option value="it">Italian</option><option value="ja">Japanese</option><option value="ko">Korean</option><option
    value="la">Latin</option><option value="lv">Latvian</option><option value="lt">Lithuanian</option><option value="mk">Macedonian</option><option value="ms">Malay</option><option
    value="mt">Maltese</option><option value="no">Norwegian</option><option value="fa">Persian</option><option value="pl">Polish</option><option value="pt">Portuguese</option><option
    value="ro">Romanian</option><option value="ru">Russian</option><option value="sr">Serbian</option><option value="sk">Slovak</option><option value="sl">Slovenian</option><option
    value="es">Spanish</option><option value="sw">Swahili</option><option value="sv">Swedish</option><option value="th">Thai</option><option value="tr">Turkish</option><option
    value="uk">Ukrainian</option><option value="ur">Urdu</option><option value="vi">Vietnamese</option><option value="cy">Welsh</option><option value="yi">Yiddish</option></select>⇄<select><option
    value="af">Afrikaans</option><option value="sq">Albanian</option><option value="ar">Arabic</option><option value="hy">Armenian</option><option value="az">Azerbaijani</option><option
    value="eu">Basque</option><option value="be">Belarusian</option><option value="bg">Bulgarian</option><option value="ca">Catalan</option><option value="zh-CN">Chinese
    (Simplified)</option><option value="zh-TW">Chinese (Traditional)</option><option value="hr">Croatian</option><option value="cs">Czech</option><option value="da">Danish</option><option
    value="nl">Dutch</option><option selected="selected" value="en">English</option><option value="et">Estonian</option><option value="tl">Filipino</option><option
    value="fi">Finnish</option><option value="fr">French</option><option value="gl">Galician</option><option value="ka">Georgian</option><option value="de">German</option><option
    value="el">Greek</option><option value="ht">Haitian Creole</option><option value="iw">Hebrew</option><option value="hi">Hindi</option><option value="hu">Hungarian</option><option
    value="is">Icelandic</option><option value="id">Indonesian</option><option value="ga">Irish</option><option value="it">Italian</option><option value="ja">Japanese</option><option
    value="ko">Korean</option><option value="la">Latin</option><option value="lv">Latvian</option><option value="lt">Lithuanian</option><option value="mk">Macedonian</option><option
    value="ms">Malay</option><option value="mt">Maltese</option><option value="no">Norwegian</option><option value="fa">Persian</option><option value="pl">Polish</option><option
    value="pt">Portuguese</option><option value="ro">Romanian</option><option value="ru">Russian</option><option value="sr">Serbian</option><option value="sk">Slovak</option><option
    value="sl">Slovenian</option><option value="es">Spanish</option><option value="sw">Swahili</option><option value="sv">Swedish</option><option value="th">Thai</option><option
    value="tr">Turkish</option><option value="uk">Ukrainian</option><option value="ur">Urdu</option><option value="vi">Vietnamese</option><option value="cy">Welsh</option><option
    value="yi">Yiddish</option></select>
    English (auto-detected) » English

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

  • 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

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

Maybe you are looking for

  • Crystal Reports - Change Line Chart Color Dynamically

    Hello, I have Crystal report 14. I'm trying to create a line chart and need to be able to set the colors of the lines at the time the report is run.   The colors the lines need to be are specified in a database and a different color could be specifie

  • Can't eject USB drive

    Hi, This is driving me crazy. Every time I used a USB drive, I am told that it can't be ejected because a program is using it. Sometimes it says the finder is using it (it shouldn't be: if the finder is using it it is only listing it as a drive). Rel

  • .Numbers" could not be opened

    After restarting my computer for some updates, this file no longer opens. are there any known ways to recover in these situations? except for from backups obviously. cheers all for any help.

  • Iphone hard drive to computer (click n drag) videos/photos

    I transferred videos/photos from iphone 5 hard drive into external hard drive using the folders that pop up when I plug my iphone into my PC (there was 2 folders in iphone) and it worked fine. I wanted to transfer some of those videos back into my ip

  • I had to deactivate PhotoShop for service on my computer.  How do I reactivate it?

    I had to deactivate PhotoShop for service on my computer.  How do I reactivate it?