Then you’re good to go. No need to worry that the current db is corrupt.
Database corruption does not mean your media, drives, etc. have problems.
Database corruption usually occurs when Plex Media Server quits abnormally while reading/writing to the db.
An easy example is a power failure which crashes the NAS. The database files would not be closed correctly and the structure of the information is damaged.
There can be other causes as well.
Corruption can usually be fixed using the methods mentioned above.
It is something of which to be aware, but do not worry about it. It is a good idea to check the log files before performing a major PMS update. For example, the 1.40 release notes specifically mention database changes.
Plex Media Server can notify you, via a Plex mobile app, when it detects corruption.
In Settings → General, enable Push Notifications.
In the Plex mobile app, Settings → Notifications → Database Corruption Detected.
