Conclusion (as I understand it): 1. There is definitely a bug in Journalctl: it crashes (segfaults) on I/O errors. 2. You have a drive that is failing, or your BIOS might not be set correctly. This is causing the I/O errors. How large is the drive? You might have to turn off settings such as "SATA legacy compatibility" or the like -- I had a 3TB drive that would cause ATA command errors on a ~2006 computer; I found this option in the BIOS and as soon as I turned it off everything worked perfectly. Although journalctl should not crash on I/O errors, I think it is not unreasonable to assume that many other apps do not tolerate I/O errors either. So I would say: you should still report this bug upstream. -- Sébastien Leblanc
