I am trying to troubleshoot a system (Arch Linux) that had systemd installed.

The volume has been mounted on an Ubuntu system (14.04) that has no systemd installed.

How can I troubleshoot said systemd journal without switching the host box to systemd?

apt-get install journalctl does not work.

9

2 Answers

chroot into the Arch Linux system:

cd /location/of/arch/root
chroot /location/of/arch/root /bin/bash

journalctl looks for the journal files in /var/log/journal/machine-id/. If you boot up with a rescue OS that has a different machine ID or a different root it hence won't find any data there.

Hence,

a) use journalctl --directory=/var/log/journal/<machine-id>

b) or journalctl -m

The "-m" swicth merges the journals of all directories in /var/log/journal/*, hence makes it unnecessary to figure out the machine id of the host.

Source

1

the command line partition recovery program called TestDisk should allow some manipulation to the systemd (Arch Linux) volume

---

this not not a full or "good" solution. but TestDisk can

1. Rebuild a partition table, recover deleted partition
2. Locate the ext2/ext3/ext4 Backup SuperBlock
3. Copy files from deleted a ext2/ext3/ext4 partition.
4. handle a non-partitioned volume
5. Rewrite the Master boot record (MBR)

give it a try.

$ sudo apt-get install testdisk

start it

$ sudo testdisk

press Enter to create a new log & select the disk with the volume you want to manipulation

select the partition table type.
yours is Intel

from here you can

• view files
• Copy files

hope it helps

3

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy