[SOLVED] Syslinux : Missing OS

xcodexif · 2013-11-01 00:31:18

Hello

On booting, Syslinux show me this error message : `Missing OS`
After, the BIOS displays its `Operating System not found` error message.

Syslinux is is properly installed (MBR right, /boot (/dev/sda1) is flagged bootable, with Syslinux on it, all this tested with HDT).
I have NOT a GPT :

# fdisk -l
Disk /dev/sda: 60.0 GB, 60022480896 bytes, 117231408 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
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63       64259       32098+  83  Linux
/dev/sda2           64260     3968054     1951897+  82  Linux swap / Solaris
/dev/sda3         3968055   117231407    56631676+  83  Linux

Disk /dev/mapper/arch_root-image: 1490 MB, 1490026496 bytes, 2910208 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

`syslinux-install_update -im` worked well.
I have a Phoenix BIOS.

Thanks for your help

Last edited by xcodexif (2013-11-01 16:52:38)

VanillaFunk · 2013-11-01 00:38:07

in your syslinux.cfg file...

did you set the correct sda to boot

the default is sda3 and that in your case it should be sda1 not the one defaulted

edit /boot/syslinux/syslinux.cfg and if neccessary post it

--edit--

also set the fallback in case you have issues later (also to sda1)

Last edited by VanillaFunk (2013-11-01 00:41:10)

xcodexif · 2013-11-01 00:53:29

Done, but nothing more.

Here is my 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 arch
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 ../initramfs-linux.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda1 rw
    INITRD ../initramfs-linux-fallback.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

skottish · 2013-11-01 00:55:00

Your root need to be sda3. It's not the boot, it's where / is.

cfr · 2013-11-01 00:56:50

Post the output from lsblk -f.

I am guessing sda1 is /boot and sda3 is /. If so, was /boot mounted when you installed the current kernel and generated the initramfs? If this is a new install, did you mount sda3 BEFORE making the directory /boot and mounting sda1 when installing?

xcodexif · 2013-11-01 01:01:41

cfr wrote:

I am guessing sda1 is /boot and sda3 is /.

Yes

cfr wrote:

If so, was /boot mounted when you installed the current kernel and generated the initramfs?

Yes. I used `mkinitcpio -p linux`, as on the french wiki

cfr wrote:

If this is a new install, did you mount sda3 BEFORE making the directory /boot and mounting sda1 when installing?

Of course

# fdisk -l
Disk /dev/sda: 60.0 GB, 60022480896 bytes, 117231408 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
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63       64259       32098+  83  Linux
/dev/sda2           64260     3968054     1951897+  82  Linux swap / Solaris
/dev/sda3         3968055   117231407    56631676+  83  Linux

Last edited by xcodexif (2013-11-01 01:04:50)

cfr · 2013-11-01 01:04:07

skottish wrote:

Your root need to be sda3. It's not the boot, it's where / is.

xcodexif wrote:

cfr wrote:

If this is a new install, did you mount sda3 BEFORE making the directory /boot and mounting sda1 when installing?

Of course

# fdisk -l
Disk /dev/sda: 60.0 GB, 60022480896 bytes, 117231408 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
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63       64259       32098+  83  Linux
/dev/sda2           64260     3968054     1951897+  82  Linux swap / Solaris
/dev/sda3         3968055   117231407    56631676+  83  Linux

If that is supposed to demonstrate the truth of the "Of course", you should know that it does nothing of the kind. But fix the error skottish pointed out first. If it still doesn't work, reconsider the order you did things in when installing.

Last edited by cfr (2013-11-01 01:06:16)

xcodexif · 2013-11-01 01:06:03

cfr wrote:

skottish wrote:
Your root need to be sda3. It's not the boot, it's where / is.

I have seen.

VanillaFunk · 2013-11-01 01:06:30

can you paste your /boot directory (sorry about that i shouldnt have assumed that root was on sda1)

