Every 3rd or 4th reboot, the ramdisk is vanished.
The virtual disk entry is there but the ramdisk entry is gone.
I have to delete the remaining entry and create a new disk from image.
This is very annoying.
Any help is appreciated.
BTW: Windows 10/64 Pro 22H2, 32GB Ram.
Kind regards
Roland
Ramdisk dissapears on reboot
Re: Ramdisk dissapears on reboot
Does the ramdisk appear in Windows Disk Management when the problem occurs?
And were there any events logged by the source "FancyRd" in the Windows Event Viewer? Please see
https://kb.romexsoftware.com/en-us/3-ge ... leshooting
And were there any events logged by the source "FancyRd" in the Windows Event Viewer? Please see
https://kb.romexsoftware.com/en-us/3-ge ... leshooting
Re: Ramdisk dissapears on reboot
Dear support.
>>Does the ramdisk appear in Windows Disk Management when the problem occurs?
Yes: Additionally I noticed some Error entries in the Event Viewer when shutdown the computer.
>>Does the ramdisk appear in Windows Disk Management when the problem occurs?
Yes: Additionally I noticed some Error entries in the Event Viewer when shutdown the computer.
Re: Ramdisk dissapears on reboot
And:
Thank you
Error_Logs as ZIP file enclosedThank you
- Attachments
-
- Error_Logs.zip
- (8.13 KiB) Downloaded 2 times
Re: Ramdisk dissapears on reboot
From the error logs, I noticed that Primo Ramdisk had an event on 2024-07-18 saying "Save on Shutdown" failed. The error code indicated that the reason is that the D drive was offline at that time. It seems that the file system on the ramdisk W: was corrupted, causing the drive W: not available.
If you still can recreate the ramdisk from the image file, I recommend the following steps.
1. Backup the contents of the ramdisk to a physical drive.
2. Delete the current ramdisk (if no file is in use). You can export the ramdisk configuration before deletion.
3. Create a new ramdisk with a new image file name and set the image path to drive C: instead of drive D:.
4. Copy the backup contents to the new ramdisk.
5. Restart the computer.
I also noticed that PrimoCache had an event on 2024-07-15 saying "Defer-Write" failed. The error code indicated that target drive was not available. So you can use Chkdsk tool to check the target drives cached by PrimoCache to see if there is any file system corruption. For more information, please see
https://kb.romexsoftware.com/en-us/3-ge ... ows-system
If you still can recreate the ramdisk from the image file, I recommend the following steps.
1. Backup the contents of the ramdisk to a physical drive.
2. Delete the current ramdisk (if no file is in use). You can export the ramdisk configuration before deletion.
3. Create a new ramdisk with a new image file name and set the image path to drive C: instead of drive D:.
4. Copy the backup contents to the new ramdisk.
5. Restart the computer.
I also noticed that PrimoCache had an event on 2024-07-15 saying "Defer-Write" failed. The error code indicated that target drive was not available. So you can use Chkdsk tool to check the target drives cached by PrimoCache to see if there is any file system corruption. For more information, please see
https://kb.romexsoftware.com/en-us/3-ge ... ows-system