When `peers.dat` is corrupted an error message is shown: `Invalid or corrupt peers.dat (Checksum mismatch, data corrupted).` then the node restart.

Most of our users aren't really tech enough to manually delete the `peers.dat` files, nor can we detect it for them. It means that this error give us lot's of work on our support team when somebody is impacted.

`peers.dat` isn't an essential file, as such Bitcoin Core should just be fine restarting without crashing.

A bash workaround to detect the checksum mismatch would also considerably help us.
Delete(nId);
            }
        }
    }
    return fInsert;
}
bool AddrManImpl::Good_(const CService& addr, bool test_before_evict, NodeSeconds time)
{
    AssertLockHeld(cs);
    int nId;
    m_last_good = time;
    AddrInfo* pinfo = Find(addr, &nId);
    
    if (!pinfo) return false;
    AddrInfo& info = *pinfo;
    
    info.m_last_success = time;
    info.m_last_try = time;
    info.nAttempts = 0;
    
    
    
    if (info.fInTried) return false;
    
    if (!Assume(info.nRefCount > 0)) return false;
    
    int tried_bucket = info.GetTriedBucket(nKey, m_netgroupman);
    int tried_bucket_pos = info.GetBucketPosition(nKey, false, tried_bucket);
    
    if (test_before_evict && (vvTried[tried_bucket][tried_bucket_pos] != -1)) {