Dell Server - RAID(?) Problem

[LeMarchand]

Got in to find sole host server running, but no VMs would launch. A reboot showed a Lifecycle error (now fixed) and that 1 of 2 virtual disks was degraded. I have identified the problematic physical disk, but the problem remains.

 

Slots 0 and 2 appear to be the OS disks in RAID 1; slots 2 and 3 to 5 the storage disks that contain the VHDs etc. in RAID 10 but this shot doesn't jibe with that.

 

 

Though this does?

 

 

Slot 0 details

 

 

Slot 2 says "ready" and "spun up".

 

Where's slot 1?

 

 

Main page

 

 

Anyone got an idea on how to fix this?

[bald_pig]

From your screenshots, image one is saying that the OS disks are 1 and 2, image two is just showing you all drives connected to the controller and has nothing to do with which drive is in which array, third image shows that there's a non-critical warning with that drive, but the problem is not shown in the image. Your storage array is just disks 3-5 according to the fourth image.

 

I'd probably start by checking the logs and Windows event viewer.

[LeMarchand]

After more fiddling I have determined that disks 0 and 1 are the OS. Well were, after some more fiddling by me, 1 became a foreigner and importing it messed both up. Now it boots off disk 1 and 0 is the foreigner.

 

I'm wondering if the problem is because only 3 of the disks in the RAID 10 are "in the gang" and I can see no way to include the fourth, This MAY be because it was probably the original 0.5TB and the others have been replaced over the years and are 1TB? But where is disk 6?

[computer_expert]

but no VMs would launch.

 

Just throwing this out there but the host hasn't been patched with the Jan 2022 windows updates has it? Lots of issues with Server 2012/2012R2 and hyper-v VMs not starting

 

KB5009586 2012

KB5009624 2012R2

Edited January 12, 2022 by computer_expert

[Steve21]

Both of those disks with the errors are version code 000B which normally means non-supported (e.g. Not Dell branded/coded drives) which is likely why they're erroring in that sense

 

If you wanted to test if that's the error, and you have OSMA 8.5+ you could turn off the flag in stsvc.ini in program files temporarily to test it if resolves the flags

 

Steve

[LeMarchand]

Just throwing this out there but the host hasn't been patched with the Jan 2022 windows updates has it? Lots of issues with Server 2012/2012R2 and hyper-v VMs not starting

 

KB5009586 2012

KB5009624 2012R2

 

Possibly; that's my first job tomorrow!

 

Both of those disks with the errors are version code 000B which normally means non-supported (e.g. Not Dell branded/coded drives) which is likely why they're erroring in that sense

 

If you wanted to test if that's the error, and you have OSMA 8.5+ you could turn off the flag in stsvc.ini in program files temporarily to test it if resolves the flags

 

Steve

 

Both disks have been fine until now (they're Seagate for some reason - probably because Dell wasn't available?). I'll check the version if the above doesn't help!

[LeMarchand]

Just throwing this out there but the host hasn't been patched with the Jan 2022 windows updates has it? Lots of issues with Server 2012/2012R2 and hyper-v VMs not starting

 

KB5009586 2012

KB5009624 2012R2

 

We have a winner!

 

Thanks so much. Our file server didn't start up with the rest, which I thought I'd fixed... except it's taking an age to complete boot. May just revert to the weekend backup.

 

Now all I have to do is look at the dodgy RAID 10 disk (probably see if we get get a Dell one) and work out how to add the RAID 1 back in without stuffing everything up again!