Unexplained SealFailed

[askender]

Describe the bug
RT: Unexplained SealFailed

To Reproduce
Steps to reproduce the behavior:

1. Run:

lotus-storage-miner init --actor=t044779 --owner=t3uooxk5q5f7tkchzkt5yidnzrquigbcbxiziqrqp7g7sdx5zazo2mip2nuoibqmykquomer3zuwf5er4kif6a
lotus-storage-miner run
lotus-storage-miner pledge-sector

2. See error

2020-04-16T22:10:25.968+0800	INFO	build	go-paramfetch@v0.0.1/paramfetch.go:127	Parameter file /var/tmp/filecoin-proof-parameters/v20-proof-of-spacetime-election-5f585aca354eb68e411c8582ed0efd800792430e4e76d73468c4fc03f1a8d6d2.vk is ok
2020-04-16T22:10:26.727+0800	INFO	build	go-paramfetch@v0.0.1/paramfetch.go:127	Parameter file /var/tmp/filecoin-proof-parameters/v20-proof-of-spacetime-election-5f585aca354eb68e411c8582ed0efd800792430e4e76d73468c4fc03f1a8d6d2.params is ok
2020-04-16T22:11:08.804+0800	INFO	build	go-paramfetch@v0.0.1/paramfetch.go:127	Parameter file /var/tmp/filecoin-proof-parameters/v20-stacked-proof-of-replication-b46f3a1051afbb67f70aae7082da95def62eee943662f3e1bf69837fb08aaae4.params is ok
2020-04-16T22:11:08.806+0800	WARN	deals	impl/provider_asks.go:86	no previous ask found, miner will not accept deals until a price is set
2020-04-16T22:11:08.810+0800	WARN	modules	modules/core.go:45	Generating new API secret
2020-04-16T22:11:08.810+0800	INFO	storageminer	storage/miner.go:112	starting up miner t044779, worker addr t3uooxk5q5f7tkchzkt5yidnzrquigbcbxiziqrqp7g7sdx5zazo2mip2nuoibqmykquomer3zuwf5er4kif6a
2020-04-16T22:11:08.815+0800	INFO	main	lotus-storage-miner/run.go:125	Remote version 0.2.8+git1120298b+api0.1.7
2020-04-16T22:20:00.206+0800	INFO	sectors	sealing/garbage.go:39	Pledge 1, contains []
2020-04-16T22:45:54.048+0800	INFO	sectors	sealing/garbage.go:63	Publishing deals for 1
2020-04-16T22:47:15.299+0800	INFO	sectors	sealing/garbage.go:99	Deals for sector 1: [1194628]
2020-04-16T23:07:46.310+0800	INFO	sectors	sealing/sealing.go:124	Start sealing 1
2020-04-16T23:07:46.327+0800	INFO	sectors	sealing/states.go:17	performing filling up rest of the sector...	{"sector": 1}
2020-04-16T23:07:46.334+0800	INFO	sectors	sealing/states.go:62	performing sector replication...	{"sector": 1}
2020-04-16T23:07:46.339+0800	WARN	sectors	sealing/fsm.go:279	sector 1 got error event sealing.SectorSealFailed: seal pre commit failed: getting cache dir: no available cache: no suitable path for sector fond
2020-04-16T23:07:46.474+0800	INFO	sectors	sealing/states_failed.go:21	SealFailed(1), waiting 59.52537311s before retrying
2020-04-16T23:08:46.005+0800	INFO	sectors	sealing/states.go:62	performing sector replication...	{"sector": 1}
2020-04-16T23:08:46.009+0800	WARN	sectors	sealing/fsm.go:279	sector 1 got error event sealing.SectorSealFailed: seal pre commit failed: getting cache dir: no available cache: no suitable path for sector fond
2020-04-16T23:08:46.119+0800	INFO	sectors	sealing/states_failed.go:21	SealFailed(1), waiting 59.880589073s before retrying
2020-04-16T23:09:46.001+0800	INFO	sectors	sealing/states.go:62	performing sector replication...	{"sector": 1}
2020-04-16T23:09:46.002+0800	WARN	sectors	sealing/fsm.go:279	sector 1 got error event sealing.SectorSealFailed: seal pre commit failed: getting cache dir: no available cache: no suitable path for sector fond
2020-04-16T23:09:46.196+0800	INFO	sectors	sealing/states_failed.go:21	SealFailed(1), waiting 59.803440678s before retrying
2020-04-16T23:10:46.005+0800	INFO	sectors	sealing/states.go:62	performing sector replication...	{"sector": 1}
2020-04-16T23:10:46.010+0800	WARN	sectors	sealing/fsm.go:279	sector 1 got error event sealing.SectorSealFailed: seal pre commit failed: getting cache dir: no available cache: no suitable path for sector fond
2020-04-16T23:10:46.091+0800	INFO	sectors	sealing/states_failed.go:21	SealFailed(1), waiting 59.908136055s before retrying
2020-04-16T23:11:46.005+0800	INFO	sectors	sealing/states.go:62	performing sector replication...	{"sector": 1}
2020-04-16T23:11:46.008+0800	WARN	sectors	sealing/fsm.go:279	sector 1 got error event sealing.SectorSealFailed: seal pre commit failed: getting cache dir: no available cache: no suitable path for sector fond
2020-04-16T23:11:46.092+0800	INFO	sectors	sealing/states_failed.go:21	SealFailed(1), waiting 59.907818307s before retrying

Expected behavior

• No SealFailed should happen
• if SealFailed happened, there should be error traceback in detail.

Version (run lotus --version):
lotus version 0.2.8+git1120298b

Others 1(may be related):

lotus/storage/sealing/fsm.go

Line 165 in 9935e3a

return m.handleSealFailed, nil

	case api.SealFailed:
		return m.handleSealFailed, nil

When willSealFailed happen?

Others 2(may be related):

2020-04-16T23:09:46.002+0800	WARN	sectors	sealing/fsm.go:279	sector 1 got error event sealing.SectorSealFailed: seal pre commit failed: getting cache dir: no available cache: no suitable path for sector fond

There is an error in the WARN log? What does that mean?

[askender]

related issue #1262 error: no suitable path for sector found

[askender]

Problem solved.
read the command lotus-storage-miner

GLOBAL OPTIONS:
   --storagerepo