Slackware :: Grub/ Grub2/ Lilo - Can't Install Any Of Them Properly?
Nov 15, 2010
I usually install grub straight away after an install but this time it hasn�t worked for some reason after installing 13.1 on a new lappy. I have tried grub, grub2 (from sbo) and lilo; nothing I install into MBR will boot my slackware installation, I have to use the boot USB stick every time.
grub-legacy would be my preferred one so i�ll ask for help specifically with that. This is what im doing so far -
I copied the extras/source/grub folder to my home folder.
I did: ./grub.SlackBuild as su.
The install went on for a long time and I saw warnings etc flash by.
I don't know if it has installed properly. I tried it before and it destroyed my grub menu. I managed to recover grub through LMDE and now, I am back for more!
Is there any way to tell if this app is installed properly before I run grubconfig?
I have a SATA boot disk with LILO installed. This disk is kinda like a recovery disk in that its supposed to boot up on any x86 PC. I'm however having trouble getting it to boot on a HP Probook laptop. I get the LILO 99 99 99 ... problem upon bootup.
I've already specified the linear option in my lilo.conf, which according to the LILO error codes might fix the problem but didn't.
Quote:
0x99: Invalid Second Stage
Mismatch between drive and BIOS geometry, or a bad map file. Some evidence that LINEAR needs to be set on the disk (see LiloNotes)
I've tried specifying the lba32 option instead, but get the same problem.
I've tried the solutions at this LILO Error Codes wiki, i.e. lilo -g and lilo -M /dev/sda
Neither solution worked.
Does anyone know how to get this working? Or recommend another BIOS independent boot loader? I was using nuni in the past for my IDE version, but nuni doesn't support SATA drives.
fyi I'm booting up the disk and running LILO on another laptop that boots it up, before plugging it into the Probook to test.
I just installed Slackware 13.37, and it's my first version of Slack.
After installing, Grub was still installed on my system, but since it is supposed to boot an OS that's no longer on the hard drive by default, it drops to the Grub Rescue prompt every time I boot.
How can I boot Slackware from grub, or get lilo to boot my system instead of grub?
I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
since ms dos wasn't meant to be booted from cd (it was used from floppy) and i have tried buring the contents of every ms dos floppy to a cd and no dice i am guessing that it needs a bootloader so i can boot up the setup wizard
before anyone suggests that this thread has nothing to do with linux i will just point out that this thread is asking about grub and that is a linux catagorie
I have been given a new old computer, Asus K8N-E with a 2GHz AMD Athlon 64.OpenBSD and Debian works like a charm. But with Slackware 13.1, LILO won't be installed properly. There are two disks: a 10GB ATA-drive with the system and a 250GB SATA-drive as a data repository.
Apparently the computer insists that the SATA is the first disk. Subsequently the bootable partition is not on the first disk and disables LILO to be installed. This is when I try to install LILO to a partition. When it is installed to MBR, it says something about overlapping and can't boot.
When I installed Slackware, I did not install LILO. Instead, in my LMDE, I ran: grub-install --recheck /dev/sda, then I ran: update-grub, then: reboot. This worked ok, although I have 4 grub enteries for Slackware - who knows why, but there are 4.I decided to install grub from the Slackware DVD. I copied the extras/source/grub folder to home and as su, ran pkgtool and selected grub from /tmp.From the root directory, as su, I did: rub-install --recheck /dev/sda but when I tried: update-grub (or grub-update), I got: command not found. I rebooted... (probably should not have done that)Grub menu sort of appeared with not boot options.I rebooted into Slackware from the Slackware DVD and now I am writing this from my Slackware installation.
I have one install (Slack 12.2) on /dev/sda11, and GRUB (GNU GRUB 0.97) boots it without a problem. I just installed a new Slack 13.1 on /dev/sda1, and GRUB fails to boot it as follows:Quote:
grub> root(hd0,0) > Filesystem id type ext2fs, partition type 0x83 grub> kernel /boot/vmlinuz root=/dev/sda1
Trying to do an install with encrypted lvm. I have made it to the end of the install and chroot /mnt and then ran mkintrd which added the modules successfully but then when I ran lilo again I got an error saying that said "fatal: can not open: /etc/lilo.conf".
I have a Dell Inspiron 1721. Recently I replaced Windows Vista Home Edition (32 bit) with Slackware Linux 13.
Lilo wouldn't work, when I turned on the computer it printed "Li" and then 20 lines of 090909... and then the computer would hang up. So I just used my Slackware-boot-flashdrive-thing that I created during installation to boot my computer and told myself that I would fix it later.
Also, when I installed, cfdisk (or it might have been sfdisk) complained that /dev/sda did not contain a valid MS-DOS partition table. fdisk still worked, so I used it to create a new table, and cfdisk worked fine and the installation went along normally.
I reinstalled Slackware about two days later (I realized that I had installed the 32 bit version instead of the 64 bit). Lilo still didn't work.
I thought it might be something wrong with the Slackware DVD, so I downloaded and attempted to install about 4 different distributions. None of the CDs would work. The computer would start up, Linux would start to load, and the computer would freeze.
Xubuntu was the only distro I had that I could get to install. Halfway through the installation, (Surprise!) I got an error, something like "Package Grub failed to install, you will not be able to boot your new operating system".
The rest of the install went fine, so I restarted my computer and tried to use another one of my CDs to boot Xubuntu. I got the error "/dev/sda does not contain a valid partition table", and later "ext4-fs: checksum failed on dev sda at sector...", and "please specify a valid partition for root=". I am absolutely positive that I entered the correct partition, I triple checked and entered other partition names to make sure.
I'd also like to add that the computer makes horrible crunching noises when it starts up and when I do stuff like press keys. So is something seriously wrong with my hardware, or is there another explanation for all of this? Because I really don't want to have to try to repair the computer and can't pay to have it repaired.
I have just install both fedora 12 and slackware 13 on my laptop I did not install lilo because fedora uses grub I am able to use slackware by using the the DVD and booting from the command prompt I have attached my grub .conf file also when i boot from cd the command is as follows
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd 0801 47428608 sda1 <-- this is my Windows partition 0802 30719552 sda2 <-- this is my Linux partition 0b00 1048575 sr0 driver:sr 0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp #mount /dev/device /slacktemp #chroot /slacktemp #cd /slacktemp/etc <-- for me it told me that doesn't exist #vi lilo.conf <-- couldn't do nothing and was frozen #lilo -v -t -b /dev/device #lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?) I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
Working on a quad boot system. Two Karmic installs (I find I tend to hork one every once in a while by playing too much, so having a backup around is nice), windows 7, and Snow Leopard. I got everything up and running, except I had Leopard installed instead of snow leopard. At that time, I had the following:
Grub2 detected everything just fine, made a real nice grub.cfg file and away I went.Now, I've made a change. Snow Leopard required GUID partitions and I had my stuff all set up as MBR and was /not/ about to reformat and start over. So I added a second drive, sdb.
Now, I can boot to that drive independently. Fine.I can boot to sda just fine and go to either Ubuntu install or windows just fine. Great. Grub2 finds Mac OSX on /dev/sdb2. Awesome (sdb1 is a fat32 bootloader for hackintosh reasons). It not only doesn't update grub.cfg, it leaves the old /dev/sda2 listing for my old Leopard install ... whose partition I deleted. It isn't visible anymore.
Code:
> sudo update-grub Generating grub.cfg ... Found Debian background: radar.png
[code]....
But nothing after Ubuntu 9.10 on /dev/sda6 shows up in grub.cfg? I'm at a loss. Any ideas how to get it to populate? I'd rather not hack grub.cfg and have to rebuild it by hand every once in a while especially as grub was fine with finding it.
my dualboot grub is not working properly. I have it set to start opensuse/W7, but when I start windows, I get an error message that the bootmgr is not working, and that I should press ctrl/alt/del/ to reboot.
i have grub1 working and chaonloading truecrypt loader if i choose "win7" in grub1 menu I want to install a new kubuntu (no upgrade) I have read that that there are problems with grub2 and truecrypt actually a bug that grub2 dont chainloads truecrypt boot loader many ppl seem to have problems with grub2 then i read somewhere that ubuntu install is not asking for grub2 to be installed and just installing it. is this right?
i think at least for the alternative install cd its wrong. i installed it on another pc and it asked me! it works for win7 and Ubuntu and i guess its grub2 but there is no truecrypt installed anyway, i wanted to ask is the live cd installer asks me for grub2 and what is the best and easiest way to stay with my grub and just change the menu.lst to the new kernel (i guess there will be one)
I work in a very restrictive environment and I want to use linux on my work laptop (currently running Windows XP prof). I am planning to install linux in a dual boot mode but I dont want to install grub/lilo or any other boot loader. i cannot even modify Windows bootloader to boot into linux partition.
Is there a way I can boot into linux partition without installing new boot loader or modifying the current windows boot loader? Any boot CD etc available that can boot into linux partition from my laptops HDD?
I'm looking for an alternative boot loader (for hard drive) to get away from GRUB and LILO. I want something that is not bloated like GRUB and does not require rebuilding a table of block numbers like LILO. Something simple and basic ... like a boot loader should be.
i installed slackware 13.1, previously i had slackware 13, i made the following partitions:
[Code]...
everything went fine until i rebooted slackware after installation. lilo didnt boot at all, just a black screen. i booted with the DVD, and checked the lilo config file. the contents on lilo looks fine, just like any other lilo on google. for example i have this: boot = /dev/sda
i installed lilo on the MBR., i then changed this to boot = /dev/sda1 , on root and nothing same thing lilo always complains at the end: Partition entry not found , but how come , /etc/fstab shows all partitions are mounted ,( i am doing this in KDE environment). i reinstalled again , same thing. I also get a warning: video doesnt not support VESA mode, i changed to vga = normal again it complains that video doesnt support vesa even when i set it to normal, (note that i am running lilo after i made those changes, even rebooting , and same thing happens.
when i installed lilo, it let me choose video modes for the boot screen because lilo showed that my video card supports vesa mode, but then it doesnt boot at all. did slackware 13.1 changed so much that my laptop is no longer supported?? everything was fine with slackware 13 or is it because slackware needs a separate /boot partition, if so how come i just installed slackware 13 with just / and swap?
I finally got everything installed and then slackware setup prompted me to reboot. then i did and it just took me back to windowsxpx64. so then i tried booting off my usb, and it worked, however when i login as root, i just get the bash commandline and not interface or programs or anything. i cannot login as any other user and the setup did not prompt me to make another user account. so how would i activate lilo or make it so i can boot with it to slackware? i rather use grub but for now i would just like to get slackware working right.
I have 2 drives, the first has Slackware 13.0 and FreeBSD 7.2. The second has Windows 7. Lilo configured to boot all three, no issues. Perfect. The first drive has 100GB of free space after FreeBSD and today I decided to install Open Solaris on that free space. The install failed, as in Solaris displayed such a message. I did read the Solaris install docs, etc. And it did mention no to install unless it preceded any Linux Swap partitions. There are, I did, but that's not my issue now.
After rebooting, it amazingly loaded FreeBSD by default. No Slackware. So I booted the slackware DVD, ran fdisk and made Slackware the default boot partition, yada yada. Now when it rebooted it gave a little message down in the left hand corner of the screen like "RRG B" highlighted in a red box. Now pressing enter will cause Windows 7 to boot from the second disk. I mounted the slackware partition from the DVD and am there now. Will just running lilo again put everything back to normal? Apparently Solaris left behind a piece of that ill behaved GRUB! (No flames!!!) :-) How do I make it go away?
I look after some small office where computers run ubuntu. Sometimes they phone me for help. For that reason, I decided to install ubuntu alongside with my slack.I seem to have problems with lilo configuration. Ubuntu is installed on software raid :
/boot = md0 (raid 1 of sda1+sdb1) / = md1 (raid 0 of sda2+sdb2)
I finally installed Slackware and now I have Windows, Slackware and Ubuntu in my laptop. I installed Ubuntu at the last order and at that time GRUB the default loader. But I feel that I'd like to use lilo more, so I booted into Slackware and run "lilo" and then lilo became the default loader.But then I cannot access Ubuntu anymore. Because in lilo there're no information about Ubuntu. So I added some information about Ubuntu according to that of Windows in lilo. But that failed. I still cannot access Ubuntu. I searched for the posts about this problem, and this is what they say:
