Unknown disks in dmesg

D

donhwyo

Member
Jan 14, 2023
108
14
23
Proxmox is working well but I see a few of these messages in dmesg.
Code: 
[  177.612691]  zd2944: p1 p2 p3 p4 < >
[  177.614193] zd2944: partition table partially beyond EOD, truncated
[  177.616583] zd2944: p2 size 143203410 extends beyond EOD, truncated
[  177.618588] zd2944: p3 start 245601720 is beyond EOD, truncated
[  177.620136] zd2944: p4 start 265458060 is beyond EOD, truncated

I am guessing they disks that are no longer there and I didn't remove them correctly. PVE has been running since version 4 and is upgraded to current as updates come out. Anyway how do I tell what they are and clean things up?

Thanks
 
Have you checked with fdisk? Have you seen what can be found under /dev? df and mount checked? Have you seen what is actually physically installed? Possibly an old USB stick or SD card that is installed somewhere in the server?
 
Fdisk shows some info about the disk.
Code: 
root@pve:~# fdisk -l |grep zd2944
Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.Disk /dev/zd2944: 51.76 GiB, 55578722304 bytes, 108552192 sectors

/dev/zd2944p1             63 102398309 102398247 48.8G 83 Linux
Partition 4 does not start on physical sector boundary./dev/zd2944p2      102398310 245601719 143203410 68.3G  7 HPFS/NTFS/exFAT

/dev/zd2944p3 *    245601720 265458059  19856340  9.5G af HFS / HFS+
/dev/zd2944p4      265458060 398283479 132825420 63.3G  5 Extended
Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
How can I tell what disk this is on or what vm may be referencing it?

Thanks
 
donhwyo said:
How can I tell what disk this is on or what vm may be referencing it?
Click to expand...
zdX are ZFS zvols, so the vitual disks of your VMs. You can check what VM that zvol belongs to by running: find /dev/zvol -type l -print -exec readlink {} \; for all zvols or udevadm info /dev/zd1234 for a single zvol.

For example "zd224":
Code: 
root@Voyager:~# udevadm info /dev/zd224
P: /devices/virtual/block/zd224
M: zd224
R: 224
U: block
T: disk
D: b 230:224
N: zd224
L: 0
S: zvol/dpool/vlt/VM8K/vm-109-disk-1
S: disk/by-diskseq/26
Q: 26
E: DEVPATH=/devices/virtual/block/zd224
E: DEVNAME=/dev/zd224
E: DEVTYPE=disk
E: DISKSEQ=26
E: MAJOR=230
E: MINOR=224
E: SUBSYSTEM=block
E: USEC_INITIALIZED=23174540
E: ID_PART_TABLE_UUID=c4ef25fb-62c6-4984-a1df-142ca454683f
E: ID_PART_TABLE_TYPE=gpt
E: DEVLINKS=/dev/zvol/dpool/vlt/VM8K/vm-109-disk-1 /dev/disk/by-diskseq/26
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
So according to the line "S: zvol/dpool/vlt/VM8K/vm-109-disk-1" it's disk Nr 1 of VM with VMID 109.
 
Last edited:
You must log in or register to reply here.
Top Bottom