The problem arose after several times of incorrect faults. When starting the system writes this

give root password for maintenance (or type control-d to continue)

After pressing ctrl + D, the system starts up normally, but the fact is that everything needs to happen automatically, because It is intended for remote use. How can I fix this?

Command output cat / proc / cmdline

 BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-486 root=UUID=1574feda-1c87-4124-8c82-92f7c65ea60a ro quiet

Startup errors:

Errors before start

 [ 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):
  • Is the root password set? - ߊߚ߀ߘ
  • 3
    you run in single-user mode instead of the usual - etki
  • one
    And there are no records about the problem with the file system? Or some other mistakes? - MAN69
  • please, in the question, give the output of the command $ lsb_release -a; cat /proc/cmdline $ lsb_release -a; cat /proc/cmdline - aleksandr barakin
  • 2
    Give the information that precedes the prompt to enter "root password". - aleksandr barakin

2 answers 2

judging by the content of the last of the images, the fsck program could not find a section with uuid ee8d17ee... :

fsck.ext4: Unable to resolve 'UUID=...'

Why did she even look for him? most likely because it is mentioned in the /etc/fstab (or in one of the files in the /etc/fstab.d/ directory, if there is one) and the last (sixth) field indicating the test order is not zero. something like this:

 UUID=ee8d17ee... Ρ‚ΠΎΡ‡ΠΊΠ°-монтирования Ρ‚ΠΈΠΏ-фс ΠΎΠΏΡ†ΠΈΠΈ-монтирования частота-создания-Π΄Π°ΠΌΠΏΠ° порядок-ΠΏΡ€ΠΎΠ²Π΅Ρ€ΠΊΠΈ

how to be? either fix this field to zero, or comment out this line by adding the # character to its beginning.

so choose - fix the sixth field or comment out? in the event that a section with such a uuid does not exist, it makes sense to comment out the line. You can see (after loading) uuids of all available partitions, for example, with the blkid program:

 $ sudo blkid
  • one
    Really. In / etc / fstab before this UUID, there were two in the sixth field. Zeroing, the system started up without any problems. - Timeon
  • As additional info: blkid may not be installed on some systems. Then you can use the command: ls -l / dev / disk / by-uuid - Crystal

enter the root password, and run fsck. Or look for how to make it so that fsck, at startup, not only checks, but also corrects errors right away. For example, as described here: http://www.opennet.ru/openforum/vsluhforumID1/51339.html

in 90% of cases this is the problem. After an emergency shutdown, the file system check is started, which, if errors are found, asks you to enter a root password in order to fix these errors.

UPD. Although the question has already been answered, but to bring the matter to the end, if the reason was precisely this:

The fsck command issues / dev / sda1 is mounted and e2fsck: Cannot continue, aborting. Photo of errors before the message added to the question

Option 1 (simple) :
Use liveCD.
Option 2 (more difficult, maybe something goes wrong):
Edit the file

vi / etc / fstab

either / dev / sda1 in ro (readonly), or comment out at all.
Then fsck.
Then:

mount -o remount, rw / dev / sda1 /

  • The fsck command issues / dev / sda1 is mounted and e2fsck: Cannot continue, aborting. Photo errors before the message added to the question. - Timeon