Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Asking for Maintenance during boot - udev
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Thu Nov 23, 2017 10:53 pm    Post subject: [SOLVED] Asking for Maintenance during boot - udev Reply with quote

Hello,

My system prompts me
Code:

starting udev
Generating a rule to create a /dev/root symlink
Populating /dev with existing devices through uevents ...
Give root password for maintenance
CTRL+D to continue

during boot.

When I continue and check dmesg after I freshly bootet it shows udev errors what might have something todo with it:
Code:

udevd[2100]: RUN{builtin}: 'uaccess' unknown /lib64/udev/rules.d/73-seat-late.rules:15
udevd[2101]: RUN{builtin}: 'uaccess' unknown /lib64/udev/rules.d/73-seat-late.rules:15

[   87.378421] FAT-fs (sdi1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.


When I try to boot my old kernel 4.12.5, dmesg shows the udev errors but my system doesn't ask me for maintenance during boot.

Please see attached my whole dmesg here

Could someone please advice what this error message means and how to fix it?

Thank you,
Kind Regards
Spargeltarzan


Last edited by Spargeltarzan on Thu Nov 30, 2017 5:29 pm; edited 1 time in total
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 5966

PostPosted: Fri Nov 24, 2017 12:15 am    Post subject: Reply with quote

run fsck on sdi1 you might be plague by openrc stupid new handling of errors.
Back to top
View user's profile Send private message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Fri Nov 24, 2017 8:11 am    Post subject: Reply with quote

sdi1 was an usb stick plugged, I removed it and the "please run fsck" warning disappeared. all others are still here
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 5966

PostPosted: Fri Nov 24, 2017 12:42 pm    Post subject: Reply with quote

you mean kernel boot fine in single mode?
perhaps you can boot normal, enter maintenance mode, remount / rw and copy that dmesg somewhere to gave the dmesg when it fail.
but it looks more like user land trouble than kernel trouble.
Back to top
View user's profile Send private message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Fri Nov 24, 2017 7:29 pm    Post subject: Reply with quote

I mean that the last message about the fsck does not have something todo with my udev issue. It was caused by a plugged bad formatted usb stick. This is now fixed, but the udev error persists.

the errors occur during a normal boot in the graphical environment.

The system launches normally, but it necessity to press CTRL+D during boot caught my attention and I checked my dmesg as attached.

So I can troubleshoot in my booted system or I can enter maintenance mode during boot - what can I do in either of them?
Back to top
View user's profile Send private message
jburns
l33t
l33t


Joined: 18 Jan 2007
Posts: 994
Location: Massachusetts USA

PostPosted: Fri Nov 24, 2017 10:18 pm    Post subject: Reply with quote

Code:
journalctl -b
will give you more information than dmesg. It will include the systemd messages as well as the dmesg output.
Back to top
View user's profile Send private message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Fri Nov 24, 2017 10:27 pm    Post subject: Reply with quote

Hi,

I do not use systemd and according to the wiki there is no equivalent for journalctl. Do you know how to get more details? What does it even mean my system proposes me to enter maintenance during boot, but finishes booting normally?
Back to top
View user's profile Send private message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Thu Nov 30, 2017 4:13 pm    Post subject: Reply with quote

My system still asks me to enter maintenance mode when booting - I have no idea why.........?
Back to top
View user's profile Send private message
Ant P.
Advocate
Advocate


Joined: 18 Apr 2009
Posts: 4511

PostPosted: Thu Nov 30, 2017 5:05 pm    Post subject: Reply with quote

Post the contents of /proc/cmdline
_________________
*.ebuild // /etc/service/*
Back to top
View user's profile Send private message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Thu Nov 30, 2017 5:10 pm    Post subject: Reply with quote

BOOT_IMAGE=/boot/vmlinuz-4.12.12-gentoo root=/dev/sda4 ro single

I tried booting kernel 4.12.5, here the boot works normally.
Back to top
View user's profile Send private message
Ant P.
Advocate
Advocate


Joined: 18 Apr 2009
Posts: 4511

PostPosted: Thu Nov 30, 2017 5:21 pm    Post subject: Reply with quote

It's giving the maintenance prompt because someone or something (the bootloader) is putting "single" on the command line. Find the source of that error and fix it, and the problem should go away.
_________________
*.ebuild // /etc/service/*
Back to top
View user's profile Send private message
Spargeltarzan
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jul 2017
Posts: 126

PostPosted: Thu Nov 30, 2017 5:29 pm    Post subject: Reply with quote

Thank you, I changed grub.cfg and now I can boot normally! :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum