After removing the bad drive, I now get the "plot block not found in free space" error when adding plots. Each plot I add ends up being corrupted (chia plots check reports it as unopenable) and it seems to usually corrupt a previously good plot as well. Do I have to start over? I have removed all the plots that the plot checker deems to be corrupted but this still happens.

szatmary / PlotFS

a fuse filesystem for efficiently storage of Chia plot files

MIT License

50 stars 9 forks source link

After removing the bad drive, I now get the "plot block not found in free space" error when adding plots. Each plot I add ends up being corrupted (chia plots check reports it as unopenable) and it seems to usually corrupt a previously good plot as well. Do I have to start over? I have removed all the plots that the plot checker deems to be corrupted but this still happens. #18

Open rabbitii opened 2 years ago

rabbitii commented 2 years ago

    @szatmary After removing the bad drive, I now get the "plot block not found in free space" error when adding plots. Each plot I add ends up being corrupted (chia plots check reports it as unopenable) and it seems to usually corrupt a previously good plot as well. Do I have to start over? I have removed all the plots that the plot checker deems to be corrupted but this still happens.

Originally posted by @ab0tj in https://github.com/szatmary/PlotFS/issues/11#issuecomment-1092994858

rabbitii commented 2 years ago

Any fix for this problem?

mower7 commented 2 years ago

I had a drive go south on me.. And If I remember right, I just needed to remove all the plots that were associated with that drive.. (basically try to open up all the plots with a script, and any that failed to open I removed). Then removed the offending device.. And then everything was happy.. (and I could add drives and plots again)

I suppose there could be some unhappiness if it was done in a different order ?

The szatmary did talk of a rebuilding utility as a twinkle in his eye.. might want to reach out to him..

johnathon-b commented 2 years ago

I had a drive go south on me.. And If I remember right, I just needed to remove all the plots that were associated with that drive.. (basically try to open up all the plots with a script, and any that failed to open I removed). Then removed the offending device.. And then everything was happy.. (and I could add drives and plots again)

This is how I handled a failing drive.

plotfs --remove_plot $PLOT_ID
plotfs --remove_plot $PLOT_ID
plotfs --remove_plot $PLOT_ID
plotfs --remove_plot $PLOT_ID
....
plotfs --remove_device $DEVICE_ID

The $PLOT_ID is the GUID within the name of the plot file.

example: plot-k32-2022-08-07-11-59-88d857cd633e7ce0e487d93a2ed28e949901579260d2048ff57d2cdddb65e71d.plot

plotfs --remove_plot 88d857cd633e7ce0e487d93a2ed28e949901579260d2048ff57d2cdddb65e71d

benengele commented 1 year ago

I am getting the similar errors, see below. Plots I am adding are consistent anyways.

warning: failed to open device: /
warning: failed to open device: /
warning: failed to open device: /
warning: plot block not found in freespace
warning: plot block not found in freespace
warning: plot block not found in freespace
warning: plot block not found in freespace
warning: plot block not found in freespace