Pichu0102

That would work, but unfortunately, just wouldn't work for me. Lots of smaller drives of various sizes. So the hunt for a compatible backup program continues.

Hello. I was wondering what my options are for backup programs out there that can backup files and folders from a pool drive directly without having to back up each individual drive in the pool (which would lead to an annoying amount of wasted space due to 3x duplication on the pool). I keep trying different ones, but either I run into ones that require VSS, or have their own set of issues, like Duplicati. I used to use Crashplan, but decided to move on. I'm now using Backblaze for online backup, but still need one for local backup. Any suggestions?

Mm, it's more the cloud drives are a stopgap until I get a new local drive to replace an older one here, but yeah. My pool has been running with 3x duplication over 3 internal and 7 external drives, so adding cloud drives is just a way to give a spare amount of space to work with, as I put the cloud pool to not allow duplicated or unduplicated files unless the other drives were all 90% full. Also have Crashplan backup everything both locally (to the 3x duplicated pool itself, forbidden from using the cloud drives to store backup files, bad practice, but local backup is more for files I need to roll back) and to Crashplan central, so I try to keep a few backup situations running. But yeah, the cloud drives are kind of expansion to give the local drives more space to work with.

I ended up testing my idea before seeing your post, sorry. I simulated failure by moving test files out of FTP Drive A's poolpart folder to the root. Drivepool only reacted once I chose to recheck duplication, and only realized the problem when it checked Pool A, not when it checked Cloud Pool A. It then reduplicated back to FTP Drive A. I was thinking about it in the wrong direction. Cloud Pool A isn't concerned about duplication or missing duplicates, as it is not duplicated, but Pool A was concerned and safely regenerated into Cloud Pool A, which put the files in FTP Drive A again. So Cloud Pool A wouldn't ask the parent pool to regenerate missing files, as that's not it's problem, but Pool A will notice and duplicate back into Cloud Pool A. My bad.

If I were to create a pool that consisted of multiple local drives, and one cloud pool with cloud drives, if a drive is lost from the cloud pool, would the cloud pool be able to regenerate from the pool above? An example: Pool A (3x duplication) Local Drive A Local Drive B Local Drive C Local Drive D Local Drive E Cloud Pool A (no duplication) FTP Drive A B2 Drive A Google Drive Drive A If one of the drives under Cloud Pool A goes kaput: Pool A (3x duplication) Local Drive A Local Drive B Local Drive C Local Drive D Local Drive E Cloud Pool A (no duplication) F̶T̶P̶ ̶D̶r̶i̶v̶e̶ ̶A̶ (Lost) B2 Drive A Google Drive Drive A Will Cloud Pool A, which had no duplication on the files in it, be able to pull files from Local Drive A, B, C, D, or E to regenerate itself and also regenerate duplication of Pool A correctly? Or will Cloud Pool A need to be destroyed then remade and readded for it to work properly?

I'm getting an error using the File Share provider on Windows 10. In addition to regularly forgetting the file share password, it also has this cryptic message randomly and fails to make a new drive: CloudDrive.Service.exe Warning 0 [IoManager:23] Error performing I/O operation on provider. Retrying. Insufficient system resources exist to complete the requested service 2016-04-30 09:15:57Z 603868056 CloudDrive.Service.exe Warning 0 [IoManager:23] Error performing I/O operation on provider. Retrying. Insufficient system resources exist to complete the requested service 2016-04-30 09:15:57Z 604266593 CloudDrive.Service.exe Warning 0 [IoManager:23] Error performing I/O operation on provider. Retrying. Insufficient system resources exist to complete the requested service 2016-04-30 09:15:57Z 604963579 CloudDrive.Service.exe Warning 0 [IoManager:23] Error performing I/O operation on provider. Retrying. Insufficient system resources exist to complete the requested service 2016-04-30 09:15:57Z 605981202 CloudDrive.Service.exe Warning 0 [IoManager:8] Error performing I/O operation on provider. Retrying. Insufficient system resources exist to complete the requested service 2016-04-30 09:15:58Z 607066835 CloudDrive.Service.exe Warning 0 [IoManager:23] Error performing I/O operation on provider. Retrying. Insufficient system resources exist to complete the requested service 2016-04-30 09:15:58Z 607300738

Hello, I was wondering, is it safe to write directly to a Poolpart folder? Nvidia Shadowplay demands high write speeds or it fails miserably, and the pool has some slow writing drives with the entire thing at 3x. However, I have an internal drive fast enough to write videos out. Is it safe to point it at the folder I want it to be in on the pool in the Poolpart folder, and let Drivepool eventually pick it up and duplicate it and move it around once it gets around to it?

I was wondering, when Scanner triggers an evacuation of files, for files already duplicated elsewhere on the pool, does it pull and duplicate copies from healthy drives, or from the unhealthy drive?

Still nothing.

