I have booted Debian Live CD, and I am trying to create lilo boot record on my disk The disk partition is mounted as /mnt/root and has the linux kernel and /etc/lilo.conf: boot=/dev/nvme0n1 root=/dev/nvme0n1p1 map=/boot/map lba32 prompt timeout=30 default=linux image=/boot/vmlinuz label=linux read-only append="rootfstype=ext4 net.ifnames=0 loglevel=4 3" the mounted partition has all the system files and the kernel image. I am not using any raid, although the debian live CD for some reason loads all md_raid modules. How can I create boot record on my disk?

This is my third Slackware 14.2 64-bit installation.  I'm installing it now on a laptop with GPT partitions. I will describe as best as possible the path I had to do with this installation. Initially I had to overcome the issue that using dd to create the USB stick for installation was not booting from the pendrive.  I had to use the usbimg2disk.sh script. Once I was able to boot from the USB I had to mount the pendrive manually as the USB was not detected when I was asked for source media. i.e., I did: mkdir /os mount /dev/sda1 /os And then I selected "install from premounted directory" and used /os/cdrom0/slackware64 All the installation went fine, but then I faced another issue, which I couldn't resolve yet. I tried with lilo and elilo options, but the boot is still showing the grub2, which was there from the Ubuntu 14.04 installed previously, with no options but the grub command line instead. I may mention that from BIOS setup I see as UEFI Hard Drive BBS Priorities Boot Option #1 which is [ubuntu], but not sure that should be an issue, as I have overridden the Ubuntu partition already.  However, I'm not sure why the ubuntu tag is there and I don't see any way to change that. The partitions I selected within the installation were: /dev/mmcblk0p3 / ext4 /dev/mmcblk0p4 /home ext4 As I had only GRUB available, I decided to learn some GRUB commands and was able to start the Slackware kernel with the below commands: grub> set root=(hd0,gpt3) grub> linux /boot/vmlinuz root=/dev/mmcblk0p3 grub> initrd /boot/vmlinuz grub> boot I thought it was going to be a successful start, but instead I got the following kernel panic error:

RAMDISK: Couln't find valid RAM disk image starting at 0. 
VFS: Cannot open root device "mmcblk0p3" or unknown-block(0,0): error

Here are two photographs of the screen during the boot:  and .  Neither is perfectly clear; look at either one, or both, or neither, as you prefer. How can I start Slackware 14.2 with GRUB commands?  I may be missing something as I am new to GRUB commands. The best solution I would be looking for is that lilo or elilo show at startup in order to start Slackware automatically.  What can I do for lilo to show as boot loader?

