2013.08-1 archboot "2k13-R2" ISO hybrid image released

tpowa · 2013-07-11 13:57:23

Hi Arch community,

Arch Linux (archboot creation tool) 2013.08-1 "2k13-R2" has been released.

Homepage and for more information on archboot:
http://wiki.archlinux.org/index.php/Archboot

Please get it from your favorite arch linux mirror:
https://downloads.archlinux.de/iso/archboot/2013.08
<yourmirror>/iso/archboot/2013.08/

Further documentation can be found on-disk and on the wiki.
Thanks to all beta testers, which reported bugs during the beta releases.
Have fun!

greetings
tpowa

Last edited by tpowa (2013-08-24 05:36:07)

fredbezies · 2013-07-13 16:16:16

There is a bug when installing grub. Looks like it doesn't set correctly linux and initrd lines.

When I try to boot, I got this error :

ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
You're being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off

Testing in VirtualBox, GPT partitionning, with grub bios.

Will retry again and report any more infos.

EDIT : after I selected grub2-bios, got this error dialog saying :

Couldn't find /install/usr/lib/grub/i386-pc/kernel.img,
installing grub pkg now...

Nothing is logged in tty7

Last edited by fredbezies (2013-07-13 16:30:21)

the.ridikulus.rat · 2013-07-13 16:28:42

fredbezies wrote:

There is a bug when installing grub. Looks like it doesn't set correctly linux and initrd lines.
When I try to boot, I got this error :
ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
You're being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
Testing in VirtualBox, GPT partitionning, with grub bios.
Will retry again and report any more infos.

Oops, my mistake. Can you edit /arch/setup and add the command "bootloader_kernel_parameters" to common_bootloader_checks() function, at the end. That should fix it.

Last edited by the.ridikulus.rat (2013-07-13 16:57:54)

fredbezies · 2013-07-13 16:32:01

Will try asap and report.

Erh... In line 3450, I have this :

bootdev="$(mount | grep "${DESTDIR}/boot " | cut -d' ' -f 1)"

common_bootloader_checks() function is in line 3431.

Will try adding bootloader_kernel_parameters after activate_special_devices in modules list and report.

Last edited by fredbezies (2013-07-13 17:00:13)

the.ridikulus.rat · 2013-07-13 17:00:02

fredbezies wrote:

Will try asap and report.
Erh... In line 3450, I have this :
bootdev="$(mount | grep "${DESTDIR}/boot " | cut -d' ' -f 1)"
common_bootloader_checks() function is in line 3431.
Will try adding bootloader_kernel_parameters after activate_special_devices in modules and report.

Sorry mentioned wrong line num. You need to add the command at the end of common_bootloader_checks() function.

fredbezies · 2013-07-13 17:04:10

Well. Will try again. Adding it in the top of the list => same problem as before.

Adding bootloader_kernel_parameters at the end of the function doesn't work. Still getting root device not found

Last edited by fredbezies (2013-07-13 17:27:06)

tpowa · 2013-07-15 07:19:29

Ok fredbezies, issue is fixed in archboot git.

fredbezies · 2013-07-15 14:50:32

Thanks. Will wait to test a new ISO, now

tpowa · 2013-07-16 05:21:07

Beta2 iso files will now sync to the mirrors, with latest fixes.

fredbezies · 2013-07-16 19:42:59

Thanks. Grabbing it now and testing asap

fredbezies · 2013-07-16 20:20:42

Nearly working. This time I got these errors

error: no such device: root.
error: file '/boot/vmlinuz-linux' not found.
error: you need to load the kernel first.

Installing in VBox, 64 bits, GPT partitionning.

Any ideas. And sorry for the bad report again

the.ridikulus.rat · 2013-07-16 20:24:47

fredbezies wrote:

Nearly working. This time I got these errors
error: no such device: root.
error: file '/boot/vmlinuz-linux' not found.
error: you need to load the kernel first.
Installing in VBox, 64 bits, GPT partitionning.
Any ideas. And sorry for the bad report again

Are you using a separate /boot partition?

EDIT: Can you post the output of "gdisk -l /dev/sda" ? And also the /boot/grub/grub.cfg file?

Last edited by the.ridikulus.rat (2013-07-16 20:28:44)

fredbezies · 2013-07-16 20:35:03

