Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  • Days Won


eduncan911 last won the day on December 14 2015

eduncan911 had the most liked content!

About eduncan911

  • Rank
    Advanced Member
  1. Two people reporting the same problem above... Just to state a commonality between the two: They were both 'formatting' drives at the time they report errors/lost data. Maybe related? Does seem scary. You shouldn't have to; but, I personally install all new drives in a separate machine first to format them (at 64KB clusters, because almost all are movies/tv). Once formatted, I move them to the server. I do this mostly from habit of back in the NT days when random $&@# happened when formatting one drive and accessing another. Absolute guess here... But, perhaps DrivePool
  2. Now that I've let it run for several hours, all disks, the HGST disks are up to 165 to 170 MB/s - all 8. That's nice. The Seagate ones are 155 MB/s. And, it looks like they will all complete within about 3 hours. That's a big improvement in the "work window."
  3. Perfect, that's what I was looking for! Ah, so setting it to 0 is unlimited. Done and done! Yep, I already disabled the throttling on the same controller. A glance over at the watt meter with all 14 HDDs scanning (8x HGTS 4GB, 3x Seagate Blue 4GB, and various other WD Green drives) shows 188 Watts at the wall. So, power consumption: check. The hottest drive is 37C, with most around 27 - 32C. The chassis fans are spinning at 50% PWM. Heat generation: low, check. Vibration.. Eh... That's actually one of the reasons I switched to HGST with their marketing advertisement for v
  4. I have set ScanMaximumConcurrent to "4" for my setup. Is there any drawbacks to this setting? Too high, too low? My server has an LSI 9211-8i HBA connected to an LSI Expander hot-swap SAS2 blackplane (the Supermicro SC846 chassis for those wondering). The Expander utilizes all 4x 6 Gbps channels to have a total of 24 Gbps, or about 3,000 MB/s (megaBytes per seconds). Since each HGST 4GB HDD I have can only substain about 130 MB/s, I was thinking "4 concurrent" at ~520 MB/s isn't an issue since that's only ~17% of the overall bus. Or, the same speed as my Sata 6 SSD I have in the po
  5. As for file permissions, I reset all permissions and force it onto all sub-files and folders like memory muscle. It's just a default action one has to make when moving NTFS volumes from one machine to another. And annoying to users that aren't familiar with the NTFS side of things. A necessary evil - and I should have mentioned that in my previous posts. Sorry about that. Good to hear it went through.
  6. The Intel i350-T4 NIC has 4 ports on it. Each port is connected to a dedicated switch (and each switch has a connection to itself). The switches are cheap built-in router switches and a few 5 port and 8 port cheap Linksys/belkin switches. All are Gigabit switches. Each Wifi router I have either acts as those dedicated switches, or is connected directly to one of the other switches. This ensures the lowest number of routes from the NIC, through a switch, to the Wifi router. @Chris (Drashna): Humm, no drive A:\ eh? That may explain the odd "why are the drives spun up?" issues I've h
  7. I should clarify that I am not using the Unsafe Direct IO... I am Windows Power Management to spin down my drives; and, I can access all SMART data through the LSI controllers (as long as I am on P20 firmware/driver versions). Microsoft has an MSDN article on "IPM Configuration and Usage." Idle Power Management (IPM) can be enabled for HBAs that do not allow Windows to power down the disks by modifying the driver's INF file to allow power management by the drivers. https://msdn.microsoft.com/en-us/library/windows/hardware/ff561476(v=vs.85).aspx I have not had any luck manually add
  8. Ah yes, I had "Fill SSD drives up to" set to 98%. I've now set that to 60%. Will monitor. But, that kind of goes against what I wanted to use a 240 GB SSD for... To cache 240 GB of files before it has to divert to the drive pool, not 140 GB (60%). Shouldn't it divert to the drive pool anyways? Even with 98% set? And yes, "out of disk space" was the error I was getting.
  9. You had me all the way to the very last sentence when you say... Which confuses me. Doesn't that contradict your Pro above? It said a Pro is to avoid disk spin up issues. But at the end, you said the default power settings do not spin up a disk unless you've manually enabled Query power mode directly from disk. Which, implies it does spin up a disk? I'm trying to decide if this effort is worth it to me... Right now, my setup with 20+ something odd disks works well with the default OS power settings. I don't know the exact state of the disks, which is
  10. Using an Internal virtual network adapter offloads the network traffic from your External-physical NICs. I previously ran into issues streaming an MKV (say, from drive 11) and my NZB process (running on another machine) copying a recent download directly to the pool over the network (to, say, disk 21). They were different disks, but, the same NIC. I got stuttering in the movies... New setup uses the two onboard Intel i210 NICs in a Team-1 for "common" network traffic. I purposely installed an Intel i350-T4 NIC, with all four NICs setup in a single Team-2 dedicated solely to "Remot
  11. FYI, for LSI HBAs, I've been playing with several and had similar issues... IBM M1015 HBA flashed to LSI 9211-8i v.14... I got SMART to work; but, only with the built-in Microsoft drivers for the LSI. If switching to LSI's v.14 drivers, it did not work. The reason to switch is to have HDD spindown by modifying the INF of the drivers. IBM M1015 HBA flashed to LSI 9211-9i v.20... Same story as the above... But, SMART now works with the LSI v.20 driver modified and installed. LSI 9211-9i HBA @ v.16... SMART data with Microsoft Drivers, no SMART pass through with v.16 drivers.
  12. Ok, I adjusted the settings to: Notice the "Not more often than every" setting that I cleared. It seems the SSD gets about 50% full now and is able to buffer the 120 GB of data, while balancing moves it off. I am still evaluating it; but so far, that seems to be what is happening (I copy a new file to SSD, and Balancing copies the older file I just finished from SSD to pool at the same time). I determine this because Scanner shows the old 2 TB and 3 TB drives I am copying from at "60 to 80 MB/s"; but yet, Scanner shows the SSD moving at 180 MB/s, with another drive in my pool
  13. Is it possible to get the C# source to this? I guess I can Reflect it and snag it if need be. From the API, is it possible to force a file/rebalance immediately after a file has been copied to, say, an SSD like this? There's a checkbox on the Settings tab that allows Balancers to force a re-balance. The problem I am running into is my "SSD" drive, a 240 GB SATA6 drive, gets "full" very quickly when I move TBs around - and doesn't get "emptied" until a full rebalance is complete. Which is annoying when trying to move 25 TBs around. I'd have to complete disable this "SSD Optimizer" j
  14. I just did the same thing (completely different hardware; but, the same steps). Yes. It will find and have the actual full Drivepool all setup and active. As long as the drives are "Online": using the built-in Disk Management application, you can check that they are online. I recommend these steps though: Get the hardware setup first before installing the software. - Deactive license, shut down old machine. - Install HDDs in new machine, do NOT install DrivePool!!! Hold off installing any software. - Go to Disk Management and verify the drives are all "Online." If they are no
  15. Yep, exactly. I was actually more concerned about DrivePool reading the existing data. But now that I think about, you said you are using the hidden NTFS metadata. Perhaps that's readable no matter the permissions. But yes, and for anyone else reading: if you have custom permissions on your drivepool (e.g. \\SERVER\Users\Mommy, \\SERVER\Users\Child1), then you will want to remove all of those permissions before switching to a new server. Easiest way to do that is to Right-Click at the root of your pool, go to editing the permissions, remove everyone but the defaults. Once you
  • Create New...