Comment 58 for bug 1705748

No, this seems to have been happening all along, if you look at the timings in earlier posts...see post #25

...but what throws me and makes it more obscure it that the suspend operations are logged on resume, and until yesterday I hadn't ever managed to check the drive was actually alive (I actually had assumed it wasn't, and the apparent delay was just until it was first accessed (var storing the logs is a mountpoint on one of the spinning SATA disks)