Jump to content
Covecube Inc.

All Activity

This stream auto-updates     

  1. Today
  2. I'm running StableBit Scanner 2.5.4.3216. I've also had to change the driver I'm using back to the default Windows (non-UASP) driver, as the ASUS UAS Storage Driver seems to be a bit buggy, but this hasn't changed the lack of health data. With the ASUS UAS Storage Driver, attempting to do a surface scan causes the drive to stop responding after completing ~5% (read speed drops to 0 in Task Manager, but the disk remains 100% active), and it'll never pass that point even after stopping and restarting the scan. Switching back to using the default Windows driver (USB Mass Storage Device) allows the entire disk to be scanned without problems.
  3. Sorry, should be released now! http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.3.1008_x64_BETA.exe And yeah, this was kind of a weird bug. But it's fixed!
  4. Yesterday
  5. Could you open a ticket at https://stablebit.com/Contact? Also, unfortunately, it may not be something that is fixable. It looks like the data is corrupted. But if you could run the StableBit Troubleshooter after opening the ticket, we'll see what we can do. http://wiki.covecube.com/StableBit_Troubleshooter
  6. You need to pass through the disks. You CANNOT pass through the pool, since there is no actual data on the pool drive.
  7. Oh boy. I know that we've had issues with JMicron stuff. For this, the "Unsafe Direct I/O" option may need to be enabled. As for the Direct IO Test, it may not actually give info, because .... this isn't SMART data. It's NVMe Health info. It's a different protocol, and different info. However, it is shown in very similar ways. Also, what version of StableBit Scanner are you using?
  8. Yup, that would do it. And that's..... super annoying! >:(
  9. Well, I wouldn't recommend using A:\ or B:\ for the pool. There is some hard coded behavior for those letters, which you may not want. Specifically, it queries those drive frequently, so it may actually keep the pooled drives awaking. that said, try rebooting the system. Sometimes when too many drives come online in a short period of time, Windows will do this. If rebooting doesn't help, double check the UI, and make sure that you only have the one pool. Otherwise, try resetting the settings: http://wiki.covecube.com/StableBit_DrivePool_Q2299585B
  10. Yes, it is fine to delete these empty folders. Though you may want to remeasure the pool after removing them. As for how, I'm not really sure. I know there is a way to handle that, but ... it escapes me.
  11. @riahc3 I don't see a ticket for you, either with the account name here or with the email attached to the forum account. If you could, post a link to the ticket, or email me DIRECTLY at "christopher@covecube.com", and let me know.
  12. I was finally able to fix the situtation by detaching the cloud drive, then removing the cloud drive from the pool, rebooting, and re-attaching and adding it to the pool. Erroneous 0kb files that could not be accessed are now gone.
  13. I submitted a support ticket some days ago and I have not receieved any type of response.... Besides paying for the product itself, I did pay for support so I expect some kind of reaction....
  14. Last week
  15. Just want to confirm that the latest beta 2.2.3.1008 fully resolves the problem with the Dedupe role on Windows Server 2019. Thanks @Christopher (Drashna)!
  16. Did that it no go. The only option left is to recover files and create another one. I can understand file corruption but I wish MBR shouldn't be that easy to corrupt. I hope they fix the issue or add additional checks.
  17. Is more information needed to help me? Would love to sort this problem out ;-) . Uploadqueue is rising...
  18. I have no clue but sorta indicates to me that you need to pass the drives and create the Pool in the VM.
  19. I have an Icy Box IB-1816M-C31 USB 3.1 Gen 2 enclosure containing a 512GB Samsung 950 Pro NVMe SSD, for which Scanner cannot read the SMART data. This enclosure uses a JMicron JMS583 USB-NVMe bridge, and shows up as a UASP device using the ASUS UAS Storage Driver (removing this driver and using the default driver, which takes it out of UASP mode, doesn't change anything). CystalDiskInfo is able to read the SMART data, as is smartctl when run with the -d sntjmicron option to correctly identify the USB device. -d sntjmicronC:\Program Files\smartmontools\bin>smartctl -a -d sntjmicron /dev/sdg smartctl 7.0 2018-12-30 r4883 [x86_64-w64-mingw32-w10-1803] (sf-7.0-1) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: Samsung SSD 950 PRO 512GB Serial Number: S2GMNXAH113261W Firmware Version: 2B0QBXX7 PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Utilization: 237,899,358,208 [237 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 002538 5161b033cd Local Time is: Sat Jul 20 17:41:36 2019 GMTST Firmware Updates (0x06): 3 Slots Optional Admin Commands (0x0007): Security Format Frmw_DL Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.50W - - 0 0 0 0 5 5 1 + 5.80W - - 1 1 1 1 30 30 2 + 3.60W - - 2 2 2 2 100 100 3 - 0.0700W - - 3 3 3 3 500 5000 4 - 0.0050W - - 4 4 4 4 2000 22000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 51 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 2% Data Units Read: 40,017,269 [20.4 TB] Data Units Written: 74,499,658 [38.1 TB] Host Read Commands: 586,596,545 Host Write Commands: 842,689,794 Controller Busy Time: 3,890 Power Cycles: 3,841 Power On Hours: 10,578 Unsafe Shutdowns: 66 Media and Data Integrity Errors: 0 Error Information Log Entries: 13,386 Error Information (NVMe Log 0x01, max 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 13386 0 0x0b0e 0x4004 0x000 0 0 - 1 13385 0 0x0609 0x4004 0x000 0 0 - 2 13384 0 0x0508 0x4004 0x000 0 0 - 3 13383 0 0x0407 0x4004 0x000 0 0 - 4 13382 0 0x0306 0x4004 0x000 0 0 - 5 13381 0 0x0a06 0x4004 0x000 0 0 - 6 13380 0 0x010a 0x4004 0x000 0 0 - 7 13379 0 0x0e06 0x4004 0x000 0 0 - 8 13378 0 0x0d01 0x4004 0x000 0 0 - 9 13377 0 0x0c00 0x4004 0x000 0 0 - 10 13376 0 0x0b0f 0x4004 0x000 0 0 - 11 13375 0 0x0a0e 0x4004 0x000 0 0 - 12 13374 0 0x090d 0x4004 0x000 0 0 - 13 13373 0 0x080c 0x4004 0x000 0 0 - 14 13372 0 0x070b 0x4004 0x000 0 0 - 15 13371 0 0x060a 0x4004 0x000 0 0 - ... (48 entries not shown) The stickied Direct I/O Test tool cannot read the SMART data either - it can only retrieve the following SSD data, no matter what method is used: Version: 40 Model: SamsungSSD 950 PRO 2B0Q Serial number: DD56419883A90 Bus type: Usb Command queuing: True Device type: 0x00 Raw device properties: 0 Removable media: False Vendor ID: Samsung Product ID: SSD 950 PRO 2B0Q Product revision: 0204 Every other option shows as a red cross, unless ScsiPassthroughJmicron is selected. In that case, SMART status under Direct I/O becomes available (but not any other option), however it reports as Status: Failing
  20. I got a dedicated SSD for my cache, maybe that is why i never encountered it. Maybe your SSD's hit their max IOPS due to the OS and more stuff also running there?
  21. . FYI I can’t reproduce this reliably with test disk and doing deeper scan after testdisk will error out and cloud drive will show this error. I have set mine to 10 threads
  22. I should have asked this earlier..Fuck. I want to know Drivepool's recommendation: Create the pool on the hypervisor and pass that pool to the guest VM or Pass all disks to a VM and create the pool in the VM? ASAP please; Im setting this up and honestly forgot to ask.
  23. Okay folks, I believe I have solved my own issue. Apparently since all of my pool drives have no letters and whatever latest Windows updates may have caused all the drives to dismounted. My many attempts to uninstalled/reinstalled Drivepool could not bring the pool drives back. The way to fix my issue of missing drives is: - Diskpart - Enable Automount - Reboot All the drives magically came back YAY!
  24. My main and only drivepool was the A, the P showed up after a windows update. How can i safely remove the 2nd drive pool without losing my files? When i open the P drivepool it is empty there's no files in it.
  25. First time, a few days ago, Uninstall Drivepool, reboot and re-install Drivepool worked. Now, the same sequence does not work anymore as I tried multiple times. Chris mentioned Windows upgrade might have caused issues with the driver. My pool has 28 drives and it shows: I need some helps ASAP please... Thanks
  26. The fix is, as suggested by Chimera is: Uninstall Drivepool, reboot and re-install Drivepool. I previously had a Beta version installed but replaced it with the Stable version just to be sure. That fixed it for me. Good luck, Kevin
  27. 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?
  1. Load more activity

Announcements

×
×
  • Create New...