B
Bernie Dwyer
Early days at a new small school, less than 30 users. I'm not onsite at the moment, just spent 5 hours trying to fix this. I will extract and upload detailed error messages tomorrow.
Hyper-v installed on Dell T320 server with 16GB memory, Dell PERC: 2 x 250GB SSD RAID1 for Hyper-v and guests, and 2 x 2TB RAID1 for user data.
Windows Server 2016 std as a VM
Debian 9.5 as a VM.
System has been running fine since January. Windows Server is the DC, clients joined domain and connected, file shares, printing, etc all OK
Over the weekend something happened - signs point to a power outage, now Windows server won't start. The machine boots and hyper-v runs, the debian VM starts, but windows server won't start.
Powershell on hyper-v console: start-vm servername gets to loading 10%, then fails with the error Microsoft emulated IDE controller didn't start <description indicates it's the Dell Perc > system cannot find the drive specified.
Hyper-v manager on a Win10Pro laptop with RSAT *used* to connect to hyper-v. Today, all I get on the laptop when I try to connect is the error about credentials delegation - I've checked group policy and it *is* enabled, but clicking "yes" on the "would you like to allow delegation" dialog just returns to the same dialog and fills up the list of hosts under the "delegation of fresh credentials" GPO - note, this laptop was able to connect to hyper-v last week, and RDP to hyper-v still works.
Using Powershell, I created a temporary VM, and attached the Windows Server VHDX file to it, and that one will start (get-vm shows it running), but it just won't pick up an IP address from the DHCP server, so I can't communicate with it except with a few powershell cmdlets.
1. UPS wasn't in this year's budget
2. Windows system backup nightly from the C: drive (RAID1) to E:\drive (RAID1)
Where to from here? Could I create a new Windows VM and restore AD from the backup on the E: drive? Could I run a repair from the Windows Server DVD?
Bernie Dwyer Clarity Computing Services
Continue reading...
Hyper-v installed on Dell T320 server with 16GB memory, Dell PERC: 2 x 250GB SSD RAID1 for Hyper-v and guests, and 2 x 2TB RAID1 for user data.
Windows Server 2016 std as a VM
Debian 9.5 as a VM.
System has been running fine since January. Windows Server is the DC, clients joined domain and connected, file shares, printing, etc all OK
Over the weekend something happened - signs point to a power outage, now Windows server won't start. The machine boots and hyper-v runs, the debian VM starts, but windows server won't start.
Powershell on hyper-v console: start-vm servername gets to loading 10%, then fails with the error Microsoft emulated IDE controller didn't start <description indicates it's the Dell Perc > system cannot find the drive specified.
Hyper-v manager on a Win10Pro laptop with RSAT *used* to connect to hyper-v. Today, all I get on the laptop when I try to connect is the error about credentials delegation - I've checked group policy and it *is* enabled, but clicking "yes" on the "would you like to allow delegation" dialog just returns to the same dialog and fills up the list of hosts under the "delegation of fresh credentials" GPO - note, this laptop was able to connect to hyper-v last week, and RDP to hyper-v still works.
Using Powershell, I created a temporary VM, and attached the Windows Server VHDX file to it, and that one will start (get-vm shows it running), but it just won't pick up an IP address from the DHCP server, so I can't communicate with it except with a few powershell cmdlets.
1. UPS wasn't in this year's budget
2. Windows system backup nightly from the C: drive (RAID1) to E:\drive (RAID1)
Where to from here? Could I create a new Windows VM and restore AD from the backup on the E: drive? Could I run a repair from the Windows Server DVD?
Bernie Dwyer Clarity Computing Services
Continue reading...