pcarey

Member
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About pcarey

  • Rank
    Member
  1. Yes, the eSATA drive is connected to the MOBO's 6GB/s Marvell SATA controller header via an eSATA slot bracket adapter. The adapter and eSATA cable are all 6GB/s-rated. It seemed to be the simplest solution as I only need to acces this drive occasionally for some data that's on it. I suppose I could switch this e-SATA drive to the ICH10-R controller and let the Intel controller manage it as a non-member drive. Maybe that would make it happy. Looks like the immediate answer to the RST problem is to connect this drive via USB, rather than eSATA. RST doesn't get into a snit and quit working when the drive is connected via USB and I've heard the Marvell SATA controllers can be flakey. Fortunately, my Vantec eSATA drive enclosure will operate just fine on either eSATA or USB. After wading through Intel's web site, it looks like the latest RST version to support the X58 / ICH10R RAID Chipset is v.11.7.0.1013. I may update it.
  2. I have two Seagate ST1000NM0033 1TB SATA drives in a RAID 1 array on my MOBO’s Intel ICH10R RAID controller with Intel Rapid Storage Technology Manager v.8.9.0.1023. OS is Windows 7 SP1 x64. I also have an external Seagate ST3500418AS 500GB SATA drive in an eSATA enclosure connected to the MOBO’s separate Marvell 6GB/s controller on an eSATA port. This drive was the system boot drive in a RAID 1 array on the same MOBO before I installed the 1TB drives and transferred the system to the new 1TB drives. There is still some data on the old drive I would like to access occasionally, but whenever I bring the eSATA drive online, either at boot or after, the Intel RST Manager shows as not working. The only way to make the Intel RST Manager start working again is to take the eSATA drive offline and re-boot. I thought that maybe it was the fact that the old drive was still marked as active, so I used DiskPart to mark the drive as “Inactive”, since I couldn’t see any reason to boot from this drive again anyway. Made no difference. Also, Windows Explorer does not list the drives in the usual order. In my experience, when you have two HDD’s, each with one Primary and one Extended partition, Windows will list the Primary partitions of each drive first, with the Extended partitions listed next in order (e.g., first physical drive primary partition – C:, second physical drive primary partition – D:, first physical drive extended partition – E:, second physical drive extended partition – F: ). However, Windows Explorer is showing my eSATA old drive at the end of my drive letter list as L: & M: ( drive letters C: through K: were already assigned) in the actual partition order on that drive. In other words, the new L: used to be C: and the new M: used to be D: on the old drive. I like this drive letter assignment a LOT better than having Windows re-arrange all the existing drive letters when a new HDD is introduced into the system. It’s much less confusing. But it bothers me because I don’t think that’s the way the OS usually does it, plus the fact that RST stops running when the eSATA drive is brought online makes me think I have a conflict somewhere. Any ideas?
  3. I recently upgraded my two 500GB SATA RAID1 HDD’s to two new identical Seagate SATA 1TB drives on my Intel ICH10R RAID motherboard controller and, after copying the old boot drive to the new boot drive, I set up RAID1 in the same configuration as before with Intel Rapid Storage Technology v.10.6.0.1002 and let the controller rebuild the new 1TB mirror drive. However, in physically installing the new drives, I mistakenly connected the primary boot drive to SATA Port 1 and the mirror drive to SATA Port 0. For various reasons, I would like my primary boot drive on SATA Port 0 and the mirror drive on SATA Port 1. Can I just switch the SATA ports that these drives are connected to? How will the controller handle it? Is there any good reason not to do it?
  4. For those of you who have not been able to get into your LSI RAID controller (HBA) Configuration Utility at boot-up, maybe this will help. The problem may be peculiar to the LSI SAS 9211-8i HBA, my ASUS P6X58D Premium motherboard or to the Intel X58 chipset, but I’ve heard of this also being a problem on some ASRock motherboards, among others. To go into the LSI SAS 9211-8i HBA Configuration Utility (at least it works this way on my ASUS P6X58D Premium motherboard) – 1. On boot-up, press F8 (or whatever your system requires) for the Boot Menu Selection screen. It will not load immediately. 2. When the LSI HBA signs on and tells you to press <CTRL C> to get into the LSI Configuration Utility, do it. You will not go in to the Configuration Utility immediately. 3. When the Boot Menu Selection screen finally appears and, if you pressed <CTRL C> at the correct time when the LSI card signed on, the LSI HBA will be one of the available selections. 3a. If you did not press <CTRL C> at the right time during the LSI HBA sign-on, the LSI HBA will NOT be one of the available selections and you’ll have to re-boot and try it all over again. 4. Select the LSI HBA for BOOT and you will then go into the LSI Configuration Utility screen where you can define your RAID Array. Lots of luck there! One of the least intuitive interfaces I’ve ever seen. Just muddle through it and you’ll eventually get your RAID Array set up the way you want it. 5. I wish I could afford an Intel RAID controller!
  5. I installed an LSI 9211-8i HBA and two new Seagate 1TB SATA drives. The card is installed in a PCIe 8x slot in my ASUS P6x58D Premium MOBO. I installed the 9211-8i hardware drivers for Windows 7 Home Premium x64 and the LSI MegaRAID Storage Manager in Windows. Win7 Device Manager says everything is fine. It can see both drives and the 9211-8i HBA and Win7 will even perform disk operations on the drives, such as initialization, partitioning, etc. Other programs can also see the two new drives. The problem is that at boot-up, the HBA is recognized, the drives are initialized and shown, but when I hit <CTRL C> to get into the HBA BIOS to configure the RAID Array, it says that it's going into the Configuration Utility, but it just continues on to boot into windows. The LSI MegaRAID Storage Manager in Windows can only see the old 500GB boot drive, not either one of the new 1TB drives. In short, the HBA BIOS sees both drives, but won't go into the Configuration Utility and the LSI MegaRAID Storage Manager in Windows cannot see either new drive, just the old boot drive. HELP!
  6. I have a new spare bare drive on the shelf that’s identical to the two installed in my system (except maybe for the firmware). Rather than wait until I get two new SATA III drives, I’ll probably clone my current primary RAID drive to the spare drive using Acronis TrueImage, remove the original primary drive, put the cloned drive as the primary in the system and try installing the LSI 9211-8i per the article. I’ll let you know how (if) it works. It will probably be a week to ten days before I get the LSI 9211-8i. BTW, thanks a bunch for being patient with a RAID newbie and for not being a RAID snob. I know you could have argued that RAID1 is practically useless and that I can’t expect much of a performance increase in going from SATA II to SATA III and that I really need a RAID card with a GB of memory and a BBU. But I'm hoping to get just a little better performance out of the new SATA III ES.3 Enterprise drives if I get them on a 6Gb/s hardware controller, rather than the 3Gb/s ICH10R RAID controller built into my MOBO. And, if this LSI 9211-8i is at least as smart as the Adaptec AHA-2940 SCSI controllers I used years ago, they'll also increase overall system performance by relieving the CPU of virtually all of the drive I/O demands that software RAID puts on it. Add in the fact that the new drives will have a 128MB cache vs. the 32MB cache on my current drives and maybe I’ll think it was all worthwhile. Besides, these drives are 3-4 years old and, although they’ve been as reliable as a stone axe, who knows how much longer they’ll last? OK, enough rationalization, I confess I just feel the urge again to tinker with the system.
  7. I ran across this - My link The document is dated 2010, so not so old as to be irrelevant. The raid card they're using is an Adaptec RAID 1220SA SATA II controller in RAID1 mode. Not in the same class as the LSI 9211-8i I'll be using, but the basic operation should be similar. They don't mention the operating system they're using, but considering the date, probably Vista or Win7. What's your opinion?
  8. Thanks for the reply and for keeping directly on topic! As you've probably assumed by now, I'm a complete newbie when it comes to hardware RAID. If my MOBO supported SATA III RAID on the ICH10R, I'd happily continue with software RAID1 since my system is (for the first time) fast enough that I really don't see any difference in operation with RAID1 enabled. I've added my basic system specs as my signature for anyone's reference. It sometimes saves a lot of questions in replies when posting. I was not too concerned about installing the LSI drivers and getting the controller working, but was afraid that I would lose data when I defined the RAID array in LSI's storage manager and let the controller initialize the drives for RAID1. You've confirmed that. One thing I don't understand, though. Since the RAID drivers are usually installed during the OS installation, apparently the controller doesn't destroy the installed OS when defining the RAID array and initializing the drives for RAID1 after the OS installation - just any other existing data?
  9. Is it possible to change from a 3GB/s SATA II Intel ICH10R software RAID1 setup on my ASUS P6X58D Premium motherboard to a 6GB/s SATA III LSI SAS9211-8i hardware RAID controller with the same type of RAID1 setup in the same MOBO without losing any data? MY OS is Windows 7 Home Premium SP1 64-bit. The two drives in my current software RAID1 array are 500GB SATA II Seagate Barracudas and I'm thinking of buying a couple of 1TB SATA III Seagate Constellation ES.3 Enterprise drives to replace the Barracudas as they're 3-4 years old now, but re-installing everything on the new drives is something I absolutely DON'T want to do. I was successful a year or so ago in installing AHCI/RAID1 using the integrated Intel ICH10R controller on this system long after Windows 7 x64 was first installed in the non-RAID IDE mode without losing anything. I've heard people say that's not possible. Took me most of a day to iron everything out and I can't say it was fun, but it's been working fine ever since. I'm sure I've seen instructions recently in a RAID controller manual about how to install the card in an existing Windows installation, but of course I haven't been able to find it again. It was probably an LSI or Dell PERC manual (actually about the same thing). Has anyone had any success in preserving the data on a primary drive while going from software RAID1 to hardware RAID1? Any suggestions would be appreciated.
  10. pcarey

    Adaptec 29160 installation - HELP!

    It's been a long time since I've had two host adapters in a system, but as I recall it was a 2942 and a 1502. I believe the 1502 could be set to a different IRQ before installing it. If I'm not mistaken, the IRQ for the 2940U2W and the 29160 are both fixed at IRQ 10. If that's true, won't that be a problem in itself? Or will XP force one of the cards to another interrupt? I'm not sure I have any IRQ's available and a host adapter will probably not share very well.
  11. I recently installed an Adaptec 29160 host adapter in an Asus P3B-F motherboard to replace an Adaptec 2940U2W. On boot-up, everything seems to proceed normally except that the XP opening screen only flashes briefly and then the system reboots itself. This continues indefinitely until I power off. If I re-install the old 2940U2W the system boots up normally. I'm thinking that the XP installation back in December of 2001 might not have had the correct (or any) drivers for the 29160 at that time. I downloaded Adaptec's latest "Released Family Manager Set Service Pack 4 drivers for the Ultra 160 series cards for Win2000 and XP", however rather than being an install package, it just consists of three files with no instructions as to where to put them! Where is the exact proper location for ADPU160M.CAT, ADPU160M.INF and ADPU160M.SYS in an XP Home installation? Any other ideas on what the problem might be would certainly be appreciated. Or am I on the right track in thinking it's the XP driver for the 29160 that's causing the problem? System configuration is as follows: The 29160 is installed in an ASUS P3B-F Pentium III motherboard in a 32-bit PCI slot. According to the P3B-F manual, all six PCI slots are PCI 2.2 compliant The 29160 fits in the slot easily without using excessive force. There is adequate clearance for the overhanging rear end of the card and the unused connectors on the rear of the card do not touch any other components. The operating system is Windows XP Home with all updates, including SP1, installed. The previous host adapter was an Adaptec AHA-2940U2W. The only changes made were to install the 29160 in place of the 2940U2W (in the same slot) and replace the previous U2W LVD cable with the new Ultra160 LVD cable that came in the 29160 kit. Otherwise, all other cables, drives and settings remain the same as when the 2940U2W was installed. SCSI device setup is as follows: On the 29160 internal Ultra160 LVD connector – Adaptec Ultra160 LVD “twist ‘n flat” cable with a built-in terminator. IBM Ultrastar DPSS-309170 Ultra160 LVD hard drive – SCSI ID 0. This device is at the end of the cable furthest from the host adapter. Quantum Atlas IV 9WLS Ultra160 LVD hard drive – SCSI ID 1. This device is on the portion of the cable closest to the host adapter. On the 29160 68-pin internal Ultra-Wide connector - Adaptec 68-pin flat Ultra-Wide cable without a built-in terminator. Plextor PX-40TSUW Ultra-Wide SCSI CD-ROM – SCSI ID 2 – internal active termination set to ON. This device is at the end of cable furthest from the host adapter. Plextor PX-R820T FAST SCSI-2 CD-R – SCSI ID 3 - internal active termination set to OFF. This device is at the middle of the cable and is connected with a DataMate SP5000-568-13 wide-to-narrow adapter. Toshiba SD-M1401 ULTRA SCSI DVD-ROM – SCSI ID 4 - internal active termination set to OFF. This device is on the portion of the cable closest to the host adapter with the same DataMate wide-to-narrow adapter as above. On the 29160 internal 50-pin Ultra SCSI connector – Adaptec 50-pin cable to an external slot cover mounted Mini50 connector. There is normally nothing connected to this connector. It is only rarely used for connecting external SCSI devices, such as DAT tape drives. On the 29160 external Ultra160 LVD connector – No devices connected.
  12. I guess you guys have answered my question. Moving my Ultra160 drives from my 2940u2w to a 29160 on my ASUS P3B-F's 32-bit PCI 2.2 bus WILL get me SOME increase in my present tranfer rate. Maybe even as much as 50% to 60% more than it is now (whatever that really is). Notice that I avoided using any MB/sec. figures in the above statement as that seems to get everyone excited! :wink: I guess I'm really trying to justify the brand-new 29160 sealed retail package I just bought at what I thought was a great price ($150). Seems I can't resist a bargain and being actually able to get some (small) benefit from it right now makes it even better! Thanks again for all the help.
  13. I'm presently running a couple of Ultra/160 SCSI hard drives on an Adaptec AHA-2940U2W in a 32-bit PCI slot and, of course, I'm only getting 80 Mb/sec. performance out of them right now. From what I'm getting from Adaptec's web site, I wouldn't be able to reach 160 Mb/sec. with the 29160 unless it's in a 64-bit PCI bus, but that it might be possible to attain up to 132 Mb/sec. with the 29160 in a 32-bit PCI 2.2 slot, depending on the hardware setup. A 50% to 60% increase might be worth the expense with my current hardware until more motherboards provide one or more PCI-X slots. Does anyone have any real info or experience with this?