3
I've just done an in-place upgrade of a Hyper-V guest from Windows Server 2008 to Server 2012 R2 (via Server 2012, as direct upgrade from 2008 to 2012 R2 is not supported). Usually one would create a new machine and seize roles, which is Microsoft's officially "preferred" option, but for organisational reasons this isn't possible. This is a test run, on a copy of the original VM disconnected from network.
All appears okay except one of the 3 data drives (separate VHDX files) shows "Access Denied" when double-clicking to open the drive in Windows Explorer. However, I can list directories and view files from the command line!
Steps taken to resolve:
- Double checked Hyper-V guest settings exactly the same as the production server
- run
chkdsk
within the VM, no errors found - disk management shows healthy active primary partition (interestingly this is the only disk with unallocated space the beginning, perhaps this is relevant?)
- also relevant: the disk cannot be marked as offline, and it was previously host to the pagefile
- moved pagefile to
C:\
(now the disk can be brought offline in disk management) - took disk offline then online again
- removed drive letter assignment and re-added
- backed up shares from registry, shutdown VM, disconnected the VHDX in question, rebooted, shutdown, re-connected the VHDX
- created a new volume in the unallocated space before the volume in question on that disk, then deleted it
- re-copied the VHDX file for this drive from the production server, in case the VHDX became corrupt during the original copy
- last ditch, I took ownership and re-permissioned the drive (this folder, all subfolders and files), and applied to child objects. Still getting "Access denied", indicating it's not an ACL (file permissions) related issue
This doesn't affect any other drives, including the system drive.
I haven't yet robocopied data to a new drive as I want to understand the root cause.
What should I try next?
You should provide more specifics, like what folder did you change the permissions on, because your answer does not make that clear. – Ramhound – 2017-06-13T15:14:13.667
My answer does actually make that clear - "...to the drive root" – sutra – 2017-06-13T15:17:49.837
I have never refered to the root directory of a drive as the "drive root" in my 25 years using a computer. I am trying to give you feedback on how to improve your answer. – Ramhound – 2017-06-13T15:54:30.863
@Ramhound I'd say "drive root" and "root of drive" are synonymous. I understood Sutra's point. That said, it doesn't address the question, because, as stated, I've already completely re-permissioned the drive and state "...indicating it's not an ACL (file permissions) related issue" – hazymat – 2017-06-15T09:56:41.070