I have had some rather bad experiences with GRUB2. I could say [*(and have said)*](https://unix.stackexchange.com/revisions/146784/1) some nasty things about its design and development process. I especially dislike its means of update: for whatever reason it must semi-automatically update several scripts - one indirectly via another in a chain - for every kernel update - or many other minor *(and seemingly unrelated)* configuration alterations. This is directly contrasted by previous experiences I had with LILO - to which I am seriously considering reverting - as I never had any problems with it, and its configuration was pretty simple. For one thing, as I remember it, I had only to update *(or, rather, it only ever updated)* a single, simply-managed configuration text-file per kernel-update. So how does LILO work on modern hardware with today's kernels? How does GRUB? How do other bootloaders? Do I have to fulfill any preconditions, or is it just about writing the configuration file and running lilo command as I fondly remember it in the old days? Does the kernel package update (Debian/Ubuntu) update LILO as it does with GRUB2?

So, to make a long story short, I was running Debian 9, decided to upgrade to '11'. Left 9 installed on sdc, used the installer to sdb which I had already partitioned as I prefer. But the installer refused to use my existing partitions so I just defaulted back to an install on the drive as one big partition (if that's what you call it when the drive is not partitioned). Got it all running fine. Using GRUB naturally. Then I partitioned sda as I prefer and manually copied all data from sdb to where it would now belong. Ah! but how to boot directly to sda from BIOS? GRUB was installed on sdb. So, since, sadly, LILO seems to no longer be installable, I stole it from sdc (Debian 9) -- just copied it to /sbin on sda -- ran this: "lilo -C rescue" with 'rescue' being: large-memory lba32 compact prompt verbose = 1 install = menu timeout = 40 vga = 0x305 boot = /dev/sda menu-title="RESCUE:sda" image = /boot/vmlinuz-5.10.0-18-amd64 initrd = /boot/initrd.img-5.10.0-18-amd64 root = "LABEL=d5-12-Deb11" label = sda:d5-D11 ---------------------------------------------- (How I love LILO, it just works! You Know and you See what it's doing!) ... and it boots sda with no trouble (here I am!). Now ... it all works, I understand it and want to keep it. But LILO is now history, so it seems, and I'm wondering if anyone can recommend a doc that will give me the best info on how to install GRUB on sda entirely manually if that's possible. Research to this point seems to say that you hafta use the install media. There's a thousand hits, Googling for answers, but I want to make sure I have the recommended doc. Or perhaps I just just leave my faithful LILO in charge? I know! -- folks can't stand things that Just Work, life is not meant to be simple. Like the government, GRUB and SystemD know what we need better than we do. Top

I'm trying to virtualize a Red Hat Linux 6.1 image. I restored a clonezilla backup on a .vmdk and I'm trying to get the image to boot successfully in the latest release of VirtualBox 5. Unsurprisingly, I'm getting a Kernel panic. Bootloader is lilo. Disk is on a SCSI (BusLogic) controller in VBox. 500MB of ram. Chipset PIIX3. Audio,Network,Serial, USB all disabled. I would like to preface this post by saying that I am not the one who designed/partitioned this image and that my knowledge of linux is average at best. Please see the screenshots. Image 1 Image 2 VFS: Mounted root (ext2 filesystem). Loading aic7xxx module scsi : 0 hosts. /lib/aic7xxx.o: init_module: Device or resource busy autodetecting RAID arrays autorun... ... autorun DONE. kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2 VFS: Cannot open root device 08:03 Kernel panic: VFS: Unable to mount root fs on 08:03 fstab: /dev/sda3 / ext2 defaults 1 1 /dev/sda2 /boot ext2 defaults 1 2 /dev/sda4 /abc ext2 defaults 1 2 /dev/sda1 swap swap defaults 0 0 none /proc proc defaults 0 0 none /dev/pts devpts gid=5,mode=620 0 0 lilo.conf: boot=/dev/sda map=/boot/map install=/boot/boot.b prompt tiemout=50 default=linux #Default kernel ( orig ) image=/boot/vmlinuz-2.2-12-20 append="mem=376M" label=linux initrd=/boot/initrd-2.2.12-20.img read-only root=/dev/sda3 When i try to boot with SystemRecovery live cd, it fails at "Checking root filesystem" and says my root partition (/dev/sda3) is mounted. Cannot continue, aborting. If i select Control-D for normal startup, it performs fsck on the other 2 partitions(/dev/sda2 and /dev/sda4) and then it just hangs. I've used a livecd and I've succesfully mounted the partitions and even did a fsck on them to see if that would help. No luck. All clean btw. Not sure if the AIC7xxx SCSI driver is causing problems... obviously the VM doesn't have an Adaptec SCSI controller... Any help would be greatly appreciated.

I have server with Debian 10 installed. I am using custom kernel, with lilo boot loader. This is my /etc/lilo.conf: boot=/dev/sda root=/dev/sda1 map=/boot/map lba32 prompt timeout=50 default=linux image=/boot/vmlinuz-5.10.46 label=Linux read-only append="rootfstype=ext4 net.ifnames=0 loglevel=4 console=tty0 2" Now I want to boot the default Debian distribution kernel. I have installed the debian kernel image: apt-get install linux-image-amd64 and added the entry to /etc/lilo.conf: image=/boot/vmlinuz-4.19.0-17-amd64 label=4.19.0-17-amd64 initrd=/boot/initrd.img-4.19.0-17-amd64 read-only append="rootfstype=ext4 net.ifnames=0 loglevel=4 console=tty0 2" However, when I boot this kernel, I get kernel panic. **How can I boot default debian distribution kernel with lilo?**

I want to use the LILO boot loader so I can use EasyBCD to show a Ubuntu listing on the Windows Boot Manager screen, but I don't know how. Please make this as simple as possible, as I don't know much about Linux or LILO. My computer is only Legacy boot mode, no UEFI

I looked around a lot but could not find any commands to display following HP logs from CLI - iLO Event Log - Integrated Management Log - Active Health Log I was also not able to display / list system health from ilo prompt. whats up with the HP folks???? By the way this is DL380p, and it is ilo v4.0 I intend to list all entries in log: like this: (the way it shows in CSV output from web) 685 01/16/2021 19:59 01/16/2021 19:59 1 Browser login: - (DNS name not found). 684 01/16/2021 19:53 01/16/2021 19:53 1 SSH login: - (DNS name not found). ... following does not work... hpiLO-> show ilo log all status=2 status_tag=COMMAND PROCESSING FAILED error_tag=INVALID OPTION Fri Jan 15 21:38:57 2021 this does not work.... hpiLO-> show /system1/log1 status=0 status_tag=COMMAND COMPLETED Sat Jan 16 19:54:14 2021 /system1/log1 Targets record1 record2 record3 record4 record5 record6 record7 record8 record9 record10 record11 record12 record13 record14 record15 record16 record17 record18 record19 record20 record21 record22 record23 record24 record25 record26 Properties Verbs cd version exit show delete hpiLO-> show /map1/log1 status=0 status_tag=COMMAND COMPLETED Sat Jan 16 19:54:34 2021 /map1/log1 Targets record1 record2 record3 record4 record5 record6 record7 record8 record9 record10 record11 record12 record13 record14 record15 record16 record17 record18 record19 record20 record21 record22 record23 record24 record25 record26 record27 record28 record29 record30 record31 record32 record33 record34 record35 record36 record37 record38 record39 record40 record41 record42 record43 record44 record45 record46 record47 record48 record49 record50 record51 record52 record53 record54 record55 record56 record57 record58 record59 record60 record61 record62 record63 record64 record65 record66 record67 record68 record69 record70 record71 record72 record73 record74 record75 record76 record77 record78 record79 record80 record81 record82 record83 record84 record85 record86 record87 record88 record89 record90 record91 record92 record93 record94 record95 record96 record97 record98 record99 record100 record101 record102 record103 record104 record105 record106 record107 record108 record109 record110 record111 record112 record113 record114 record115 record116 record117 record118 record119 record120 record121 record122 record123 record124 record125 record126 record127 record128 record129 record130 record131 record132 record133 record134 record135 record136 record137 record138 record139 record140 record141 record142 record143 record144 record145 record146 record147 record148 record149 record150 record151 record152 record153 record154 record155 record156 record157 record158 record159 record160 record161 record162 record163 record164 record165 record166 record167 record168 record169 record170 record171 record172 record173 record174 record175 record176 record177 record178 record179 record180 record181 record182 record183 record184 record185 record186 record187 record188 record189 record190 record191 record192 record193 record194 record195 record196 record197 record198 record199 record200 record201 record202 record203 record204 record205 record206 record207 record208 record209 record210 record211 record212 record213 record214 record215 record216 record217 record218 record219 record220 record221 record222 record223 record224 record225 record226 record227 record228 record229 record230 record231 record232 record233 record234 record235 record236 record237 record238 record239 record240 record241 record242 record243 record244 record245 record246 record247 record248 record249 record250 record251 record252 record253 record254 record255 record256 record257 record258 record259 record260 record261 record262 record263 record264 record265 record266 record267 record268 record269 record270 record271 record272 record273 record274 record275 record276 record277 Properties Verbs cd version exit show delete hpiLO->

I've just installed slackware on a new SSD on dual boot with windows.
I installed it using a botable flash drive. Without it Elilo keeps stuck on the loading screen prompting:

Loading kernel vmlinuz ... done

In the folder /boot/efi/EFI/Slackware/ I have only elilo.conf, elilo.efi and vmlinuz. My /boot/efi/EFI/Slackware/elilo.conf:

chooser=simple
timeout=1

image=vmlinuz
     label=vmlinuz
     read-only
     append="root=/dev/sda5 vga=normal ro"

What happened to its initrd.gz and why am I using this image instead of the standard huge kernel when first install it? How can I safely fix it? Had to reinstall it because I enabled the generic kernel and edited elilo.conf and all efi/ content was lost out of nothing. Just like that.
**Why does it need the installation media to boot like this?**
This the first time it happens to me and never had any problems using slackware until now.

I'm trying to install 64-bit Debian stable on a Lenovo Thinkpad. When I get to the installation step that installs the bootloader, I get this message: > An installation step failed. You can try running the failing item again from the menu, or skip it and choose something else. The failing step is: Install the GRUB boot loader on a hard disk Going back to the menu and selecting LILO gives me the same error. The installation log says May 1 13:24:23 main-menu: WARNING **: Configuring 'grub-installer' failed with error code 1 May 1 13:24:23 main-menu: WARNING **: Menu item 'grub-installer' failed. May 1 13:24:28 main-menu: INFO: Menu item 'lilo-installer' selected May 1 13:24:28 main-menu: WARNING **: Unable to set title for fdisk-udeb. May 1 13:24:28 main-menu: WARNING **: Configuring 'lilo-installer' failed with error code 1 May 1 13:24:28 main-menu: WARNING **: Menu item 'lilo-installer' failed. I'm not using LVM or RAID. So far, I've tried 1. Disabling UEFI boot and using legacy boot instead. The error still occurs, with both GRUB and LILO. 2. Following the instructions on [this question](https://unix.stackexchange.com/q/165137/49592) and running parted /dev/nvme01 set 1 bios_grub on from TTY2, but I get an error that says parted not found. On my system /dev/nvme01 is the only hard disk 3. Check for hardware errors. When I first purchased the system I ran all the available hardware tests, both from within the BIOS and from within Windows, and it passed all of them. I'm assuming that means the hardware isn't malfunctioning. 4. Per [this thread](http://crunchbang.org/forums/viewtopic.php?id=31675) that had a similar error, albeit with LVM, I tried redoing the partitioning with a small /boot partition at the beginning, formatted with ext2. Same error. 5. Switching to TTY4 to look at the installation output, I also see the error chroot: can't execute 'grub-probe': No such file or directory Searching for information on that turns up [this thread](http://ubuntuforums.org/showthread.php?t=2001720) and [this bug report](https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344) related to GRUB, but a) those are old, and b) I've run through the installation up to this point over a dozen times now and I get the error every time, so it doesn't seem like a one-off thing. 6. I've used Gparted to check that the hard disk is completely empty. 7. Secure boot is disabled in the BIOS. 8. I've run the installation using the full DVD and the netinstall CD; both are booted from USB, but the problem persists. I was able to successfully create an msdos partition table and three partitions (for /, /home, and swap) on the drive in the previous installation step, so I don't know why GRUB suddenly can't write to the drive. How do I fix this and get Debian installed? As of now, the (brand new!) system is completely unusable because I can't get an OS on it. --- Could part of the problem be that Debian/parted recognizes the disk incorrectly? It says the disk is 512.1 GB, which is true in the sense that the specs say 512 GB and that's what is advertised, and it will let me allocate all 512 GB to various partitions. However, if I load it in Gparted, the actual disk space is closer to 476 GB, but I assumed that's just the usual 1024 vs 1000 stuff. (I also posted a version of this question on the [Debian forums](http://forums.debian.net/viewtopic.php?f=17&t=128212&p=614831#p614831) , so I'll update my question with anything important from that thread and vice versa.)

When my machine boots, lilo menu appears with different boot options. I can either select option, or wait for default option to boot automatically. Now, I would like to have the possibility select a boot option, and change the kernel command line parameters (what is defined in the append line). In syslinux (a different boot loader), when I am presented with the menu, I can move to desired item in the menu and press TAB, and the append line appears on the command line so that I can edit it. How can I to do the same in lilo? Below is my lilo.conf: boot=/dev/sda root=/dev/sda1 map=/boot/map lba32 prompt timeout=50 default=Linux image=/boot/vmlinuz label=Linux read-only append="rootfstype=ext4 net.ifnames=0 loglevel=4 console=tty0 console=ttyS0,115200n8 3"

All, I have a USB stick that used to boot fine. I thought I'd reuse it. Reformatted it, copied some files over, and now it won't boot. I've used "lilo -M /dev/sdc mbr" with no luck. Note that the stick itself isn't busted, I can boot *to* it, but not *from* it but the computer refuses to like it as a boot device. Any idea what I broke, and how to fix it? As a backup it's usable so long as I boot it from a floppy, but I want it to boot directly like it used to. I erased everything off it in case the ext4 FS was somehow at fault (maybe the partition table or something), but no luck. However, if I 'dd' an .iso image to the stick, it boots to that just fine. I can then use lilo to write to the stick and have it boot to anything (ignoring the .iso), and all is well, *but* if I then delete the .iso, it's back to 'Non-system disk'. So it seems the .iso file is somehow involved in/with the MBR. Nothing like this ever happens with HDDs that I'm aware of. My understanding is that the MBR is a world unto itself and if it is 1st stage lilo bootable then it cares nothing about any other file on the disk until the 2nd stage is reached. I use floppies like that all the time (MBR only, no files at all) to control my boot. I can just leave the .iso there of course, and use partitions on the rest of the stick, but that seems very inelegant. Thoughts?

is it possible to use append="something" in /etc/lilo.conf to disable completely secondary disk ? The disk /dev/sdb reports errors, and it takes a long time to boot. I would like the disk to be ignored completely, without having to physically remove it.

I just installed my first linux distro: slackware. The installation went fine. I followed this tutorial for the setup and this other tutorial for formatting the disk. Unfortunately, slackware won't boot after completing the installation. After some googling I found out that it's most likely due to LILO not working. I've installed LILO using the simple installation, selecting standard and then the MBR option (just like in the first YT video). After rebooting I'm getting the syslinux boot: menu again. If I reboot without installation USB I'll get the same as prior to installing slackware. Entering liloconfig in the boot: menu as some people online suggested resulted in something like > liloconfig... no such file or directory found Can any one of you help me out? _P.S.- If it matters, I'm installing on a stripped HP Probook 4710s_

I have two SATA drives, but their names /dev/sda and /dev/sdb are chosen randomly by Linux. How can I correctly set up LILO? How can I put a stable reference to the hard drives in lilo.conf? **ADDED.** Can I use udev's names (like /dev/disk/by-id/*) in lilo.conf? LILO doesn't read lilo.conf at each boot, but only once on setup MBR when I run 'lilo' without arguments. At this stage udev names are available. But how do LILO store information about disks to MBR and boot-files? I use dual-boot with Windows, but NTFS disks have no UUID. I want to use udev's id.

Without rebooting, is it possible to tell if the boot loader currently present was LILO. GRUB 0.97 or GRUB 1.9X? I was thinking about reading MBR, but not sure about it. Just by checking the files on system, i.e /etc/lilo.conf doesn't testify anything Any ideas?

After installation of android, I modified lilo.conf to boot it. I just wrote image=/mnt/android-4.4-r2/kernel root=/dev/sda7 label=android read-only because I saw the only filename that looked like a kernel image was that. But after some chunks of messages output, it said "5 seconds to boot". As I saw an initrd.img, I then added it to lilo.conf: image=/mnt/android-4.4-r2/kernel initrd=/mnt/android-4.4-r2/initrd.img root=/dev/sda7 label=android read-only This time the booting process went on longer, but finally it said: Detecting Android and there it seems to have hanged. Any way to use lilo to boot the android OS? Of course, lilo when run did not output any errors. EDIT: Yes, it is. I got it from android-x86.org.

I am running a web server under Debian and I currently have GRUB installed. Should I consider using LILO instead of GRUB? And what are the advantages of each?

I upgraded from Squeeze to Wheezy without problems. But after upgrading to Jessie the system cannot boot anymore (using LILO). LILO ERROR: Duplicated Volume ID O 24.1 Loading Linux ....(snip) BIOS data check successful Loading, please wait [ 14.948425] end_request: I/O error, dev fd0, sector 0 mdadm: /dev/md3 has been started with 1 drive (out of 2). [ 27.196906] end_request: I/O error, dev fd0, sector 0 ...snip modprobe: module unknown not found in modules.dep fsck from util-linux 2.25.2 mount: mounting /dev/root on /root failed: No such file or directory ...etc. And i get to the (initramfs) prompt When I try to list partitions of one of the RAID disks they don't show up. (initramfs) ls /dev/sda* /dev/sda Examining the disk says (initramfs) mdadm --examine /dev/sda /dev/sda: Magic : Intel Raid ISM Cfg Sig. Although the onboard RAID controller is disabled in BIOS. When I access the disks with KNOPPIX (7.0.5) I can access and sync the partitions (sda1, sdc1) without problems. So I guess: * The RAID disks have been created some time in the past using the onboard RAID controller * Because debian didn't support ICH9 chipset the support for this was disabled in BIOS * Jessie seems to look not only at the superblocks of the partitions but also on the superblocks of disks and fails because they are identical? How should I fix this problem? * Enable ICH9 raid in BIOS resync the disks there? Will the system boot? * Zero-out the superblocks using mdadm on the disks

I have a really old hard drive with DOS and Linux partitions with LILO as the boot loader. I want a clone of this hard drive that works exactly like the original. I made a clone using Knoppix and dd_rescue. When I plug in the newly cloned drive, the LILO boot loader stops at "LI" meaning LILO failed at that point. Is this because I need to actually run the LILO command on the LILO partition on the new hard drive before it will work? If so, how do I do that from a live CD? **Update:** Booted from Knoppix live CD: I don't know what "open /dev/hda: Device not configured" is telling me.