Yes, I'm using a separate boot partition.

1) gdisk -l /dev/sda

GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 268435456 sectors, 128.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A775FFE9-38CB-40A6-912D-9D59910BD4AC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 268435422
Partitions will be aligned on 2048-sector boundaries
Total free space is 12254 sectors (6.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            6143   2.0 MiB     EF02  BIOS_GRUB
   2            8192         1056767   512.0 MiB   EF00  UEFI_SYSTEM
   3         1058816         2107391   512.0 MiB   8300  ARCHLINUX_BOOT
   4         2109440        10498047   4.0 GiB     8200  ARCHLINUX_SWAP
   5        10500096        52443135   20.0 GiB    8300  ARCHLINUX_ROOT
   6        52445184       268435422   103.0 GiB   8300  ARCHLINUX_HOME

2) generated grub.cfg

if [ "${grub_platform}" == "efi" ]; then
    set _UEFI_ARCH="${grub_cpu}"
    
    if [ "${grub_cpu}" == "x86_64" ]; then
        set _SPEC_UEFI_ARCH="x64"
    fi
    
    if [ "${grub_cpu}" == "i386" ]; then
        set _SPEC_UEFI_ARCH="ia32"
    fi
fi


insmod part_gpt
insmod part_msdos

# Include fat fs module - required for uefi systems.
insmod fat

insmod 
insmod 
insmod 

insmod search_fs_file
insmod search_fs_uuid
insmod search_label

insmod linux
insmod chain

set pager="1"
# set debug="all"

set locale_dir="${prefix}/locale"


if [ -e "${prefix}/${grub_cpu}-${grub_platform}/all_video.mod" ]; then
    insmod all_video
else
    if [ "${grub_platform}" == "efi" ]; then
        insmod efi_gop
        insmod efi_uga
    fi
    
    if [ "${grub_platform}" == "pc" ]; then
        insmod vbe
        insmod vga
    fi
    
    insmod video_bochs
    insmod video_cirrus
fi

insmod font

search --fs-uuid --no-floppy --set=usr_part  
search --fs-uuid --no-floppy --set=root_part  

if [ -e "(${usr_part})/share/grub/unicode.pf2" ]; then
    set _fontfile="(${usr_part})/share/grub/unicode.pf2"
else
    if [ -e "(${root_part})/usr/share/grub/unicode.pf2" ]; then
        set _fontfile="(${root_part})/usr/share/grub/unicode.pf2"
    else
        if [ -e "${prefix}/fonts/unicode.pf2" ]; then
            set _fontfile="${prefix}/fonts/unicode.pf2"
        fi
    fi
fi

if loadfont "${_fontfile}" ; then
    insmod gfxterm
    set gfxmode="auto"
    
    terminal_input console
    terminal_output gfxterm
fi


# DEVICE DETAILS: /dev/sda2 PARTUUID=65fbc856-2a07-425a-b550-5a0ddbdfc931 PARTLABEL=UEFI_SYSTEM UUID=B58D-5782 LABEL=EFISYS
# DEVICE DETAILS: /dev/sda3 PARTUUID=01278dbb-21ae-43d9-be20-0a2adf488a08 PARTLABEL=ARCHLINUX_BOOT UUID=75934fc2-f49d-46cd-b648-37aff7d1a8c2 LABEL=BOOT_ARCH
# DEVICE DETAILS: /dev/sda4 PARTUUID=ba34f61e-a39e-49f5-8b2a-5796f855fb31 PARTLABEL=ARCHLINUX_SWAP UUID=922826ec-b2da-49ab-acaf-060fe0de7217 LABEL=SWAP_ARCH
# DEVICE DETAILS: /dev/sda5 PARTUUID=69be011d-5fef-48ac-a27e-3dc31e9a61c0 PARTLABEL=ARCHLINUX_ROOT UUID=e8a2fa19-9cc2-422b-ac7c-70e89c2b722a LABEL=ROOT_ARCH
# DEVICE DETAILS: /dev/sda6 PARTUUID=cb00f67d-2607-4146-9689-d79f7a228bbf PARTLABEL=ARCHLINUX_HOME UUID=45dca558-759a-42aa-b0f8-6793343d61c7 LABEL=HOME_ARCH


