Newbi to proxmox VE, Unable to create a VM write error/no space left

S

subafr

New Member
Jan 28, 2020
24
1
3
43
Hello all !
I am a newcomer to proxmox world and I dont understand something.
I chose a default install with the proxmox APPLIANCE, I create a EXT4 partition with full disk size. ( 7TB )
Proxmox create a LVM group with all the disk space, install ok and I reboot.

After that proxmox show disk usage for the pve group at 98%. If I try to create a VM, installer failed ( centos ) with no space left / write error ...
I have try to reinstall proxmox with a smaller LVM size for PVE like 600gb, and create a second LVM group with the free disk space, add the storage into proxmox.

Again I try to create a VM to the new storage and always the same error, write error, no space left on device ...

I think iam missing something about LVM and proxmox, but i dunno what ..

Can someone help me ?

Thanks
 
Can you please show us the output of the commands lsblk, df -h and lvs?

Please wrap them in [code][/code] tags.
 
Hello Aaron, thanks for your help, i really would like to use proxmox in production.
I have reinstall proxmox VE and choose EXT4 with default disk options ( empty fields for maxroot, minfree, maxvz ). Always the same problem.

Code: 
NAME               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                  8:0    0   7.3T  0 disk
├─sda1               8:1    0  1007K  0 part
├─sda2               8:2    0   512M  0 part /boot/efi
└─sda3               8:3    0   7.3T  0 part
  ├─pve-swap       253:0    0     8G  0 lvm  [SWAP]
  ├─pve-root       253:1    0    96G  0 lvm  /
  ├─pve-data_tmeta 253:2    0  15.8G  0 lvm
  │ └─pve-data     253:4    0   7.1T  0 lvm
  └─pve-data_tdata 253:3    0   7.1T  0 lvm
    └─pve-data     253:4    0   7.1T  0 lvm
sdb                  8:16   1  28.8G  0 disk
├─sdb1               8:17   1   238K  0 part
├─sdb2               8:18   1   2.8M  0 part
├─sdb3               8:19   1 651.9M  0 part
└─sdb4               8:20   1   300K  0 part

Code: 
root@node01:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   16G     0   16G   0% /dev
tmpfs                 3.2G  8.9M  3.2G   1% /run
/dev/mapper/pve-root   94G  1.5G   88G   2% /
tmpfs                  16G   25M   16G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                  16G     0   16G   0% /sys/fs/cgroup
/dev/sda2             511M  316K  511M   1% /boot/efi
/dev/fuse              30M   16K   30M   1% /etc/pve

Code: 
root@node01:~# lvs
  LV   VG  Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data pve twi-a-tz--  7.13t             0.00   0.19                          
  root pve -wi-ao---- 96.00g                                                  
  swap pve -wi-ao----  8.00g

Thanks again for your help !
 
Last edited:
Hm, that Initramfs unpacking failed: write error is not caused by the storage. Check if the ISO you have is good and not corrupted first.

Is there a reason you install Proxmox VE 5.4 instead of the newest 6.1 version?
 
I have the same problem with proxmox 5.4 and 6.1 versions and I have the same problem with ubuntu/debian/centos, all linux distribution. Windows ISO give me bluescreen at setup loading.
 
Accessory, if I use the SAME centos ISO in virtualbox it works :(
Capture d’écran de 2020-01-28 12-11-45.png
I think Iam missing a basic things but i dont know why .
 
subafr said:
I have the same problem with proxmox 5.4 and 6.1 versions and I have the same problem with ubuntu/debian/centos, all linux distribution. Windows ISO give me bluescreen at setup loading.
Click to expand...
Okay, that does sound weird.

On what hardware do you try this? (Manufacturer, Model, CPU type, ...)
Can you show the final config of a VM? Best if you ssh into the server and run qm config <vmid> and paste the output here into CODE tags.
 
I have try on multiple computer, first time on a classic laptop with intel VT enabled, since it was not working ( same error write error, no space left ), i have try to use proxmox on a real server.

Actually i am on a DELL R340:
CPU: Intel(R) Xeon(R) E-2124 CPU @ 3.30GHz

Motherboard:
description: Motherboard
product: 045M96
vendor: Dell Inc.
physical id: 0
version: A01
serial: .2WFWJ23.CNWS3009CC00E5.

RAM: 32GB

Code: 
root@node01:~# qm config 100
bootdisk: sata0
cores: 2
ide2: local:iso/CentOS-8.1.1911-x86_64-dvd1.iso,media=cdrom
memory: 512
name: centos
net0: virtio=F2:DD:71:96:22:85,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-100-disk-0,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=c3424983-efd1-4306-8880-ed5757152c0f
sockets: 1
vmgenid: be27d313-a2bf-4236-bf8b-f7c2addd4bcd

Thanks a lot for your precious help
 
Try installing with 2G of Ram - not sure CentOS 8 will be happy with only 512 M
 
subafr said:
ITS WORKING ! Nice Stoiko, you have made my day :)
Click to expand...
Oh interesting. I tried to reproduce this situation and was able to get the installer started with just 512MB RAM with the CentOS-8-x86_64-1905-dvd1.iso ISO.
 
Weird, I can now install Centos and windows Server, but Ubuntu hardlocking during install
proxmox2.jpg

This is ubuntu config
root@node01:~# qm config 102
bootdisk: sata0
cores: 2
ide2: local:iso/ubuntu-19.10-desktop-amd64.iso,media=cdrom
memory: 2048
name: ubuntu
net0: virtio=6A:50:88:6C:27:DB,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-102-disk-0,size=32G
smbios1: uuid=df8891ac-c21b-4502-9802-c0f53242658b
sockets: 1
vmgenid: 249de21b-37ec-4692-bb8c-45afb9b8c33b
 
Same problem for me with an Ubuntu 20.04 server ISO. I used all defaults for VM creation, except for 2 CPU cores instead of 1.

Bumping memory up to 1GB solved the issue for me.

I think the default amount of ram for Proxmox VM creation needs to be bumped up to 1024 MB.
 
Elliott Partridge said:
Same problem for me with an Ubuntu 20.04 server ISO. I used all defaults for VM creation, except for 2 CPU cores instead of 1.

Bumping memory up to 1GB solved the issue for me.

I think the default amount of ram for Proxmox VM creation needs to be bumped up to 1024 MB.
Click to expand...

Default is 2048 (if you use current stable version 6.x).
 
  • Like
Reactions: Elliott Partridge
I am using proxmox-ve/6.1-2 and pve-manager/6.1-8, and it fills in 512MB as the default. I'll try updating to the latest (pve 6.2-1, pve-m 6.2-11). Sounds like it was fixed somewhere along the way. Thanks!
 
BobhWasatch said:
Or you could, you know, read the Ubuntu installation guide.
Click to expand...
Do you read an installation guide every time you install an OS? After I got the error, I actually did look up the min install criteria, and came here to note the issue with the incorrect defaults. Which have since been updated, so the point is moot.

tom said:
Default is 2048 (if you use current stable version 6.x).
Click to expand...
Thanks. Updating to 6.2-x changed the defaults on the web dialog to 2048. All good now!
 
Elliott Partridge said:
Do you read an installation guide every time you install an OS? After I got the error, I actually did look up the min install criteria, and came here to note the issue with the incorrect defaults.
Click to expand...

Yes, I do check what the requirements are if I don't know them. I do not assume that the Proxmox defaults are correct, since it is impossible for them to be correct for every OS and the application scenario that it will be running.
 
You must log in or register to reply here.
Top Bottom