Arch Linux

MutantJohn

Member

Registered: 2012-12-17

Posts: 95

[SOLVED] So about the new /etc/mkinitcpio.conf hooks...

Hello All,

I recently started getting the error at boot, "root device was not configured to be mounted..." blah blah, something.

And I checked around it seems like the solution is to open up /etc/mkinitcpio.conf have the rw hook, assuming it doesn't exist.

So, my hook line looks like this:

HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

and I'm just wondering, am I really supposed to change it to this,

HOOKS="base udev autodetect modconf block filesystems keyboard fsck rw"

?

Sorry, I'm a nervous kitty when it comes to changing files like this as I have entirely not one idea what I am doing.

Last edited by MutantJohn (2013-08-07 18:39:59)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

You're looking in the wrong place. You need to change your bootloader config, not mkinitcpio.conf.

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

https://bbs.archlinux.org/viewtopic.php?id=167631

MutantJohn

Member

Registered: 2012-12-17

Posts: 95

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

Alright, I checked the file /etc/grub.d/10_linux as per that link karol posted.

I found the line :

  message="$(gettext_printf "Loading Linux %s ..." "${version}")"
  sed "s/^/$submenu_indentation/" << EOF
	echo	'$(echo "$message" | grub_quote)'
	linux	${rel_dirname}/${basename} root=${linux_root_device_thisversion} rw ${args}
EOF

But I still got the warning the last time I booted up so my file's updated to the solution that's supposed to work. So I'm just curious why I got that message then and if it'll happen again. I'm too lazy to reboot right now.

They also said, a solution was to remove the fsck hook which I'm assuming I through mkinitcpio.conf, right?

forumache

Member

From: Netherlands

Registered: 2011-09-02

Posts: 57

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

After modifying the file, have you regenerated grub configuration?

MutantJohn

Member

Registered: 2012-12-17

Posts: 95

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

How do I regenerate my grub configuration?

yiip

Member

Registered: 2013-08-07

Posts: 2

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

You can generate your config like this:

# grub-mkconfig -o /boot/grub/grub.cfg

For more Information, see https://wiki.archlinux.org/index.php/Gr … fig_file_2

Last edited by yiip (2013-08-07 08:26:14)

DexterLB

Member

Registered: 2011-06-20

Posts: 51

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

The intended way to do this is to use the systemd hook. Just change your HOOKS like this:

HOOKS="systemd autodetect modconf block filesystems leopard fsck"

e.g. replacing base and udev with systemd. Then do

# mkinitcpio -p linux

The idea is that when you're not using the systemd hook systemd needs to know if the root filesystem has already been checked, and the only way to do that is when it's mounted as rw. If, however, you use the systemd hook, which is now the recommended way, you avoid the issue altogether. You don't need to change kernel boot settings or mess with grub.

---

The best solution to a problem is usually the easiest one.

Mr.Elendig

#archlinux@freenode channel op

From: The intertubes

Registered: 2004-11-07

Posts: 4,097

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

Calling the systemd hook recommended at this point is a bit of an overstatement....
Not all the other hooks have been ported to work with it, and there are other downsides too, eg that it can be quite a bit slower.

---

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

DexterLB

Member

Registered: 2011-06-20

Posts: 51

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

Calling the systemd hook recommended at this point is a bit of an overstatement....
Not all the other hooks have been ported to work with it, and there are other downsides too, eg that it can be quite a bit slower.

Oops. Thanks for correcting my ignorance. It's still an option though, I haven't had any problems with it so far.

---

The best solution to a problem is usually the easiest one.

MutantJohn

Member

Registered: 2012-12-17

Posts: 95

Re: [SOLVED] So about the new /etc/mkinitcpio.conf hooks...

Oh, making sure the kernel boot line included the "rw" flag and regenerating the grub configuration file seems to have fixed all my issues.

I was cranky last night lol.

But thank you, everyone, for responding and helping me through this!