Hi, there!
Today I upgraded my home server from Intel Xeon E3-1275v1 on a Asus P8E-E/4L motherboard over to a AMD Ryzen 3900X on a Asus Pro WS X570-ACE motherboard.
I'm still using the same LSI MegaRAID 9211-8i in IT-mode for my 8x Seagate IronWolf 10TB disks, and I also had to carry over a Intel i350-t4 NIC as the on-board Intel I211-AT just refuses to work with Windows Server 2019.
I cloned by installation from my previous Samsung 850 PR0 256GB over to my new Samsung 970 EVO Plus 1TB. Booted up, and everything was fine and dandy besides a few drivers which I had to install.
My only issue is with my virtual disk on my storage pool. My storage pool consists of 8x Seagate IronWolf 10TB and 2x Samsung 850 Pro 1TB drives. The virtual disk is a mirror with tiering, so the 2x Samsung 850 Pro's are used for write-back cache up to 100 GB.
The virtual disk attaches, all the data is there and it behaves as normal but the server keeps complaining about the virtual disk being unhealy reason unknown. Repair-VirtualDisk just hangs for a few minutes without doing anything. Detaching and reattaching doesn't do anything.
Health on each individual drive is okay. Health on the storage pool is okay, health on the filesystem running on the virtual disk is okay.
It's rather hard for me to pinpoint what exactly is wrong as Windows Server 2019 isn't really telling me anything. The virtual disk reports: Unhealthy: Unknown and it's also reporting Provisioning: Unknown, Operation Status: Unknown, Storage Layout: Blank.
If I go into details on the virtual disk it says OperationalStatus Value 53284 which isn't telling me much. ParityLayout: NonParityBasedLayout. PhysicalDiskRedundancy: 0. Redundancy: Blank.
There is obviously several things wrong in the listings here. I suspect the issues are related to the fact that my 2x Samsung 850 Pro 1TB's are no longer residing on a Intel SATA-controller using the Intel Intel SATA AHCI Controller drivers, but are now residing on a AMD-controller using the Microsoft Standard SATA AHCI Controller drivers.
I figured the best thing would be to use EaseUS and clone the virtual disk onto another drive, redo the storage pool and virtual disk and clone it back again.
But do any of you have any experience with this? Shouldn't you be able to move a Windows Storage Space / Storage Pool and virtual disk from one server to another?
Best regards,
Thomas Andre aka RamGuy
Today I upgraded my home server from Intel Xeon E3-1275v1 on a Asus P8E-E/4L motherboard over to a AMD Ryzen 3900X on a Asus Pro WS X570-ACE motherboard.
I'm still using the same LSI MegaRAID 9211-8i in IT-mode for my 8x Seagate IronWolf 10TB disks, and I also had to carry over a Intel i350-t4 NIC as the on-board Intel I211-AT just refuses to work with Windows Server 2019.
I cloned by installation from my previous Samsung 850 PR0 256GB over to my new Samsung 970 EVO Plus 1TB. Booted up, and everything was fine and dandy besides a few drivers which I had to install.
My only issue is with my virtual disk on my storage pool. My storage pool consists of 8x Seagate IronWolf 10TB and 2x Samsung 850 Pro 1TB drives. The virtual disk is a mirror with tiering, so the 2x Samsung 850 Pro's are used for write-back cache up to 100 GB.
The virtual disk attaches, all the data is there and it behaves as normal but the server keeps complaining about the virtual disk being unhealy reason unknown. Repair-VirtualDisk just hangs for a few minutes without doing anything. Detaching and reattaching doesn't do anything.
Health on each individual drive is okay. Health on the storage pool is okay, health on the filesystem running on the virtual disk is okay.
It's rather hard for me to pinpoint what exactly is wrong as Windows Server 2019 isn't really telling me anything. The virtual disk reports: Unhealthy: Unknown and it's also reporting Provisioning: Unknown, Operation Status: Unknown, Storage Layout: Blank.
If I go into details on the virtual disk it says OperationalStatus Value 53284 which isn't telling me much. ParityLayout: NonParityBasedLayout. PhysicalDiskRedundancy: 0. Redundancy: Blank.
There is obviously several things wrong in the listings here. I suspect the issues are related to the fact that my 2x Samsung 850 Pro 1TB's are no longer residing on a Intel SATA-controller using the Intel Intel SATA AHCI Controller drivers, but are now residing on a AMD-controller using the Microsoft Standard SATA AHCI Controller drivers.
I figured the best thing would be to use EaseUS and clone the virtual disk onto another drive, redo the storage pool and virtual disk and clone it back again.
But do any of you have any experience with this? Shouldn't you be able to move a Windows Storage Space / Storage Pool and virtual disk from one server to another?
Best regards,
Thomas Andre aka RamGuy