Pledge sectors not beeing sealed/proved after 3 initial sectors are proved

Does anyone know why after 3 sectors are sealed/proved, pledging more sectors does not make those new sectors “seal-able” anymore? i.e the miner stops working on those unsealed newly-pledged sectors

“lotus-storage-miner info” shows that 3 sectors (32GB) are proved and registered on the network, but “lotus-storage-miner sectors list” doesn’t show any of the newly pledged ones (although in the miner logs, it did register them when they were ‘pledged’. NOTE: those pledged sectors’ files are visible in the $LOTUS_STORAGE_PATH/unsealed/ directory.

There is no issue with available free disk space.

Can you clarify ‘those’ in this statement?

those pledged sectors’ files are visible in the $LOTUS_STORAGE_PATH/unsealed/ directory.

Are you talking about the sectors which are listed as proving or the additional sectors from running lotus-storage-miner sectors pledge

Can output of lotus-storage-miner sectors list might help answer your question.

It could be that you ran out of space and are unable to seal any new sectors.

To clarify and add more details to my question…

The “those” refers to the first 3 sectors that I pledged when I first started my miner.

When my miner was intialized, I ran the following command 3 times:

lotus-storage-miner sectors pledge

, and I let it run…and waited…and waited… and about 2 days later, I see that those sectors are registered on the Filecoin network, and the output of “lotus-storage-miner info” shows something like the following ( this is from memory; I have reset my miner and restarted afresh again):

# lotus-storage-miner info
Miner: t0121xxx
Sector Size: 32 GiB
Byte Power:   96 GiB / 24.01 PiB (0.0002%)
Actual Power: 96 Gi / 21 Pi (0.0002%)
        Committed: 96 GiB
        Proving: 96 GiB
Below minimum power threshold, no blocks will be won
Miner Balance: 0.000275176012032679
        PreCommit:   0
        Locked:      0.000267158129239418
        Available:   0.000008017882793261
Worker Balance: 49.999724823987915463
Market (Escrow):  0
Market (Locked):  0

Sectors:
        Total: 3
        Proving: 3

Essentially, it was showing a total 3 sectors, which were committed and yet continued to be in Proving state.

Whenever I ran “lotus-storage-miner sectors pledge”, the miner would not get to a point where it would show “Sectors: Total: 4 , or PreCommit1: 1, or PreCommit: 2, etc”.

The disks for the Worker Path and Storage Path had free space available (3TB).

I let it run for 2 more days, and then gave up… and reset the miner…

The proving state is the end state of a properly sealed and power providing sector.

I would expect that when running lotus-storage-miner sectors pledge for there to be, as you yourself expect, an increase in the total number of sectors and a new listing for PreCommit1 almost immediately (well, the Packing state is first, but that occurs fairly quickly. At minimum it should show up in the total, and under lotus-storage-miner sectors list. This might be an obscure bug.

I see. Thank you for the information.
It does look to be an obscure bug (and a confusing, confidence reducing event for a newbie).

Well, my “reset” miner has just finished proving 3 sectors again now. (This time, I pledge one sector at a time (after one is proved/committed), insteads of pledging 3 sectors at one time like I did the last time.)

AND! This time it seems to be working as expected.

Some output to share:

finished proving/committing 3 sectors (one at a time)

~# lotus-storage-miner info
Miner: t0121361
Sector Size: 32 GiB
Byte Power:   96 GiB / 25.28 PiB (0.0003%)
Actual Power: 96 Gi / 22 Pi (0.0004%)
        Committed: 96 GiB
        Proving: 96 GiB
Below minimum power threshold, no blocks will be won
Miner Balance: 0.000405198561783174
        PreCommit:   0
        Locked:      0.000393392725026705
        Available:   0.000011805836756469
Worker Balance: 49.999594801438137229
Market (Escrow):  0
Market (Locked):  0

Sectors:
        Total: 3
        Proving: 3

pledge one more (4th) sector:

~# lotus-storage-miner sectors pledge
[miner log]
    2020-07-15T22:28:48.146-0700    INFO    sectors storage-fsm@v0.0.0-20200625160832-379a4655b044/garbage.go:24    Pledge {121361 3}, contains []
    2020-07-15T22:28:48.147-0700    DEBUG   advmgr  sector-storage@v0.0.0-20200630180318-4c1968f62a8f/localworker.go:69     acquired sector {121361 3} (e:0; a:1): {{0 0} /lotus-storage/unsealed/s-t0121361-3  }

after ~10min:

[seal-worker log]
2020-07-15T22:39:21.702-0700    INFO    stores  stores/remote.go:165    Fetch http://127.0.0.1:2345/remote/unsealed/s-t0121361-3 -> /lotus-worker/unsealed/s-t0121361-3
2020-07-15T22:39:42.075-0700    INFO    stores  stores/remote.go:251    Delete http://127.0.0.1:2345/remote/unsealed/s-t0121361-3
2020-07-15T22:39:42.076-0700    DEBUG   advmgr  sector-storage@v0.0.0-20200630180318-4c1968f62a8f/localworker.go:69     acquired sector {121361 3} (e:1; a:0): {{0 0} /lotus-worker/unsealed/s-t0121361-3  }
2020-07-15T22:39:42.083-0700    DEBUG   advmgr  sector-storage@v0.0.0-20200630180318-4c1968f62a8f/localworker.go:69     acquired sector {121361 3} (e:1; a:6): {{0 0} /lotus-worker/unsealed/s-t0121361-3 /lotus-worker/sealed/s-t0121361-3 /lotus-worker/cache/s-t0121361-3}

lotus-storage-miner info output

~# lotus-storage-miner info
Miner: t0121361
Sector Size: 32 GiB
Byte Power:   96 GiB / 25.28 PiB (0.0003%)
Actual Power: 96 Gi / 22 Pi (0.0004%)
        Committed: 96 GiB
        Proving: 96 GiB
Below minimum power threshold, no blocks will be won
Miner Balance: 0.000405198561783174
        PreCommit:   0
        Locked:      0.000393392725026705
        Available:   0.000011805836756469
Worker Balance: 49.999594801438137229
Market (Escrow):  0
Market (Locked):  0

Sectors:
        Total: 4
        Proving: 3
        PreCommit1: 1

sectors listing

~# lotus-storage-miner sectors list
0: Proving    sSet: YES pSet: YES tktH: 82542 seedH: 86261 deals: [0]
1: Proving    sSet: YES pSet: YES tktH: 85788 seedH: 89483 deals: [0]
2: Proving    sSet: YES pSet: YES tktH: 90020 seedH: 93471 deals: [0]
3: PreCommit1 sSet: NO  pSet: NO  tktH: 0     seedH: 0     deals: [0]

Strange (but great!) that it is working this time! Maybe I just have to pledge one sector at a time to be “safe”…and to work around (maybe) some bugs or system limitation…