xcodexif · 2013-11-01 01:08:28

cfr wrote:

If that is supposed to demonstrate the truth of the "Of course", you should know that it does nothing of the kind

No, I wrote this message too fast. You asked me for this before.

Last edited by xcodexif (2013-11-01 01:13:32)

xcodexif · 2013-11-01 01:10:25

VanillaFunk wrote:

can you paste your /boot directory (sorry about that i shouldnt have assumed that root was on sda1)

No problem.

Here is :

# ls -R /mnt/boot
/mnt/boot:
initramfs-linux-fallback.img  lost+found/  vmlinuz-linux
initramfs-linux.img	      syslinux/

/mnt/boot/lost+found:

/mnt/boot/syslinux:
cat.c32        ethersel.c32  kontron_wdt.c32  mboot.c32     rosh.c32
chain.c32      gfxboot.c32   ldlinux.c32      meminfo.c32   sanboot.c32
cmd.c32        gpxecmd.c32   ldlinux.sys      menu.c32	    sdi.c32
config.c32     hdt.c32	     libcom32.c32     pci.ids	    sysdump.c32
cptime.c32     hexdump.c32   libgpl.c32       pcitest.c32   SYSLINUX_AUTOUPDATE
cpuid.c32      host.c32      liblua.c32       pmload.c32    syslinux.cfg
cpuidtest.c32  ifcpu64.c32   libmenu.c32      poweroff.c32  vesainfo.c32
debug.c32      ifcpu.c32     libutil.c32      prdhcp.c32    vesamenu.c32
disk.c32       ifmemdsk.c32  linux.c32	      pwd.c32	    vpdtest.c32
dmitest.c32    ifplop.c32    ls.c32	      pxechn.c32    whichsys.c32
elf.c32        kbdmap.c32    lua.c32	      reboot.c32    zzjson.c32

xcodexif · 2013-11-01 01:16:01

cfr wrote:

Post the output from lsblk -f.

Oh, I saw `fdisk -l`. Sorry...

Here is :

NAME              FSTYPE   LABEL       UUID                                 MOUNTPOINT
sda                                                                         
-sda1            ext2                 635fdeb1-ff33-49eb-88fd-8ed620831018 /mnt/boot
-sda2            swap                 c3da14f1-2154-46d3-be7b-daa6720a4b8e 
-sda3            ext4                 a05ad52d-3980-40fd-94f8-7398d19731b3 /mnt
sr0               iso9660  ARCH_201307 2013-07-01-07-32-58-00               /run/archiso/bootmnt
loop0             squashfs                                                  /run/archiso/sfs/root-image
loop1             ext4                 06710541-dc70-4d8f-9a9c-e19e6bdf1c89 
-arch_root-image ext4                 06710541-dc70-4d8f-9a9c-e19e6bdf1c89 /
loop2             ext4                 06710541-dc70-4d8f-9a9c-e19e6bdf1c89 
-arch_root-image ext4                 06710541-dc70-4d8f-9a9c-e19e6bdf1c89 /

Last edited by xcodexif (2013-11-01 01:18:54)

VanillaFunk · 2013-11-01 01:19:46

you said you ran:

syslinux-install_update -im

shouldnt it have been

syslinux-install_update -i -a -m

