logical1

Member
  • Content Count

    128
  • Joined

  • Last visited

Posts posted by logical1


  1. Comments inline:

    Anyone with a Highpoint 2320 RAID5 array check in here. Here is the info I'm looking for:

    1) HD Tach Tests -

    --> Burst speed: 287mb/sec

    --> Access Time: 13.2ms

    --> CPU Usage: 4%

    --> Sustained transfer: 127.8mb/sec

    2) Read/Write Performance

    3) What disks you're using - WD3200KS

    4) Number of disks - 8

    5) Rebuilt time - 2 hours

    6) Comments and your overall opinion of the card

    Seems to work well for my usage in a server with GigE.

    Thanks


  2. It's kinda odd. I have an almost completely different setup but my transfer graphs from me RAID controller (Elite 1600) from my drive (Atlas 15K II) look nearly identical to yours. My setup is single Celeron 2.66Ghz CPU on a Asus P5RD1-V board with everything onboard and a single card in the system on the PCI bus (LSI MegaRAID Elite 1600). That only has a 3 end cable hooked up with one end to the card, one to the single drive configured as RAID0 and an active terminator at the end of the bus on the final connector. No matter what I have done, I cannot get a higher throughput than the same 37mb/sec or so that you show on your graphs and mine look the same. I'm interested in a solution too if you find one. Also, the drive hits 98/sec on my home system, but the controller, cable and terminator are all different.

    Aero, while your points are valid about PCI bus speed, that doesn't account for why he is only seeing 1/3 to 1/4 the possible speed of the bus with a set of drives that should easily hit 100mb/sec on the bus (I have a RAID0 of MAS 36's on a 21320-IS at home that can hit 96mb/sec sustained over the entire usable space on a max'd out PCI bus where every slot on the board is filled with various things from two different network cards to a secondary video card). Also, his controller may be old and have a slower processor, but how much processing does RAID 0 really require of your card onboard CPU? Yes, I have seen adapter problems cause such issues, but in my case, I have a 68-pin drive plugged into a 68-pin cable and still see an identical result. Also, the poster says that 5 out of the 6 drives use these convertors and if they are the problem, that would explain it for those drives, but not for all the drives.


  3. It's really going to depend on how much of that stuff you're doing at the same time since you'll see the biggest gains when running multiple different processes simultaneously. You'd get much better performance from the audio and video compression if your app supports multithreading, but office apps and the internet will see pretty much no improvement in speed.


  4. Yes, and he said it's a four drive chassis, so I'd think he'd be putting 1 reader and 3 writers in it rather than trying to jam 6 5.35" drives into a case designed for 4. Granted, Ultra SCSI would still be maxed out since it would be reading for 6mb off one drive and writing to 3 drives at 6mb each totalling 24mb/sec transfer which is just higher than the 20mb/sec available. Best bet would be to read from the reader to an image on a drive on another channel and then send to the 3 writers.


  5. I've seen reference information for some printers implying that the Windows Firewall in SP2 may be blocking access to the 127.0.0.1 address as well as the 127.0.0.0 subnet and that this can cause driver installation failure as well as the printer not to work. You may try setting an exception for the 127.0.0.0/255.0.0.0 subnet and seeing if the drivers will install and the printer will work.


  6. Right-click drive, Properties, Security, Owner, highlight the name of your user account, check the box to apply to subfolders, hit Apply, wait.

    After that finishes, try to access files. That should do it in any circumstance except where you have the files on an encrypted file system. If that's the case, reinstall the drive and copy them off to another drive or remove the encryption.


  7. Any wireless on the network? That can complicate your life infinitely more to try to find the box as it could even be outside the confines of your office. If it is all hard wired, then using some kind of port monitoring on each switch will help you isolate it. For the future, getting switches that support SNMP is very useful as you'll be able to monitor traffic via a web-based interface with graphs to see what ports are using how much bandwidth and at what intervals with MRTG or similar.


  8. My option is still viable since as long as there is no gateway on the XP machine from network A that is connecting to the other network, then it doesn't have internet access and unless you specifically set the gateway and turn on internet connection sharing or TCP/IP forwarding in XP, then the other computers will not have internet access. If you prefer to complicate matters more, just pick a random address besides 1 or 254 for the gateway address of the other network, so even someone guessing will have to go through a lot of tries before even being able to get the XP machine of network A on the internet. One other thing that would slow them down is to setup IE so that all internet addresses are in the Restricted sites zone and then put in a bogus proxy server address. That'll take someone some time to figure out.