Duet2 RepRap v2.x to v3.41 upgrade

BlueDust

I finally upgraded my CoreXY to RepRap v3. Have been dreading it as, at the time the printer was having issues and wanted to get it working again first. Still having those issues but this past week thought to upgrade it anyways (might as well try to see if it fixes it right?).

The upgrade went as expected. Upgraded to v3.01 first and then when upgrading to 3.41 I had a problem.
The Duet2 was not accessible at all. Over the network, or via Panel Due.
After some troubleshooting and no luck, I put the SD card into my PC to see what I had and it was not seen by the PC. Put the config on a new card, and plugged that into the Duet2, and it started up with no problems.

I want to believe the card just died on its own (no fault to the board), but is it possible that the card was finished off by the update process? If possible, how? Could this be a warning of things to come?
This all just sounds unlikely, and betting this was just a bad coincidence.

Phaedrux

Depending on the age of the card it could have been the additional writes from all the DWC files that finally did it in. SD card writes are pretty limited. Such is the nature of flash. I can't remember ever seeing a failure of the card on firmware update before, so it's likely a coincidence rather than an issue, otherwise a lot more people would have reported it by now.

BlueDust

@phaedrux
That was my thought. It was just finished off.
You pretty much confirm that by verifying this situation was never seen before.

This is what I am currently thinking in regards to possible wear on the SD.
This SD card is a 16GB SAN Disk, and I may have only deleted a large number the gcode files printed 3 times over the last two years so there wasn't a lot of read/write/delete actions (except for the log file, and that was also never deleted).
So the config and other sys files were the only thing that had any read/writes that would matter and they are not really changed much once the printer is working. So unless there was some sort of wear occurring (like caching space) that I was unaware of on the same physical block location on the SD card, I would guess it failed prematurely.

Thanks!