Proxmox installation stuck on 3% "Creating LV's" PLEASE HELP GUYS

[chill9]

I also ran into this issue on my Beelink SER5 Max with the included Phison NVMe. I started the installer with the debug logging and got to a terminal and noticed that it was running this command while it was stuck at 3% creating the LVM volumes.

/sbin/lvconvert --yes --type thin-pool --poolmetadatasize 8732672K pve/data

I did an strace on its PID and saw this:

ioctl(3, BLKZEROOUT, [7157579776, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7158628352, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7159676928, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7160725504, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7161774080, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7162822656, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7163871232, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7164919808, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7165968384, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7167016960, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7168065536, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7169114112, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7170162688, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7171211264, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7172259840, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7173308416, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7174356992, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7175405568, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7176454144, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7177502720, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7178551296, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7179599872, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7180648448, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7181697024, 1048576] <detached ...>

So, it looks like it is zeroing out the NVMe drive. The process did eventually finish, but it was a relief to see the installer doing something in the strace. I hope this helps.

 

[marcosscriven]

I also ran into this issue on my Beelink SER5 Max with the included Phison NVMe. I started the installer with the debug logging and got to a terminal and noticed that it was running this command while it was stuck at 3% creating the LVM volumes.

/sbin/lvconvert --yes --type thin-pool --poolmetadatasize 8732672K pve/data

I did an strace on its PID and saw this:

ioctl(3, BLKZEROOUT, [7157579776, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7158628352, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7159676928, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7160725504, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7161774080, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7162822656, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7163871232, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7164919808, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7165968384, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7167016960, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7168065536, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7169114112, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7170162688, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7171211264, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7172259840, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7173308416, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7174356992, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7175405568, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7176454144, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7177502720, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7178551296, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7179599872, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7180648448, 1048576]) = 0
ioctl(3, BLKZEROOUT, [7181697024, 1048576] <detached ...>

So, it looks like it is zeroing out the NVMe drive. The process did eventually finish, but it was a relief to see the installer doing something in the strace. I hope this helps.

I just found this thread Googling "proxmox create lvs stuck". I see it was started a couple of years ago, but then there's been a few posts, all regarding the N100.

I've installed Proxmox dozens of times and never seen this, so I wonder why it's an issue just on some of these N100 mini PCs?

Thanks for digging in @chill9!

 

[Synth0344]

Same here installing PVE 8.2 on a 2TB NVMe SSD (LVM/ext4). The HDD LED indicator flashes, meaning that the behavior fits to what chill9 described above - the installer seems to be zeroing out the disk. This also means that the size of your disk and its write performance will influence how long it will take.

My previous installation was on a 500GB SATA SSD, and there the installation was instantaneous - for some reason there was no zeroing out.

Anyway, the installer should at least inform about this behavior.