not 100% sure on that but not sure what running it now would do (id wait till someone says so before unless you back up your /boot directory first

xcodexif · 2013-11-01 01:22:23

VanillaFunk wrote:

you said you ran:
syslinux-install_update -im
shouldnt it have been
syslinux-install_update -i -a -m
not 100% sure on that but not sure what running it now would do (id wait till someone says so before unless you back up your /boot directory first

I done this because with -a option, the `FAILED to set attribute Legacy BIOS Bootable` error appears. Anyway, I make sda1 bootable manually. HDT shows sda1 as bootable.

xcodexif · 2013-11-01 01:24:18

VanillaFunk wrote:

id wait till someone says so before unless you back up your /boot directory first

Ho, It's just the fourth install today... Nothing to back up

VanillaFunk · 2013-11-01 01:26:59

just not sure if itd break summin to rerun syslinux-install_update (never had to and i wouldnt want to make your issues worse)

-- the reason to back up would be to recreate it and recopy if something went wrong --

Last edited by VanillaFunk (2013-11-01 01:27:47)

xcodexif · 2013-11-01 01:29:34

VanillaFunk wrote:

just not sure if itd break summin to rerun syslinux-install_update (never had to and i wouldnt want to make your issues worse)
-- the reason to back up would be to recreate it and recopy if something went wrong --

I done this lot of times today on lot of installs.
I have nothing to loss, except 15 minutes of time each install...

VanillaFunk · 2013-11-01 01:32:08

xcodexif wrote:

VanillaFunk wrote:
just not sure if itd break summin to rerun syslinux-install_update (never had to and i wouldnt want to make your issues worse)
-- the reason to back up would be to recreate it and recopy if something went wrong --
I done this lot of times today on lot of installs.
I have nothing to loss, except 15 minutes of time each install...

has it consistently been the same point where things go wrong ? and did you use the begginers guide?

never had issues when following this

https://wiki.archlinux.org/index.php/Beginners%27_Guide

VanillaFunk · 2013-11-01 01:37:40

not trying to overstep the advice of cfr n skottish they would know better than me
just trying to be of help so ...

cfr · 2013-11-01 03:04:54

I am not even a syslinux user .

I know that others have reported that the automated install sometimes doesn't work. So I suggest you try manual installation as the next step.

You don't need to keep reinstalling the entire system, by the way. You can just redo the boot loader bits.

jrussell · 2013-11-01 05:53:46

Perhaps see what grub says, could you post the errors you get after running syslinux-install_update -iam

xcodexif · 2013-11-01 10:17:20

cfr wrote:

You don't need to keep reinstalling the entire system, by the way. You can just redo the boot loader bits.

That's what I am doing, but last time I excluded some packages from base group. I thought that it could be the problem. But no. I'll try to use the english beginners guide.

xcodexif · 2013-11-01 10:48:24

If you want, this is my installation procedure :

loadkeys fr-pc
bash

# Check the date
date

############# PARTITIONING #############

cfdisk
	
#	[ Delete ] all the partitions	
#
#	sda1	boot	prim	linux	100MB
#	sda2		prim	swap	2GB
#	sda3		prim	linux	[REST]
#
#	[ Write ] yes
#	[ Quit ]

lsblk
	# We check the partitions

mkfs.ext2 /dev/sda1
mkfs.ext4 /dev/sda3
mount /dev/sda3 /mnt
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot

mkswap /dev/sda2
swapon /dev/sda2

############# NETWORK (without dhcp) #############

echo [HOSTNAME] > nano /etc/hostname

ifconfig
	# Get the right ethernet interface

ip link set dev [INTERFACE] up
ifconfig [INTERFACE] [IP] netmask [NETMASK] broadcast [BROADCAST]
# OR without broadcast
ip addr add [IP]/[MASKBITS] dev [INTERFACE]
ip route add default via [GATEWAY] dev [INTERFACE]
nano /etc/resolv.conf
#	nameserver [NAMESERVER]
#	[ Save ]

ping www.torproject.org    # Hello (internet) world !

############# PACMAN INSTALLATIONS #############
# Think about french mirrors

	# Excluding some packages from `base` group
	# __MUST BE IN BASH__
	# TO EXCLUDE : perl, dhcpcd, vi, texinfo, sed, pcmisc, vfsutils, xfsprogs, reiserfsprogs, pcmciautils, mdadm, heirloom-mailx
	# TO ADD : lynx, wget, fbset, fakeroot, sudo
base=$(pacman -Qgq base | grep -Ev "[PACKAGE1]|[PACKAGE2]|[...]")
pacstrap /mnt $base [PACKS_TO_ADD]
pacstrap /mnt syslinux

############# CONFIGURATIONS #############

genfstab -U -p /mnt >> /mnt/etc/fstab
cat /mnt/etc/fstab	# Verify

arch-chroot /mnt bash
	
	nano /etc/vconsole.conf
	#	KEYMAP=fr-pc
	#	[ Save ]
	
	mkinitcpio -p linux

		# SYSLINUX install and configuration
	/usr/bin/syslinux-install_update -im
	nano /boot/syslinux/syslinux.cfg
	#	TIMEOUT 20
	#	...
	#	MENU TITLE ArchLinux - [HOSTNAME]
	#	MENU COLOR [...]
	#	...
	#	LABEL arch
	#		...
	#		APPEND ... vga=773

	passwd
	#	[MACHINECODE][SECRET][USER]
	
	exit

umount /mnt/boot /mnt
reboot

############# AFTER-INSTALL CONFIG #############

xcodexif · 2013-11-01 13:14:49

# /usr/bin/syslinux-install_update -iam
Syslinux BIOS install successful
FAILED to set attribute Legacy BIOS Bootable on /dev/sda1

# /usr/bin/syslinux-install_update -im
Syslinux BIOS install successful
Installed MBR (/usr/lib/syslinux/bios/gptmbr.bin) to /dev/sda

teateawhy · 2013-11-01 13:25:37

Don't exclude sed.

Arch Linux

#1 2013-11-01 00:31:18

[SOLVED] Syslinux : Missing OS

#2 2013-11-01 00:38:07

Re: [SOLVED] Syslinux : Missing OS

#3 2013-11-01 00:53:29

Re: [SOLVED] Syslinux : Missing OS

#4 2013-11-01 00:55:00

Re: [SOLVED] Syslinux : Missing OS

#5 2013-11-01 00:56:50

Re: [SOLVED] Syslinux : Missing OS

#6 2013-11-01 01:01:41

Re: [SOLVED] Syslinux : Missing OS

#7 2013-11-01 01:04:07

Re: [SOLVED] Syslinux : Missing OS

#8 2013-11-01 01:06:03

Re: [SOLVED] Syslinux : Missing OS

#9 2013-11-01 01:06:30

Re: [SOLVED] Syslinux : Missing OS

#10 2013-11-01 01:08:28

Re: [SOLVED] Syslinux : Missing OS

#11 2013-11-01 01:10:25

Re: [SOLVED] Syslinux : Missing OS

#12 2013-11-01 01:16:01

Re: [SOLVED] Syslinux : Missing OS

#13 2013-11-01 01:19:46

Re: [SOLVED] Syslinux : Missing OS

#14 2013-11-01 01:22:23

Re: [SOLVED] Syslinux : Missing OS

#15 2013-11-01 01:24:18

Re: [SOLVED] Syslinux : Missing OS

#16 2013-11-01 01:26:59

Re: [SOLVED] Syslinux : Missing OS

#17 2013-11-01 01:29:34

Re: [SOLVED] Syslinux : Missing OS

#18 2013-11-01 01:32:08

Re: [SOLVED] Syslinux : Missing OS

#19 2013-11-01 01:37:40

Re: [SOLVED] Syslinux : Missing OS

#20 2013-11-01 03:04:54

Re: [SOLVED] Syslinux : Missing OS

#21 2013-11-01 05:53:46

Re: [SOLVED] Syslinux : Missing OS

#22 2013-11-01 10:17:20

Re: [SOLVED] Syslinux : Missing OS

#23 2013-11-01 10:48:24

Re: [SOLVED] Syslinux : Missing OS

#24 2013-11-01 13:14:49

Re: [SOLVED] Syslinux : Missing OS

#25 2013-11-01 13:25:37

Re: [SOLVED] Syslinux : Missing OS

Board footer