Not sure if I'm doing this right :(
-
@luxe said in Not sure if I'm doing this right :(:
@TellezMiotta
Error code 1117 is generated by the Windows operating system and is always caused by I/O (Input / Output) throughput issues with either the disk or the controller that it is attached to.
Try tochkdsk d: /r /fsource: http://kb.macrium.com/KnowledgebaseArticle50130.aspx
Also you said you decreased memory?! Could maybe be a issue, use the size you initially had.
There is no problem with changing memory after a file has started. I have switched from 12 to 8 to 4 to .5 on the same file with no issues.
I would suggest if you have not already tried it, i assume this D: drive is internal. Take a small USB drive, hook it up and try to write to it. In this case you will have to decrease the nonces to the drive size, or just use -n 0 to fill the unused space. If you can write to it then there has to be something wrong with the d: drive.
-
This post is deleted!
-
@rds I have no USB drive to do that test on.... (yes, the d drive is an internal HDD) is there other way i can know if it is good or bad?
@luxe ... the file i downloaded from the website you posted recognized my .bat for eth mining as a virus... and it is not helping me out to scan my drive at all :S
-
@TellezMiotta sry for that, i just google the error ... will remove the link, mentioned that i could be scam ... did you try chkdsk ? Thats for sure no problem.
-
Im no sure how can i try that command? Should i write a bat file containing that line of instructions?
-
@TellezMiotta you can just start command line https://www.lifewire.com/how-to-open-command-prompt-2618089 and type it in there. Also a bat file would work.
I start command line via WIN+Q and type in cmd in search.
-
Ok i will translate what it says...
chkdsk could not run because the volume it's being used by another process. chkdsk could run if this volume could be previously released. ALL THE OPEN IDENTIFIERS WITH THIS VOLUME WILL NOT BE VALID.
Would you like to release this volume? Y/N
I have no idea of what that means or if I even translated correctly...
-
-
@TellezMiotta Guess it says: Stop all application accessing this drive, or chkdsk can not repair it. So if miner or plotter still running on this drive you have to close them first. Guess 'release Y' would block any other application from accessing the drive ... so would maybe also work. I would try close application accessing the drive and retry.
-
Ok... I just did that... It looks like running something or analyzing something.... so I must have done it correctly this time
-
This process look like is going to take a while as well... can I ETH mine while doing it? Please tell me that I will not have to start the plot ALL OVER AGAIN once this process is done... :S
-
@TellezMiotta Just do not access the drive while the repair is running, if it helps and all goes out fine, you should be able to continue plotting were it stopped .. but i can promise nothing :-)
-

This is a capture of the cmd window for the scan.... It looks like i can ETH mine while doing this....
-
-
@luxe ... is it normal that the process takes SO LONG? it says estimated remaining time: 277:28:01 and that hasn't moved in the last couple of hours :S
-
I mean... why you don't have at least a MINIMUM of suspicion that it could be the plotter itself what's wrong and that i should re download it and re install it? just wondering... After all that's what keeps crashing over and over...
-
@TellezMiotta The Error code 1117 you got has nothing to do with the plotter, it indicates a hardware issue ... i searched for a way to solve this issue, and what i found was that chkdsk could help (http://kb.macrium.com/KnowledgebaseArticle50130.aspx), i did not know that it would take that long ... i suggest just let it run ... another way could be to re-format the drive and start over with plotting ... i can not provide the perfect solution ... just assist and tell you, what i would do in such a case ... after all it is your decision how you want to contain ... as there is only a plotfile on that drive, there is no big risk in data get lost, so you could also just cancel that repair tool.
-
I understand... Well... As i told you... since i don't have a desktop... I have to plot the drives using the mining rigs... and that action stops the ETH mining... It is not profitable for me... I was willing to do so however just as an experiment... but re plotting would be a total waste of time o.O.... I think I will just run this chkdsk....
However... just in case i find a desktop... would re-formating the hdd make this error disappear?
One more thing... It stopped at 58% (aproximately) that means that, if i mine with the plot how it is... it would be like mining with 2.5 TB? right?
-
@TellezMiotta https://en.wikipedia.org/wiki/CHKDSK ... it can only repair problems in filesystem ... if there is a physical problem with your drive, it can not fix that.
-
@luxe said in Not sure if I'm doing this right :(:
@TellezMiotta The Error code 1117 you got has nothing to do with the plotter, it indicates a hardware issue ... i searched for a way to solve this issue, and what i found was that chkdsk could help (http://kb.macrium.com/KnowledgebaseArticle50130.aspx), i did not know that it would take that long ... i suggest just let it run ... another way could be to re-format the drive and start over with plotting ... i can not provide the perfect solution ... just assist and tell you, what i would do in such a case ... after all it is your decision how you want to contain ... as there is only a plotfile on that drive, there is no big risk in data get lost, so you could also just cancel that repair tool.
@TellezMiotta, If you do decide to abandon the half plotted file, I would:
-
download off the internet and install: AOMEI partition assistant (free)
-
download off the internet and install: HD Tune (free for 15 days)
-
Run AOMEI and delete all partitions on the drive.
-
Run HD Tune and do a write benchmark test, a read benchmark test and an error check (check the quick option or it will take forever).
If everything checks out then reformat the drive using either the Windows formatter or the AOMEI program. I format first with AOMEI then reformat with the Windows formatter and select 64k as the cluster size.
Then create the Burst and plots subdirectory on the newly formatter drive.
Then rerun xplotter as before with one big exception. Do not use -n 0 to fill the drive.
Plot the drive 1TB at a time. That way if there is an issue with any file you only have to deal with 1TB of replot not 4 or 5 or 8TB.
Here is a typical bat file to fill an 8TB drive.
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2700000000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2703815000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2707630000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2711445000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2715260000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2719075000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2722890000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2726705000 -n 3815000 -t 4 -path e:\burst\plots -mem 2GOnce you are done you will rerun the bat file, if everything worked out you will get an error saying the plot is already done for each file which is what you want to see. I usually write a second bat file with a pause between each
file to I can read the cmd window output to assure everything is ok.pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2700000000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2703815000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2707630000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2711445000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2715260000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2719075000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2722890000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pause
c:\burst\XPlotter.v1.0\XPlotter_avx.exe -id 23470867970884553098 -sn 2726705000 -n 3815000 -t 4 -path e:\burst\plots -mem 2G
pauseLook, you are frustrated, however, many here are trying to help you, for free. I and probably everyone else here went through growing pains as you are now. I was helped tremendously by many on this board when I first started mining Burst. I, and others are helping you now. I think when you pay your dues you will ultimately be in a position to help other newcomers.
-


