Arch Linux

jamespharvey20

Member

Registered: 2015-06-09

Posts: 129

New archiso install iso (archlinux-2015.06.15-dual.iso) nfs error

I'm trying to build my own install iso (with today's date, archlinux-2015.06.15-dual.iso) by running archiso with no changes.  I ultimately want to make changes, but I'm trying to get this working first.

Are the official iso installers using modifications to archiso (or build.sh options) to prevent the error I'm getting below?

Or, did I run into a bug or incompatibility with the new packages that have come out in the last two weeks?

(Note IE auto changes systemd to system for me - think I changed them all back, but if there is a "d" missing anywhere, it's from IE, not the actual system.)

I can copy the official archlinux-2015.06.01-dual.iso into /boot, and boot from it using the following addition to /etc/grub.d/40_custom:

--- I'm running btrfs with default subvolume /root, so the /root/boot below refers to the /boot directory on the /root subvolume -- it does not refer into the root user's folder ---
menuentry "Arch ISO" {
   set isofile="/root/boot/archlinux-2015.06.01-dual.iso"
   loopback loop $isofile
   echo 'Loading Linux linux ...'
   linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201506 img_dev=$imgdevpath img_loop=$isofile earlymodules-loop
   echo 'Loading initial ramdisk ...'
   initrd (loop)/arch/boot/x86_64/archiso.img
}

But, if I:

pacman -S archiso
mkdir archlive
cp --recursive /usr/share/archiso/configs/releng/* archlive
cd archlive
./build.sh

Then, this creates out/archlinux-2015.06.15-dual.iso, which I copy into /boot and make a corresponding menuentry identical to that above, except for "2015.06.15".

When I boot from it, I get the following errors:

[FAILED] Failed to start Load Kernel Modules.
See "systemctl status systemd-modules-load.service" for details.
[    7.308911] systemd[1]: Failed to start Load Kernel Modules.
...
[FAILED] Failed to start Load Kernel Modules.
See "systemctl status systemd-modules-load.service" for details.

dmesg includes
systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE

systemctl status systemd-modules-load.service -l shows:
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/system/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2015-06-15 21:04:08 UTC; 25s ago
     Docs: man:systemd-modules-load.service(8)
               man:modules-load.d(5)
  Process: 551 ExecStart=/usr/lib/system/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 551 (code=exited, status=1/FAILURE)

Jun 15 21:04:08 archiso systemd[1]: Starting Load Kernel Modules...
Jun 15 21:04:08 archiso systemd-modules-load[551]: Failed to lookup alias 'nfs': Function not implemented
Jun 15 21:04:08 archiso systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Jun 15 21:04:08 archiso systemd[1]: Failed to start Load Kernel Modules.
Jun 15 21:04:08 archiso systemd[1]: Unit systemd-modules-load.service entered failed state.
Jun 15 21:04:08 archiso systemd[1]: systemd-modules-load.service failed.

Other than that, it boots, and I'm not using nfs, so I guess it's something I could ignore...

qinohe

Member

From: Netherlands

Registered: 2012-06-20

Posts: 1,498

Re: New archiso install iso (archlinux-2015.06.15-dual.iso) nfs error

Are the official iso installers using modifications to archiso (or build.sh options) to prevent the error I'm getting below?
Or, did I run into a bug or incompatibility with the new packages that have come out in the last two weeks?

Try it yourself, if you use the standard config, there should be no difference, though.
I think I would first build a ISO with the standard config and than start editing the files (releng) and tweak them so it becomes what you like.

If you build the ISO, use verbose for more output.

#./build.sh -v

Please use code tags, see https://bbs.archlinux.org/help.php#bbcode

BTW. There are no bugs, it builds without any issues.

jamespharvey20

Member

Registered: 2015-06-09

Posts: 129

Re: New archiso install iso (archlinux-2015.06.15-dual.iso) nfs error

Are the official iso installers using modifications to archiso (or build.sh options) to prevent the error I'm getting below?
Or, did I run into a bug or incompatibility with the new packages that have come out in the last two weeks?

Try it yourself, if you use the standard config, there should be no difference, though.
I think I would first build a ISO with the standard config and than start editing the files (releng) and tweak them so it becomes what you like.

If you build the ISO, use verbose for more output.

#./build.sh -v

Please use code tags, see https://bbs.archlinux.org/help.php#bbcode

BTW. There are no bugs, it builds without any issues.

Yeah, to start I'm using the standard config and not making my own changes.  Just executing:

cp --recursive /usr/share/archiso/configs/releng/* archlive
cd archlive
./build.sh

It builds just fine for me, but upon booting it through grub is when I get the "Failed to start Load Kernel Modules" failure.

There's no way for me to build an iso using packages as of a date and time, is there?  So, I could use the date and time the 2015.06.01-dual.iso was made, and see if it works then?  And if that works, I could binary search out what update causes the issue.

qinohe

Member

From: Netherlands

Registered: 2012-06-20

Posts: 1,498

Re: New archiso install iso (archlinux-2015.06.15-dual.iso) nfs error

Yeah, to start I'm using the standard config and not making my own changes.  Just executing:

cp --recursive /usr/share/archiso/configs/releng/* archlive
cd archlive
./build.sh

It builds just fine for me, but upon booting it through grub is when I get the "Failed to start Load Kernel Modules" failure.

Trying to understand what went wrong on your side, but I have no clue. I even rebuild a releng, whitout any problems, it boots just fine. Though I can only test x86, because my main machine died:(

There's no way for me to build an iso using packages as of a date and time, is there?  So, I could use the date and time the 2015.06.01-dual.iso was made, and see if it works then?  And if that works, I could binary search out what update causes the issue.

I'm not quite clear what it is you mean here, but, are you editing your own or  the Arch ISO, because of the date (2015-06-01) in the ISO name, or is that coincedence?
I would only change 'iso_name' in build.sh, and leave 'iso_label' for what it is.
You say it boots, you should be able to add packages to the list than.