Not sure if I'm doing this right :(
-
@TellezMiotta Please post the command you try to restart xplotter with (content of bat file) ... also could you provide a screen of the plotfile folder ... was a 2nd file created with zero size ? To restart you need to specify the number of nonces (-n 7629448).
XPlotter_avx.exe -id 1272343243245029898 -sn 100000000 -n 7629448 -t 4 -path C:\data\burst -mem 4GThe problem i had was i tried to run the following an Xplotter tried to create a new file instead of finish the existing one.
XPlotter_avx.exe -id 1272343243245029898 -sn 100000000 -t 4 -path C:\data\burst -mem 4G
-
These are the screen shots
First... the folder that my hard drive has
secondly... a screen shot of my bat \
I have tried creating my own bat instead of using that one, I have also tried -t 1 instead of 2... nothing works
-
As you can see... I'm trying to mine as well to see where I am at this point... because im not willing to start all over again because I do not want to stop mining eth any longer :S... so please... PLEASE provide me with a solution in which i do not start ALL OVER AGAIN
-
@TellezMiotta Sadly you have another issue than i thought ... So if you start xplotter it crashes? You run it as admin? you could add an new line to bat file with 'pause' in it, so that command line does not disappear and you can maybe post a error. Not sure if '@pause' does the same.
Oh i see, you did that and get this 1117 error ...
-
the bat hast @pause in it already
This translates to ''Xploter_avi.exe stopped working'' (is in spanish)
-
-
@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.
-
@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....
