TASK ERROR: zfs error: cannot open 'rpool/data/subvol-100-disk-0': dataset does not exist

[luca63]

a good day from Italy.
I have a big problem , pve gives me this error , and I can't get it to work.

root@pve:/# zfs list
NAME USED AVAIL REFER MOUNTPOINT
hdd 442K 448G 95.6K /hdd
rpool 11.3G 204G 104K /rpool
rpool/ROOT 11.3G 204G 96K /rpool/ROOT
rpool/ROOT/pve-1 11.3G 204G 11.3G /
rpool/data 96K 204G 96K /rpool/data
rpool/media 96K 204G 96K /rpool/media

vi /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,vztmpl,backup

zfspool: local-zfs
pool rpool/data
content images,rootdir
sparse 1

zfspool: hdd
pool hdd
content images,rootdir
mountpoint /hdd
nodes pve

root@pve:/# pvesm status
Name Type Status Total Used Available %
hdd zfspool active 469580352 442 469579909 0.00%
local dir active 225517056 11823232 213693824 5.24%
local-zfs zfspool active 213693936 96 213693840 0.00%

root@pve:/# zpool status
pool: hdd
state: ONLINE
config:

NAME STATE READ WRITE CKSUM
hdd ONLINE 0 0 0
draid2:1d:4c:1s-0 ONLINE 0 0 0
ata-WDC_WD5000AAKX-75U6AA0_WD-WCC2E2CNHCVL ONLINE 0 0 0
ata-ST500DM002-1BC142_S2A1V3ZL ONLINE 0 0 0
ata-WDC_WD5000AAKX-75U6AA0_WD-WCC2EXR37953 ONLINE 0 0 0
ata-ST3500413AS_S2A3HYBP ONLINE 0 0 0
spares
draid2-0-0 AVAIL

errors: No known data errors

pool: rpool
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: scrub repaired 0B in 00:00:41 with 0 errors on Sun Mar 10 00:25:03 2024
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-KINGSTON_SUV400S37240G_50026B776B013619-part3 ONLINE 0 0 0
ata-SSD_256GB_AA000000000000001408-part3 ONLINE 0 0 0

but the container status is stopped and the erroro is in object .... help me

 

[leesteken]

I have a big problem , pve gives me this error , and I can't get it to work.

root@pve:/# zfs list
NAME USED AVAIL REFER MOUNTPOINT
hdd 442K 448G 95.6K /hdd
rpool 11.3G 204G 104K /rpool
rpool/ROOT 11.3G 204G 96K /rpool/ROOT
rpool/ROOT/pve-1 11.3G 204G 11.3G /
rpool/data 96K 204G 96K /rpool/data
rpool/media 96K 204G 96K /rpool/media

Please note that this is more readable when using CODE-tags. It appears that the virtual disk-0 of container 100 is indeed does not exist.
Do you have a backup of container 100? What happened? Did you delete the disk? Did your system crash?

 

[luca63]

Thanks for the quick reply, not understanding anything in proxmox I wouldn't know what you mean by using CODE-tags.The disk, or rather the disks crashed last week and instead of 4 it was telling me there were 2 and I deleted everything, changing the raid2 type. I can't retrieve the backup of container 100 . although it was an experiment , so I would also gladly do it again, but how can I do since on gives me the option to delete it?

Translated with DeepL.com (free version)

 

[leesteken]

Thanks for the quick reply, not understanding anything in proxmox I wouldn't know what you mean by using CODE-tags.

That is not about Proxmox but about this forum. Have a look at the buttons above the part where you type your messages.

The disk, or rather the disks crashed last week and instead of 4 it was telling me there were 2 and I deleted everything, changing he raid2 type. I can't retrieve the backup of container 100 . although it was an experiment , so I would also gladly do it again, but how can I do since on gives me the option to delete it?

So your disks crashed and you lost the data, thank you for clearing that up. Maybe reinstall Proxmox and start again with only the working disks?

 

[luca63]

I don't think that in case of errors like this the only possibility is to delete everything and redo.Is it possible that there is no metoro to delete the CT (100) and redo it from new ?

 

[leesteken]

I don't think that in case of errors like this the only possibility is to delete everything and redo.Is it possible that there is no metoro to delete the CT (100) and redo it from new ?

Just delete it? Or, if all virtual disk are already deleted/missing, just delete the configuration /etc/pve/lxc/100.conf.

 

[luca63]

deleted because it was no longer working , but I don't see any file in /etc/pve/lxc/100.conf

i see in /etc/pve/local/lxc/100.conf
arch: amd64
cores: 1
features: nesting=1
hostname: borgbackup
memory: 1024
mp0: hdd:subvol-100-disk-0,mp=/borg_repos,mountoptions=nosuid;noexec;noatime,size=1300G
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:AA:6D:B5,ip=192.168.1.100/24,type=veth
net1: name=dhcp,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:12:AC:43,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: local-zfs:subvol-100-disk-0,size=16G
swap: 1024
unprivileged: 1

but there is a possibilities to refer to this

 

[leesteken]

deleted because it was no longer working , but I don't see any file in /etc/pve/lxc/100.conf

i see in /etc/pve/local/lxc/100.conf
arch: amd64
cores: 1
features: nesting=1
hostname: borgbackup
memory: 1024
mp0: hdd:subvol-100-disk-0,mp=/borg_repos,mountoptions=nosuid;noexec;noatime,size=1300G
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:AA:6D:B5,ip=192.168.1.100/24,type=veth
net1: name=dhcp,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:12:AC:43,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: local-zfs:subvol-100-disk-0,size=16G
swap: 1024
unprivileged: 1

Then your Proxmox is broken and I don't know how to fix it. Maybe someone else here knows.