Replies: 2 comments 4 replies
-
|
Are you certain this is good advice? I believe that before a sector puts a message on chain such as PreCommit, you can/should use remove, but once you put a message on chain, you should really use terminate to reduce your penalty. |
Beta Was this translation helpful? Give feedback.
-
|
@stuberman yeah. i think i do the same thing as you said in the tutorial |
Beta Was this translation helpful? Give feedback.
-
|
@stuberman which part of my tutorial mislead you? |
Beta Was this translation helpful? Give feedback.
-
|
The question is how soon can you use terminate, can it be used during the SubmitPreCommitBatch task? |
Beta Was this translation helpful? Give feedback.
-
|
Ｉdon't think you can use terminate during SubmitPreCommitBatch. that's another problem when you get stuck in SubmitPreCommitBatch |
Beta Was this translation helpful? Give feedback.
-
|
If you are using venus, replace |
Beta Was this translation helpful? Give feedback.
-
How to properly delete sectors
Before you delete a sector please make sure that you have taken the necessary rescue measures, such as encountering storage failure, network failure, scheduling failure, etc. you should go through a series of debugging, troubleshooting , and finally consider deleting the sector, carefully delete the sector, do not forget that the command has an option --really-do-it
1: How to delete the sectors in packing,PreCommitFailed and SealPreCommit1Failed status?
These sectors can be deleted directly with the following command because they are not yet pledged. All sectors before the completion of precommit phase can be deleted by this method.
2: What if the delete status is PreCommit1, PreCommit2 and keeps getting stuck on sectors in those states?
1:First you should try the following command to delete
If the above two commands fail to remove, you can perform the following steps
2. Find a free worker (if all workers are working full, then you can remove it by executing
Disable all tasks, wait for the worker to finish executing the current task, there will be no more tasks, Then recover with the following command
create empty sector files with corresponding sector IDs in the unsealed and sealed directories of the LOTUS_WORKER_PATH of the worker, assuming the sector ID is 100
Then, in the unsealed and sealed directories respectively, execute.
3. Restart that worker, watch the Worker's log to see if the sector will start sealing, if it doesn't start sealing, you can restart Miner again.
4. After the sector starts to sealing and you can see it in the lotus-miner sealing jobs list, you can execute the command to terminate the task first.
5: Execute
3: What if the delete status is Committing and keeps getting stuck on sectors with those statuses?
1: Do the same for 2.1 2.2 2.3
2: After creating and restarting the Worker, the Sector will not appear in the list of lotus-miner sealing jobs, but will directly become CommitFailed, at this time, execute the following command to delete the Sector
4: It is not recommended to remove commitfaied. finalizedfailed and all sectors that completed precommit or completed provcommit
It is recommended to restore the error sector to the state before the error and redo this step for the error
5: How to delete a sector that cannot be recovered because of a storage failure
Delete sectors must be deleted on the chain first and then locally, so as to minimize the loss, please remember the order of execution, this is quite important
1: Execution
Delete sectors must be chained first and then deleted locally to minimize the loss.
The main purpose of this step is to clear the data on the chain and minimize the penalty
2: Wait until the sector status changes to finalfinality
3: Execute
The main effect of this step is to clear the storage
6: Remove the most common errors in sectors
Many people will directly execute: lotus-miner sectors remove --really-do-it , which is wrong. Then they can't find the sector number and can't terminate. In this case, you can remove the sectors by
to see the sector number, and then run
Thanks @Tears and @bugxzhu for their help
Beta Was this translation helpful? Give feedback.
All reactions