|
|
|
| Grub Boot Errors |
- grub> duh...
- you could be missing the /boot/grub/menu.lst file
- check the contents of /boot/grub/menu.lst file
- GRUB GRUB GRUB GRUB ... forever ...
- Error 15: File missing
- check the /boot/grub/device.map file for its definition of hd0, hd1, ..
- set the correct value for root
- Possible Remedies
- if you are moving the bootable media ( usb-stick, hard disk ) from one PC to another,
you will have grub boot problems
- Remove the incorrect /boot/grub/device.map
- mv /boot/grub/device.map /bot/grub/device.old
- grub-install /dev/hda -- to reinstall the MBR on /dev/hda
- grub-install will recreate the correct device.map file
- ALWAYS Download and install the latest GRUB
Linux-Boot.net Grub-Download-From-CVS.sh.txt
Gentoo.org Grub Error Collection
Gentoo.org Grub-Error-Guide
LinuxQuestions.org Grub Tutorial
LinuxQuestions.org Grub Trouble shooter
|
| Lilo Boot Errors |
/usr/doc/lilo-22.7.1/README
- lilo -v -v -v >/boot/lilo.log 2>/boot/lilo.logerr
- /boot/lilo.logerr == should be empty if the boot configuration was correctly
- /boot/lilo.log == geometries and BIOS device numbers LILO will use
- fdisk -l /dev/hda
- lilo -T geom
Freshmeat.net lilo
IBM.com
Snow.nl Trouble Shooting Lilo
Ibiblio.org BootDisk-HOWTO
TLDP.org BootDisk-HOWTO
Washington.edu RH-9 - lilo
Washington.edu RH-EL3 - lilo
Suse.com ide-scsi
Suse.com lilo err msg
- L First stage boot loaded and started.
Usually indicates disk problems or invalid options in /etc/lilo.conf.
- LI Second stage boot loaded from /boot
invalid params in /etc/lilo.conf or /boot/boot.b was moved without re-running /sbin/lilo.
- LIL Second stage loader started
the descriptor table can't be loaded due to a bad disk or invalid parms in /etc/lilo.conf.
- LIL? Second stage loaded at an incorrect address
invalid parms in /etc/lilo.conf or /boot/boot.b was moved without re-running /sbin/lilo.
- LIL- Descriptor table is corrupt
invalid parms in /etc/lilo.conf or /boot/boot.b was moved without re-running /sbin/lilo.
- 1010101010101
- LILO All of LILO loaded correctly
- LILO: Keytable read/checksum error
- Some LILO Error Codes ^ L 99 99 99 99
- /usr/doc/lilo-22.x.y/README ( lilo-22.7.1 is the latest )
wlug.org.nz LiloErroCodes ( local copy )
wlug.org.nz LiloNotes
SlackwareHelp.org error codes
00 no error
01 invalid disk command
02 address mark not found
03 disk write-protected
04 sector not found
06 floppy disk removed
08 DMA overrun
0A bad sector flag
0B bad track flag
20 controller failure
40 seek failure (BIOS)
40 cylinder>1023 (LILO)
99 invalid second stage index sector (LILO)
9A no second stage loader signature (LILO)
- Possible Sources of Errors
- Incorrect lilo.conf file
- disk drive geometry mismatch
- /boot/vmlinuz too big ( 1.44MB for typical kernels )
- / ( rootfs ) or /boot is over 1023 cylinder boundry
- remove /boot/map and rerun lilo , /boot/map is created by lilo
- Possible Remedies
- if you are moving the bootable media ( usb-stick, hard disk ) from one PC to another,
you will have lilo boot problems
- Remove the incorrect /boot/map
- mv /boot/map /bot/map.old
- lilo -C /etc/lilo.CF.conf -- to reinstall the MBR on compactflash
boot=/dev/hda
map = /boot/map.hda
- lilo -C /etc/lilo.USB.conf -- to reinstall the MBR on usb-stick
boot=/dev/sda
map = /boot/map.sda
- lilo will recreate the correct map file
- ALWAYS Download and install the latest lilo
- You might need to specify cylinder/head/sector info
- Try (deprecated) linear vs lba32
|
| SysLinux Boot Errors |
- nothing on the screen
- you're probably missing /ldlinux.sys or /ldlinux.bin
|
|
|