-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improper declaration of a faulty sector #3522
Comments
It has happened to me twice, where a sector in the process of finishing C2,(or just finished sealing, but not yet transferred to the storage drive) is included in a sector check and declared faulty. corresponding lines show 2020-09-07T19:24:01.594-0400 INFO rpc go-jsonrpc@v0.1.2-0.20200822201400-474f4fdccc52/client.go:213 rpc output message buffer {"n": 2} 2020-09-07T19:24:31.417-0400 WARN advmgr sector-storage/faults.go:54 CheckProvable Sector FAULT: cache an/or sealed paths not found {"sector": {"Miner":15927,"Number":58}, "sealed": "", "cache": ""} 2020-09-07T19:26:32.067-0400 INFO storageadapter storageadapter/provider.go:284 Storage deal 89018 activated at epoch 40486 2020-09-07T19:27:34.465-0400 DEBUG stores stores/util_unix.go:28 move sector data {"from": "/media/chris/storage2/filecoinStore/unsealed/fetching/s-t015927-58", "to": "/media/chris/storage2/filecoinStore/unsealed/s-t015927-58"} The system is looking for sector 58, It has finished sealing, but time needs to be given for the files to be transferred to the proper drive. 2020-09-07T19:21:56.728 INFO filcrypto::proofs::api > seal_commit_phase2: finish 2020-09-07T19:26:00.919-0400 INFO stores stores/remote.go:221 Fetch http://127.0.0.1:5678/remote/unsealed/s-t015927-58 -> /media/chris/Seal_2/filecoinSeal/unsealed/fetching/s-t015927-58 |
should be fixed by #3839 |
Please provide all the information requested here to help us troubleshoot "commit failed" issues.
If the information requested is missing, we will probably have to just ask you to provide it anyway,
before we can help debug.
Describe the problem
A windowedPost was taking place, I believe, as a sector was completing sealing and error
message for a faulty sector came up.
2020-09-02T18:54:30.391-0400 INFO storageminer storage/wdpost_sched.go:208 at 26029, doPost for P 23264, dd 46
2020-09-02T18:54:30.914-0400 WARN advmgr sector-storage/faults.go:54 CheckProvable Sector FAULT: cache an/or sealed paths not found {"sector": {"Miner":15927,"Number":17}, "sealed": "", "cache": ""}
2020-09-02T18:54:30.915-0400 WARN storageminer storage/wdpost_run.go:102 Checked sectors {"checked": 17, "good": 16}
2020-09-02T18:54:30.916-0400 ERROR storageminer storage/wdpost_run.go:251 DETECTED FAULTY SECTORS, declaring faults {"count": 1}
2020-09-02T18:54:33.490-0400 WARN storageminer storage/wdpost_run.go:273 declare faults Message CID {"cid": "bafy2bzacebt5haqcdrru4felpomsc3xachtq2ma3dqf25bczyz5zziyu5drya"}
It seems it is looking for storage path for sector 17, but i am not sure. At this time though sector 17 was not finished, in commit or commitWait. Sector 17 would be the 18th sector, and only 17 were checked.
lotus-miner sectors status --log 17
SectorID: 17
Status: Proving
CIDcommD: baga6ea4seaqe6mt75ils2j4tuyhrbsl3nfaw4l6eqy2ftrombhglgt2ftae34hy
CIDcommR: bagboea4b5abcatwahuxzmwilnnpc56obll3boafd2fqeot6sog5zq4c7vxtredr4
Ticket: c5cd035c862ec9a407993385a0f9f707273bf4e01d7bd6fa71f1f41aafefee49
TicketH: 24159
Seed: 8e7f88fb84fdf8e577ee137ebe73187986ba2fe8e79fb67b7250fc08c9de4268
SeedH: 25914
Precommit: bafy2bzacec4tkpxwjsbm5tnkoer7l57nesxqgwv3qsz2eprzcqyhupr4vkery
Commit: bafy2bzaceac34ddv5p3bhhen7nvkwqdeu46tdvn3all2ln3k4rk5voluuwnyy
Proof: a70b8994e1e57bb674dfea8cf4eebfe4ebc4ca239776a01800752b59e46e7546343ce4cbe278f5419bcfae915958fb63b941c1adacfead23068a758d03130a3a2465aad102bf17ad0101254f5f4dab6b164240ad12cd0c06d8d9e0078e30b3cd13607aa8944d0b7945d470c9db433304d5093586038f25a770159ff585fdb2ae9b31ee84627000199f793a72197a206093cc20ccc5449d915e2be0a185758fb429ae1f00009fcbfb3dbb3004c7d35fd14a391904af5f422668d1beaa211dc5b3b34745e904a1381a8d6023913a9ef739fdfd2dd7d74f42cd79a1d27154891005723e7ee9fd132354161cbf69a9eb0cfa921f1aed31455145282fe8247b233155b08b4234c7d1bfaf93fbdebae43d5f832c38c4d01c560baf84ff55ce837afbe914444c6d38a328f8d4202ade0657375562a376f1a45458845ecdc30d22ed35ed77787281a2cbef944b6d520bbcee3068a0ddca650cc052631a6193417aa219f9a522220af5f42c6f54bee3b701b76a22191afad10ce8cd4b2b0d92c040350a36ab83db3b25a33c24d2531740424d605aa2f58e540990ed9c4a5950e356f71de377eec8ffce22132c4434d20295d434178c327b9f8c515db3535f920d56d60344f3a22eb22bf003918fcbf2cb952cd63ba9a39b8af4dfcf9f1ab639db8afdd9700950c296e5e8aea1aea19693e6b2537c14e092904d532fa39ddb4b7969d06184d4c46f61456f9efe1c4962602498adb8afea441bd4eddf518a9a4b10e60ff9514c2a8067e2f2e112b7f93be99e8b65f39e9d890df5d225e75b5712217caa3fc885e98546c4081fa9538dfc5163a1fe868e5c744155e6c37c5908d88c08727da20ad722086b180453da4870f05bdfc08083f9a5e9c7c921814746c8b7c82d4b3732a81e0b7f37e242cdc434e298fc34e83b3fdec81899fb920e11dd8e8b732bb10829d84a048a90e70d62b1be73c3c0bb5249c892bdee684886c2d702d4eee5b85eeace6db0e4e6b0411ecc8212803200a061d3027c745f297ba1e0f88467f8ab007e79b810feff1ce3c4be6bfc7a58c326c82466b3ca2a6af975d2a4ed1d2a7099eb556497c759a13f49681a812cc8f48d4b41b6f9955c93419e3a7f46c477bd93f545b481908d1a7909a982801db4ca85a78e2c10265b1542988af896f43074b67769662dc4ff3240d9c8c0ec9c0f8d8b1cf8ec72f8a1a5d2cb07333f0128bb1525df74c1dd17ddf9377955416999be6ef06f36b73a6759746310459d33b8553aab7866b4b9849f9e4c463ede19027f97e150dd280e370275fc03ad39df3ca57c08f1873bd485f2a18c19e12078a76019a76b4d3c394a0a70543dfa8dd9fe498821155338ab5f6a61f90ea78f7cf1ce62b4319227e859ca1057ee65c0c4e15f204e7202adf39d686321a8a62a3b68be98cd9bd9875eaccb5699d55768cbd0ce32b642bf0f44f39d3576074602d638839d7cd79e0d0f3298c53fd163a487edb410565078f1a11bc9d8ba3215c234b0e569d6a2c34936e30f1324673e9ca0238e6450bd0f1063d8c96f695790635768f18a3d0215082dd41c911fbe6d0a3df6d186d095801d82a8de2ba3faf760cc66832eeac582ed7d32702f83ab5286bf0fc7b9fa171dfc4e1eb7d64561846bdb074e2d51270832cefbb1002defd31718fadb8462bb3d42bede02c821ad4cd2a615af976be4e7016737be3ed898dd88f35d2c3c186561c680ed06c6c766d7a0edc4c310a8a7ce83154b8890b59fd54857f2fc198c8045ebe19b37c1c7b3b43309316170056e7f433d8679b5e356bcdfe5a26838b5e10dabcb3cbfe6696b0832e32222acbdf00eab81ed87c54336abffdee521a658897f8c240ddd0d30f764f516263e75dbc020e00a332295611e1f48baf64a8bcf06e3e32e622c8841c052f7a5fc3a4b5abfae300e32d81951421ff8b11feccbd28c9b4f1025a31f6960838172f34b90507b72e2a62bd75fd0f3d9c7de01ee73901e73fd306cd93bf19858e42a53b4a9e360d7ac8ec57f3084d8f8016f5c101173ec1fba8bdeb353656bfaa24137795dc567c9aaf3d999ce3e19bae3973d41913ee3d7c6c2be364ad8ba840fcec6aa88a99325d30ec39b173b6e5092f6a628f8220fdffd1e11c5013f808c589afda00596fbefbc161f66dbce12691f1fdfb2b1cbf8317d9f2e0230cd99e1396ff49b11c697bee7a08f6e5f475096a6271e8ec728958c75bc054e011d244e2a2883108f57235b6758c38e7697190f8c07dce69b466a4687d61109a23e3876e56daa98bc71a9ba77fdbd248742cdc370cfdfcc151229de1144646e74e9d85f71405f8fa3bbaf09e0b06569d5a74745f7db0b82973717dc7b9bb8f2e5006835d4ec907cae79d049dab47508353608fd6aa6fbb29ead9aa74f0f17841a9f8cf75d399d8b4fe221ba08d048cffe9f213388bfa372a59bffe4d54348f4fe294f4a4d9250d78f4d09ec23debfc17bc5ffe760d5579d738ed1521b1236bc6d2f22f967678f168767c250c3946a69782f1c4e421df7030d1af2704fdc980613b78d7d8ea2d2cb1ebb3ba2d65558b26640388fbd729c5116969716be41d6a85eedd266cbf46a8eb4762eeadfbb5b9252b50c1a4010975c0e4a999b42a52e005fa6fe3495b3f472a867c9d2545094d1a0502a205fe3f633c4c6322a719343053b7a07b080fa0b0f6ec7ac4e5005d1111368dd9a9915031a
Deals: [66664 66815 67153 0 0 0 0 0 0 0]
Retries: 0
Event Log:
0. 2020-09-02 09:33:29 -0400 EDT: [event;sealing.SectorStart] {"User":{"ID":17,"SectorType":3}}
If you have modified parts of lotus, please describe which areas were modified,
and the scope of those modifications
occurred on 5.7 updated to
Daemon: 0.5.8+git.5426ef0b.dirty+api0.14.0
Local: lotus version 0.5.8+git.5426ef0b.dirty
The text was updated successfully, but these errors were encountered: