Pve unreachable after a powerloss autostart

[digamman]

Hi all I’ve go a strange issue on my pve, I set my s5 option in the bios as last state or power on after an ac power loss and it works( auto start ok).
My system boot up. But it show that it can be reached via it ip etc but nothing.

It is finally rechable after login via cli and reboot the system via cli. My question is how to solve that ?

It seems that the auto start after power loss makes a mess with the ethernet adapter ( in the pic nic0 is the usb-c adapter i use to get ethernet on the machine)

if possible i think i can make an autorestart after power loss start but i don’t know how to make the difference with a normal start.

 

[digamman]

 

[UdoB]

Please post the content of /etc/network/interfaces

"nic0" is DOWN - usually this means that it has to connection to a switch. Check that cable; look for LEDs showing "Link" established - on both ends. Use another cable if that fails. ... ...

 

[digamman]

The cable is new out from box from legrand and a cat6a so i don’t think so but i’ll check it asap when i’ll be back at home

 

[digamman]

Could it be the autostart off ?

 

[leesteken]

Could it be the autostart off ?

That is normal. The nic0 should be started automatically (without Autostart) when vmbr0 is started (which has Autostart on).
Did the name of the network device change maybe? Check the nic0 systemd script against the boot log.

 

[digamman]

Hum I'm quite a new user in proxmox, so I don't know how to check that, could you give me the path to get the log ?

 

[leesteken]

You can start reading the system log from the latest start using journalctl -b 0. I don't have much experience with the new stable network names, sorry. It's strange that nic0 (or whatever the actual PCI(e) network device is) does not start. There might be a clue in the system log.