Pool not detected after reboot. All disks visible, CoveFs running, hints not working

[skurbee]

Hi all, hoping someone can help me track down why my pool vanished after a reboot today.

Setup:
- StableBit DrivePool 2.3.13.1687
- Windows 11 (10.0.26200.0)
- ~13 drives in the pool
- Pool mounted as Z:\

What happened:
Booted up today and DrivePool showed no pool at all — just "Create a New Pool" with 3 non-pooled disks (boot drive, game drive, and one unrelated drive). Restarting the service and rebooting did not help.

What I've verified:
- PoolPart folders are intact on the drives (confirmed visually)
- CoveFs is running (STATE: 4 RUNNING, WIN32_EXIT_CODE: 0)
- All physical drives are visible to Windows via Get-PhysicalDisk (see below)
- The ProgramData\StableBit DrivePool\Service\Store folder is intact and has 99 files modified today
- Service log shows a clean startup with no errors
- `dpcmd list-poolparts Z:\ 1` shows only 1 of 13 pool parts mounted (the WD 6TB, Device 1, HarddiskVolume9)
- `dpcmd refresh-all-poolparts` did not recover the missing disks
- Ran `dpcmd hint-poolpart` on all 17 candidate volumes from mountvol output — no effect
- Restarted service after hints — no change
- The DrivePool UI does show all 13 pool slots as "Disk is missing" after interacting with the UI, so the database is intact

**Get-PhysicalDisk output:**
```
DeviceId  FriendlyName                           Size
0         TOSHIBA DT01ACA100             1000204886016
1         WDC WD6003FZBX-00K5WB0         6001175126016
2         WDC WD101EFBX-68B0AN0         10000831348736
3         WDC WD10JPVX-75JC3T0           1000204886016
4         TOSHIBA MQ04ABF100             1000204886016
5         WDC WD101EFBX-68B0AN0         10000831348736
6         Samsung SSD 990 EVO Plus 2TB   2000398934016
7         Samsung SSD 970 EVO 1TB        1000204886016
8         ASMT 2115                       500107862016
9         ASMT 2115                       500107862016
10        ASMT 2115                       500107862016
11        ASMT 2115                      1000204886016
12        ASMT 2115                      2000398934016
13        ASMT 2115                      1000204886016
14        ASMT 2115                       500107862016
15        ASMT 2115                       500107862016
16        COVECUBE CoveFsDisk_____       2199023255552
```

**dpcmd list-poolparts Z:\ 1 output:**
```
Pool ID '97e2ad00-8f62-4104-84b4-c351ebc5f756':
  - '\\?\GLOBALROOT\Device\HarddiskVolume9\PoolPart.ceaa3e43-7485-45c9-9d91-9e0e79d02d63' [Device 1]
    - Volume Size: 6,000,636,588,032 B (5.46 TB)
    - Used: 4,811,055,149,056 B (4.38 TB)
    - Free: 1,189,581,438,976 B (1.08 TB)
```

Was working fine for months. What changed today: I removed 2 drives from the pool just fine. I then added 2 new drives to my machine, and those were being scanned. Not added to the pool quite yet. I restarted my computer during this, and poof

If I assign a drive letter, the UI goes from "Disk 5" Missing, to "Disk D:" Missing. So it can see the drives in a sense.

Only that one disk is mapping. The other 12 pool members are physically present and visible to Windows but DrivePool can't attach to them. Data is safe, I just can't access the pool. Any ideas what's gone wrong here and how to force the re-association?

[Shane]

Hmm. What happens if you run "dpcmd unignore-poolpart poolpartfullpath" for one of the "missing" disks?

For example if you mounted one of the "missing" disks under the drive letter "M" you'd run something like (replacing the poolpart's folder name appropriately):

dpcmd unignore-poolpart m:\poolpart.12345678-90ab-cdef-1234-567890abcdef

Or if you had all of your poolpart disks mounted as folders under a physical disk instead of having drive letters of their own, it'd be something like:

dpcmd unignore-poolpart e:\mounts\disk05\poolpart.12345678-90ab-cdef-1234-567890abcdef

Does that disk come back? Just wondering if the unexpected restart in the middle of adding the new disks mangled the pool's part tagging.

[skurbee]

So I've 'fixed' this issue somewhat manually. Still not sure what's causing it.

Every time I boot up my computer, DP UI shows no disks. I have to run this in powershell:
 

$dpcmd = "C:\Program Files\StableBit\DrivePool\dpcmd.exe"
$tempLetter = "D"
$diskNumbers = @(0, 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 13, 14, 15)

foreach ($diskNum in $diskNumbers) {
    # Get the largest Basic partition with no drive letter on this disk
    $part = Get-Partition -DiskNumber $diskNum |
        Where-Object { $_.Type -eq "Basic" -and [string]$_.DriveLetter -eq "" } |
        Sort-Object Size -Descending |
        Select-Object -First 1

    if ($null -eq $part) {
        Write-Host "Disk $diskNum - No eligible partition found, skipping."
        continue
    }

    Write-Host "Disk $diskNum - Partition $($part.PartitionNumber) ($([math]::Round($part.Size / 1GB, 1)) GB) - Assigning $tempLetter`:\"
    $part | Add-PartitionAccessPath -AccessPath "$tempLetter`:\" -ErrorAction SilentlyContinue
    Start-Sleep -Seconds 2

    Write-Host "Disk $diskNum - Hinting DrivePool..."
    & $dpcmd hint-poolpart "$tempLetter`:\"
    Start-Sleep -Seconds 1

    Write-Host "Disk $diskNum - Removing $tempLetter`:\"
    $part | Remove-PartitionAccessPath -AccessPath "$tempLetter`:\" -ErrorAction SilentlyContinue
    Write-Host "Disk $diskNum - Done."
    Write-Host ""
}

Write-Host "All disks processed!"


This goes through and mounts the drive letter D:\ to the largest empty partition on each drive that is supposed to be pooled, hints drivepool of that drive, then unmounts the letter and moves on. 

I have to run this every boot in order for my pool to reappear. 

Not the worst thing in the world, but definitely annoying. It can take 20-30 minutes after running the script for the 'Measuring' step to be complete.

[Shane]

I would suggest opening a ticket with StableBit with what's happened and your workaround, hopefully they can both resolve it permanently for you and fix whatever the underlying cause is.

Tagging @Christopher (Drashna) in the meantime.