Harri

Hello, for a few days I had now severe problems with my combination out of Scanner, Drivepool and Clouddrive. Today I managed to get some time to look further into the issue. It looks like the last Scanner Beta somehow manages to bring all the external (USB) HDDs to 100% usage while nothing is being transferred. I can reproduce this starting and stopping Stablebit Scanner. Drivepool (which I considered first) works now after stopping the Scanner. Anyone else with this behaviour?

Is more information needed to help me? Would love to sort this problem out ;-) . Uploadqueue is rising...

Hi all, since yesterday I have trouble using Clouddrive on one maschine 19:22:00.4: Warning: 0 : [ChecksumBlocksChunkIoImplementation:15] Expected checksum mismatch for chunk 439804651256, ChunkOffset=0x00600000, ExpectedChecksum=0xb25990f640cc5ab1, ComputedChecksum=0x44aa4b13478d1aa6. 19:22:07.7: Warning: 0 : [IoManager:64] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:07.9: Warning: 0 : [IoManager:54] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:08.1: Warning: 0 : [IoManager:64] [W] Error writing range: Offset=2.127.888.384. Length=4.096. Checksum mismatch. Data read from the provider has been corrupted. 19:22:08.1: Warning: 0 : [IoManager:60] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:08.2: Warning: 0 : [IoManager:54] [W] Error writing range: Offset=2.121.793.536. Length=4.096. Checksum mismatch. Data read from the provider has been corrupted. 19:22:08.3: Warning: 0 : [IoManager:60] [W] Error writing range: Offset=2.126.774.272. Length=4.096. Checksum mismatch. Data read from the provider has been corrupted. 19:22:09.4: Warning: 0 : [IoManager:58] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:09.6: Warning: 0 : [IoManager:58] [W] Error writing range: Offset=2.125.398.016. Length=212.992. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.2: Warning: 0 : [IoManager:57] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.4: Warning: 0 : [IoManager:57] [W] Error writing range: Offset=2.122.776.576. Length=327.680. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.4: Warning: 0 : [IoManager:66] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.6: Warning: 0 : [IoManager:66] [W] Error writing range: Offset=2.131.165.184. Length=110.592. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.8: Warning: 0 : [IoManager:71] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.8: Warning: 0 : [IoManager:65] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:10.9: Warning: 0 : [IoManager:65] [W] Error writing range: Offset=2.129.920.000. Length=69.632. Checksum mismatch. Data read from the provider has been corrupted. 19:22:11.1: Warning: 0 : [IoManager:71] [W] Error writing range: Offset=2.132.672.512. Length=655.360. Checksum mismatch. Data read from the provider has been corrupted. 19:22:11.1: Warning: 0 : [IoManager:15] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:11.3: Warning: 0 : [IoManager:15] [W] Error writing range: Offset=3.069.116.416. Length=69.632. Checksum mismatch. Data read from the provider has been corrupted. 19:22:11.3: Warning: 0 : [IoManager:42] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. 19:22:11.4: Warning: 0 : [IoManager:9] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted. Used version is 1.1.1.1131. Duplication is activated since the last update. What can I do to repair the volume?

What do you mean by triggering the error? Trying to open some of the files? Copying them? Anything else?

Any news?

#done

The problem is still there. Just uploaded the log as requested. CHKDSK on all drives was fine and found no issues.

Since it all the files were readable when I opened them directly I expected something else. Chkdsk will check them now. Might take a couple of days... Phase 2: Die Dateinamenverknüpfung wird untersucht... Status: 382812 von 464978 fertig; Phase: 82%; Insgesamt: 0%; ETA: 999:00:00

The faulty drives are already pulled... I'm in the restoring process (reduplicating etc.) . I would think fixing the NTFS stuff is the next step. Edit: I have tried to fix the issue following http://community.covecube.com/index.php?/topic/2038-fix-file-permissions-windows-10/ result: Any ideas on how to fix this? Perhaps Update to a newer beta?

You are damn right... its the pool. Thanks for mountvol. Did not know this. Once more something learned :-) . When I try to run check-pool-fileparts on the problematic subfolder I get: PS C:\> dpcmd check-pool-fileparts 'K:\sortiert\normal wichtig\' dpcmd - StableBit DrivePool command line interface Version 2.2.0.834 Error: Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch And yeah... looks like some Security stuff is not working... One exemplaric file shows me: Any ideas on how to fix this?

