HELP PLEASE - Problem upgrading to PVE7

[Malli2602]

Hi guys,
I just started the upgrade to pve7.
Then my browser with the open session crash. how can I go back in to that session to see what the upgrade is doing?

Thanks for help.

Cheers
Stephan

 

[bbgeek17]

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

 

[Malli2602]

It was the session whatever is open when i click in browser on shell session :-/
Sorry I'm not that experianced

 

[Malli2602]

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.

 

[Malli2602]

root@pve:~# dpkg --configure -a
dpkg: error: unable to access the dpkg database directory /var/lib/dpkg: Read-only file system

 

[Malli2602]

reboot?

 

[bbgeek17]

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

 

[bbgeek17]

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

 

[Malli2602]

nothing of that post is helping me unfortunately

 

[bbgeek17]

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

 

[Malli2602]

I definitely need help.


Has someone an idea how to do a repair installation of a pve usb root device?

Cheers,
The crying man :_(

 

[Malli2602]

ok a manual fsck on the /dev/mapper/pve-root has fixed some issues so I can boot to maintenance mode.
What I can provide here to get the repair on track?

 

[Malli2602]

looks like there is something with the /dev/sdf device

 

[Malli2602]

Ok, the machine is pingable but I couldn't ssh into it.

 

[Malli2602]

Every time I try to start a service the machine is kicking me out of the session.
Think I need to fix first the broken sectors.

 

[bbgeek17]

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