Long story short:
ssd is full, can boot server w some errors on boot, can login root, but can not run any qm commands even qm list - i/o error
what to do? If I add some drive does it help? How to add drive without web interface?
May I just move VMs manually to new hdd, format and setup proxmox 5 on same ssd from scratch and move those VMS manually or from web interface back? I want to upgrade to 5 anyway.
Long version:
1. Proxmox 4.x (I guess 4.4, spring 2017), zfs 250 GB SSD, Win10 templates and VMs, OSX templates and VMs. Direct pass through of video card and USB's. Only ssh, no LAN, so no web interface, I use USB Wi-Fi in VMs.
2. After automatic update on win10 (probably on 2 win VM,s one by one) win got boot loop/restore to previous version.
3. I found out in proxmox terminal i/o error, disk full, can not write...
4. shot down of win 10 from ssh qm manager do not work (can not write some file, disk full I guess)
5. manual shutdown of a proxmox server (power)
6. boot w errors, root OK, no qm list, no qm destroy VM xxxx, (I thought Rican destroy one of VMS and free some space)
ssd is full, can boot server w some errors on boot, can login root, but can not run any qm commands even qm list - i/o error
what to do? If I add some drive does it help? How to add drive without web interface?
May I just move VMs manually to new hdd, format and setup proxmox 5 on same ssd from scratch and move those VMS manually or from web interface back? I want to upgrade to 5 anyway.
Long version:
1. Proxmox 4.x (I guess 4.4, spring 2017), zfs 250 GB SSD, Win10 templates and VMs, OSX templates and VMs. Direct pass through of video card and USB's. Only ssh, no LAN, so no web interface, I use USB Wi-Fi in VMs.
2. After automatic update on win10 (probably on 2 win VM,s one by one) win got boot loop/restore to previous version.
3. I found out in proxmox terminal i/o error, disk full, can not write...
4. shot down of win 10 from ssh qm manager do not work (can not write some file, disk full I guess)
5. manual shutdown of a proxmox server (power)
6. boot w errors, root OK, no qm list, no qm destroy VM xxxx, (I thought Rican destroy one of VMS and free some space)