Skip to content
Discussion options

You must be logged in to vote

I did find a work around for this issue if anyone needs assistance in this.
After some research I found that the miner was running C1 on these sectors and it was then getting stuck looking for the data to move forward to the next step.
Mine was for sector 630

I then shut down my miner and made a back up.
I created a dummy file in the sealed/ folder of my sealing repo called s-t047419-630 (touch /sealingrepo/sealed/s-t047419-630)
I also created a empty dir in the /cache folder of my sealing repo called s-t047419-630 (mkdir /sealingrepo/cache/s-t047419-630)

After that I rebooted miner and it then found the bad files and removed the sector.
Here is the log after miner rebooted and finally re…

Replies: 8 comments

Comment options

jennijuju
Sep 29, 2020
Maintainer Author

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

jennijuju
Nov 9, 2020
Maintainer Author

You must be logged in to vote
0 replies
Comment options

jennijuju
Nov 11, 2020
Maintainer Author

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by jennijuju
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sealing status/archived Archive label, use when closing/locking old discussions.
6 participants
Converted from issue

This discussion was converted from issue #4086 on June 18, 2021 05:18.