Debian сразу не стартует, просит нажать Ctrl+D
После нажатия ctrl+D система нормально запускается, но дело в том, что нужно, чтобы все происходила автоматически, т.к. предназначен он для удаленного использования. Как можно исправить это? Вывыод команды cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-486 root=UUID=1574feda-1c87-4124-8c82-92f7c65ea60a ro quiet 
Ошибки при старте:
[ ok ] Starting the hotplug events dispatcher: udevd. [ ok ] Synthesizing the initial hotplug events. done [. ] Waiting for /dev to be fully populated. [ . spkr' is already registered, aborting. done. [ ok ] Setting preliminary keymap. done. [ ok ] Setting parameters of disc: (none). [ ok ] Activating swap. done. [. ] Checking root filesystem. fsck from util-linux 2.20.1 /dev/sda1: clean, 120539/376752 files, 794127/1526784 blocks done. [info] Loading kernel module loop. [ ok ] Cleaning up temporary files. /tmp. [ ok ] Activating lbm and md swap. done. [. ] Checking file systems. fsck from util-linux 2.20.1 fsck.ext4: Unable to resolve 'UUID=ee8d17ee-f799-4ee4-911f-3f2310f3f880' fsck died with exit status 8 failed (code 8). [. ] File system check failed. A log is being saved in /var/log/fsck/checkfs i [FAILt location is writable. Please repair the file system manually. . failed! [. ] A maintenance shell will now be started. CONTROL-D will terminate this sh [warn] ell and resume system boot. . (warning). Give root password for maintenance (or type Control-D to continue): Не загружается CentOS 7
Прошу помощи с CentOS 7: Машина стоит виртуалкой на HyperV. Сегодня утром сервер начал тупить и я его решил ребутнуть. Долго ждал загрузки пока не подключился удаленно и не посмотрел, а там такой текст:
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue): Сделал по рекомендациям:
- загрузка с LiveCD или LiveUSB (например: GParted, SystemRescueCd)
- заходим под рутом
- просмотр дисков и разделов: fdisk -l
- узнать тип файловой системы: file -s /dev/sda1
- отмонтировать ФС: umount /dev/sda1
- вывести, что можно выполнить для данной ФС: fsck -N /dev/sda1
- проверка целостности ФС с исправлением всех ошибок в автоматическом режиме: fsck.ext4 -y /dev/sda1
- Проверку остальных разделов жесткого диска
- Перезагрузка, проверка.
Из-под HyperV не могу скопировать текст — не дает. Потому прикладываю скрин
Мануал не помог. По-прежнему не грузится. Подскажите, что можно сделать или может я что-то пропустил? Есть у кого какие мысли? и нужно ли после проверки с исправлением обратно маунтить sda1?
Give root password for maintenance (or press Control-D to continue):
Thanks for your kind reply. I changed 3 physical keyboards but still same problem. Perhaps this is not the main issue in my case as all keyboards that I changed are working well in linuc as well as in windows environment
Jan 26 at 8:26
0
You must log in to answer this question.
- boot
- grub2
- password
- recovery-mode
- password-recovery
-
The Overflow Blog
Linked
Hot Network Questions
Subscribe to RSS
Question feed
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.10.27.43697
Ubuntu and the circle of friends logo are trade marks of Canonical Limited and are used under licence.
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Tech Tips
Linux | Windows | Email | Security | Database | Network
How to exit emergency mode and boot to default mode in Linux? Linux
There would situations when the OS can go into emergency mode due to several reasons. This particular method is when one of the filesystems in corrupted. This document describes how to exit emergency mode and boot to default mode in Linux.
You will see the following screen –
Welcome to emergency mode! After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, “systemctl default” or ^D to try again to boot into default mode.
Give root password for maintenance (or type control-D to continue):
The below steps exits emergency mode and boot the server to default mode in Linux
Step 1: Please type in the root password. This may be your password. Reboot the server if required.
Step 2: CTRL+D and try again to reboot if it fails again.
Step 3: Press CTRL+ALT+DELETE which will reboot the server
Step 4: If the above steps do not resolve the issue, restart the server with CTRL+D with the root password and try following commands to reboot the server in default mode.
Step 5: Note down all valid mount points before running the unmount command. The following commands will unmount all the disks
Step 6: The next step is to edit the fstab file in /etc folder (/etc/fstab). Comment using the # the unmounted mount points.
Step 7: The next to reboot the server and the system will reboot in default mode.
At Velan, our server support engineers can help you on how to exit emergency mode and boot to default mode for your servers. We troubleshoot problems like these for our clients every day. If you are interested in our service, please fill the Quick connect form to get in touch with us