Tag Archives: vdisk

The Storage Pool Does Not Have Sufficient Eligible Resources

Posted on by
Reply

KB ID 0001562

Problem

When attempting to  create a vDisk in Tiered Windows Storage Spaces you see this;

Failed to create virtual disk – Not Supported

Extended Information:
The storage pool does not have sufficient eligible resources for the creation of the specified virtual disk.

Recommended Actions:
-Choose a combination of FaultDomainAwareness and NumberOfDataCopies (or PhysicalDiskRedundancy) supported by the storage pool.
-Choose a value for number of columns that is less than or equal to the number of physical disks in the storage fault domain selected for the virtual disk.

Of if you are using PowerShell, the error will look more like this;

Solution

I’ve seen the same error when trying to create a disk from a pool that has 1 SSD, and 1 HDD, and also from a pool with many SSD’s and HDD’s. Ive seen it with both ‘Simple’ and ‘Mirrored’ storage.

Recreate the vDisk, but this time DONT use ‘Maximum Size’, drop the Tier sizes, like so.

OK, this is a bit hit and miss ‘I grant you,‘ but, you will need to experiment with the sizes. As a ‘rule of thumb’ aim to lose about 4GB per physical disk. Annoyingly you will need to delete the vDisk and keep retrying (so don’t put a volume on it just yet, or you will have to go to Computer Management and delete that every time!) until you get the size optimal.

Related Articles, References, Credits, or External Links

NA

HP MSA P2000 (G3) Error – ‘Unwritable write-back cache data exists for a volume’

Posted on by

KB ID 0000817 

Problem

Seen on a G3 P2000 SAN, the client had also had an MSA70 shelf, which contained a failed array. I was removing the MSA and after the job, this error was getting logged.

Unwritable write-back cache data exists for a volume (vdisk: unknown name, volume: unknown name, SN {Serial Number} it comprises {number}% of cache.

Solution

Essentially, there was data in the cache that needed writing to the array/vdisk, when it failed. If the volume was going to get repaired and brought back online the data would have got written back. However this volume was never coming back.

1. Connect to a controller via Telnet.

2. Issue the following command;

[box] clear cache [/box]

Related Articles, References, Credits, or External Links

NA

 

HP MSA P2000 – ‘The Disk May Contain Stale Metadata’

Posted on by

KB ID 0000874

Problem

The call came in this morning, a client had replaced a failed drive in his SAN, (an MSA P2000 2324sa). He was asking if there was anything he needed to do. I said “Just mark it as a global spare and that should be it”. He rang back some time later to say he was still having problems.

When I dialled on I could see his ‘new’ drive was marked as LEFTOVR and was flagged with the following warning;

The disk may contain stale metadata. Recommended action: Clear the metadata to rescue the disk.

Solution

You see this error because this is a ‘recycled’ disk, and it still has data on it that refers to the array and/or vdisk that it was in originally. This is the ‘metadata’ that it is referring to.

Note: You can see, (from the image above) the disk I’m dealing with is disk 8 (make a mental note of that).

1. With the MSA Selected > Tools > Clear Disk Metadata.

2. Remember our disk is in in slot 8, so tick it and click ‘clear metadata’.

3. You can now treat this disk as if it were a new disk and add it as a global spare, (your failed vdisk will then claim the disk and the RAID should rebuild it without further intervention).

Related Articles, References, Credits, or External Links

NA