Martijn Kools Posted January 7, 2016 Share Posted January 7, 2016 Sup ppl, Got a problem with PVS 7.7. When I set the disk to read-only / cache in device ram with overflow, a check disk is being forced when I boot the servers from it. I already made an entire new vdisk from scratch, same issue occurs. Any idea how to prevent this? Specs: - Windows 2008 R2 SP1 - XenApp 7.7 - PVS 7.7 - ESX 5.5, VM HW v10. - NFS Storage type Link to comment
0 Martijn Kools Posted January 22, 2016 Author Share Posted January 22, 2016 Replying on my own topic again lol. Anyway in PVS 7.7 the D: or E:-drive (System Drive) will be visible / mounted with a drive letter after provisioning and setting the vdisk to read-only. To prevent chkdsk from running all you have to do is delete the HKLM\bla\MountedDevices\\DosDevices\E: as I mentioned above.Then the drive won't be visible and chkdsk won't run any longer. Cheers. 1 Link to comment
0 Martijn Kools Posted January 7, 2016 Author Share Posted January 7, 2016 To follow up on this, it seems to start with the system reserved disk. Chkdsk keeps trying to scan this, also before imaging the System Reserved disk is not visible in explorer but after imaging a drive letter E: is connect to it and it is visible. Any idea why that is? I didn't see this behavior in 7.6. Link to comment
0 Martijn Kools Posted January 8, 2016 Author Share Posted January 8, 2016 Ok so I'm the only one with this problem I guess :) Anyway if you have this as well here's a workaround: Disable chkdsk: 1. Mount the vdisk on the PVS server. 2. Open Regedit, Select HKLM, click file > load hive and select the mounted OSDrive of the vdisk C:\Windows\System32\Config\System 3. Name the hive (bla) 4. Go to HKLM\bla\ControlSet001\Control\Session Manager 5. Edit BootExecute and replace the current value with autocheck autochk /k:C /k:D /k:E *PvsVmBoot (Default is autocheck autochk * PvsVmBoot) 6. Repeat for ControlSet002 Remove E: for system drive 1. Mount same key as above. 2. Delete the value HKLM\bla\MountedDevices\\DosDevices\E: That's it! :) Link to comment
0 sathish Logan Posted April 13, 2017 Share Posted April 13, 2017 Hi, I'm unable Load Hiva BLA from C:\windows\system32\config\system. I'm using PVS7.9 and Windows 10 OS VDIsk Could you please help me on this. Link to comment
0 Piyush Nayak Posted July 4, 2017 Share Posted July 4, 2017 Hi Martjin Kools, Just wanted to thank you and share my experience. Infra details: PVS 7.7 running on Windows 2012, Target Devices: Windows 2008 R2 servers with XA6.5 PVS Disk details as seen in Windows Explorer: C:\ = System Disk or Local Disk , D:\=WriteCache, E:\=CitrixBoot-DVD Drive PVS Server houses vDISKs which are stored on SAN. E:\= boots the VM and points to DHCP location and PVS server for vdisk ************************************* Issue: HDD runs in CHKDSK -> master device and clone(Target devices) Quick workaround in Production: Stop the running of CHKDSK and it will boot fine->master and clone both Permanent Fix: On Master Device Mount the vDisk on PVS Server->it will pick next available Drive letter(G:\ in my case)-> regedit-> Sellect HKLM-> File-> Load the Hive->point to c:\windows\system32\system->Givesome key name = BLAH-> Navigate to HKLM\BLAH\MountedDevices and delete the key: \\DOSDevices\E: I just verified the other keys: HKLM\SYSTEM\CurrentControlSet001\SessionMnager = autocheck autochk * (Same value for CurrentControlSet002) -> which is same as per "other working PVS target machines" After deleting \\DosDevices\E: ->unload the hive. To unmount the vDisk from G:\drive on Windows 2012-> diskmgmt.msc->Right Click on G:\ ->Offline (Windows Explorer will refresh and G:\ disappears)-> Again Right Click and then unmount Close diskmgmt.msc Boot the master -> and it won't go for CHKDSK -> but will boot normally and it will recreate those reg entries back. Thank you for all your help. Appreciate it! Link to comment
0 John Francis1709160537 Posted July 13, 2019 Share Posted July 13, 2019 On 1/8/2016 at 6:16 AM, Martijn Kools said: Ok so I'm the only one with this problem I guess :) Anyway if you have this as well here's a workaround: Disable chkdsk: 1. Mount the vdisk on the PVS server. 2. Open Regedit, Select HKLM, click file > load hive and select the mounted OSDrive of the vdisk C:\Windows\System32\Config\System 3. Name the hive (bla) 4. Go to HKLM\bla\ControlSet001\Control\Session Manager 5. Edit BootExecute and replace the current value with autocheck autochk /k:C /k:D /k:E * PvsVmBoot (Default is autocheck autochk * PvsVmBoot) 6. Repeat for ControlSet002 Remove E: for system drive 1. Mount same key as above. 2. Delete the value HKLM\bla\MountedDevices\\DosDevices\E: That's it! :) Hi Mktools I am having the same issue. I loaded the hive and went to HKLM\bla\ControlSet001\Control\Session Manager and I had BootExecute - autocheck autochk * as the value and I replaced that with autocheck autochk /k:C /k:D /k:E *. I did not have CurrentControlSet002. PVS 7.15 LTSR version and Windows 10 is the Operating System. I have System drive E and I have Local Disk F that was mounted when I mounted the vdisk. You say Remove E: for system drive. I am not sure how I can remove it? I right clicked on the drive and I could not. 1. Mount same key as above - When you say Mount the same key, not sure what this means? 2. Delete the value HKLM\bla\MountedDevices\\DosDevices\E: Link to comment
Question
Martijn Kools
Sup ppl,
Got a problem with PVS 7.7. When I set the disk to read-only / cache in device ram with overflow, a check disk is being forced when I boot the servers from it.
I already made an entire new vdisk from scratch, same issue occurs.
Any idea how to prevent this?
Specs:
- Windows 2008 R2 SP1
- XenApp 7.7
- PVS 7.7
- ESX 5.5, VM HW v10.
- NFS Storage type
Link to comment
6 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now