Pool disks not showing up properly on the interface

viniciusferrao

Contributor
Joined
Mar 30, 2013
Messages
192
Hello, I've a pool that three disks aren't showing up as member of the pool on the GUI, here's the outputs on the terminal:

Code:
  pool: pool0
 state: ONLINE
  scan: resilvered 127G in 00:48:19 with 0 errors on Tue Jun  6 17:35:44 2023
config:

    NAME                                      STATE     READ WRITE CKSUM
    pool0                                     ONLINE       0     0     0
      raidz2-0                                ONLINE       0     0     0
        06ef7774-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        09ff9347-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        08bc2b61-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        0a3eb6cc-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        09f13b84-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        09e1fc7e-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        0a1f949a-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        06fa51c9-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        0a0f7341-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        0a2f088a-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        09d246a8-3adb-11ed-8896-0cc47a859fe4  ONLINE       0     0     0
        b7af91d7-fd19-4870-b5fb-c8b377bda21d  ONLINE       0     0     0
    cache
      068fb4d8-3adb-11ed-8896-0cc47a859fe4    ONLINE       0     0     0

errors: No known data errors


And the same on the web interface:
1686083969696.png


1686083995576.png


You can see on the first image that the disk icon is missing, also on the second one the pool is marked as N/A.

I don't know why this is this way.

Thanks,

PS: Shrinked down version of fdisk -l:

Code:
Disk /dev/nvme0n1: 372.61 GiB, 400088457216 bytes, 781422768 sectors
Disk /dev/sdc: 59.63 GiB, 64023257088 bytes, 125045424 sectors
Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdk: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdi: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdg: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdm: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdh: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdl: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdj: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdn: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sde: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdf: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdo: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdp: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdv: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdt: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sds: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdw: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdr: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdu: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdz: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdx: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdy: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sdq: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk /dev/sda: 59.63 GiB, 64023257088 bytes, 125045424 sectors
Disk /dev/md127: 2 GiB, 2144337920 bytes, 4188160 sectors
Disk /dev/md126: 2 GiB, 2144337920 bytes, 4188160 sectors
Disk /dev/md125: 2 GiB, 2144337920 bytes, 4188160 sectors
Disk /dev/mapper/md127: 2 GiB, 2144337920 bytes, 4188160 sectors
Disk /dev/mapper/md126: 2 GiB, 2144337920 bytes, 4188160 sectors
Disk /dev/mapper/md125: 2 GiB, 2144337920 bytes, 4188160 sectors
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
I'm sure I've seen many of these recently on SCALE, but it smelled much older to me...


Seems it was fixed some time back on CORE, so maybe somebody can log a bug for it on SCALE to get it fixed there too.
 
Top