Jump to content
Covecube Inc.

dsteinschneider

Members
  • Content Count

    27
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by dsteinschneider

  1. When I started with my single Probox connected to a Rosewill SiL 3132 card everything worked great. Then I bought a second Probox and couldn't get it to work reliably with the second eSATA port. Mediasonic recommended the Asmedia 106x and that has been working rock solid with the pair of Proboxes for 5 years. I did have one misadventure when I decided to try Windows 10 in 2017. Everything installed nicely and appeared to work but I had two major problems in subsequent operation - drives were disappearing and network connectivity was intermittently slow. I simply popped the Windows 7 SSD I put
  2. I suspect it might be some issue with MBR or the OS. Will try MBR fix and make sure drivers and BIOS are up to date
  3. Found this posted by Christopher (Drashna) in 2017: Deactivate licenses, disconnect drives, install OS, install software, activate licenses, reconnect pool.
  4. Two years ago I tried running DrivePool on Windows 10. Everything seemed ok during the install but I had problems where Windows 7 mediacenter computers had problems opening the movie files. I wasn't sure if the problem was caused by the pair of MediaSonic ProBoxes connected with the Asmedia 106x SATA controller or ethernet driver issues. I just put the Windows 7 OS SSD I put aside back in and continued until now with Win7. I've now upgraded all the mediacenter computers to Windows 10 with Chameleon Media Center. Does anyone have a Drive Pool machine with a pair of ProBoxes/Asmedia 10
  5. I've got a Dell Vostro 420 running fine as storage for our media computers. Movies load right up and all is well except that sometimes to restart the computer I have to press F12 and manually choose the boot drive which is a 4 year old Kingston SSD Now V300 120GB. Scanner reports no issues with the drive. I took it out and scanned it for viruses with several scanners. I used Kingston's drive software which reported it healthy. I cloned the drive and the clone, an out of the box Evo 860 behaved exactly the same way. So I guess it's something corrupt in the Windows 7 OS. I mentioning
  6. I used Veeam endpoint protection to restore the Win7 image. The motherboard broadcom 57XX gigabit ethernet on the motherboard would only run at 10MB for some reason on Win10. The AsMedia based SIL3132 driver was wonky. File transfers took a minute before the file would start to copy. One of the rare times the Windows 10 upgrade was horrible. Nothing but DrivePool and Scanner run on the machine so I'm going to stick with W7 until I hear about a solid Win10 compatible mutliplex capable SATA PCIe card.
  7. I had a bunch of 1.5TB greens fail on me. They had the head parking issue which I figured out mid way. Haven't had a red fail yet. My drives are all installed in MediaSonic Probox's that have the fan set full time. Temperature is the enemy of HDD's. If you don't have Scanner you should check it out. It's gives a lot of helpful info on the drives and tests them regularly. I feel with Scanner running and DrivePool that I have a reliable JBOD storage system
  8. Can anyone recommend a port mutliplier SATA PCIe card that works reliably with Windows 10 1903?
  9. I put a new TP Link 1gb network card in just to eliminate that as a potential cause. It's something related to DrivePool. I copied a 5GB file to a share on the boot drive which has no DrivePool related folders. That file immediately copied at the speed expected. It's files on the DrivePool drive that take almost a minute to start copying. StableBit Scanner says all drives are healthy. Shoud I reinstall DrivePool? Thanks EDIT1: I'm realizing that it could be the MediaSonic HP1-SS3 Sata card drivers as the Pool drives are operating off two ProBoxes connected to it. EDIT2: Up
  10. Apologize that I haven't begun researching this before asking the question but figured perhaps someone here might have encountered what is happening. I made an image backup of my DrivePool dedicated storage server computer running on Windows 7 and then ran the Windows 10 upgrade assistant just to see what would happen. The upgrade appeared to go fine and Drive Pool seems to be operating fine. The issue we're encountering is very slow transfer speeds from that machine to other computers on the network. Hopefully it's just the network driver Win10 used but wanted to see if this happened to anyon
  11. Some type of permissions solution would logically be the right solution. With duplicated folders and scanner doing it's thing I'm not worried about hardware failure. It would be great if there was some way to make folders read-only even to the ransomware running with admin level permission.
  12. I do small business IT support. I've seen my share of ransomware and was just thinking it would be hard to recover all the Austin City Limits I've recorded on WMC7. My main remedy for ransomware is backup but I don't really want to backup 20TB of things recorded from TV. I do have them duplicated so hardware failure is unlikely to be an issue. User error is possible though as is ransomware encryption. I was thinking that it would be neat if the duplicated copy in DrivePool was hidden from the copy that shows up in shares so it can't be encrypted by ransomware. What are people using for b
  13. Thanks for the link - that would work fine - agree - who needs drive letters! Just a comment on drive "naming". I use a Brother label printer for each HDD. I name them WDC_8TB_01, WDC_8TB_02, SEA_8TB_01, SAM_4TB_01 etc. I also use the rename drive in Windows with the same name. That way I'm never in doubt what physical drive is the one, for instance, I'm removing.
  14. The Probox just arrived. I had it out of the box and up and running with 4 drives in 10 minutes. It's amazing how simple it is to setup the second unit. I took out the Rosewill RC-219 eSATA card and installed the second Mediasonic eSATA card. The RC-219 can only multiplex one of the two ports so isn't the right card for a DrivePool box. Before I had the Mediasonic eSATA card I thought I would be limited to two external SATA enclosures (the Vostro 430 I'm using for DrivePool only has two PCIe slots). Now I can easily add another ProBox each time I need to add storage. As 8TB drives work (have o
  15. eSATA port multiplex question: I went ahead and ordered a second Mediasonic HF2-SU3S2 ProBox 4 Bay Hard Drive Enclosure with USB 3.0 & eSATA. I also ordered a second Mediasonic ProBox 2 Port External SATA 3 / III 6.0 card because I'm under the impression that only one of the two eSATA ports on these cards can be used for multiplex. It's only a $14 extra and I wouldn't mind having a spare on hand but will a single card multiplex both eSATA ports? (edit to answer my own question - apparently both ports can multiplex - card supports up to 8 drives)
  16. Hi Gavin, I bought the Mediasonic 2 Port External SATA card back in April after you confirmed Drashna's original recommendation but never put it in until about 3 weeks ago (July). My 3 year old ProBox has been running flawlessly since - I'm just about to order a second one along with another Mediasonic card. I need a few of the drive docks I've been using for a backup project so I'm swapping those out. I find the drives run cooler in the ProBox (have the fan set to stay on the middle speed) than in drive docks. Doug
  17. The Probox hasn't dropped off for two days but I ordered the Mediasonic eSATA card anyway
  18. Thanks for confirming card and the thread. I just updated my Rosewill RC-219 64 bit driver to 15.0.6 from 15.03 and the conversions have been reading off it for over 24 hours so perhaps I've solved the issue.
  19. Thanks for sharing your experience. Hopefully the right card will fix this issue. Is this the correct card?: Mediasonic ProBox 2 Port External SATA 3 / III 6.0 Gbps PCI Express Card HP1-SS3
  20. I'm looking for recommendations for a PCIe eSATA card and 4 or 8 bay enclosure. Maybe someone might know why I'm having the issues described below: Back story: I have a Rosewill RC-219 connected to a MediaSonic Probox 4 drive enclosure. For 3 years I ran this card and enclosure in an Optiplex GX-620 running WHS 2011 and DrivePool. After about a year and a half of solid performance the Probox started to occasionally disappear. If I cycled its power it would come back without doing anything else. I replaced the Optiplex GX-620 with a Dell Vostro 430 running Windows 7 Pro 64. I also repl
  21. Hi Chris, Thanks for reply. I am currently running WHS2011 on an old Pentium D 3.4Ghz Dell Optiplex 520 SFF (circa 2005) machine with a PCI gigabit NIC that delivers only half the speed of newer onboard NIC's When I play MKV files over 8GB on machines running WMC they stutter. The same MKV's play fine when placed on local drive of WMC machines. If you pause the movie for 10 seconds it will then play for about 10 minutes before it stutters again. The DrivePool drives are all 6GB WD Reds. I'm hoping the same eSATA docks and MediaSonic ProBox HF2-SU2S2 connected via PCIe eSATA cards
  22. Two years later I'm ready to build a new "DrivePool server". Someone gave me a box that has mutliple PCIe slots, I5 processor and tons of RAM. As an MS action pack subscriber I can use any OS they make. I'm not backing up workstations and don't use the media streamer. I just need reliable, duplicated storage for WMC - movie folders, MKV's and photo files. I actually have a powerful Hyper-V server running lot's of VM's for domain server, SQL etc. From re-reading Chris' posts I'm inclined to install 2.x on a reinstall of WHS2011 (will be migrating from 1.3) The box already has Wind
  23. Agree, its great to be able turn a Windows 7 box into a JBOD storage server that's so easy to manage and performs so well
  24. Hi Blueman, You've convinced me to upgrade from 1.x to 2 (along with Drashna's remark that 2.x is where the new developments will happen). You reminded me of something - I actually hate the slowness of the WHS dashboard. Plus it's Friday afternoon - what could be more fun than upgrading Drivepool? Doug
  25. To britgeezer, I would just stay with 2.x. The fact that 1.x was a WHS plugin doesn't have any advantage except that the install is streamlined. The mechanics of Drive Pool are the same. I'm staying with 1.3 because it's stable and I wouldn't use the 2.x features. I will definitely go to 2.x or whatever DrivePool is current when I retire this WHS server in the future.
×
×
  • Create New...