SATA / PATA Drive Detection Issues

I have my SATA hard disk on the primary (0) SATA channel and my DVD-RW on the primary PATA channel. This has worked fine since I've had this set up, but I've recently run into some trouble with it.
I hooked up a PATA hard drive in place of the DVD-RW to pull some data off it. When I tried to boot, it only detected the new drive and couldn't boot from it (Win 2000 blue screen). It didn't even see the original hard drive.
I messed around with the various modes under "On-chip IDE Configuration" and no matter what I do I cannot get it to detect 2 devices at once. There doesn't seem to be any consistency to the results it produces.
I have updated to the latest BIOS (2.2).
Firstly, why can you select SATA / PATA Only, and then keep the other enabled? What is the best setting for my two drives? I originally had it set to PATA Only and keep SATA enabled I think (on advice from people on this board).
If i'm not using RAID, I can disable "Onboard Promise IDE" right?
All help greatly appreciated.
Many thanks in advance.

The most likely reasons for the SATA to not be detected in the Standard Cmos in the order I would check them:
1. Data and power cables firmly connected(remove and re-attach to be sure).
2. Bios>>Integrated Peripherals>>On Chip IDE Config:
    - SATA Keep enabled-Yes
    - Configured as Raid- NO (Yes removes it from the Standard CMOS Features)
3. Drive no good
Make sure you have other IDE HDD's removed till you get this working again.
And yes, if you have nothing attached to Serial3&4, IDE3 you can set the Promise controller to Disabled.
Edit:
Oops, I didn't see the last post. Glad you got it!

Similar Messages

  • Boot drive detection issue [solved]

    Hi,
    I upgraded my Arch install yesterday (pacman -Syu). The last one was four weeks ago. Among the packages updated were the stock kernel 2.6.17 and mkinitcpio, so the update generated another image /boot/kernel26.img.
    Now I am having random errors while booting. One out of two (yes, 50%) boots ends with kernel panic while identifying the root fs type after initramfs and modules have been loaded. Something like "Can't find device dev(0,0)".
    The apparent reason is that sometimes the boot partition is identified as hda2, sometimes as hde2. Because I have the kernel option root=/dev/hda2, boot is successful when boot partition is identified as hda2, and fails with the above message when it is identified as hde2.
    My particular hardware is a Abit Be-6 motherboard (quite old) which has two ide ports and two other ide ports controlled by a Highpoint HPT366 controller (which support DMA 66). My HD is connected to one of those.
    I suspect that the drive detection relies on some kind of information sent by the bios and that this information is sometimes sorted in one order, sometimes in another one, i.e. sometimes the ide ports first, sometimes the hpt366 ports first.
    For information, the install cd-rom would see my drive as hde (always, not 50%) and until yesterday, the boot process would see it as hda (again, always, not 50%).
    So now the questions for you, talented forum participants, are:
    1/ I would like to understand how disk and partition letters/numbers are allocated: why hde2 and not hda2? Can I force the naming to hda2, whatever the Bios says (for example based on a HD ID or a IDE port ID)?
    2/ I read the mkinitcpio wiki. From what I understand, I can configure what modules will be loaded at boot time for detecting my boot drive, either at image generation time, or at boot time with a kernel parameter. Would blacklisting ide modules and leave only hpt366 module help? Conversely, assuming I plug my HD in an IDE port, would blacklisting hpt366 module help?
    Help will be much appreciated.

    Michel F wrote:The only thing is that I guess I have now to include /etc/mkinitcpio.conf in the NoUpgrade list in pacman.conf to avoid surprises when it upgrades.
    The /etc/mkinitcpio.conf file is marked as "backup" in the mkinitcpio package. Therefore, if the default configuration changes, it will be extracted as /etc/mkinitcpio.conf.pacnew and your own configuration won't be touched.

  • USB/mount drive detection issue (using AIR 2)

    I'm creating a drive mount listener in Flash Builder.  For the most part, it works well.  Lately, I have had a problem actually getting the event of a drive being mounted.
        var s:StorageVolumeInfo=StorageVolumeInfo.storageVolumeInfo;
         s.addEventListener(StorageVolumeChangeEvent.STORAGE_VOLUME_MOUNT,USBM ounted);
    Then the handling method:
        private function USBMounted(e:StorageVolumeChangeEvent):void
            Alert.show("Drive Unmounted");
            printDirectory(e.rootDirectory);
    My two questions:
    - Has anyone ever used this method to read all drives being mounted (CD, SD card, etc)?
    - Is there any way to get this to work using a USB hub?
    Thanks

    > You can write on "usb" because the right are : drwxrwxrwx
    They appear only when I use 'sudo mount -o rw,noauto,async,user,umask=1000' instead of plain 'sudo mount /dev/sdb1 /mnt/usb2'.
    I use vfat for that USB stick, so maybe that's why it works for me. The first two listings in your first post show the drives in different order, but of course the mountpoints show that the offending drive is ext2 not vfat, my bad.
    Edit: This is how my ext3 USB stick behaves like:
    [karol@black test]$ sudo mount /dev/sdb1 /mnt/usb
    [karol@black test]$ mount | grep sdb1
    /dev/sdb1 on /mnt/usb type ext3 (rw)
    [karol@black test]$ ls -l /mnt
    total 8
    drwxr-xr-x 2 karol users 4096 07-03 01:08 usb
    drwxr-xr-x 2 root root 4096 2009-09-14 usb2
    This time /mnt/usb is an ext3. As you can see, there's no root, I (karol) an the owner, so I can rw to my heart's content. Maybe you should change the ownership - 'chown' (man chown if you're not familiar w/ that command).
    Last edited by karol (2010-07-02 23:05:52)

  • USB Drive detection issues

    Hello,
    I have been using a 16 GB Sandisk Cruzer Fit thumbdrive for the past year.  I tried to access it this morning and it has no files on it.  I checked properties and it says 0 out of 0 GB available.  I tried the drive in another computer with success.  I am able to access a 1 GB thumbdrive on this computer...What's the problem?  What other information do I need to supply?

    I also can't perform a system restore. Any suggestions?

  • Internal sata hard drives detected as removable?

    why?

    Yes, I installed that driver. It would be nice to know if it's necessary. You can always hide the icon but I use removable flash drives and when I do, I like the icon there. So I can't hide it but maybe you can.

  • Slow auto-detect times for PATA drive

    Problem:
    Very long auto-detect times for the PATA drive.  During boot up, the system pauses at "auto-detecting" for this drive, for about 30 seconds.  This is by far the longest period in my entire boot process.  Occassionally the drive is not found at all, and I cannot boot.  When I go into the BIOS, it's identified correctly.  This is my OS/apps drive (the SATA drive is solely for audio and video).  Any ideas?  Also, is there a way I can get my system running in Native mode without losing the DVD drive?
    My system:
    865PE NEO2-FISR
    1x160GB WD PATA drive, IDE 1, last spot on cable, jumpered as master
    1x120GB WD SATA drive, SATA 1, jumpered as factory
    1xOptoRite DVD-RW, IDE2, last spot on cable, jumpered as master
    BIOS Setup:
    Legacy/PATA+SATA (I tried both Native settings--SATA only/Keep PATA enabled, PATA only/Keep SATA enabled, but the system could not see my DVD-RW drive in either setting).

    BIOS 1.7.  I'm going to take the jumper off, thanks for that information.  Should I set my DVDRW to cable select?  
    I also see that the beta BIOS fixes some problems with similar HDD issues, so I guess I'll try that if it isn't fixed by the jumper.

  • Problem when booting from PATA drive on IDE-3 with SATA RAID on ICH5R

    Hello,
    I have a PATA drive installed as Master on IDE-3 (Promise Controller), using Windows XP as the operating system. I also have an aditional drive as Slave on IDE-3.
    I recently bought 2 SATA drives which I would like to use as a RAID array, so I connected them to SER-1 and SER-2, on the ICH5R controller.
    I set the On-Chip IDE Configuration as follows:
    Native Mode
    SATA Only
    Keep PATA Active - Yes
    PATA Channel selection - Both
    Configure SATA as Raid - Yes
    I have my PATA Master IDE-3 drive as the firts boot device...unfortunatly now my system does not boot up.
    It goes through the Intel Raid Bios screen, then the Promise Controller screen, and then when it was supposed to start loading windows, the screen remains black for about 2 minutes and after it I receive an error message warning me that Windows has detected a hardware configuration problem.
    I went back to BIOS and changed the "Configure SATA as Raid" to NO, and now everything works fine, except for the fact that I have no RAID array installed.
    Can anyone help me with this?
    Thanks,
    Mihalis

    The PATA IDE channel associated with the Promise controller is exclusively designed to be used as a RAID solution. It seems you have an invalid hardware installation of your 2 EIDE drives. Although you succesfully installed WinXP using that configuration, you're destined to have unpredictable behavior because of it.
    WinXP looks to the BIOS first to identify hard drives. Then it does something that no other OS has done before (except maybe Win2K), it attempts to detect the hard drive directly through the wires itself. If it finds something, it installs resources to get it to work right. In your case, WinXP has bypassed the BIOS and detected the drives but doesn't really know where they are. WinXP just knows they are there so it supplied the necessary resources to complete the installation.
    That drives that are connected to the Promise controller must use the Promise RAID drivers supplied with your motherboard so that the Promise controller can properly report to the OS. You could have conected the same two drives on the same controller, but they needed to be configured as RAID drives within the Promise controller utility.
    To have them recognized as separate drives, you need to define each drive as a stripe, except you would have a 1 + 0 stripe instead of a 1 + 1 stripe. The drives are still connected the same way (Master/Slave) as you have them now. This congiguration would allow you to take advantage of the Ultra ATA 133 feature of that channel as long as you attached hard drives which support that standard.
    Finally, you would set the "Onboard Promise IDE" menu as "RAID" to have the drives properly recognized through the BIOS. Currently, you have that set as "S-ATA" but you have no S-ATA drives installed on that controller.
    I realize this does not resolve your original problem, but at this point, I would recommend that you back-up data at your earliest convenience and start over.
    If you do decide to start over, you may want to consider attaching your S-ATA drives to the promise controller instead of on the Intel controller. Aside from getting better performance, it makes for a much simpler install through the Promise controller utility and then everything is manageable through the PAM utility at the desktop.

  • Can you have SATA and PATA drives at the same time?

    Right now I have 2 PATA drives hooked up to the board. Is it possible to hook up a SATA drive that will be a non-boot drive for just storage purposes?

    You can havepata disks + Sata, with sata as boot or not, you just need to update the Hard disk boot order in advanced bios settings.
    luck

  • 6560b notebook - no sata-III ssd drives detected - hardware problem - HP employee needed

    hello,
    I'm one of the authors of this thread about the problem statet in the title.
    As the current forum thread might be slightly misplaced under 'Notebooks>Updates', I opened this thread here to get contact to one of the experts from HP.
    We need technical support. We have tried every possible solution to fix this problem.
    As several owners of the 6560b have experienced, sata-III SSD drives don't work in any of the two internal drive slots of the 6560b.
    Most recent firmware updates on ssd / notebook are installed. The SSD drives work fine in other computers. The problem is reproducable. The drives are not correctly recognized on BIOS level at boot.
    There is no known 6560b notebook running an internal sata-III drive.
    Some of the drives that are reproducably failed to be recognized:
    Kingston HyperX 120GB - Sata-III
    Corsair Force3 120GB - Sata-III  
    Corsair Force GT 120GB - Sata-III
    Intel 510 - Sata-III
    OCZ Vertex 3 - Sata-III
    OCZ Agility 3 - Sata-III
    Sata-III drives appear to work and are bootable* via the external esata connection.
    (verified by one user)
    This, however, is no usuable workaround.
    A short summary of the impact of this bug:
    -it appears to affect every notebook
    -the problem is not limited to SSDs with sandforce chips, one manufacturer, one drive size or one bios version of the 6560b.
    Just to repeat this: the chipset as well as the sata-chipset are from Intel. Yet modern Intel drives (510 series) fail to be recognized. Therefore, this problem cannot be 'simple' chipset incompatibilties either, as Intel would not ship SSDs that have incompatibilities with their <6mo. old chipsets.
    The problem does not directly relate to the hardware failures of sata-II ports known as 'intel-sata-bug' as the affected models include newer mainboards of revised steppings.

    I have the same problem on my 6560b notebook. A brand new Kingston HyperX 240GB - Sata-III is unable to boot. Drive is not seen/detected at boot time by BIOS. BIOS is latest available (F.50). Chipset is Sandy Bridge HM65.
    UEFI has been enable. I have to degrade manually, in BIOS settings, SATA3 (6Gbps) to SATA2 (3Gbps) for the drive to be usable. But perfs are not here for that kind of drive, so I'm very upset about that.
    Any BIOS fix appreciated.

  • SATA/IDE channel configuration issues

    Ok here's the setup:
    First SATA Channel: Seagate 7200RPM 80GB HDD
    Primary IDE Channel: LG 52x CD-ROM Drive
    Secondary IDE Channel: Western Digital 7200RPM 160GB HDD
    OS: Windows XP SP1
    Mobo: MSI 865PE Neo2-P MS-6728 Version 2
    The bios can detect all drives.
    If I use the recommended On-chip IDE Configuration mode as mentioned on page 3-23 in the manual, Windows XP loads and then goes through the process of detecting the Primary and Secondary IDE channel.
    After detecting it reports that Windows reports that the "Driver is not intended for this platform".
    If you look under Administrative Tools in Control Panel is refuses to detect the PATA drive as well.
    I tried swapping the PATA and the CD drives around but the above applied.
    If I try the following drive configuration and set the bios ATA Configuration to PATA & SATA then all drives are detected in Windows:
    First SATA Channel: Seagate 7200RPM 80GB HDD
    Primary IDE Channel Master: LG 52x CD-ROM Drive
    Primary IDE Channel Slave: Western Digital 7200RPM 160GB HDD
    So what's up? I've tried tinkering around with Legacy/Native, PATA/SATA Only etc and I've run out of ideas.

    I got similiar problem as b52 when I plugin an old P-ATA deathstar drive as master on first primary IDE and a LITE-ON dvd-rom as master on secondary. When I enter Windows the hardware auto wiz starts working and after a little while reports that two devices of type "IDE channel" have "Driver is not intended for this platform". I currently use the settings Danny recommends above. Weird thing is both the deathstar and the LITE-ON drive seem to work great. Of course I want to get rid of the exclamation marks in my device manager though. I read elsewhere drive emulation software could be a culprit, and renaming/deleting atapi.sys could be a problem solver - but not for me it turned out. Anyone got other methods to try out?
    Elsewhere:
    http://www.hardforum.com/showthread.php?s=545275f1f62ce2dd760878210076e500&t=860407

  • Installing a second SATA hard drive - Problems booting

    Hi,
    I currently have one Maxtor 160GB SATA hard drive in my system with my operating system installed. I have another identical hard drive that I'm attempting to install now, into the second of five available SATA ports on my MSI P965 Neo motherboard.
    When I plug in the second hard drive, though, Windows will not boot. It gets to the Windows logo screen with the progress animation, but before even the animation can begin, it stops and the screen freezes. This does not fix itself with waiting.
    My boot priorities are set to: DVD-ROM, CD-RW, hard risk. The hard disk priorities are also as they should be to my knowledge - although it can be tricky because when ordering, both disks have the same name. I have tried with either one on top of the list, and you cannot remove a drive from the list alltogether.
    The SATA cable is in perfect condition. My BIOS is up-to-date.
    When I plug the hard drive in when the system is already running, Windows will detect it and files can be written/read flawlessly. As soon as I restart, however, I run into the same issue.
    The first HDD, with the OS on it, is in SATA 1, the second HDD is in SATA 4. Ports 3, 6, and 7 are unused.
    I'm out of ideas at this point, I don't see any other options that need to be changed.
    I'd appreciate any input you can offer - thanks in advance!

    I would debug this drive you are talking about which clears off all data and partitions information. Take out the good drive and leave in the dodgy one. Boot to a floppy with this dell win95 boot disc.
    http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R19775&formatcnt=1&libid=0&fileid=19601
    When at the A: prompt: type debug and enter, you get a (-) prompt and then enter the following script exactly:
    F 200 L1000 0 (enter)
    A CS:100       (enter)
    xxxx:0100 MOV AX,301  (enter)
    xxxx:0103 MOV BX,200  (enter)
    xxxx:0106 MOV CX,1     (enter)
    xxxx:0109 MOV DX,80   (enter)
    xxx:010C INT 13    (enter)
    xxxx:010E INT 20   (enter)
    xxxx:0110             (enter)
    g                        (enter)
    q                         (enter)
    restart your system.
    Now you can put back in your first drive as well, boot up into windows and use the disc manager to repartition and format.
    Old school! If you are still having problems I would replace the drive.

  • MD3000 Drive detected errors is increasing

    Hi,
    we are using md3000 with sas connection.
    since some days, we are facing big performance issues.
    the system is running with 15 drives:
          TRAY, SLOT  STATUS   CAPACITY    TYPE  CURRENT DATA RATE  PRODUCT ID                                FIRMWARE VERSION
          0, 1        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 2        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 3        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 4        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 5        Failed   931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 6        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 7        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 8        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 9        Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 10       Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 11       Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 12       Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 13       Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 14       Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
          0, 15       Optimal  931.513 GB  SATA  3 Gbps             Hitachi HUA722010CLA330                   JP4OA3JH
    here the information on disk 5:
    Drive at Enclosure 0, Slot 5
       Status:                  Failed
       Mode:                    Assigned
       Raw capacity:            931.513 GB
       Usable capacity:         931.013 GB
       World-wide identifier:   50:00:cc:a3:9a:c7:9f:50:00:00:00:00:00:00:00:00
       Associated array:        md3000g0
       Drive path redundancy:  Lost
       Drive type:             Serial ATA (SATA)
       Speed:                  7,200 RPM
       Current data rate:      3 Gbps
       Product ID:             Hitachi HUA722010CLA330
       Package version:        JP4OA3JH
       Firmware version:       JP4OA3JH
       Serial number:          JPW9P0N00JSU2D
       Vendor:                 Not Available
       Date of manufacture:    Not Available
    it is already replaced by hotspare disk 13 and the array is in optimal status.
    but the error counter is still increasing:
    DRIVE CHANNELS----------------------------
       SUMMARY
          CHANNEL  PORT       STATUS   
          1        Expansion  Optimal  
          2        Expansion  Optimal  
       DETAILS
          DRIVE CHANNEL 1
             Port: Expansion
                Status: Optimal
                Max. Rate: 3 Gbps
                Current Rate: 3 Gbps
                Rate Control: Switched
                DRIVE COUNTS
                   Total # of attached drives: 15
                   Connected to: A
                      Attached drives: 15
                         Drive enclosure: 0 (15 drives)
                CUMULATIVE ERROR COUNTS
                   Controller A
                      Baseline time set:               4/2/15 9:15:42 AM  
                      Sample period (days, hh:mm:ss):  33 days, 03:07:36  
                      Controller detected errors:      9                  
                      Drive detected errors:           3640802            
                      Timeout errors:                  0                  
                      Total I/O count:                 31288381           
                   Controller B
                      Baseline time set:               4/2/15 9:15:42 AM  
                      Sample period (days, hh:mm:ss):  33 days, 03:01:02  
                      Controller detected errors:      8                  
                      Drive detected errors:           3512795            
                      Timeout errors:                  0                  
                      Total I/O count:                 754965630          
             DRIVE CHANNEL 2
                Port: Expansion
                   Status: Optimal
                   Max. Rate: 3 Gbps
                   Current Rate: 3 Gbps
                   Rate Control: Switched
                   DRIVE COUNTS
                      Total # of attached drives: 15
                      Connected to: B
                         Attached drives: 15
                            Drive enclosure: 0 (15 drives)
                   CUMULATIVE ERROR COUNTS
                      Controller A
                         Baseline time set:               4/2/15 9:15:42 AM  
                         Sample period (days, hh:mm:ss):  33 days, 03:07:36  
                         Controller detected errors:      0                  
                         Drive detected errors:           0                  
                         Timeout errors:                  0                  
                         Total I/O count:                 5708758            
                      Controller B
                         Baseline time set:               4/2/15 9:15:42 AM  
                         Sample period (days, hh:mm:ss):  33 days, 03:01:02  
                         Controller detected errors:      0                  
                         Drive detected errors:           0                  
                         Timeout errors:                  0                  
                         Total I/O count:                 247629779          
    do i have to "unassign" the disk 5 or how to find out, where these "Drive detected errors" come from?
    thanks.
    patrick

    Somya, check your parameters:
    1 * Last added file name (lastfile) ....... [I:\ORACLE\SMD\SAPDATA2\SR3_11\SR3.
    DATA11]
    2 * Last added file size in MB (lastsize) . [<b>420</b>]
    3 - New file to be added (file) ........... [I:\oracle\SMD\sapdata2\sr3_12\sr3.
    data12]
    4 # Raw disk / link target (rawlink) ...... []
    5 - Size of the new file in MB (size) ..... [420]
    6 - File autoextend mode (autoextend) ..... [yes]
    7 - Maximum file size in MB (maxsize) ..... [<b>10000]</b>
    8 - File increment size in MB (incrsize) .. [<b>20</b>]
    option 2: your datafile will use 420MB to begin with.
    option 7: it can grow up to 10000MB
    option 8: it will grow with increments of 20MB
    so, you need at least 10GB in your filesystem.
    your warnings are saying that datafiles of 3 tablespaces, if they grow to their maximum file size, will overflow your filesystem (PSAPSR3,PSAPSR3700,PSAPSR3DB).
    solutions:
    1. increase filesystem size
    2. decrease value of maximum size of datafiles, I would especially check the maximum size of ALL datafiles of PSAPSR3.
    3. move some datafiles on another filesystem.
    good luck.

  • Sometimes cannot start PC: problem with Hitachi SATA Hard drive and K7N2G-ILSR

    I have major problem with my 160Gb SATA Hitachi hard drive and my MSI K7N2G-ILSR motherboard.  Sometimes the PC can be started, sometimes it cannot.
    After I installed a clean build of Windows XP Pro SP1 onto my new hard drive (as the only hard drive in my PC) and install all the necessary drivers, the system runs smoothly.  However, after about 2 to 3 weeks, sometimes when I start the PC, it cannot detect the hard drive and hence it claimes that it cannot find any VMI Pool Data (i.e. no OS detected).  What makes it really horrible is that, it is like the lottery everytime when I start the PC.  Sometimes it works, sometimes it doesn't.  The highest record was 8 consecutive failures (by resetting or by turning the power off and on again) before I can start the machine properly.  Also, the system sometimes just crashes in the middle of operating.
    I have already sent the hard drive back to Hitachi.  Got the same model of hard drive back as replacement, but the replacement has the same problem, except with the replacement drive the PC can be started eventually after many tries, while with the previous drive it is possible that the PC cannot be started until after a few days later.
    Also, it seems that my drive can detect either SATA hard drive or PATA hard drive, but not both.  (If I leave my old PATA drive connect in the primary IDE channel, Windows cannot detect the new SATA drive.)
    Is my motherboard faulty?  Can it only use PATA drive?
    My PC's spec is as follows:
    AMD Athlon XP 2500+
    512Mb PC3200 SDRAM (set to run at 166MHz)
    Hitachi 160Gb SATA Hard drive on 1st SATA channel (Model #HDS722516VLSA80)
    Sony DVD+-RW drive and Panasonic DVD-ROM drive on secondary IDE channel
    Use onboard video (GeForce MX)
    US Robotech V92 internal PCI modem
    SoundBlaster Audigy 2 Player soundcard
    Onboard audio disabled
    300W PSU
    OS is Windows XP Pro SP1 (with all latest security patches up to date)

    Quote
    Originally posted by Raven_
    Quote
    Originally posted by boucher91
    Along the same lines the sata drives use more power than the pata drives...
    sata usually faster spin rate, pata is slower spin rate...
    that is not entirly correct.
    many harddrives just come with different ways to connect them.
    the only sata drives i now that spins faster is western digital raptors 10k rpm.
    all other is running at 7200rpm.
    older drives run at 5400rpm
    Yes to get the full benefit of RAID, the Raptors are the way to go.Anything else, no significant difference.

  • SATA Hard Drives

    Hi all, just about to build my first AMD 64 PC wtih SATA and i need help!
    Have some questions  
    1. How easy is it to have a bootable SATA drive, I'm using a Maxtor DiamondMax 10 200GB. Any tips about installing this would be of help!
    2. The MSI K8N Neo mainboard supports SATA 1 but the hard drive says it is a SATA 2, well interface wise, but it doesn't have a 3GB per sec speed only 1.5GB-I'm confused at this?????????????
    Will this SATA hard drive work?
    many thanks

    DM 10 may be an issue with the newer interface & the bigger cache but DM 9s are perfectly fine.
    A bootable SATA drive should be as easy as a bootable PATA drive. I have dual-boot 30-bit & 64-bit OS from the same (SATA) raid array, both set up without any issue. When I get time I'll add Mandrake 10.1 64-bit & tripple boot.
    [edit] whoops! The muli-boot A64 box is running the raid with Raptors. But I do have a bootable array (stripe) using SATA DM 9s on my KT6 Ultra - and I set that up even though at the time the VIA VT8237 controller was decidedly dodgy. In fact I kept getting disc errors for ages and was on the point of losing faith in the Maxtors when VIA finally brought out a decent raid BIOS & drivers and fixed the issue, thus revealing that the Maxtors were perfectly fine all along.
    All too easy to blame the wrong thing...

  • Hard Drive detects imminent failure

    Please can anyone help. i have a compaq 6735s lap top which is about  months ols. Today when i switch on I have a black screen with the following message: 1720-SMART hard drive detects imminent failure.
    What should i do now

    Hi,
    How many months?
    The error message might or might not be true. It is worth your time to go ahead and back up all of your data to an external hard disk
    Boot into Windows and go to Device manager look at the disk drive device click on the + to expand the category and post the model number (the complete alphanumeric string next to the icon)  here in your thread. There is a possibility that your hard drive requires a firmware update. I will do a bit of research to see if that is indeed the issue.
    There are some Maxtor drives that have had to have the update done to correct the SMART reporting feature which caused an error message virtually identical to the one you are getting.
    regards,
    erico.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

Maybe you are looking for