As far as I can see it has something to do with the space... PS C:\> dpcmd get-duplication 'K:\sortiert\normal wichtig\' dpcmd - StableBit DrivePool command line interface Version 2.2.0.834 Illegales Zeichen im Pfad. Usage: dpcmd get-duplication [parameter1 [parameter2 ...]] Command: get-duplication - Outputs duplication related information about the specified path. Parameters: poolPath - Path to a file or folder on the pool. PS C:\> dpcmd get-duplication 'K:\sortiert\unwichtig\' dpcmd - StableBit DrivePool command line interface Version 2.2.0.834 Found '\\?\K:\sortiert\unwichtig\' Expected number of copies: 1 Found number of copies: 7 Is directory: True Has multiple sub-duplication counts: False - \Device\HarddiskVolume11\PoolPart.4857b717-fa72-47c5-bee7-6ab1a4e0664d\sortiert\unwichtig - \Device\HarddiskVolume13\PoolPart.d7fdd86d-6c12-4f6e-8ceb-c45d30ecfef2\sortiert\unwichtig - \Device\HarddiskVolume15\PoolPart.1189118a-3918-478f-a9dc-7b142f590df3\sortiert\unwichtig - \Device\HarddiskVolume16\PoolPart.f8d3cd48-4620-4834-9ae7-34da99876cfa\sortiert\unwichtig - \Device\HarddiskVolume19\PoolPart.71b3a753-c025-4135-b4fa-4f8b289d17a7\sortiert\unwichtig - \Device\HarddiskVolume21\PoolPart.ee0b4b43-faa7-46dc-895f-66a1f41e30cc\sortiert\unwichtig - \Device\HarddiskVolume9\PoolPart.d519d779-4fa6-4186-90cb-7fedcd0a8bf0\sortiert\unwichtig PS C:\> I have found nearly all of those 16 missing files on the defective hdd. One example: DrivePool.Service.exe Warning 0 [FileDuplication] Error checking file \\?\Volume{b9960c42-ebe0-4a40-8306-56ef4d360ade}\sortiert\normal wichtig\yyy\xxx\unsortiert\ccc Tag 1\aaaa.mp4 for duplication consistency. Das System kann den angegebenen Pfad nicht finden 2017-10-07 00:45:24Z 1444277650406 However the indicated Volume-ID is not in use by any of the installed disks. And checked against the removed hdd none of them has this ID. I also checked my mailalerts. No hints to this ID. Is there a possbility to check what this ID belongs to? Edit: And those problematic files are in a folder which should be duplicated... Edit 2: I checked the Folder directly on all HDDs and found all the missing files there, at least once. Intact and usable. However if I use the Pool i get some errors or they are unusable.

Version is 2.2.0.834 Beta. Since the message is being shown and it ends with ... isn't there a way to get the full paths?

You can use compressed air. But the fan must be fixed somehow (with a pencil f.ex) . Otherwise it may generate energy and this can be quite bad.

Hi all, I'm still trying to get everything back running. Atm I removed two faulty drives from the pool. One is showing significant errors on at another computer and chkdsk sorts tons out... The other one is running fine on another computer. However my plan is still to clear it out completely and see what I will do then. After days of rebalancing and duplicating I'm now getting some errors. Drivepool is showing "Duplication Warnings". Most of them are "The system could not find the path." or so. Is there a easy possibility to get a complete list of failed files? Where can I find it? dpcmd fails with "illegal char in path" (there is a blank space which is the problem). Using " " around the filename does NOT help.

Okay. Those SSDs are mSATAs and connect like a dynamic disk. So no possibility to use them as a cache. Next question ^^. I have a couple of problems with a FTP Provider. 14:28:58.2: Information: 0 : [Disks] Got drive letter assign (volume ID: 95cc2933-5347-48cd-8461-43ee22e01e94)... 14:29:13.5: Information: 0 : [Disks] Updating disks / volumes... 14:29:23.1: Warning: 0 : [ApiFtp:90] Error using FTP client. Unable to parse server response to PWD command. 14:29:23.2: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. Unable to parse server response to PWD command. 14:29:37.4: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:29:51.9: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:29:52.0: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. The server has closed the connection. 14:30:06.5: Warning: 0 : [PinDiskMetadata] Error pinning file system metadata. Zugriff verweigert 14:30:07.1: Warning: 0 : [ApiFtp:90] Error using FTP client. Unable to parse server response to PWD command. 14:30:07.1: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. Unable to parse server response to PWD command. 14:30:21.3: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:30:55.9: Warning: 0 : [ApiFtp:90] Error using FTP client. Unable to parse server response to PWD command. 14:30:55.9: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. Unable to parse server response to PWD command. 14:31:11.1: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:31:25.4: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:31:25.4: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. The server has closed the connection. 14:31:39.0: Warning: 0 : [ApiFtp:90] Error using FTP client. Unable to parse server response to PWD command. 14:31:39.0: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. Unable to parse server response to PWD command. 14:31:54.7: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:32:08.0: Warning: 0 : [ApiFtp:90] Error using FTP client. Unable to parse server response to PWD command. 14:32:08.0: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. Unable to parse server response to PWD command. 14:32:43.1: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:33:18.4: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. 14:33:18.5: Warning: 0 : [IoManager:90] Error performing I/O operation on provider. Retrying. The server has closed the connection. 14:33:51.6: Warning: 0 : [ApiFtp:90] Error using FTP client. The server has closed the connection. Is there a possibility to get the full FTP log? I'm unsure on where the error happens since WinSCP is working normally... (however quite slow)