HDDs not seen after resume from sleep - W8.1

Over the last week or so my system does not find the 3 spinner HDDs on resuming from sleep. My searching has not found a description of a similar issue. My system has 2 SSDs, (both single partition, the Intel 520 has w8.1 and all apps, the other SSD has W10TP) 3 HDDs, and 2 optical drives. On resume from sleep the 3 HDDs are missing, a reboot finds them again, and all is well till I put the system in sleep mode.
I am now not certain just when this issue began, I installed all the applicable November patch Tuesday updates, and the 2 out-of-band updates issued a week later. I also updated the Windows 10 Technical Preview when that was issued. The Windows 10 install is on a (single partition) separate SSD.
This issue also is present on resuming after sleep when running the Windows 10 TP.
I did not disconnect the other drives when updating W10. Could that be the culprit?
Motherboard is an ASUS P8Z77-V. I have reset the BIOS to "Optimized Defaults" - no change to this issue. All drives are visible in the BIOS screens, and on the Post screen.
My most recent image is nearly 2 months old (yes, I know I should image more frequently, but have been away.) So I'd like to find a fix to this issue without reverting that far back, if possible.
All suggestions appreciated. TIA
lmod

Have you tried disabling both Hibernation and Sleep in Power Options to see if that's where the problem lies? I find both features to be more problematic than they are worth, prefer the screen saver setting to blank the screen and the Windows key plus L to lock the screen.

Yes, all sleep, hybrid sleep and hibernation options have been set to "Never" since this issue appeared. But without effect. It was my procedure to manually invoke sleep when I was finished with my computer for the day.

I have exactly the same problem.
My two spinner HDDs are not accessible after resuming from sleep.

The problem only started yesterday.

I dual boot Windows 8.1 and 10 and the problem occurs in both operating systems.

I changed the SATA cables but it made no difference.

Then it is probably your Mother Board.

Thanks for the replies. I see The Doctor also has an ASUS mobo of the same family as mine, but a higher spec version. I have never used any Linux OS, so know nothing about them, but google sez that later versions do support S3 (suspend to RAM.)
@ The Doctor, do your Linux installations support S3? If so, do they resume from sleep OK with all drives seen?

Hi Imod,

I am starting to narrow the problem down a bit.

I have noticed that that if either Windows 8 or Windows 10 doesn't shut down cleanly, then whatever OS I boot up next has problems reading the secondary D: and E: disks. In this circumstance, Linux reports that the file system on these disks is unclean.

If I reboot and start either Windows 8.1 or 10, shut down cleanly and then boot into Linux, it sees the secondary disks as perfectly OK.

Linux has been OK with S3 sleep so far.

The Doctor said:

Hi Imod,

I am starting to narrow the problem down a bit.

I have noticed that that if either Windows 8 or Windows 10 doesn't shut down cleanly, then whatever OS I boot up next has problems reading the secondary D: and E: disks. In this circumstance, Linux reports that the file system on these disks is unclean.

If I reboot and start either Windows 8.1 or 10, shut down cleanly and then boot into Linux, it sees the secondary disks as perfectly OK.

Linux has been OK with S3 sleep so far.

Click to expand...

I think your observation that Linux is OK resuming from S3 absolves the motherboard. When you say, "shut down cleanly" do you mean that you shut down the system completely, rather than going into sleep mode? A "Restart" or a complete shutdown, and a power button start from the "off" state has always recovered the drives that are missing when I resume my system from S3.

Yes, confirming "reboot" means shutdown and restart, not sleep.

I recognise dual booting two different versions of Windows can cause problems, but I never had any problems dual booting Windows 7 and 8 as long as I didn't access the Win 8 system partition from Win 7 and vice versa.

In our case I am more inclined to suspect one of the following:

- an incorrect setting in the BIOS. My fiddling with the Secure Boot and Compatibility settings hasn't made any difference so far.

- the BIOS itself may be due for an update. My board's last BIOS update was 16-Sep-2013.

Well, the BIOS is 'old' - I also have version 2104 dated 2013 09 16. And that is the latest offered by ASUS. But I hadn't made any changes to the BIOS for a long time, certainly well before this issue surfaced. I wonder if the system is storing some flag when going into sleep that is misread when resuming.