Fazza Posted May 16, 2019 Posted May 16, 2019 Connected to a Server 2016 Hyper-V host is an array of JBODs set up in Storage Pools. The server only had 1 hard disk drive for the OS so no redundancy. Recently purchased a second hard disk drive for the server so it is now mirrored. We have re-installed Server 2016 on to the server and attached the virtual disk to the server. The problem we have is after a reboot when we log back on we have to keep re-attaching the virtual disk: Surely it should do this automatically (like before the OS re-install) or am I doing something wrong?
kmount Posted May 16, 2019 Posted May 16, 2019 Maybe this is relevant? - https://blogs.msdn.microsoft.com/virtual_pc_guy/2015/09/18/fixing-a-storage-space-that-does-not-attach-on-reboot/ 1
Fazza Posted May 16, 2019 Author Posted May 16, 2019 (edited) That could be it! Just run get-virtualdisk and it is indeed set to manually attach so I shall change it to False and reboot in a bit to prove it (just waiting for the backup to complete). [EDIT] The command in the screenshot shown in the above link didnt work for us and by the looks of things it didnt work for a lot of other people. It's seems on re-attaching a storage pool to a different/replacement server installation it is set to manually attach by default! The way to change it (that worked for us) is as follows: Get-VirtualDisk | Where-Object {$_.IsManualAttach –eq $True} Get-VirtualDisk | Where-Object {$_.IsManualAttach –eq $True} | Set-VirtualDisk –IsManualAttach $False Edited May 16, 2019 by Fazza
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