We have read it multiple times that mount points are breaking, were done wrong after moving a node or replacing the harddrive. This often results in the nodes being DQed for missing pieces.
This is my proposal to solve this problem:
When the node starts, it checks in with the satellite. Now without any files, the node doesn’t know if it is new or pretty old. So let the satellite answer the check-in with some information about the node (e.g. used space on the satellite or 20 random piece-ids or just node age and if data is being stored on the node).
The storagenode then realizes that it doesn’t have any of those files/no used space for storj and stays offline because the most likely case would be a wrong mounting point. The satellite could send the SNO an email and put the node into suspension mode.
This way the SNO gets a warning about his misconfiguration and can fix easily fix it. If he doesn’t fix it in time, the suspension becomes a DQ just like it was proposed in the downtime DQ mechanism.
That would solve a lot of unneeded DQs and frustration among SNOs as well as making the risk and fear of moving a storagenode a lot lower.
This way the SNO can correct his problem in suspension mode but we’re not even touching the area of recovering from missing files or getting new files that might need to be merged or similar.