recovering old information - success - 5.15.158-1 - HowTo restore GRUB?

iPanini

Well-Known Member
Mar 30, 2019
59
2
48
65
Hi everyone,

I'd like to request some help to see if I can:
- get an old system connected to the network again
- see what files are possibly recoverable

History:
A couple of years ago, probably 2019, I started out with Proxmox. At that time I ended up with two Proxmox machines.

Today:
Those older machines are not in use anymore, and I found a couple of loose 8TB harddrives that I would like to:
- be able to repurpose
- but would first like to investigate what data is worth while recovering

So what did I do:
- I have a NUC whit Debian on it.
- I also have a Sharkoon dual drive usb dock. (where you can put 3 1/2" drives in that then connect via USB to the computer)
- I first had a look at the drives using Gparted: one of the drives seems to have a zpool on it (but Gparted could not make much of that one). The second drive is a member of an LVM.

Then what happened:
- I did install LVM on the Debian NUC and to be sure I did a fresh reboot...
- I was then surprisingly encountered with a display that said: "Welcome to Proxmox Virtual Environment. Please use your web browser to configure this server - connect to:
https: //192.168.1.80:8006

This was a bit of a surprise to me, so what I know is that:
- there are disks missing from the LVM
- also it seems somehow the NUC running Proxmox seems to have no network? As I was totally unsure whether this was due to the NUC hardware or to maybe missing drivers or missing setup, I tried connecting a usb network adapter.
From this usb network adapter, I can see the led flashing, so I assume it is network capable.
- however the NUC / Proxmox has no connection to the network: I can not ping it, nor can I ping my home network from the NUC.

What advise can you give me?
- what steps do I need to take to get the network up again?
- in the best case scenario, if network can be brought up, will the Proxmox web interface be available?
- what are the mount points that I can check to see if / what data might be available on this old Proxmox LVM drive that still boots standalone into Proxmox?

Thanks for helping out!
 
Follow up: slight improvement

Hi,
I'm following up on the previous post.
One way or the other the "old" and original network config does not work. I think this is normal, because I'm trying to operate a single LVM Proxmox harddrive on totally different hardware.

I've now been able to add a usb network adapter, and have configured it to use DHCP. Mind, I'm no linux specialist at all, so most is throug search and try to follow an example.
So the status is that the 2nd network card using dhcp gets an IP address allright, and the next good thing is that I can access the Proxmox GUI using that same DHCP network address at port 8006.

Here's a copy of IP address show
---------------------------------------------------------
root@pve-0:~# ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 8c:0f:6f:72:c5:79 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
3: enx00249b2047d8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 00:24:9b:20:47:d8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.224/24 brd 192.168.1.255 scope global dynamic enx00249b2047d8
valid_lft 83231sec preferred_lft 83231sec
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 2e:b8:de:2d:b5:72 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.80/24 brd 192.168.1.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::2cb8:deff:fe2d:b572/64 scope link
valid_lft forever preferred_lft forever
5: tap106i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
link/ether 56:30:87:0b:da:e0 brd ff:ff:ff:ff:ff:ff
root@pve-0:~#
---------------------------------------------

And here's a copy of /etc/network/interfaces:
----------------------------------------------
root@pve-0:/etc/network# cat interfaces
auto lo
iface lo inet loopback

# iface enx00249b2047d8 inet manual

# Primary network interface
auto enx00249b2047d8
iface enx00249b2047d8 inet dhcp

auto vmbr0
iface vmbr0 inet static
address 192.168.1.80
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports enx00249b2047d8
bridge_stp off
bridge_fd 0

iface enx00249b2047d8 inet manual
root@pve-0:/etc/network#
----------------------------------------------
Now my questions:
How should I proceed to get eno1 configured and working?
(I've started the same machine / NUC with another distro, and both NIC's work allright with DHCP, so I think there's things with the network config of Proxmox that I do not properly understand)

I've tried upgrading using apt, but I run into trouble.

Here's the output of cat /etc/os-release
---------------------------------------------
root@pve-0:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@pve-0:~#
----------------------------------------------
What should I change /etc/apt/sources.list to so that:
- I can upgrade to Debian 12
- Upgrade Proxmox


Thanks for helping out!
Image 2.png
 
Last edited: