RAM disk loses shares after reboot

Started by Asad

Asad

RAM disk loses shares after reboot   30 November 2022, 10:54

Folder on RAM disk is shared.
After Server is rebooted, the SMB share on RAM disk is unshared.
To fix, the folder need to be shared again.
But after reboot Windows SMB share on RAM disk is unshared again.
The folder is configured/added in RAM disk as well.

OS: Windows Server 2019 (standard edition).
SoftPerfect Support forum - Ann avatar image
Ann

Re: RAM disk loses shares after reboot   30 November 2022, 11:05

Firstly, please make sure you are using a RAM disk that is mounted At Startup, not at logon. A boot-time disk is initialised much earlier and is available to system services.

Secondly, try ticking Hard Disk Emulation in the RAM Disk properties. Windows treats those disks differently, and we received feedback from other customers reporting that this helped them with the same issue.

And lastly, it may be a timing issue where a RAM disk becomes ready after the Server service has started. This is more likely to happen for large RAM disks as they take more time to initialise. The easiest workaround here is to change the Server service to Delayed Start. Delayed start usually takes place 2-3 minutes after boot, by which time the RAM disk should be ready.

SoftPerfect support forum
Asad

RAM disk loses shares after reboot - Solved   01 December 2022, 09:32

Thanks, that works! Enabling Hard Disk Emulation in the RAM Disk properties solved the issue.

Reply to this topic

Sometimes you can find a solution faster if you try the forum search, have a look at the knowledge base, or check the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • Write in English. If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 **      **  **     **  ********   ********   **    ** 
 **  **  **  ***   ***  **     **  **     **  ***   ** 
 **  **  **  **** ****  **     **  **     **  ****  ** 
 **  **  **  ** *** **  **     **  **     **  ** ** ** 
 **  **  **  **     **  **     **  **     **  **  **** 
 **  **  **  **     **  **     **  **     **  **   *** 
  ***  ***   **     **  ********   ********   **    ** 

Message: