Jump to content
Covecube Inc.

No0bstacles

Members
  • Content Count

    11
  • Joined

  • Last visited

Posts posted by No0bstacles


  1. Just wanted to share what I saw today using my cloud drive with Google, I know they are marked as warnings, but the fact I see "failed" makes me a bit nervous.
    Is this bad or a sign of bad things to come perhaps? Or just normal behavior to safely ignore?
      15:26:27.4: Warning: 0 : [ApiGoogleDrive:37] Google Drive returned error: [unable to parse]
      15:26:27.4: Warning: 0 : [ApiHttp:37] HTTP protocol exception (Code=InternalServerError).
      15:26:27.4: Warning: 0 : [ReadModifyWriteRecoveryImplementation:37] [W] Failed write (Chunk:50901, Offset:0x00000000 Length:0x01400500). HTTP Status InternalServerError
      15:26:27.6: Warning: 0 : [TemporaryWritesImplementation:37] Error performing read-modify-write, marking as failed (Chunk=50901, Offset=0x00000000, Length=0x01400500). HTTP Status InternalServerError
      15:26:27.6: Warning: 0 : [WholeChunkIoImplementation:37] Error on write when performing master partial write. HTTP Status InternalServerError
      15:26:27.6: Warning: 0 : [WholeChunkIoImplementation:37] Error when performing master partial write. HTTP Status InternalServerError
      15:26:27.6: Warning: 0 : [IoManager:37] HTTP error (InternalServerError) performing Write I/O operation on provider.
      15:26:27.6: Warning: 0 : [IoManager:37] Error performing read-modify-write I/O operation on provider. Retrying. HTTP Status InternalServerError
      15:26:31.9: Warning: 0 : [ApiGoogleDrive:37] Google Drive returned error (notFound): File not found: 1MhgSaAvhGpIjRBQnrE6ngWuIvXNzM4P4.
      15:26:31.9: Warning: 0 : [ApiHttp:37] HTTP protocol exception (Code=NotFound).
      15:26:38.8: Information: 0 : [IoManager:48] All writes complete.

    I did see similar messages for another Chunk:138 twice as well

    Appreciate the help!


  2. So I have noticed that every time I attach and unlock a cloud drive I get the following warning:
      Warning: 0 : [PinDiskMetadata] Error pinning file system metadata. The request could not be performed because of an I/O device error
    Then when the timer expires for the next metadata operation (I think it is an hour) the Pinning metadata starts and normally completes without error and warning.

    I know its marked warning but I am still curious if this is worth looking into or just ignore.
    Thanks
     


  3. Awesome,

    Just an FYI too, I ended up having a Windows Update and a forced reboot. I have attached/detached my cloud drives a few times and I am no longer seeing this issue. I am not sure if this means I will never see it again. Maybe it was something related to the fact that it was the first time I ever installed CloudDrive and the first drive I ever created? Also when I created subsequent drives I did not get the format warning and CloudDrive was able to successfully format the disk without me needing to manually do it.

    Just thought I would pass this along, the ticket you opened on my behalf probably can move even lower on the list, but probably still worth looking at, at some point.

    Thanks!


  4. 4 hours ago, Christopher (Drashna) said:

    The box for the capacity is a text box. You can type on any value you want (that ... is supported, at least, so up to 1PB). As long as your provider has the free space for it. 

     

    Just remember that the largest cluster (allocation unit) size may be 64kb on most versions of Windows, which means 256TB volume, max.  

    Also, note that you may not want to have partitions/volumes that are larger than 63TBs, as Windows has issues with disk checking if the volume is NTFS and 64TBs or larger...  You can partition and pool the partitions to avoid the issue, if needed... But ....

    Thanks so much for the information, much appreciated.
    I thought I had tried this after selecting the 10TB from the drop down. But I don't think I cleared it out first.

    Is there any recommended or general practice for sizes for a GSuite unlimited Google Drive location, I would like to create a single storage drive as large as I can without running into problems down the road?  Based on what you have said I would guess anything under 63 TB would be fine?




  5. I have been reading the documentation regarding maximum drive sizes for CloudDrive.
    So far I have found:
      The absolute maximum size of your cloud drive is 1 PB, but it may be further limited by the Windows file system.
      For example, the maximum size of a NTFS volume using 4 KB clusters (which is common) is 16 TB.
      Cluster sizes on NTFS:
        4 KB = 16 TB maximum drive size

    However in the CloudDrive UI I cannot create a drive larger than 10 TB? Does this make sense, did I just miss this in the documentation somewhere?

    I am running:
      Windows 10 1709 16299.309
      StableBit CloudDrive 1.0.2.976

    Thanks!


  6. I am a first time user of the CloudDrive software. I am trying to learn as I go here while using it.

    I am running:
      Windows 10 1709 16299.309
      StableBit CloudDrive 1.0.2.976

    I created:
      Google Drive cloud drive
      Name: GD00001
      Cloud drive size: 4.00 TB
      Local cache size: 4.00 GB
      Cache Type: Expandable (recommended)
      Full drive encryption enabled
        Password key

    The first issue I have encountered is a message after creation in the CloudDrive notifications that I need to manually initialize and format the drive.
    I did go ahead and do this through Windows Disk Management using all defaults for NTFS with a drive label of GD00001

    I have been using the drive copying/deleting/renaming/streaming/opening/etc with roughly 100+GB of data and all seems to working quite nicely.
    Now I am just going through the UI to get myself familiar with the other options/logs/etc.

    I noticed the following message being repeated roughly every minute in the Service Log:
      Warning: 0 : [PinDiskMetadata] Cloud drive is not found in VDS' basic disks collection.

    This seems to be the only message in the Service Log. I know it is just a warning but I am curious about it and whether or not I should or need to remedy this.

    I also noticed in the drive properties for the disk in Windows Disk Management Events the following:
      Covecube Virtual Disk

      3/24/2018 4:16:11 PM  Device not migrated

      Device SCSI\DiskCOVECUBECloudFs_________0001\1&2afd7d61&0&{e75ddbfc-175e-45b8-8163-85720eeaaaa6} was not migrated due to partial or ambiguous match.

      Last Device Instance Id: USBSTOR\Disk&Ven_&Prod_Patriot_Memory&Rev_PMAP\120107930D000028&0
      Class Guid: {4D36E967-E325-11CE-BFC1-08002BE10318}
      Location Path: 
      Migration Rank: 0xF000FFFF8000F130
      Present: false
      Status: 0xC0000719

    That Patriot_Memory is likely an old USB drive which is not currently connected. Right now I have no USB drives connected to my machine.

    Any help or insight is greatly appreciated.
    Thanks!

×
×
  • Create New...