Can't create Hard drive

Reuven

Member
Oct 22, 2019
73
2
11
57
Hi. I can not create any hard drive in proxmox 6.04...i keep getting this message


lvcreate 'pve/vm-100-disk-0' error: Aborting. Could not deactivate thin pool pve/data. at /usr/share/perl5/PVE/API2/Qemu.pm line 1314. (500)

Why does proxmox needs to deactivate thin pool pve/data ?

Thanks for the help reuven
 
Which version are you running? pveversion -v
 
root@pve:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1
 
That version is already a bit older. Can you please update and try if the error is still present?
 
Hi. Thanks for your reply and help

it says the following when I try to update:

Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Your System is up-to-date

starting shell
dircolors: no SHELL environment variable, and no shell type option given
root@pve:/#
 
Did you run a Refresh before?
 
Sorry...by refresh do you mean to run an update like this:

apt-get update
apt-get dist-upgrade

if not, please let me know the command...

Thanks reuven
 
Sorry, I meant the Refresh button in the GUI which trigger an apt update.

If you have done that and don't see any updates to be installed there might be something wrong with your sources files.

What do you have in your
Code:
/etc/apt/sources.list
/etc/apt/sources.list.d/*
files?
 
Hi Aaron. Thanks for your reply and help.

As requested the contents of my /etc/apt/sources.list is:

deb http://ftp.us.debian.org/debian buster main contrib non-free

deb http://ftp.us.debian.org/debian buster-updates main contrib non-free

# security updates
deb http://security.debian.org buster/updates main contrib non-free

deb [arch=amd64] http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster main
# deb-src [arch=amd64] http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster main
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

and

my /etc/apt/sources.list.d/* is:

nothing..nano reports it empty...maybe i am doing something wrong ??

All the best reuven
 
Hi Stephan. Thanks for your help.

I am entering:

nano /etc/apt/sources.list.d/?

and I am getting an empty file
 
my /etc/apt/sources.list.d/* is:

nothing..nano reports it empty...maybe i am doing something wrong ??
The * is usually a wildcard for any item in that directory. You can run ls /etc/apt/sources.list.d to get a list with all the files in there.
 
Hi Aaron. Thanks for your help.

This is what I got:

root@pve:~# ls /etc/apt/sources.list.d
root@pve:~#

looks like there is nothing in that directory...is it normal ?

All the best

reuven
 
looks like there is nothing in that directory...is it normal ?
It's a little bit unusual, but not necessarily wrong.
Aaron, do you think it's safe to replace "stretch" with "buster" in the proxmox repo line and do an upgrade?
Reuven, did you install this system initially? To me it seems that it was "buster" once and was replaced with "stretch" later. Strange - I have no idea why somebody would do this... :-|
 
Aaron, do you think it's safe to replace "stretch" with "buster" in the proxmox repo line and do an upgrade?
Ah, I totally overlooked that...
Yeah @Reuven please change the
Code:
 deb http://download.proxmox.com/debian/pve stretch pve-no-subscription
line in your /etc/apt/sources.list file to
Code:
 deb http://download.proxmox.com/debian/pve buster pve-no-subscription
and run a apt update afterwards.
 
Hi. Thanks for your help.

The server was installed originally as proxmox 6. Now, I found in the syslog the following:

Dec 08 03:55:01 pve CRON[1489516]: pam_unix(cron:session): session opened for user pcp by (uid=0)
Dec 08 03:55:01 pve CRON[1489517]: (pcp) CMD ( /usr/lib/pcp/bin/pmlogger_check -C)
Dec 08 03:55:02 pve CRON[1489516]: pam_unix(cron:session): session closed for user pcp
Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 Sense Key : Medium Error [current]
Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 Add. Sense: Unrecovered read error
Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 f0 00
Dec 08 03:55:10 pve kernel: print_req_error: critical medium error, dev sde, sector 0 flags 4000
 
Hi. Thanks for your help.

I did as suggested and got this :

root@pve:~# apt update
Hit:1 http://ftp.us.debian.org/debian buster InRelease
Hit:2 http://security.debian.org buster/updates InRelease
Hit:3 http://ftp.us.debian.org/debian buster-updates InRelease
Hit:4 http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster InRelease
Hit:5 http://download.proxmox.com/debian/pve buster InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
39 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@pve:~#

Then I ran 'apt list --upgradable' and got this:

root@pve:~# apt list --upgradable
Listing... Done
corosync/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
ifupdown/stable 0.8.35+pve1 amd64 [upgradable from: 0.8.35]
libcfg7/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
libcmap4/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
libcorosync-common4/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
libcpg4/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
libknet1/stable 1.13-pve1 amd64 [upgradable from: 1.10-pve1]
libnvpair1linux/stable 0.8.2-pve2 amd64 [upgradable from: 0.8.1-pve1]
libpve-access-control/stable 6.0-5 amd64 [upgradable from: 6.0-2]
libpve-common-perl/stable 6.0-9 all [upgradable from: 6.0-2]
libpve-guest-common-perl/stable 3.0-3 all [upgradable from: 3.0-1]
libpve-http-server-perl/stable 3.0-3 all [upgradable from: 3.0-2]
libpve-storage-perl/stable 6.1-2 all [upgradable from: 6.0-5]
libquorum5/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
libspice-server1/stable 0.14.2-4~pve6+1 amd64 [upgradable from: 0.14.0-1.3]
libuutil1linux/stable 0.8.2-pve2 amd64 [upgradable from: 0.8.1-pve1]
libvotequorum8/stable 3.0.2-pve4 amd64 [upgradable from: 3.0.2-pve2]
libzfs2linux/stable 0.8.2-pve2 amd64 [upgradable from: 0.8.1-pve1]
libzpool2linux/stable 0.8.2-pve2 amd64 [upgradable from: 0.8.1-pve1]
lxc-pve/stable 3.2.1-1 amd64 [upgradable from: 3.1.0-61]
novnc-pve/stable 1.1.0-1 all [upgradable from: 1.0.0-60]
proxmox-ve/stable 6.1-2 all [upgradable from: 6.0-2]
proxmox-widget-toolkit/stable 2.1-1 all [upgradable from: 2.0-5]
pve-cluster/stable 6.1-2 amd64 [upgradable from: 6.0-4]
pve-container/stable 3.0-14 all [upgradable from: 3.0-3]
pve-docs/stable 6.1-3 all [upgradable from: 6.0-4]
pve-edk2-firmware/stable 2.20191002-1 all [upgradable from: 2.20190614-1]
pve-firewall/stable 4.0-9 amd64 [upgradable from: 4.0-5]
pve-firmware/stable 3.0-4 all [upgradable from: 3.0-2]
pve-ha-manager/stable 3.0-8 amd64 [upgradable from: 3.0-2]
pve-i18n/stable 2.0-3 all [upgradable from: 2.0-2]
pve-kernel-5.0/stable 6.0-11 all [upgradable from: 6.0-5]
pve-kernel-helper/stable 6.0-12 all [upgradable from: 6.0-5]
pve-manager/stable 6.1-3 amd64 [upgradable from: 6.0-4]
pve-qemu-kvm/stable 4.1.1-2 amd64 [upgradable from: 4.0.0-3]
qemu-server/stable 6.1-2 amd64 [upgradable from: 6.0-5]
spl/stable 0.8.2-pve2 all [upgradable from: 0.8.1-pve1]
zfs-initramfs/stable 0.8.2-pve2 all [upgradable from: 0.8.1-pve1]
zfsutils-linux/stable 0.8.2-pve2 amd64 [upgradable from: 0.8.1-pve1]

is this Ok? should i do something else ?

All the best reuven
 
The server was installed originally as proxmox 6.
Looks to me like you copied the no subscription repo from an older source, that's why you had stretch instead of buster.

Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 Sense Key : Medium Error [current]
Dec 08 03:55:10 pve kernel: sd 12:0:0:0: [sde] tag#0 Add. Sense: Unrecovered read error
This does not look good! Check the SMART status of that drive. This could also be caused by a bad cable to the drive.
If that drive is part of the logical volume on which you got the initial error, this could also be a reason for it.

is this Ok? should i do something else ?
The list with the updates looks okay.
 
I tried to create a lvm-thin disk and got the same message:


lvcreate 'pve/vm-100-disk-0' error: Aborting. Could not deactivate thin pool pve/data. at /usr/share/perl5/PVE/API2/Qemu.pm line 1314. (500)

Why does it need to "Could not deactivate thin pool pve/data" ?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!