Proxmox installation "Trying to detect country"
- Thread starter ajocius
- Start date
Still happening on a fresh install on version 8.1. Got past it by going to a shell (Alt+F3 for me) then killing the traceroute process (kill -9 <pid>).
First post N00b here
The installer aborted and dumped me to root shell. There was no traceroute running (checked px ax | grep [t]raceroute) returned nothing.
Weirdly, the first attempt to install went fine because despite not detecting a country because the installer failed and duped to the CLI installer which worked fine. This only happened once and able to reproduce it.
Was able to install via the CLI.
The installer aborted and dumped me to root shell. There was no traceroute running (checked px ax | grep [t]raceroute) returned nothing.
Weirdly, the first attempt to install went fine because despite not detecting a country because the installer failed and duped to the CLI installer which worked fine. This only happened once and able to reproduce it.
Was able to install via the CLI.
Hi,
just to give an update: I have just sent out a patch-series, which should fix this issue: https://lists.proxmox.com/pipermail/pve-devel/2024-February/061677.html
Unfortunately - as evidenced by this thread, it is a very peculiar issue and more or less pure luck to reproduce. But all in all, this at least fixes a very weird interaction, which seems to have been the cause of the issue.
just to give an update: I have just sent out a patch-series, which should fix this issue: https://lists.proxmox.com/pipermail/pve-devel/2024-February/061677.html
Unfortunately - as evidenced by this thread, it is a very peculiar issue and more or less pure luck to reproduce. But all in all, this at least fixes a very weird interaction, which seems to have been the cause of the issue.
Had the same issue - was stopping with "trying to detect country...". Disconnecting Ethernet helped.
I encountered this issue for the first time installing ProxMox on a laptop with DHCP IP. However, this is also the first time I am installing ProxMox on other than server grade hardware.
Didn't have this problem when the network cable was unplugged. The ethernet adapter is a very common Realtek 8111/8168/8411 type.
Last edited:
Thanks for this, killing traceroute worked for me.
Strangely, the same traceroute command executed successfully when I switched to tty3 while the original was still stuck.
I ran into this issue installing Proxmox VE 8.2 (c96ad84eacbbcef299ab8f407f9602f832abb5ceb08a9aa288c1e1164df2da97) on my Dell R710.
I'm not that versed in Linux but after reading all the comments I decided to pull the additional NIC out of Riser 1. Ran the Graphical installation again, it sat at at 3% for about 3 mins "creating LV's" and the rest of the installation completed in about another 3-5 or so mins.
Tried it twice to see if it was consistent. Hope this helps some one.
I'm not that versed in Linux but after reading all the comments I decided to pull the additional NIC out of Riser 1. Ran the Graphical installation again, it sat at at 3% for about 3 mins "creating LV's" and the rest of the installation completed in about another 3-5 or so mins.
Tried it twice to see if it was consistent. Hope this helps some one.
I will admit I 'abandoned' by attempt to load Promox 9 via the installer. At the point where I was receiving the 'trying to detect country' and stopping the boot Just proved unnerving for me. Then again, I was dealing with other issues involving the machine. So, I loaded ubuntu server 26.04. Don't know if I will try Promox install again. Just venting.
You could install plain Debian Trixie. (Minimal version, without a Desktop.)
When it runs sufficiently you can add PVE: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie
Yes, I id create a Debian stand-alone boot disk. I probably 'judged' my Promox efforts too harshly. I was grappling with a 5-year old Supermicro server (trying to get the display to work [IPMI-related] -- Downloading Supermicro utility files. Things just became frustrating. So, I changed to Ubuntu (Since it was said that Promox would run well there, too). The 'bottom-line' of things was that the BIOS screen was showing through the installed graphics card (I forgot from 2019). Things are working now --- I still may install Promox. Gonna' let things 'settle' for just a little bit. Thanks for the reply.