All storages with grey "?" question mark

G

gabricampaa

New Member
Aug 3, 2025
5
0
1
Hi everyone. This is my first post, so excuse me if i'm lackcing some of the guidelines for posting here.

As my title reads, a week ago i started my machine (Lenovo ThinkCentre Mini Pc Tiny, Intel i7-6700 4 Core 3.4Ghz, Ram 8GB SSD 240Gb) and all the storages were marked with the grey question mark, so the uknonwn state. The first weird thing is that also the local storage is marrked as with "?", whichc is pretty weird cause it's where proxmox is installed. In fact, i can access the "main" shell and see the mounted disks frorm there (and all seems to be fine).

all my lxc wont start because their images are stored in another disk, called STORAGE_1 (which i can see mounted when running lsblk and which i'm sure works 100%).

i tried rebooting countless times, updating and upgrading, disconnecting and reconnecting the drive, stopping the pve services.

What other info can i give you?

Thanks in advance for the help

1754425484259.png
 
Last edited:
Impact said:
Please try
Bash: 
systemctl status pvestatd
systemctl restart pvestatd
Click to expand...
Hello, thanks for your reply. I tried but the problem persists also after a reboot despite the service being active and running. can i give you some output or something that might help?
 
What happens when you run: pvesm status

PS all of the status is pulled up through a daemon called "pvestatd". If this program is hung for any reason, then all objects in GUI would show the question mark, as GUI can't talk to "pvestatd". There is probably one cause for all of this, and it is likely unrelated to local storage.

Examine your system's log: journalctl -b0
Look for anything suspicious.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
Impact said:
@gabricampaa I was hoping you'd share the output of systemctl status pvestatd.
Click to expand...
sorry, my bad. here it is:

Bash: 
root@pve:~# systemctl status pvestatd
● pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-08-06 19:19:18 CEST; 13min ago
    Process: 1066 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
   Main PID: 1078 (pvestatd)
      Tasks: 1 (limit: 9310)
     Memory: 143.1M
        CPU: 786ms
     CGroup: /system.slice/pvestatd.service
             └─1078 pvestatd

Aug 06 19:19:17 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
Aug 06 19:19:18 pve pvestatd[1078]: starting server
Aug 06 19:19:18 pve systemd[1]: Started pvestatd.service - PVE Status Daemon.
root@pve:~#
 
Last edited:
bbgeek17 said:
What happens when you run: pvesm status

PS all of the status is pulled up through a daemon called "pvestatd". If this program is hung for any reason, then all objects in GUI would show the question mark, as GUI can't talk to "pvestatd". There is probably one cause for all of this, and it is likely unrelated to local storage.

Examine your system's log: journalctl -b0
Look for anything suspicious.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
exactly as you hinted, as soon as i call "pvestatd", the shell just stops working. it stays hung up, showing no output as if an infinite loop.

Bash: 
root@pve:~# pvesm status

i'm trying to analyze the log, gonna take a while!

Bash: 
Aug 06 19:17:44 pve kernel: sd 5:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Aug 06 19:17:44 pve kernel: sd 5:0:0:0: [sdb] Write Protect is off
Aug 06 19:17:44 pve kernel: sd 5:0:0:0: [sdb] Mode Sense: 28 00 00 00
Aug 06 19:17:44 pve kernel: sd 5:0:0:0: [sdb] No Caching mode page found
Aug 06 19:17:44 pve kernel: sd 5:0:0:0: [sdb] Assuming drive cache: write through
Aug 06 19:17:44 pve kernel:  sdb: sdb1
Aug 06 19:17:44 pve kernel: sd 5:0:0:0: [sdb] Attached SCSI disk
...
Aug 06 19:17:46 pve systemd[1]: Found device dev-disk-by\x2duuid-0691e2d5\x2d07be\x2d42a5\x2dba4c\x2dc751f2337030.device - WDC_WD5000BPVT-22HXZT1 1.
Aug 06 19:17:46 pve systemd[1]: Mounting mnt-pve-LG_bianco.mount - Mount storage 'LG_bianco' under /mnt/pve...
Aug 06 19:17:47 pve kernel: EXT4-fs (sdb1): recovery complete
Aug 06 19:17:47 pve kernel: EXT4-fs (sdb1): mounted filesystem 0691e2d5-07be-42a5-ba4c-c751f2337030 r/w with ordered data mode. Quota mode: none.
Aug 06 19:17:47 pve systemd[1]: Mounted mnt-pve-LG_bianco.mount - Mount storage 'LG_bianco' under /mnt/pve.

.....
Aug 06 19:22:24 pve kernel: sd 5:0:0:0: [sdb] tag#0 timing out command, waited 180s
Aug 06 19:22:24 pve kernel: sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=181s
Aug 06 19:22:24 pve kernel: sd 5:0:0:0: [sdb] tag#0 Sense Key : Unit Attention [current] 
Aug 06 19:22:24 pve kernel: sd 5:0:0:0: [sdb] tag#0 Add. Sense: Not ready to ready change, medium may have changed
Aug 06 19:22:24 pve kernel: sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 01 2a e0 00 00 08 00
Aug 06 19:22:24 pve kernel: I/O error, dev sdb, sector 76512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 06 19:22:24 pve kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1683: inode #2: comm task UPID:pve:0: reading directory lblock 0
Aug 06 19:24:16 pve dbus-daemon[628]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.2' (uid=0 pid=647 comm="/usr/lib/snapd/snapd" label="unconfined")
.....
Aug 06 19:34:06 pve kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
Aug 06 19:34:29 pve kernel: sd 5:0:0:0: [sdb] tag#0 timing out command, waited 180s
Aug 06 19:34:29 pve kernel: sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=181s
Aug 06 19:34:29 pve kernel: sd 5:0:0:0: [sdb] tag#0 Sense Key : Unit Attention [current] 
Aug 06 19:34:29 pve kernel: sd 5:0:0:0: [sdb] tag#0 Add. Sense: Not ready to ready change, medium may have changed
Aug 06 19:34:29 pve kernel: sd 5:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 1d 04 08 00 00 00 08 00
Aug 06 19:34:29 pve kernel: I/O error, dev sdb, sector 486803456 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Aug 06 19:34:29 pve kernel: Buffer I/O error on dev sdb1, logical block 60850176, lost sync page write
Aug 06 19:34:29 pve kernel: JBD2: I/O error when updating journal superblock for sdb1-8.
 
Last edited:
You don't normally run "pvestatd" directly.

Based on the log snippet , one of your disks is failing and possibly tripping the daemon.
Examine your /etc/pve/storage.cfg, save the file, then remove all non-essential entries. Or, if you know the entry using "sdb" - start with that one.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
You don't normally run "pvestatd" directly.

Based on the log snippet , one of your disks is failing and possibly tripping the daemon.
Examine your /etc/pve/storage.cfg, save the file, then remove all non-essential entries. Or, if you know the entry using "sdb" - start with that one.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
this is stoarge.cfg

Bash: 
  1 dir: local
  2         path /var/lib/vz
  3         content vztmpl,rootdir,iso,backup,images
  4         shared 0
  5 
  6 dir: LG_bianco 
  7         path /mnt/pve/LG_bianco
  8         content snippets,images,backup,vztmpl,rootdir,iso
  9         is_mountpoint 1
 10         nodes pve
 11

LG_bianco is sdb1
 
Sounds like you are on the right path. Remove the PVE storage entry, unmount the disk, find and remove the automatic mount (fstab?).
This should unstuck the PVE. You can then try to mount the disk and save the data prior to throwing the disk into a bin.

Cheers

PS It could, theoretically, be any part of the disk chain : cable, motherboard, if the disk is external : cable or port. Hardware troubleshooting is a somewhat outside the scope of the forum. Given that PVE is Linux at its base - all the regular Linux troubleshooting applies.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
You must log in or register to reply here.
Top Bottom