Description of problem: Running lilo gives the error Reading boot sector from /dev/fd0 Fatal: open /dev/fd0: No such device or address Running it a second time works. Version-Release number of selected component (if applicable): [root@M4 lilo]# lilo -V LILO version 24.0 (released 07-Juni-2013) How reproducible: Very. First attempt after a reboot fails, subsequent attempts succeed. Might be hardware related - I have only noticed it on one machine. Steps to Reproduce: 1. Reboot 2. Do this... Password: [root@M4 ~]# cd /mnt/lilo/lilo/ [root@M4 lilo]# ll total 827 -rw-r--r-- 1 root root 647 Apr 19 14:56 image.conf -rw-r--r-- 1 root root 575 Apr 18 16:28 image.conf~ -rw-r--r-- 1 root root 1895 Apr 18 16:30 lilo.floppy.conf~ -rw-r--r-- 1 root root 1614 Jan 19 20:42 lilo.M3.floppy.conf -rw-r--r-- 1 root root 1409 Jan 19 21:58 lilo.M4a1r.conf -rw-r--r-- 1 root root 1749 Jul 14 11:23 lilo.M4.floppy.conf -rw-r--r-- 1 root root 1341 Feb 16 11:54 lilo.M4root.conf -rw-r--r-- 1 root root 2216 Jul 14 11:24 lilo.V.floppy.conf -rw-r--r-- 1 root root 2173 Apr 19 18:50 lilo.V.floppy.conf~ -rw------- 1 root root 712704 Mar 25 19:00 map.floppy.Vinux -rw------- 1 root root 38912 Jan 19 21:59 map.M4a1r -rw------- 1 root root 53760 Jul 14 11:25 map.mbr -rw-r--r-- 1 root root 12288 Sep 3 2013 oldswap -rw-r--r-- 1 root root 1197 Apr 19 18:51 other.conf -rw-r--r-- 1 root root 1193 Apr 19 15:22 other.conf~ [root@M4 lilo]# ll /dev/fd0 brw-rw---- 1 root floppy 2, 0 Jul 14 16:22 /dev/fd0 [root@M4 lilo]# lilo -C lilo.M4.floppy.conf Reading boot sector from /dev/fd0 Fatal: open /dev/fd0: No such device or address [root@M4 lilo]# echo $? 1 [root@M4 lilo]# lilo -C lilo.M4.floppy.conf Reading boot sector from /dev/fd0 Warning: boot record relocation beyond BPB is necessary: /dev/fd0 Using MENU secondary loader Calling map_insert_data Warning: The boot sector and map file are on different disks. Skipping /dev/sda10 Skipping /dev/sda10 Skipping /dev/sda3 Skipping /dev/sda3 Boot other: /dev/sdb10, loader CHAIN Pseudo partition start: 12269568 Added sdB10_Vinux * Boot other: /dev/sdb10, loader CHAIN Pseudo partition start: 12269568 Added sdB10_alt_Vinux Boot other: /dev/sdb3, on /dev/sdb, loader CHAIN Added sdB3_test Boot other: /dev/sdb3, on /dev/sdb, loader CHAIN Added sdB3_alt_test Boot other: /dev/sdb1, on /dev/sdb, loader CHAIN Added sdB1_Win Boot other: /dev/sdb1, on /dev/sdb, loader CHAIN Added sdB1_alt_Win Boot other: /dev/sda1, on /dev/sda, loader CHAIN Added sdA1_Win Boot other: /dev/sda1, on /dev/sda, loader CHAIN Added sdA1_alt_Win Boot image: /mnt/M4/boot/vmlinuz -> vmlinuz-3.12.21-desktop-2.mga4 Mapping RAM disk /mnt/M4/boot/initrd.img -> initrd-3.12.21-desktop-2.mga4.img Added M4 Boot image: /mnt/M4/boot/vmlinuz.old -> vmlinuz-3.12.20-desktop-1.mga4 Mapping RAM disk /mnt/M4/boot/initrd.img.old -> initrd-3.12.20-desktop-1.mga4.img Added M4.old Boot image: /mnt/vinux/vmlinuz -> boot/vmlinuz-3.5.0-52-generic Mapping RAM disk /mnt/Vinux/initrd.img -> boot/initrd.img-3.5.0-52-generic Added Vinux Boot image: /mnt/vinux/vmlinuz.old -> boot/vmlinuz-3.5.0-51-generic Mapping RAM disk /mnt/Vinux/initrd.img.old -> boot/initrd.img-3.5.0-51-generic Added Vinux.old Writing boot sector. /boot/boot.0200 exists - no boot sector backup copy made. Boot sector relocation performed 2 warnings were issued. [root@M4 lilo]# lilo -V LILO version 24.0 (released 07-Juni-2013) [root@M4 lilo]# whereis lilo lilo: /usr/sbin/lilo /usr/share/man/man8/lilo.8.xz [root@M4 lilo]# rpm -qif /usr/sbin/lilo Name : lilo Epoch : 1 Version : 24.0 Release : 1.mga4 Architecture: x86_64 Install Date: Sat 19 Apr 2014 14:50:11 EST Group : System/Boot and Init Size : 558489 License : MIT Signature : RSA/SHA1, Sat 19 Oct 2013 09:53:38 EST, Key ID b742fa8b80420f66 Source RPM : lilo-24.0-1.mga4.src.rpm Build Date : Sat 19 Oct 2013 09:38:10 EST Build Host : sucuk.mageia.org Relocations : (not relocatable) Packager : pterjan <pterjan> Vendor : Mageia.Org URL : http://lilo.alioth.debian.org/ Summary : The boot loader for Linux and other operating systems Description : LILO (LInux LOader) is a basic system program which boots your Linux system. LILO loads the Linux kernel from a floppy or a hard drive, boots the kernel and passes control of the system to the kernel. LILO can also boot other operating systems. [root@M4 lilo]# Reproducible: Steps to Reproduce:
Created attachment 5288 [details] lilo config file
Created attachment 5289 [details] file system table
I think udev precreate the device node, but the actual module loading is deferred to the first time a program tries to open /dev/fd0 which takes some time so the first access fails.
CC: (none) => mageia, thierry.vignaudSource RPM: lilo-24.0-1.mga4 => lilo-24.0-1.mga4, systemd
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD