Error reading file
-
@Jumper chkdsk might not be giving you the full picture. test your drives with the tool below, it might reveal more info regarding your drives.
http://rwthaachen.dl.osdn.jp/crystaldiskinfo/65980/CrystalDiskInfo7_0_3ShizukuUltimate-en.exe
-
I installed it and this is what shown for my G derive:
and the bottom part of the list:
Do you see anything there which can be the issue?
-
@Jumper can you check RAM? http://www.memtest86.com/download.htm (need to create a bootable USB Drive / CD and need some hours for testing)
OS copy data to RAM, then miner read it.@iKnow0 miner do the same (if "UseHDDWakeUp": true) - reads list of directory every 4 mins
-
@Jumper Your disk looks fine, any errors would be highlighted by CrystalDisk. How are the disks connected, each on a separate USB port or through an external USB hub. Are they USB 2.0 or USB 3.0. (do they have the latest drivers). Have you tried other usb cables? Have you also tried running just one disk at a time to see it there is anything different.
-
@Jumper Just noticed there is a caution on your F: drive, which parameter is giving the caution?
-
I have already done that and there was no RAM error
Will test all my disk one by one and then recreate the plot file as well.
What I do not understand that if there would be an issue with USB cable, USB 2 or 3 type why the C drive also give the same error time to time?
If the drive is faulty, why it can read it for 30 min 1 hours then display the error? Why when I simply restart the miner the error goes away for another 30 min 1 hour?
I am working in IT so yes, i have done some test already but these things are just not make any sense.
So as a last resort, will do a test, disk by disk, re-plotting them and will see where the issue start.
Will let you guys know my findings.
-
C drive is in the laptop. Is an SSD drive
the others are USB drives with their own power supply, connected to USB 2 ports. No USB hub at this stage.
Where did you see the "Caution" for my F drive? I did not posted any screenshot related to F drive as far I know.
-
-
Oh I see. Will check it. Will deep format the drives and will do a check on them before creating plot file.
Thanks for the help so far.
-
@Jumper As all the drives are read in parallel, the caution on the F: drive could be causing the (CRC error=23) error. The reason why the error is intermittent may be that only when you read a certain part of the F: drive does it gives the error, as far as i know only a tiny fraction of each drive gets read each time for each mining round, so it would take a good few rounds to find the damaged section. Disconnect drive F: and see does the rest work ok.
-
That would make sense, yes.
I am started to format the E drive.
For the miner, I set it to use the G drive only, so I am monitoring if it would give any error.
-
Quick update here:
Yesterday, I did disconnected the E and F drive, and left the miner running with internal C and USB G drive.
I did not see any error since which is more that 12 hours now. Best result so far without having an error.
So this kind of confirms that one problematic drive can trigger errors in a perfectly fine drives as well.
@Blago: Can you modify the miner in a way that if an error is detected in a drive/plot file it will skip it, so miner will not trigger error in the other drives, or something similar?
As for now, I have deep formatted the E and F drive, run check on them but did not found any error so I am recreating currently the plots file, and once ready, will add it to the miner.
Let see how it goes.
-
@Jumper done, I make it for future version.
If miner got error - you will see errors nonces/stagger times and then will try to read next plot
-
Thanks.
I still confirm that with C and G drive, there is no error :) I almost finished re-plotting the E drive so in few minutes, I will add it to the miner and will see how it performs.
I also have a question: I think I hooked with Burstcoin, so I have played with creating my own pool. On a virtualbox/win7 image I was able to set it up in about an hour. really easy. However, my question is: Is it worth to run my own pool to use by myself and/or let others use it as well?
(If someone want to know how easy to set up a pool, I can write a step by step instruction in a new thread.)
-
@Jumper if you want be pool's owner - why not?
If you will use pool for yourself - don't do it, better use solo mode
-
hey.. I hope some is able to help me :(
Burst Mining (Wallet Miner) was working for months now... no issues!
Different drives (SATA + USB 3.0)After I made the update to 3.9.3 I´m getting read errors... after a few minutes / seconds...
- it is not just one drive
- PlotsChecker --> no issues
- HDD check --> 100% working
I have no ideas anymore :/ since this started with the update obviously..
-
@thedue can you post a screenshot?
-
sure.. I already deleted lots of plots until I found out that this happens to every HDD :/
-
@thedue seems HDD H/W error at drive "I". can you send to me miner's logs files from Logs folder?
blagodarenko@gmail.com
-
sent you some
plus I disconnected drive I (it is slower because it´s connected through USB 3.0 instead of SATA btw) and trying without it right now
