Q.E.D.

Member
  • Content Count

    67
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Q.E.D.

  • Rank
    Member
  1. Q.E.D.

    Power Sata hdd ON/OFF while PC on.

    if you look at a sata hard drive connectors you will notice a few things. The length of the power connectors, versus the data connectors is different, the depth that they sit. I use 5 sata hard drives in a supermicro hot swap bay. And at anytime, i can pull out any one of those hard drives at will. (only one of the 5 due to raid5.) I have tried this and this does not ruin the drive. at least not my seagate 7200.7 The SATA controller does need to support hot swap connections. I use a raid controller that does support this. A Broadcom 4852. If your controller specs say it will support hot swap. Most likely you could be able to turn the power off. How ever you still may run into problems if the LOGIC of the sata connector is still connected. The controller might get confused due to seeing an unpowered device on the other end. Like mentioned before, you should only attempt this if the drive can be disabled via software also. Otherwise you may loose alot of data. Leaving the data connected, all while turning the power on or off to a drive may actually ruin the drive. You might havta do it in a certain order. Disconnect data cable. then power down. Power up, then reconnect data cable. The best thing to do is contact a tech from the hardware makers to see if what your doing is going to fry any thing. BUT, with the right equiptment, Raid controller, Hot swap bay, hot plugging drives with sata is just like hot plugging scsi to me.
  2. Q.E.D.

    Raidcore Problems

    well ya of coarse its the Seagate 200Gb SATA drives NOT 200Mb.. LOL
  3. Q.E.D.

    Raidcore Problems

    I have purchased 5 of the Seagate 200Mb SATA drives and the BC4852 less than 1 month ago. Its all set up and running in a RAID5. No hot spare. The 5 drives are in a supermicro 5 hot swap bay enclosure. I can rip any one of my 5 hard drives out at any time (without disabling it or anything to simulate a total drive failure) (except during a rebuild or integrity check naturally) And the system will not even hiccup. The rebuild then takes me around 6-8 hours. I get awesome speeds from this card, using my 66mhz 64bit slot in my dual board. I would reccommend that you purchase the BC4852 with the seagate hard drives. Rock solid preformace for me so far.
  4. Q.E.D.

    LSI MegaRAID SATA 300-8

    After speaking with LSI, this card won't be available untill Q1 of 2005. (if you call them they won't tell you, you havta put the pieces together) They "PAPER" released this in february2004 also, and here they are, at it again, 6 months before any idea of when it will be in stores. These press releases are nothing more than huff to try to get people pumped up for a product that won't see the light of day for ages more. Makes me mad. They have been "talking" about this card for so long. I was thinking about waiting for it, but obviously the fluff of the product and the fact that it is true vaporware currently, drove me to purchasing a Broadcom 4852. I love the broadcom, and don't regret the purchase at all. I am glad I didn't wait, becuase I am willing to bet that LSI is going to price the hell outta these cards in 05. Most likely they will be the most expensive cards out there for sata raid.
  5. Q.E.D.

    7200.7 Martians?

    I havent noticed any noise during idle of my 200gb seagate drives. I have 5 of them in a hot swap bay, and with 5 if they were "thrashing" at idle i am sure I would notice. But even when putting my ear to them, I hear nothing, cept if I were to access the drive, some minor clicking of the drive accessing. No different from any other drive that I have.
  6. Heh, after rebooting it worked however, it doesn't seem to display the speed properly. I guess the only way to test is it put a 33mhz pci card into the other 66mhz slot to force the raid card to 33mhz and then do some benchmarking to see if there is a difference.
  7. This program gives me an error on start up. No device detected. May be claimed by another appliation. But my other pc it works fine in.(the one with out the PCI64bit card of coarse) I dunno.
  8. Q.E.D.

    Delayed Write failed and slow performance

    a delay write failed is a result of the drive being disconnected from the system prematurely. I have it happen to me with my usb Secure digital card reader. It happens if I don't tell my system to eject the card, before I take it outta the card reader. Most likely , disconnect is the problem. I think SCSI devices have something to allow or dis allow disconnect in the SCSI controllers BIOS. Try changing your setting on this. Other than that, I don't know. But this is definetly a result of the drive disconnecting its self from the system. If your LSI controller is a PCI device. I would suggest physically moving the device to another PCI slot. some system devices don't like to share IRQs with other certain devices. And most motherboards share IRQ's based on what PCI slot your device is in. (you can see IRQ sharing at boot. the black and white table listing all your devices. It will show: Mass storage controller. (2 of them, one scsi, and one ide) most likely these devices are using the same IRQ number as other devices in the list. Theres no way to get around this, except moving the PCI card to another PCI slot. Sometimes, it helps, sometimes not. But there is no way to get around IRQ sharing. You can only manage which devices share with eachother to a limited degree by PCI position.
  9. Are you reading this from the BIOS boot up table? Or from windows IRQ list? The windows IRQ list retoutes the IRQ's. Ignore windows. Read the IRQ values from the BIOS table. If you did then never mind. I say this because in my BIOS IRQ table, there are many devices that share the same IRQ. But when looking in windows, those IRQ's have changed to fake like they are not sharing anymore. Most likely this is an attempt by Microsoft to get around IRQ sharing, by faking programs into thinking that the devices have different IRQ's. I think this works because the devices trade off when sharing an IRQ. They take turns when getting data thru the IRQ. (im guessing that icreasing the PCI latency, allows the device to hold onto the IRQ for longer, before sharing it with its partner(s)
  10. Are you reading this from the BIOS boot up table? Or from windows IRQ list? The windows IRQ list retoutes the IRQ's. Ignore windows. Read the IRQ values from the BIOS table. If you did then never mind.
  11. I just recently ran into problems with my onboard IDE controller and my sound card. I moved my sound card to a PCI slot that shared the IRQ with my IDE controller. The result was ugly, my CDROM transfers were really slow, and If I tried to play music while transfering comething from the CDROM the music would skip, chop or totaly stop untill the transfer was done. I suggest you try moving your PCI devices around. Also, I noticed a improvement when changing something called. PCI Latency in my BIOS. It was 32, and after I increaed it to 64 My speeds between many of my devices became faster. (cdrom transfers, Ethernet file transfers ETC. Just throwing some ideas your way.
  12. I am trying to determine if my 64-bit-66mhz raid controller is running at 64-bit/66mhz speeds like it should in my 64-bit/66mhz slot. How can I see this, my bios dosen't tell me. Is there any software?
  13. Q.E.D.

    Newegg, Send Me My Drives!

    P.S. and they delivered it to me on saturday..(of coarse its more expensive) but they still WOULD do it. it makes me mad when companys just str8 out refuse saturday delivery option. yeah, most people don't need it, but sometimes hardware dies right before the weekend, and you need to replace it.
  14. Q.E.D.

    Newegg, Send Me My Drives!

    yeah I heard about that. Well, now I know, and check THIS out. www.memorylabs.com shipped my hard drives like this! TALK about AWESOME!
  15. where is your sound card in relation to your video card. are they right next to eachother? Also, are all your sound card drivers updated? I had hard lockups with an old version of my sbaudigy2 platinum driver, ONLY when I installed a raid controller. never had that problem before the raid. Just shows how picky sound card drivers are. make sure your chipset drivers are also up to date. if you have an intel chipset...(intel chipset installer) look at your list of devices at boot. you should see a list of installed hardware, each showing the IRQ assignments. If your video card, sound card, or STORAGE CONTROLLER is sharing an IRQ with any other then your problem might be that. When I had a PCI card installed into the slot right next to my RAID controller, I ran into huge problems. the raid would not format a drive, a simple action, but otherwise looked like it was working. its possible that your system works in non-game environments, but when the 3 (hard drive, video card, sound card) are all used in the same setting, you run into problems. If your devices are sharing IRQ's that most likely is your problem. Also, a simple OS reinstall helps too.(if your at your ropes end)