On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can do?
- Thread starter nick
- Start date
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
The server only ask if it needs user intervention, i.e. to correct files system inconsistencies.
You can't change that. But you can by yourself an UPS.
The server only ask if it needs user intervention, i.e. to correct files system inconsistencies.
You can't change that. But you can by yourself an UPS.
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
I have an UPS...but sometimes the power failure it's bigger then UPS capacity.
I understand that....but what what we need to check. Where I can see the errors. I look in /var/log files but I can't find anything...
I have an UPS...but sometimes the power failure it's bigger then UPS capacity.
I understand that....but what what we need to check. Where I can see the errors. I look in /var/log files but I can't find anything...
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
On the console - when you press <ctrl-d>
On the console - when you press <ctrl-d>
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
When I press CTRL+D the system ask me for root password and that's it. wait for a command. To continue load the system we type Exit and press Enter.
No instructions about the maintenance command.
That's why I ask where to search in LOG to see what is the error and what I can do to correct.
I imagine that the system write this errors into a log file.
When I press CTRL+D the system ask me for root password and that's it. wait for a command. To continue load the system we type Exit and press Enter.
No instructions about the maintenance command.
That's why I ask where to search in LOG to see what is the error and what I can do to correct.
I imagine that the system write this errors into a log file.
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
Really - normally it prints information about what's wrong - including instruction what do to (i.e. run fsck).
Really - normally it prints information about what's wrong - including instruction what do to (i.e. run fsck).
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
man fsck
typically something like "fsck.ext3 -p /dev/mapper/pve-data" could do (if it's your pve-data that has been hit)
otherweise the path could be /dev/pve/root
but the few lines on the screen before "press ctrl+d" should explain quite clearly what's wrong.
Anyway, I'm impressed that simply logging in and rebooting helps along in this case.
regards
hk
man fsck
typically something like "fsck.ext3 -p /dev/mapper/pve-data" could do (if it's your pve-data that has been hit)
otherweise the path could be /dev/pve/root
but the few lines on the screen before "press ctrl+d" should explain quite clearly what's wrong.
Anyway, I'm impressed that simply logging in and rebooting helps along in this case.
regards
hk
Re: On each restart the PVE server requiere "Press CTRL+D to continue". What Ii can d
Hi,
another possibility is, that your hw-clock is wrong (e.g. 1 hour back). Ifn the filesystem time is in the future, the mounting fail.
Udo
Hi,
another possibility is, that your hw-clock is wrong (e.g. 1 hour back). Ifn the filesystem time is in the future, the mounting fail.
Udo