Still nothing on the 0748, even with NoWMI checked, NoWMI and Unsafe checked, and only Unsafe checked. DirectIO test program unsafe returns SMART values on the 0748 though. Smart attributes for device: 8 Version: 16 Offline data collection status: NeverStartted Self-test execution status: PreviousCompletedNoErorrOrNoTestRun Self-test percent remaining: 0 To complete off-line data collection: 03:05:00 Off-line data collection capability: ExecuteOffLineImmediate, Vendor1, OffLineReadScanning, SelfTest, ConveyanceSelfTest, SelectiveSelfTest SMART capability: SmartAutoSaveOnPowerModeSwitch, SmartEnableDisableAndAttributeAutosaveSupported Error logging capability: True Short self-test polling time: 00:02:00 Extended self-test polling time: 02:02:00 Conveyance self-test polling time: 00:05:00 Attributes: 17 1: 200 [0x000000000000] 3: 179 [0x000000000802] 4: 96 [0x000000001320] 5: 200 [0x000000000000] 7: 100 [0x000000000000] 9: 70 [0x00000000561A] 10: 100 [0x000000000000] 11: 100 [0x000000000000] 12: 100 [0x000000000061] 192: 183 [0x000000003229] 193: 78 [0x00000005999C] 194: 116 [0x00000000001F] 196: 200 [0x000000000000] 197: 200 [0x000000000000] 198: 100 [0x000000000000] 199: 200 [0x000000000000] 200: 100 [0x000000000000] Checksum valid: True Summary of \\.\PHYSICALDRIVE8: SATA compliance: Sata SATA spec: SATA Rev 3.0 SATA speed: 3.0 Gbps of 3.0 Gbps Max PATA speed: DMA mode: Multiword DMA Mode 0 UDMA mode: Ultra DMA Mode 6 Multiword DMA mode: Multiword DMA Mode 2 Major version: ATA8-ACS Sector count: 976,773,168.00 TRIM Support: CoveNativeSafe.Info.AtapiIdentify+ Identification of \\.\PHYSICALDRIVE8: Model: WDC WD5000BMVW-11S5XS0 (0x57, 0x44, 0x43, 0x20, 0x57, 0x44, 0x35, 0x30, 0x30, 0x30, 0x42, 0x4D, 0x56, 0x57, 0x2D, 0x31, 0x31, 0x53, 0x35, 0x58, 0x53, 0x30) Firmware: 01.01A01 Serial number: WD-WXF1E32UHYX3 ATAPI major version: ATA_1, ATA_2, ATA_3, ATA_ATAPI_4, ATA_ATAPI_5, ATA_ATAPI_6, ATA_ATAPI_7, ATA8_ACS ATAPI minor version: 0 Logical cylinders: 16383 Logical heads: 16 Logical sectors per track: 63 Commands supported 1: Smart, SecurityMode, MandatoryPowerManagement, WriteCache, LookAhead, HostProtectedArea, WriteBuffer, ReadBuffer, Nop Commands supported 2: DownloadMicrocode, AdvancedPowerManagement, SetMaxSecurityExtension, _48BitAddress, DeviceConfigurationOverlay, MandatoryFlushCache, FlushCacheExt, AlwaysPresent Commands supported 3: SmartErrorLogging, SmartSelfTest, GeneralPurposeLoggingFeature, _64BitWorldWideName, IdleImmediateWithUnload, AlwaysPresent Commands supported 4: ReadWriteDmaExtGplOptional, SegmentForDownloadMicrocode, AlwaysPresent Commands enabled 1: Smart, MandatoryPowerManagement, WriteCache, LookAhead, HostProtectedArea, WriteBuffer, ReadBuffer, Nop Commands enabled 2: DownloadMicrocode, AdvancedPowerManagement, _48BitAddress, DeviceConfigurationOverlay, MandatoryFlushCache, FlushCacheExt, CommandSet4Valid Commands enabled 3: SmartErrorLogging, SmartSelfTest, GeneralPurposeLoggingFeature, _64BitWorldWideName, IdleImmediateWithUnload, AlwaysPresent Commands enabled 4: ReadWriteDmaExtGplOptional, SegmentForDownloadMicrocode, AlwaysPresent Capabilities 1: DmaSupported, LbaSupported, IordyMayBeDisabled, IordySupported, StandbyTimerValuesSupported Capabilities 2: VendorSpecificStandbyTimerValueMinumum, AlwaysPresent Trusted computing: 0 Maximum logical sectors: 268,435,455.00 Additional supported: 0 Queue depth: 32 SATA capabilities: SataGen1SignalingSpeed_1_5_Gbs, SataGen2SignalingSpeed_3_0_Gbs, Ncq, ReceiptOfHostInitiatedPowerManagement, SataPhyEventCountersLog, UnloadWhileNcqCommandsOutstanding, NcqPriorityInformation SATA features supported: DmaSetupAutoActivation, InitiatingPowerManagement, SoftwareSettingsPreservation SATA features enabled: SoftwareSettingsPreservation Multiword DMA: MultiwordDma0Supported, MultiwordDma1Supported, MultiwordDma2Supported, MultiwordDmaMode0Selected UltraDMA: UdmaMode0Supported, UdmaMode1Supported, UdmaMode2Supported, UdmaMode3Supported, UdmaMode4Supported, UdmaMode5Supported, UdmaMode6Supported Advanced power management: MinimumPowerConsumptionWithoutStandby (80) Automatic acoustic management: [CURRENT] VendorSpecific (00) [DEFAULT] VendorSpecific (00) Sector count (LBA): 976,773,168.00 Logical sectors / physical: 8 (Flags: 0x6000) World wide name: 0x50014EE6AD26ADAD (Authority=0x5, Organization=0x14EE, Vendor=0x6AD26ADAD Organization name: Western Digital Technologies, Inc. Organization address: 20511 Lake Forest Dr. Lake Forest Ca 92630 UNITED STATES Words per logical sector: 0.00 Security: SecuritySupported, EnhancedSecurityEraseSupported Device nominal form factor: NotReported Current media serial: The 07A8 requires Unsafe IO in the test program as well, but shows up normally in Scanner, while the 0748 only returns SMART info from the test program. Odd, that.

Nope, not even with DirectIO Unsafe checked, either.

No more false damaged disk warnings.

ID: USRYRN9X Also, bad sectors popped up on all disk scans while on the Beta you linked.

Nope, still not getting smart data from that drive in Scanner. Edit: And I had to downgrade to the official release because the Beta decided all my drives had random bad sectors. Not good.

Here's what it says: Smart attributes for device: 6 Version: 16 Offline data collection status: NeverStartted Self-test execution status: PreviousCompletedNoErorrOrNoTestRun Self-test percent remaining: 0 To complete off-line data collection: 03:05:00 Off-line data collection capability: ExecuteOffLineImmediate, Vendor1, OffLineReadScanning, SelfTest, ConveyanceSelfTest, SelectiveSelfTest SMART capability: SmartAutoSaveOnPowerModeSwitch, SmartEnableDisableAndAttributeAutosaveSupported Error logging capability: True Short self-test polling time: 00:02:00 Extended self-test polling time: 02:02:00 Conveyance self-test polling time: 00:05:00 Attributes: 17 1: 200 [0x000000000000] 3: 179 [0x0000000007E9] 4: 96 [0x0000000012FD] 5: 200 [0x000000000000] 7: 200 [0x000000000000] 9: 71 [0x000000005393] 10: 100 [0x000000000000] 11: 100 [0x000000000000] 12: 100 [0x000000000058] 192: 185 [0x000000002E2C] 193: 85 [0x000000054E15] 194: 115 [0x000000000020] 196: 200 [0x000000000000] 197: 200 [0x000000000000] 198: 100 [0x000000000000] 199: 200 [0x000000000000] 200: 100 [0x000000000000] Checksum valid: True

v2.5.1.3062 Also, whoops, wrong drive. Accidentally tried to directio check the 07A8 drive when the 0748 drive is the one having problems. Oops. Oddly enough, both drives behave the same to DirectIO, but not scanner, with ScsiPassthrough and Scsipassthrough48 working on both, default options with nothing checked not working, and yet Scanner can read SMART from the 07A8. Strange. Attached screenshots.

I get a similar issue with a USB drive, except it appears when the USB box is checked. Files attached.

I'm curious if anyone else has tried running Steam games off their pool with 2x duplication enabled. Did you have to filter your files onto the fastest drives so they wouldn't get stuck on slow ones for it to work well? Also, is there a filter onto fastest drives for a folder plugin anyone has made that checks Drivepool's performance information?

Hello, I was wondering where in the log I could find what balancer(s) called for a rebalance, if that's possible. I'm slightly curious as to when and what tripped one of the balancers.

Ah, okay. Thank you very much.

I have a SATA 3 drive, a SATA 2 drive, 2 USB 3s and 2 USB 2s in my pool. Is there a way to tell Drivepool to balance less used files to slower drives and more accessed files to the faster drives on a regular basis?

Balancing settings match those screenshots. Checking never allow files to be placed on other drives fixed the issue and now the pool's organization is back to 100% with no warning in the file placement tab. Thanks!

I'm having a weird issue where drive balancing isn't emptying files off drives to other drives in order to respect file placement rules. Basically, I'm trying to get it to move files it can off the drives above to other ones to make room for file placement rules. As in, existing files on the drives with file placement rules applying to the drive moving to drives with no file placement rules.

Is there a way to, say, add my C drive to the pool and have it not store anything on it unless other drives become 90% full? The Drive Usage Limiter is a little sparse on documentation of what the options do. If full pool duplication is on, doesn't unchecking unduplicated files do nothing since everything will be duplicated? Also, if both unduplicated and duplicated are unchecked, will it never place files on that drive no matter what? Furthermore, why is there another slider that says don't fill disk space above 90% here when this is also in the Prevent Drive Overfill balancer? Edit: I tried to simulate drive errors in Scanner to see if it would react the way I wanted it to, where if a drive is failing, it evacs the drive to the unused C drive. It, well, didn't. Balancer Settings: Moving Scanner's priority below Drive Usage Limiter didn't try to balance anything onto the C drive either. Didn't get screenshots of that, but it was still trying to keep files on the failing drives while the C drive went unused with no target for rebalancing. Odd behavior.