Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

About Scuro

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. I downloaded and installed the latest beta because of failed duplications with a VM. I've since moved the VM off of drivepool. However drivepool will only load the UI on first boot and then fail to show it afterwards. Task manager shows Drivepool.ui.exe running in the background multiple times if clicked more then once. I'm not sure if this is a known issue. Drivepool is installed on a device running windows 10 1909
  2. As an update I was able to narrow down where the problem occurs. innodb_temp_data_file_path=/temp/ibtmp1:12M:autoextend:max:1G This variable, if selected on a drivepool mount, will generate the errors: 2018-12-05 11:03:42 0 [ERROR] InnoDB: Operating system error number 24 in a file operation. 2018-12-05 11:03:42 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2018-12-05 11:03:42 0 [ERROR] InnoDB: File \\.\D:: 'DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY)' returned OS error 224. And cause
  3. I've switched to Linux VMs for MariaDB. However, I still have my old database available to test this again on drivepool. I tested it and it resulted in the exact same errors again. I enabled logging and submitted it just now as described in http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection
  4. Scuro

    Can't Update DrivePool

    Nevermind. I figured it out. I like to run everything as services so service starts and stops are handled automatically and gracefully without logins. I had set many services to have drivepool dependency that stored data on the drivepool. MSI installer doesn't know how to handle the depency even though the service is not restarted till reboot? Anyways, removing drivepool dependencies allowed the update to finish installing. Is it possible for the MSI updater to handle drivepool dependencies so that I don't have to remove them every update?
  5. I am trying to update to latest beta version and every time I try to update, I get 0x80070643 error. Already tried restarting. Log wasn't helpful.
  6. Scuro

    New drive not balancing

    I am on which is newer (the latest release on http://dl.covecube.com/DrivePoolWindows/release/download/). I have "File placement rules respect real-time file placement limits set by the balancing plug-ins." and "Unless the drive is being emptied." unchecked.
  7. Scuro

    New drive not balancing

    Still not finishing it's balance. I believe I can tell why. Based on the balance targets, it is trying to balance my SSD that it is not able to add more data because of file placement restrictions. I only allow a few folders on my SSD. The balance plugin seems unaware of this and tries to balance regardless.
  8. Scuro

    New drive not balancing

    Just an update for this thread, I've updated to the latest version ( and still unable to get balance to finish. Drivepool will recognize it's unbalanced but will randomly stop balancing in the middle of it's balance task.
  9. Christopher, I have submitted another troubleshooter report to avoid confusion. I made sure mariadb was back on the pool before submitting. The errors returned again after moving it back to the pool. I moved it back off the pool after the troubleshooter was submitted.
  10. Thanks for your help B00ze. I however believe that is a Linux OS error code. Windows seems to have a limit around 17 million open files.
  11. I submitted the troubleshooter with the requested ticket ID in the thread I linked. Was that data lost or never make it?
  12. Thanks for your time Christopher. I already submitted a troubleshoot report in this thread: I am not sure if it would just be redundant for me to submit another. In that thread I had thought my problems were because of a new power supply I had gotten around the time the errors first started happening. After thinking about it, I remembered I switched the mariadb database to drivepool at roughly the same time I got the new case/power supply. So it should contain all the same data as mariadb was still on the drivepool at the time the troubleshooter was run.
  13. Windows 10 Pro version 1709 with stablebit RC. I have had zero problems and errors after moving the database off the drivepool. I had been hammering my head trying to figure out where all these IO errors were coming from and had thought it was a power supply in another thread (every drive was throwing IO errors in event log). Turns out I was getting those IO errors because every drive was part of the pool. Once I removed mariadb from the pool, it has been running flawlessly. Due to the instability of the OS as well as IO errors in event log, I don't believe incorrect permis
  14. Apache/PHP were also throwing errors at random for parse_ini_file() saying "parse_ini_file failed to open stream" when duplication was enabled. Placing the ini file used for the script outside of the pool on the same drives that were duplicated in the pool solved that problem as well. Edit: The drives that were used in the the drivepool for the database were SSDs that one shares with the OS and the other VMs. Neither have shown problems outside of using drivepool for mariadb or apache/php files with duplication enabled.
  15. Have you tested it with folder duplication? I have tested it outside of the pool now on the two drives I had it duplicated on with the exact same permissions. Both drives have completely solved all instability errors and problems if I use the database outside of the pool. The errors come back immediately if I copy it to the drivepool.
  • Create New...