emergency mode after update

[vikozo]

Hello
after a update and a reboot, Proxmox is booting and stops with the following Information.

Welcome to emergency mode! after logging in type
"journalctl -xb" to view system logs
"sysstemctl reboot" to reboot,
"systemctl default" to try again to boot into default mode

give root password for maintenance
or press ctrl - D to continue
-------
with sysstemctl reboot it hangs on the shutdown
with systemctl default it hangs also when shutdown

journalctl -xb
there are 1178 line some in red

any idea what i should check to make it run again??

have a nice day
vinc

 

[vikozo]

with systemctl default
after a long time 10 minutes or more
i got a
number INFO task plymouth 1719 blocked for more then 120 second
number "echo 0 > /proc/sys/kernel/hung_task_timout_secs" disable this message
and this information came many time

 

[vikozo]

there is also a error
"not tainted 4.2.8.1 pve #1"
after 6hours i had this and the error above <20 time but i stoped or froze

 

[spirit]

How do you have update ?

apt-get dist-upgrade ? (the right way) or apt-get upgrade ?

 

[vikozo]

i used the proxmox GUI to do it

but this afernoon i will check it if the apt-get will work, with ping a can reach the server

 

[vikozo]

Hello
a apt-get dist-upgrade did not help too all is the newest
a apt-get update found just a new file - so i am sure to have a least a web connection.

what should i do or how to solve this problem?
Thanks for any sugestion....

 

[vikozo]

any idea how to solve my problem?

 

[vikozo]

Please any sugestion how to solve this Problem?!

 

[vikozo]

i also have done a RAM Test which passed 3 time and 100% OK! please help the Server is not running.....

 

[RobFantini]

I think you should supply some or all of the log.

 

[vikozo]

how should i do that, on the comand line a lots of commands are not working - the sshd Server is not working too so i can't acces from remote ...

 

[fabian]

If mount works, you can try to mount some external disk/usb drive and put the log files there (either the binary journal files if available, or the journalctl output, or both).

 

[vikozo]

so i got it
journalctl xb > error-txt
the file is attached

i don't know how to format the file better - sorry

 

[fabian]

How did you originally install this system? There are a lot of errors in your log:
- a failing mount point "/mnt/NAS02-2TB"
- a non-existing or non-executable if-up.d snippet "vzifup-post" which prevents your vmbrX from coming up
- a kernel module that fails to load: "ipmi_si"
- plymouth configured, but the executable does not exist?

all but the last one could feasibly lead to systemd booting into emergency mode, depending on your exact configuration.. I would focus on the first two for now, my bets are on the failing mount point. You should probably not configure mount points depending on external systems as local file systems (Hint: "local-fs.target" fails right after the mount point fails). If systemd thinks your local file systems are not (all) available, it's no wonder it won't continue booting normally.

 

[vikozo]

Thnaks for your Feedback
i had at first ISO file which installed it without Problem and was up and runnig over a year with all updates and Upgrades too and some reboots too.

"/mnt/NAS02-2TB" was a try in the Proxmox GUI to add a storage NAS to put the backup in.
in the Proxmox -GUI i removed it because it did not work! i belive removing in GUI did not remove it on the host.
so how to delet this Mount Point?

i don't know this file - but i will look for it (non-executable if-up.d snippet "vzifup-post")
i don't know this file too- but i will look for it (Plymout)

 

[RobFantini]

you could try to remove the storage by editing this file: /etc/pve/storage.cfg

 

[vikozo]

Hello
in /etc/pve/storage.cfg was not the NAS02-2TB mentioned

put there was another nas i tryed to attach which did not work
but i deleted and rebootet

in /mnt is still a "file" called NAS02-2TB should i delet it?

 

[RobFantini]

Hello
in /etc/pve/storage.cfg was not the NAS02-2TB mentioned

put there was another nas i tryed to attach which did not work
but i deleted and rebootet

in /mnt is still a "file" called NAS02-2TB should i delet it?

deletions are only up to you.

If it is a file then that could be why the directory was not mounted.

or is it an empty directory?

 

[vikozo]

it is a empty directory

then mentioned storage i found in the directory /mnt/pve/

 

[RobFantini]

if you choose to delete it then use

rmdir /mnt/NAS02-2TB

So is your system all set?