You are not logged in.
Pages: 1
Topic closed
TLDR:
ext4 was using 64bit by default. Reformat with -O ^64bit
Oh right, I installed arch a lot of times on different hardware, and I always use Syslinux. The thing is, the last two netbooks I installed with syslinux, throws that error.
Chroot and here are some outputs>
[root@archiso /]# syslinux-install_update -iam
Syslinux BIOS install successful
Boot Flag Set - /dev/sda1
Installed MBR (/usr/lib/syslinux/bios/mbr.bin) to /dev/sda
[root@archiso /]# ls -l /boot/syslinux/
total 2112
-rw-r--r-- 1 root root 0 Aug 4 18:41 SYSLINUX_AUTOUPDATE
-rw-r--r-- 1 root root 1596 Aug 4 18:41 cat.c32
-rw-r--r-- 1 root root 24716 Aug 4 18:41 chain.c32
-rw-r--r-- 1 root root 1228 Aug 4 18:41 cmd.c32
-rw-r--r-- 1 root root 3660 Aug 4 18:41 cmenu.c32
-rw-r--r-- 1 root root 1464 Aug 4 18:41 config.c32
-rw-r--r-- 1 root root 4184 Aug 4 18:41 cptime.c32
-rw-r--r-- 1 root root 4480 Aug 4 18:41 cpu.c32
-rw-r--r-- 1 root root 1748 Aug 4 18:41 cpuid.c32
-rw-r--r-- 1 root root 2748 Aug 4 18:41 cpuidtest.c32
-rw-r--r-- 1 root root 1568 Aug 4 18:41 debug.c32
-rw-r--r-- 1 root root 4040 Aug 4 18:41 dhcp.c32
-rw-r--r-- 1 root root 1988 Aug 4 18:41 disk.c32
-rw-r--r-- 1 root root 8660 Aug 4 18:41 dmi.c32
-rw-r--r-- 1 root root 11928 Aug 4 18:41 dmitest.c32
-rw-r--r-- 1 root root 3232 Aug 4 18:41 elf.c32
-rw-r--r-- 1 root root 2716 Aug 4 18:41 ethersel.c32
-rw-r--r-- 1 root root 10436 Aug 4 18:41 gfxboot.c32
-rw-r--r-- 1 root root 1576 Aug 4 18:41 gpxecmd.c32
-rw-r--r-- 1 root root 165464 Aug 4 18:41 hdt.c32
-rw-r--r-- 1 root root 3704 Aug 4 18:41 hexdump.c32
-rw-r--r-- 1 root root 1804 Aug 4 18:41 host.c32
-rw-r--r-- 1 root root 4120 Aug 4 18:41 ifcpu.c32
-rw-r--r-- 1 root root 1720 Aug 4 18:41 ifcpu64.c32
-rw-r--r-- 1 root root 4260 Aug 4 18:41 ifmemdsk.c32
-rw-r--r-- 1 root root 1872 Aug 4 18:41 ifplop.c32
-rw-r--r-- 1 root root 1648 Aug 4 18:41 kbdmap.c32
-rw-r--r-- 1 root root 4896 Aug 4 18:41 kontron_wdt.c32
-rw-r--r-- 1 root root 116368 Aug 4 18:41 ldlinux.c32
-r--r--r-- 1 root root 60928 Aug 4 18:41 ldlinux.sys
-rw-r--r-- 1 root root 5076 Aug 4 18:41 lfs.c32
-rw-r--r-- 1 root root 182532 Aug 4 18:41 libcom32.c32
-rw-r--r-- 1 root root 66744 Aug 4 18:41 libgpl.c32
-rw-r--r-- 1 root root 101840 Aug 4 18:41 liblua.c32
-rw-r--r-- 1 root root 24172 Aug 4 18:41 libmenu.c32
-rw-r--r-- 1 root root 23672 Aug 4 18:41 libutil.c32
-rw-r--r-- 1 root root 4700 Aug 4 18:41 linux.c32
-rw-r--r-- 1 root root 2960 Aug 4 18:41 ls.c32
-rw-r--r-- 1 root root 6820 Aug 4 18:41 lua.c32
-rw-r--r-- 1 root root 10200 Aug 4 18:41 mboot.c32
-rw-r--r-- 1 root root 2452 Aug 4 18:41 meminfo.c32
-rw-r--r-- 1 root root 26084 Aug 4 18:41 menu.c32
-rw-r--r-- 1 root root 3336 Aug 4 18:41 pci.c32
-rw-r--r-- 1 root root 1011638 Aug 4 18:41 pci.ids
-rw-r--r-- 1 root root 3460 Aug 4 18:41 pcitest.c32
-rw-r--r-- 1 root root 2956 Aug 4 18:41 pmload.c32
-rw-r--r-- 1 root root 1640 Aug 4 18:41 poweroff.c32
-rw-r--r-- 1 root root 3116 Aug 4 18:41 prdhcp.c32
-rw-r--r-- 1 root root 1476 Aug 4 18:41 pwd.c32
-rw-r--r-- 1 root root 12356 Aug 4 18:41 pxechn.c32
-rw-r--r-- 1 root root 1356 Aug 4 18:41 reboot.c32
-rw-r--r-- 1 root root 13792 Aug 4 18:41 rosh.c32
-rw-r--r-- 1 root root 1608 Aug 4 18:41 sanboot.c32
-rw-r--r-- 1 root root 3148 Aug 4 18:41 sdi.c32
-rw-r--r-- 1 root root 15428 Aug 4 18:41 sysdump.c32
-rw-r--r-- 1 root root 7544 Aug 4 18:41 syslinux.c32
-rw-r--r-- 1 root root 2513 Aug 4 18:10 syslinux.cfg
-rw-r--r-- 1 root root 3068 Aug 4 18:41 vesa.c32
-rw-r--r-- 1 root root 2180 Aug 4 18:41 vesainfo.c32
-rw-r--r-- 1 root root 26632 Aug 4 18:41 vesamenu.c32
-rw-r--r-- 1 root root 1840 Aug 4 18:41 vpdtest.c32
-rw-r--r-- 1 root root 2460 Aug 4 18:41 whichsys.c32
-rw-r--r-- 1 root root 3528 Aug 4 18:41 zzjson.c32
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda1 rw
INITRD ../intel-ucode.img,../initramfs-linux.img
Tried without "intel-ucode", still. Any ideas?
Last edited by forbi (2016-08-05 13:10:48)
Offline
I'm not sure how it would cause this error, but there is clearly something wrong with that syslinux.cfg.
What is your partition layout? Right now you have sda1 as both a boot parition and root parition.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
@Trilby
FWIW, I don't understand what you're getting at. I can't see anything clearly wrong with the menu entry he posted, so I can't help but wonder if you mean to suggest having "sda1 as both a boot parition and root parition" is a problem.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
@Trilby
Sorry, but I can't see any errors in that menu entry.
And that line was the only one modified. (sda1 and intel in initrd)
root@archiso ~ # fdisk -l
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x73230cb6
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 104859647 104857600 50G 83 Linux
And here is syslinux.cfg, ingore the line about sda2
root@archiso ~ # arch-chroot /mnt
[root@archiso /]# cat /boot/syslinux/syslinux.cfg
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT linux
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda1 rw
INITRD ../intel-ucode.img,../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda1 rw
INITRD ../initramfs-linux-fallback.img
LABEL linux
MENU LABEL Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda2 rw
INITRD ../intel-ucode.img,../initramfs-linux.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
Last edited by forbi (2016-08-04 23:40:35)
Offline
which filesystem are you using on sda1?
Offline
ext4
By the way, GRUB works just fine, which makes it weirder.
Last edited by forbi (2016-08-05 00:06:33)
Offline
Oops, sorry - I've never used syslinux on a single (boot on root) partition. I misunderstood how it would work. Sorry for the noise.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
ext4
Did you disable 64bit volume support when creating the filesystem?
From http://www.syslinux.org/wiki/index.php?title=Filesystem
As of Syslinux 6.03, "pure 64-bits", compression and/or encryption are not supported.
Quoting part of the release notes of version 1.43 of e2fsprogs (May 17, 2016):
Mke2fs will now create file systems with the metadata_csum and 64bit features enabled by default.
Users should rather (manually) disable the 64bit feature in the mke2fs command when creating / formatting a boot volume with ext2/3/4; otherwise, the bootloader (as of version 6.03) will fail.
passing '-O ^64bit' option to mkfs should do the trick.
EDIT: You might want to make sure that the '64bit' feature is actually enabled with dump2fs before wiping your partition
Last edited by ooo (2016-08-05 02:05:54)
Offline
@ooo
Thanks a lot man. I can confirm that ext4 was using 64bit and that was causing syslinux to fail.
Solved!
Offline
Not to necro, but this is the top google result, and the advice given here is needlessly complicated.
Instead of reformatting and reinstalling, one can simply use `resize2fs` with the -s flag to convert a 64 bit ext4 to 32 bit. This can be done from the Arch live install image.
Offline
Not to necro, but this is the top google result, and the advice given here is needlessly complicated.
Instead of reformatting and reinstalling, one can simply use `resize2fs` with the -s flag to convert a 64 bit ext4 to 32 bit. This can be done from the Arch live install image.
This worked for me.
- Installing on an oldish Dell notebook
- Using rufus to create the USB stick
- Using a single partition /dev/sda1
- Following the instructions to install syslinux
- Getting the message in the thread title.
Booting from the USB stick and running resize2fs -s /dev/sda1 fixed it.
Many thanks.
Offline
Thanks for sharing, but I'm going to go ahead and close this old topic now.
Closing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed