HELP PLEASE - Problem upgrading to PVE7
- Thread starter Malli2602
- Start date
If it was an ssh session and not console that crashed, then most likely it got killed and process got interrupted mid-way. Your best and only way is to restart whatever step you were on.
In the future you should use "screen" to run important interactive tasks over ssh.
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
In the future you should use "screen" to run important interactive tasks over ssh.
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
root@pve:~# apt dist-upgrade
W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
A very basic intro - from ssh session:
- apt install screen
- screen
- run your commands
if you want to disconnect from screen and leave it running: ctrl-A-D
if you want to reconnect, either from manual disconnect or network crash: screen -r
There is much more to screen functionality, you can find many tutorials online - search for "GNU screen"
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
- apt install screen
- screen
- run your commands
if you want to disconnect from screen and leave it running: ctrl-A-D
if you want to reconnect, either from manual disconnect or network crash: screen -r
There is much more to screen functionality, you can find many tutorials online - search for "GNU screen"
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
https://askubuntu.com/questions/269...access-dpkg-status-area-read-only-file-system
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
There are many more google hits to that error message, i.e. :
https://askubuntu.com/questions/287...error-when-i-run-something-as-sudo-and-try-to
The issue is not Proxmox specific, its an OS upgrade problem that many people have run to over the years. Go through a few google hits and see what helps. There is no way for anyone to know what state your system is in now without detailed information.
Good luck.
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
https://askubuntu.com/questions/287...error-when-i-run-something-as-sudo-and-try-to
The issue is not Proxmox specific, its an OS upgrade problem that many people have run to over the years. Go through a few google hits and see what helps. There is no way for anyone to know what state your system is in now without detailed information.
Good luck.
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Judging from the screenshots you have major issues with hardware. 3 disks are missing (USB?), and sdf has went caput.
My advice would be to build a bootable live USB, boot from it and deal with each disk you expect to be present one by one from the console.
Make sure they are visable by OS, accessible and readable, ie dd if=/dev/device of=/dev/null
Good luck
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
My advice would be to build a bootable live USB, boot from it and deal with each disk you expect to be present one by one from the console.
Make sure they are visable by OS, accessible and readable, ie dd if=/dev/device of=/dev/null
Good luck
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox