Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About KungFury84

  • Title
  1. I'm actually glad it was just a bug in the 2019 GUI in the end (Kinda bad for Microsoft and they should probably get on that ASAP) Seeing as PS is pretty much in everything these days I think I'm going to have to brush up my PS knowledge more. Thanks for your help guys
  2. I was thinking this earlier just for peace of mind as these drives where shipped to me. I have now started the process of extended testing each drive and so far only tested one (takes about 9 hours each, so 3 days of just testing right there) They all passed the quick test which is promising so hopefully they all pass the extended tests.
  3. I think this has fixed it, I that PS command and it worked without any problems so i started increasing the size gradually until i got to the maximum size the GUI reported in previous attempts (29,736GB) These are the end naming scheme i ended up going with too. PS C:\Users\Administrator> New-VirtualDisk -StoragePoolFriendlyName ZeusPool -FriendlyName ZeusVDisk -ResiliencySettingName Parity -Size 29735GB -ProvisioningType Fixed -MediaType HDD -PhysicalDiskRedundancy 2 FriendlyName ResiliencySettingName FaultDomainRedundancy OperationalStatus HealthStatus Size FootprintOnPool Storag eEffic iency ------------ --------------------- --------------------- ----------------- ------------ ---- --------------- ------ ZeusVDisk Parity 2 OK Healthy 29.04 TB 43.56 TB 66.66% I then extended the virtual disk to pick up the remaining space and left me with a 29.1TB virtual disk. Now my question is why did this work?
  4. I recreated the pool (you StoragePool1 as the name this time) and it returned the following FriendlyName MediaType BusType Usage ------------- --------- ------- ----- HDD SATA Auto-Select HDD SATA Auto-Select HDD SATA Auto-Select HDD SATA Auto-Select HDD SATA Auto-Select HDD SATA Auto-Select HDD SATA Auto-Select HDD SATA Auto-Select
  5. Hello, So i currently have the following Server 2019 box Motherboard: SuperMicro X11SCA-F CPU: Intel Xeon E-2186G (6 Core, 12 Theards @ 3.80GHz) RAM: 64GB DDR4 2666mhz ECC System Drive: Samsung 970 Pro 512GB HDD Pool: 8 x 6TB SATA Seagate Ironwolf NAS drives PSU: SilverStone 600W Strider 80 Plus Titanium Currently Server 2019 is refusing to create a Virtual Disk for my storage pool. I know this is most likely a logic error on my behalf but I have a feeling there is a small setting or limitation i can not find. The error the wizard returns is as follows Failed to create virtual Disk – Not Supported Extended information This storage pool does not have sufficient eligible resources for the creation of this specified virtual disk. Recommended Actions: - Choose a combination of FaultDomainAwareness and NumberOfDataCopies (or PhysicalDiskRedundancy) supported by this storage pool. - Choose a value of NumberOfColumns that is less than or equal to the number of physical disks in the storage fault domain selected for the virtual disk. The steps i used to create the Pool as as follows 1. Named the Pool and gave it a description 2. selected all 8 physical disks and created the Pool This worked fine and the final pool had a capacity of 43.7TB The steps i used to create the Virtual Disk 1. Named the virtual disk and gave it a description (create storage tiers on this virtual disk was grayed out and unchecked) 2. "Enable enclosure awareness" was grayed out and unchecked 3. Selected "Parity" for storage layout 4. Selected "Dual Parity" for resiliency settings 5. Selected "fixed" for provisioning type 6. Selected "maximum size" for virtual disk size 7. Clicked "Create" and then returned mentioned error message. What I'm trying to achieve I'm trying to add all eight drives to a pool and then create a virtual disk that has a 2 drive fault tolerance similar to that of a RAID6 setup. Thanks in advance,
  6. That's the one thing i wasn't 100% sure about, Thanks for your help
  7. So I have a Supermicro X11SCA-F with a Intel Xeon E-2186G Coffee Lake 3.80 GHz and 4x16 Samsung M393A2K40CB2-CTD 16GB DDR4-2666 ECC REG DIMM So I put it all together and i keep getting 5 short 1 long beeps (after looking in the manual it says "memory not detected") So I checked what the motherboard accepted which was the following Memory Capacity Up to 64GB Unbuffered ECC/non-ECC UDIMM, DDR4-2666MHz, in 4 DIMM slots Memory Type 2666/2400/2133/1866/1600MHz ECC/Non-ECC DDR4 SDRAM 72-bit 288-pin UDIMM DIMM Sizes 1GB, 2GB, 4GB, 8GB, 16GB Memory Voltage 1.2V And the Samsung Memory I have is as follows TECHNICAL INFORMATION: STORAGE CAPACITY: 16GB MEMORY TECHNOLOGY: DDR4 SDRAM NUMBER OF MODULES: 1 X 16GB MEMORY SPEED: 2666MHZ DDR4-2666/PC4-21300 DATA INTEGRITY CHECK: ECC FEATURES: SINGLE RANK, REGISTERED CAS LATENCY TIMINGS: CL19 NOW to my knowledge this may be just as simple as the motherboard requiring a Bios update and if so is it possible to do so on this board without any memory installed? OR have i buggered something up with the memory specs, I know the memory is not on the bios supported memory list but only 2 kits are.