You are not logged in.
Hi,
there's a message during boot that I'd like to see, but it's gone too
fast. It's not visible in `dmesg`, and also not via `journalctl -b`
(executed as root). Also `systemctl status` reports nothing
suspicious.
From what I could see the message seems to be surrounded by a
box of asterisks `*`, but I have no chance to read what it's about.
Any ideas where to look?
Thanks
Stefan
Last edited by stefan (2016-09-03 20:31:42)
Offline
have you tried all other options listed in the wiki ?
specifically this : https://wiki.archlinux.org/index.php/Ge … ay_on_tty1
Last edited by Inxsible (2016-08-24 16:56:07)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Hi, thanks for replying
have you tried all other options listed in the wiki ?
Well, `systemd`, `dmesg`, Kernel-parameter does not have `quiet`.
I've tried Ctrl-S/Q repeatedly, and I can stop before the message
appears, but when it appears it immediately scrolls through and is
gone, even if I hit Ctrl-S/Q almost simultaneously.
what else?
specifically this : https://wiki.archlinux.org/index.php/Ge … ay_on_tty1
Hmmm. This has the rather adverse effect that the screen becomes all
black, clearing all messages. Even the tty login prompt does not
appear until I hit Return.
Offline
Try to boot by editing grub menu by pressing 'e' key at menu and at line
linux /boot/vmlinuz-linux...... quiet
and remove the 'quiet' option.
Also take a look at
systemctl --state=feiled --all
There might be not something serious, just some delay starting a service but I don't know why you have to press enter to goto login.
Offline
Try to boot by editing grub menu by pressing 'e' key at menu and at line
I have to press Tab instead of `e`. Does that mean anything?
and remove the 'quiet' option.
There is no `quiet`.
Also take a look at
systemctl --state=feiled --all
root@tauhou:~# systemctl --state=feiled --all
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
root@tauhou:~# systemctl --state=failed --all
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
Offline
*sigh* I took a camera and filmed the boot process... I can't upload
the image, so here's the message transcribed:
:: performing fsck on '/dev/mapper/root'
********************** WARNING **********************
* *
* The root device is not configured to be mounted *
* read-write! It may be fsck'd again later. *
* *
*****************************************************
:: mounting '/dev/mapper/root' on real root
This does *not* show up in fsck:
root@tauhou:~# journalctl -b | grep fsck
Aug 25 10:27:59 tauhou systemd[1]: Created slice system-systemd\x2dfsck.slice.
Aug 25 10:27:59 tauhou systemd-fsck[435]: /dev/sda1: clean, 79/16384 files, 43559/65536 blocks
Aug 25 10:28:42 tauhou kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Note, `sdc1` is not the root device.
Two questions:
1. Is it a bug that the warning is not logged, i.e., should I file a
report? If so, then a bug of what? fsck, systemd, whatever?
2. What to do about the warning? When the system's running, I see
root@tauhou:~# mount | grep root
/dev/mapper/root on / type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
so `rw` means read-write. And is there even an `fsck` for BTRFS?
Offline
It is not clear to me what boot loader you are using. You will need to figure out how to change the kernel command line for the loader you are using.
Find out what the kernel command line you are using as follows
ewaller@turing ~ 1043 %cat /proc/cmdline
\vmlinuz-linux rw root=UUID=b395c435-49e5-411a-ab9c-196da7c8262c initrd=/intel-ucode.img initrd=/initramfs-linux.img acpi_backlight=native
ewaller@turing ~ 1044 %
Note the rw just before the root= clause? If you don't have that, edit your boot loader configuration to add it.
Inxsible: Hey, good to see you on the forums. Keeping busy?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
It is not clear to me what boot loader you are using.
Syslinux.
Find out what the kernel command line you are using as follows
ewaller@turing ~ 1043 %cat /proc/cmdline \vmlinuz-linux rw root=UUID=b395c435-49e5-411a-ab9c-196da7c8262c initrd=/intel-ucode.img initrd=/initramfs-linux.img acpi_backlight=native
Ah! I have the following in `/boot/syslinux/syslinux.cfg`, `ro` at the very end!
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/mapper/root cryptdevice=/dev/disk/by-uuid/1c75222f-8ab4-410f-8381-bb9ec2e45edf:root cryptkey=/dev/disk/by-label/key:ext2:key ro
INITRD ../initramfs-linux.img
I've copied that and created a second menu entry
LABEL arch2
MENU LABEL Arch Linux 2
LINUX ../vmlinuz-linux
APPEND root=/dev/mapper/root cryptdevice=/dev/disk/by-uuid/1c75222f-8ab4-410f-8381-bb9ec2e45edf:root cryptkey=/dev/disk/by-label/key:ext2:key rw
INITRD ../initramfs-linux.img
Booting this makes the message disappear.
Being positioned at the very end of the line, I was assuming ro/rw to
relate to the device with the key on, but thatwas obviously wrong.
Thank you very much!
Stefan
Offline
Cool. If it is solved, be sure to edit your first post in the thread and edit the thread title by prepending [SOLVED]
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Inxsible: Hey, good to see you on the forums. Keeping busy?
Very !!
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline