Linux – Are there rc logs in arch

arch linuxlogs

One of my processes is failing to start fairly early in the boot process (I suspect mdadm and I suspect that it's just taking longer than the rc script allows for) but I can't quite catch/see it during boot and Arch clears the screen before the login prompt appears. Does Arch keep any logs of the init process that might show or is there any way to see what was on the screen before it clears or keep it from clearing the screen?

update I'm really talking about the rc scripts and output to the screen… This does not actually translate to things sent to the system logs or errors output by daemons unfortunately. Gentoo had a special log just for the boot output, but it wasn't enabled by default, I'm hoping Arch has something similar.

Best Answer

If you add a -i option to the getty command in /etc/inittab this will stop the screen from clearing. So try something like:

c1:2345:respawn:/sbin/agetty -i -8 38400 tty1 linux

Related Solutions

Arch Linux Logs – Where to Find SSHD Logs

Try this command to view the log from systemctl:

journalctl -u sshd |tail -100

Linux – Arch Linux Encrypt entire drive

There are three separate issues involved in what you are trying to accomplish.

Encrypting an existing system. The correct way to do this would be to back up your exisiting install to another drive and start with a fresh install and rsync your relevant system files across once you have set up your encrypted Pi. This way you would be sure that you would not lose any data and would have a genuinely encrypted Pi (using the method described on the Arch Wiki LUKS page).
The problem with this approach is that the Archlinux ARM images are distributed as .img files and are intended to be dd'ed onto an SD Card, so—using the standard installation method—there is no opportunity to implement a more complex install, such as LUKS or LVM. One of the Archlinux ARM developers addressed this in a forum post and recommended using this script. This blog post has some specifics.
The third issue you will face is unlocking the encrypted device remotely. The standard method for doing this is using busybox and dropbear, as described in this U&L answer. This blog post has the details for a Debian Pi, but it should work for the Arch version.

Best Answer

Related Solutions

Arch Linux Logs – Where to Find SSHD Logs

Linux – Arch Linux Encrypt entire drive

Related Question