There are some third party tools that can access the drive info, windows has one built in from the CLI - Try this command:
wmic diskdrive get model,status,errordescription,lasterrorcode
If it says the drive status says OK, then generically I would say the disk is not in danger of failure.
You could also watch Resource Monitor (link at bottom of performance tab in Task manager) while loading up BC and see if you can find the process(s) eating your IO. Look at the disk tab, then look under disk activity, and sort by Total (highest to lowest).
I see sustained Reads of over 200MB/s off a SSD, pointing at my DB, so there is definitely a high IO demand on the SQL side during BC loadup. I watched the active query manager on the DB and now I see why. During loadup, BC requests a row count of every table, which on my system seems to average 250ms per table. I have 209 tables in my DB x 250ms average count query = ~52 seconds, which is basically what my startup time is.
@BrunDog - Do you know/can you ask what the purpose of the row count is on loadup?