# (0) Arch Linux
menuentry "Arch Linux" {
    set gfxpayload="keep"
    search --fs-uuid --no-floppy --set=root  
    linux /boot/vmlinuz-linux root=PARTUUID=69be011d-5fef-48ac-a27e-3dc31e9a61c0 rootfstype=ext4 rootflags=,relatime,data=ordered 
    initrd /boot/initramfs-linux.img
}


# (1) Arch Linux Fallback
menuentry "Arch Linux Fallback" {
    set gfxpayload="keep"
    search --fs-uuid --no-floppy --set=root  
    linux /boot/vmlinuz-linux root=PARTUUID=69be011d-5fef-48ac-a27e-3dc31e9a61c0 rootfstype=ext4 rootflags=,relatime,data=ordered 
    initrd /boot/initramfs-linux-fallback.img
}


if [ "${grub_platform}" == "efi" ]; then
    
    ## UEFI Shell 2.0
    #menuentry "UEFI Shell ${_UEFI_ARCH} v2" {
    #    search --fs-uuid --no-floppy --set=root  
    #    chainloader /EFI/tools/shell${_SPEC_UEFI_ARCH}_v2.efi
    #}
    
    ## UEFI Shell 1.0
    #menuentry "UEFI Shell ${_UEFI_ARCH} v1" {
    #    search --fs-uuid --no-floppy --set=root  
    #    chainloader /EFI/tools/shell${_SPEC_UEFI_ARCH}_v1.efi
    #}
    
fi


if [ "${grub_platform}" == "efi" ]; then
    if [ "${grub_cpu}" == "x86_64" ]; then
        ## Microsoft Windows via x86_64 UEFI
        #menuentry \"Microsoft Windows x86_64 UEFI-GPT\" {
        #    insmod part_gpt
        #    insmod fat
        #    insmod search_fs_uuid
        #    insmod chain
        #    search --fs-uuid --no-floppy --set=root  
        #    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
        #}
    fi
fi


if [ "${grub_platform}" == "pc" ]; then
    
    ## Microsoft Windows via BIOS
    #menuentry \"Microsoft Windows 7 BIOS-MBR\" {
    #    insmod part_msdos
    #    insmod ntfs
    #    insmod search_fs_uuid
    #    insmod ntldr
    #    search --fs-uuid --no-floppy --set=root 69B235F6749E84CE
    #    ntldr /bootmgr
    #}
    
fi

Hope it helps

Last edited by fredbezies (2013-07-16 20:44:31)

the.ridikulus.rat · 2013-07-16 20:58:57

@fredbezies: I found out whats the issue (no UUIDs at the end of "search" lines of grub.cfg), but this time I can't find any mistake in the /arch/setup code. Can you try changing

_GRUB_PROBE_="LD_LIBRARY_PATH=${DESTDIR}/usr/lib ${DESTDIR}/usr/bin/grub-probe"

to

export LD_LIBRARY_PATH="${DESTDIR}/usr/lib/:/usr/lib/"
_GRUB_PROBE_="${DESTDIR}/usr/bin/grub-probe"

in do_grub_config() function inside /arch/setup and try again?

Last edited by the.ridikulus.rat (2013-07-18 16:42:34)

fredbezies · 2013-07-17 07:25:21

Your modification is working. Another bug bites the dust. Thanks for the answer

arokh · 2013-07-21 18:31:10

Great work but found one bug. The module "efivars" is missing from the ISO. It's needed for using efibootmgr when installing a bootloader in UEFI boot mode. As it is grub-install runs and seemingly works fine. On reboot though, the system won't find the boot record.

Also, creating the package list takes a very long time. Any way to skip that and just go with the default set of packages? How about scripting the whole setup process like Redhat's kickstart? That would be awesome!

Last edited by arokh (2013-07-21 18:34:10)

tpowa · 2013-07-22 16:08:50

arokh wrote:

Also, creating the package list takes a very long time. Any way to skip that and just go with the default set of packages? How about scripting the whole setup process like Redhat's kickstart? That would be awesome!

Yes say not to enable [extra], then it is faster. Scripting is not possible with this setup, it's not coded for this purpose.

Derson5 · 2013-07-30 14:25:40

New kernel is in core, and I see many changes after release beta2. Is there will be new beta, or maybe stable version now?

