Hi, I'm new here and i have a problem that i encountered during my training for windows server 2019, which i ran through oracle Virtual Box manager. Namely, now i need to create a disk pool, and I'm not sure why out of the two created disks, only one disk appears in the VB manager when i want to create a disk pool on the Windows server.
Did i make a mistake when creating virtual disks in VB manager? I would like someone to help me configure the "disk pool" properly (starting with disk configuration in VM Virtualbox, and also in File and Storage Services i WS 2019) so that it can continue the exercises. Here is the attached picture, if i didn't explain it well enough. I thank you.
Creating storage pool problem
-
Zijad_Sarajevo
- Posts: 1
- Joined: 14. Sep 2024, 20:51
Creating storage pool problem
- Attachments
-
- Screenshot_4.png (57.44 KiB) Viewed 4401 times
-
- Screenshot_3.png (46.45 KiB) Viewed 4401 times
-
- Screenshot_2.png (42.48 KiB) Viewed 4401 times
-
verbchar
- Posts: 1
- Joined: 17. Sep 2024, 11:05
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: VirtualBox
- Location: https://geometrydashgame.org/
Re: Creating storage pool problem
In VirtualBox:
Make sure you have created two separate virtual disks:
Open VirtualBox Manager > Select your VM > Settings > Storage.
Add new virtual hard disks for each drive needed (e.g., by selecting "Controller: SATA" and adding new disks).
On Windows Server 2019:
Open File and Storage Services > Storage Pools.
Ensure both disks are visible. If not, they may not be properly attached in VirtualBox or initialized.
Initialize both disks if needed, and create your storage pool using these disks.
Make sure you have created two separate virtual disks:
Open VirtualBox Manager > Select your VM > Settings > Storage.
Add new virtual hard disks for each drive needed (e.g., by selecting "Controller: SATA" and adding new disks).
On Windows Server 2019:
Open File and Storage Services > Storage Pools.
Ensure both disks are visible. If not, they may not be properly attached in VirtualBox or initialized.
Initialize both disks if needed, and create your storage pool using these disks.
Re: Creating storage pool problem
Hi,
I am running the latest VBOX on the latest Debian and having the exact same issues. I tried win server 2019 / 2022, same problem. I tried reinstalling VBOX and recreating the servers from zero. Same problem. I did the same by NOT installing the Guest Editions. Same Problem.
I tried creating bigger 15gb pre-allocated disks too. I tried VDI, VHD, VMDK type of virtual disks. I tried mixing them up too, just in case.
There is only one of two disks that shows up in storage pool creation, but still both are visible and available in the DISKs section.
If I initialized any of the disks in advance, non of them would show up in the storage pool creation. I think it is a kind of WinServer GUI / VBOX compatibility issue. I have tried all sorts of solutions, tinkering around permissions, firewall, installing other win server stuff for possible dependency issues for 3 days. Not sure what is going on.
I am not sure if can include here some PS commands, but in like 20 sec you can create your storage pool with this:
Storage POOL Creation in Windows Server when GUI Fails
# add two disks in VBOX, equal Size VDI or VHD, not hotpluggable, SSD can be ticked
Get-PhysicalDisk | Select-Object DeviceID, FriendlyName, OperationalStatus, Size
Get-Disk -Number 1 | Initialize-Disk -PartitionStyle GPT # initialize disk 1
Get-Disk -Number 2 | Initialize-Disk -PartitionStyle GPT # initialize disk 2
Get-StorageSubsystem # this will give the Storage Subsystem Friendly name that you have to write after "StorageSubsystemFriendlyName"
New-StoragePool -FriendlyName "MyStoragePool" -StorageSubsystemFriendlyName "Windows Storage" -PhysicalDisks (Get-PhysicalDisk | Where-Object { $_.DeviceID -eq 2 -or $_.DeviceID -eq 1 })
I am running the latest VBOX on the latest Debian and having the exact same issues. I tried win server 2019 / 2022, same problem. I tried reinstalling VBOX and recreating the servers from zero. Same problem. I did the same by NOT installing the Guest Editions. Same Problem.
I tried creating bigger 15gb pre-allocated disks too. I tried VDI, VHD, VMDK type of virtual disks. I tried mixing them up too, just in case.
There is only one of two disks that shows up in storage pool creation, but still both are visible and available in the DISKs section.
If I initialized any of the disks in advance, non of them would show up in the storage pool creation. I think it is a kind of WinServer GUI / VBOX compatibility issue. I have tried all sorts of solutions, tinkering around permissions, firewall, installing other win server stuff for possible dependency issues for 3 days. Not sure what is going on.
I am not sure if can include here some PS commands, but in like 20 sec you can create your storage pool with this:
Storage POOL Creation in Windows Server when GUI Fails
# add two disks in VBOX, equal Size VDI or VHD, not hotpluggable, SSD can be ticked
Get-PhysicalDisk | Select-Object DeviceID, FriendlyName, OperationalStatus, Size
Get-Disk -Number 1 | Initialize-Disk -PartitionStyle GPT # initialize disk 1
Get-Disk -Number 2 | Initialize-Disk -PartitionStyle GPT # initialize disk 2
Get-StorageSubsystem # this will give the Storage Subsystem Friendly name that you have to write after "StorageSubsystemFriendlyName"
New-StoragePool -FriendlyName "MyStoragePool" -StorageSubsystemFriendlyName "Windows Storage" -PhysicalDisks (Get-PhysicalDisk | Where-Object { $_.DeviceID -eq 2 -or $_.DeviceID -eq 1 })