How to read boot log in rescue mode? – A server stack is the collection of software that forms the operational infrastructure on a given machine. In a computing context, a stack is an ordered pile. A server stack is one type of solution stack — an ordered selection of software that makes it possible to complete a particular task. Like in this post about How to read boot log in rescue mode? was one problem in server stack that need for a solution. Below are some tips in manage your linux server when you find problem about linux, log-files, boot, ubuntu-16.04, .
I have a remote server running Ubuntu 16.04 server that hangs on boot. In order to find the error I booted it in rescue mode, mounted devices to /mnt and chrooted to /mnt.
Here’s what I did so far:
root@rescue ~ # mount /dev/md2 /mnt
root@rescue ~ # mount /dev /mnt/dev
root@rescue ~ # mount /dev/pts /mnt/dev/pts
root@rescue ~ # mount /proc /mnt/proc
root@rescue ~ # mount /sys /mnt/sys
root@rescue ~ # chroot /mnt
Now when I try to read the boot log using journalctl I get
root@rescue ~ # journalctl
No journal files were found.
-- No entries --
Any suggestions how to get the boot log entries? Btw. there is no /var/log/boot.log
If the server hangs before filesystem is mounted (ie, early in boot stage), you are not likely to find anything in log file. Looking at error messages during normal boot process can give you clues
In your specific case, the error was in /etc/fstab which can lead to “unable to mount root filesystem” error if you boot without rescue mode.