tpowa · 2013-07-30 16:59:25

There will be a RC run soon when new syslinux,systemd will appear to be stable.

DarkPoe · 2013-08-02 21:10:47

Hello,

I'm a little new to the forums, but i wanted to ask something:

I boot with the Archboot ISO x86_64 (And seems Archlinux regular ISO too), i have a FakeRAID with ICH10R (Gigabyte G1 Sniper 3) and mdadm seems to recognize the array (RAID0) as /dev/md126, but the installer doesn't recognize them, just the USB partitions and with "dmraid -ay" it says the raid cannot be activated because of a stripe parse something... So i booted with Ubuntu live cd and followed the instructions to install from another linux distribution but it was messy and it doesn't boot correctly so I wanted to install with Archboot (which i have done before) but I have this problem.

Any suggestions?

tpowa · 2013-08-05 06:24:07

Oh ok, i never thought about this option.
The installer thinks mdXX devices as not partitionable.
You can blacklist mdadm activation during boot process.
EDIT:
disablehooks=arch_mdadm should do the trick.

The exact error message of dmraid -ay -I -Z would be really interesting.
Unfortunatly I cannot emulate such a device with qemu,
it must be something dmraid cannot handle but mdadm has code for it.

Could you run cfdisk or parted on this md device? and if yes how are the partitions called afterwards?

Last edited by tpowa (2013-08-05 19:40:14)

tpowa · 2013-08-08 06:32:28

New beta3 ISO will now sync to the mirrors.
Now also syslinux can be used as bootloader and many other fixes were implemented.
ISO is based on archboot-2013.08-1.

fredbezies · 2013-08-08 18:00:58

First test : i686 + ms-dos "like" partitions + grub2 = ok. It boots. Grub is correctly installed.

Will try x86_64 and gpt partitions asap.

DarkPoe · 2013-08-08 18:34:24

tpowa wrote:

Oh ok, i never thought about this option.
The installer thinks mdXX devices as not partitionable.
You can blacklist mdadm activation during boot process.
EDIT:
disablehooks=arch_mdadm should do the trick.
The exact error message of dmraid -ay -I -Z would be really interesting.
Unfortunatly I cannot emulate such a device with qemu,
it must be something dmraid cannot handle but mdadm has code for it.
Could you run cfdisk or parted on this md device? and if yes how are the partitions called afterwards?

I tried those options

With the beta2 and they didn't work it just didn't see the partitions

I don't know what you mean with cfdisk or parted but when i boot with gparted live it sees the partitions and i can work with them /dev/sdc1,2,3,4

I tired dmraid -ay -I -Z and it says that in the screenshot

I tried the beta3 and now it sees the partitions but i can't format the partition nor even mount it it says error mounting on /install

Any suggestions?

tpowa · 2013-08-08 20:20:34

I'm on your issue, the problem is udev, it runs mdadm before dmraid is executed.
Next iso will try to fix this, reassembling of the initrd is needed to fix this.
https://projects.archlinux.org/archboot … 3111c255ab

Arch Linux

#1 2013-07-11 13:57:23

2013.08-1 archboot "2k13-R2" ISO hybrid image released

#2 2013-07-13 16:16:16

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#3 2013-07-13 16:28:42

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#4 2013-07-13 16:32:01

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#5 2013-07-13 17:00:02

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#6 2013-07-13 17:04:10

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#7 2013-07-15 07:19:29

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#8 2013-07-15 14:50:32

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#9 2013-07-16 05:21:07

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#10 2013-07-16 19:42:59

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#11 2013-07-16 20:20:42

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#12 2013-07-16 20:24:47

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#13 2013-07-16 20:35:03

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#14 2013-07-16 20:58:57

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#15 2013-07-17 07:25:21

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#16 2013-07-21 18:31:10

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#17 2013-07-22 16:08:50

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#18 2013-07-30 14:25:40

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#19 2013-07-30 16:59:25

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#20 2013-08-02 21:10:47

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#21 2013-08-05 06:24:07

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#22 2013-08-08 06:32:28

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#23 2013-08-08 18:00:58

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#24 2013-08-08 18:34:24

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

#25 2013-08-08 20:20:34

Re: 2013.08-1 archboot "2k13-R2" ISO hybrid image released

Board footer