What does "GetDiskFreeSpace failed" error mean in Blago's miner?
-
Today I have been getting the "GetDiskFreeSpace failed" error in Blago's miner, and would like to know what it means.
-
@Propagandalf that's happened to me when i was optimizing, uploading and downloading all to the same disk. So i'm guessing that's something to do to your disk cache being full...
-
@Propagandalf with the amount of plots you have you might be better off on pool.burst-team.us , but thats just my take on it
-
@ddos 6TB - pool.burstcoin.biz or pool.burstcoin.eu would be appropriate. The entry bar for pool/burst-team.us is higher than 6.
-
@Propagandalf Interestingly, the first time I saw this error. Can you give extended information about the system (HDD / USB, OS, cluster size of F: and E: ) ?
-
@Blago After I restarted my machine (it had been running for many days already), the problem disappeared. Although, I don't think the error actually affected my mining, as I got confirmed deadlines anyway.
I am running a Lenovo Y50 laptop with windows 10, 1x internal SSD, 2x external HDD (Seagate) connected through a USB 3 hub into a USB 3 port. F and E are the externals, and both have 4 KB cluster size.
-
@Propagandalf seems USB-hub can't access for 2 HDDs in parallel and one of them get error.
if you see error - restart system, coz miner skip the plot at reading after error
-
@Blago I have to disagree cause I have a usb 2.0 hub with 2 parallel hdd and have no problem. But I see he is talking about 2 usb 3.0 so it maybe a power issue! Does each hdd have its own power supply?
-
@Blago I have only seen this error two or three times and each time I could tell it was on a plot that I had on microsoft one cloud. This makes since because Microsoft has trouble maintaining a good connection.
In my case it was my setup for sure. Just throwing that out there
-
@Blago @tross @crutsy
Based on your feedback I could have maybe yanked the usb hub cable so it disconnected and connected again, causing some kind of issue or something... However, I totally forgot that drive G with 56 GB is a Google drive, so that might have been the one acting up!
