sidux.com :: View topic - Grub questions

sidux.com

Installation - Grub questions

tuxracer - Jul 06, 2008 - 01:59 AM
Post subject: Grub questions

I have some questions for a potential sidux install. I am a newbie and would like to prepare in case of boot problems/issues. I also am inexperienced using grub and boot loaders. I have only recently used partitioning programs (Gparted). I've read that the best way is a dedicated partition for Grub but I'm still confused on how to achieve this. I don't have a floppy drive so I'd have to pursue a different method.

If I just control the boot loader by editing grub (my /boot/grub/menu.lst?) and repairing grub via the main grub methods, I am still somewhat confused how unless I use a LiveCD that has a 'grub restore/repair' utility (e.g. Mepis LiveCD, Knoppix LiveCD – used to have one? Ubuntu's?).

I am wondering if someone can steer me to a direction that will allow me to prepare my system for a sidux install and how I prepare using grub.

I have read this so far:

http://manual.sidux.com/en/sys-admin-gr ... #dual-boot

This is what is on my machine now:
Windows XP
Mepis 7
Debian Testing – Lenny

Ultimately/Eventually, I plan to have:

Windows XP
Mepis 7
Debian Testing – Lenny
sidux
Kubuntu – Hardy Heron 8.04
Fedora 9

I am planning on my next OS being sidux.

I appreciate any instructions, advice, recommendations and any links to help me figure this out.

I have collected several links including 'the grub page.'

http://users.bigpond.net.au/hermanzone/p15.htm

infinitycircuit - Jul 06, 2008 - 05:39 AM
Post subject: RE: Grub questions

I'm not sure I really understand your question. The easiest way to manage grub is to not let new installations overwrite the MBR. You can manage all your GRUB entries on a single partition and manually edit the /boot/grub/menu.lst to fit the new installs. On debian-based systems. make sure to put manually editted entries at the bottom so they aren't changed by update-grub.

tuxracer - Jul 06, 2008 - 11:52 AM
Post subject:

Okay, then my question is how to do all that?

This is a clueless newbie here especially when it comes to grub. I can get to the /boot/grub/menu.lst from an editor but that's as much as I know. I can create the partitions but then I'm not sure how to create the dedicated grub partition and then where do I install when using a distro's install CD/DVD?

I'm used to installing to the MBR.

None of my distros have 'misbehaved' so far but I'm sure one will sooner or later.

Edit: I guess I have the choice to install grub there from whichever distro CD/DVD I use? It will detect ext2 or ext3 partitions?

I need to copy stage1, stage2, menu.lst and stage1_5 files to the partition?

What do you mean by this, 'bottom' of what?:

Quote:

On debian-based systems. make sure to put manually editted entries at the bottom so they aren't changed by update-grub.

You mean when partitioning and the install sequence or do you mean in menu.lst? Sorry... Question

sleekmason - Jul 06, 2008 - 02:25 PM
Post subject:

When installing off of the live cd you have the option to install to the 'mbr' or to the partition you installed your system to. What I do that works very well is 'chainloading' the distro I am installing.

To start: When you get to the option to install to either mbr or partition, make sure you install grub to the partition of your new install, not the mbr. This means it will not affect your grub menu on start up at all, and you will have to manually edit your 'menu.lst' in grub. Here's how.

After you have installed your system and reboot for the first time you will notice that your new installation does not show up in the grub boot up screen. That is fine. The grub for your new system is installed as PART of that system and what we are going to do is point to that. Anyway, once you are on your desktop (i'm assuming kde but it is the same for xfce) goto menu/system and look for the entry that will open your file manager as 'super user' Click on it. Enter your root password then inside your file manager goto file system/boot/grub/menu.lst.

Down at the very bottom you will see a line that says:

### END DEBIAN AUTOMAGIC KERNELS LIST
right after that make an entry that looks like this:

title sidux
root (hd0,4)
chainloader +1

Where root is the partition where you have grub installed for your new system. In using this remember that the numbers listed for root (hd0,4) are one less than the partition. In other words, my second sidux is located at hda5, but for this application it will be hd0,4 If I had installed to hda9 it would be:

title sidux
root (hd0,8)
chainloader +1

If your drive is hdb instead of hda it would be:
title sidux
root (hd1,8)
chainloader +1 . . .where the number 0 or 1 is hda or hdb

That it. Now when you reboot you will see a new entry for sidux in the grub menu, and when you click on it it will bring you to another grubmenu . . . for your new system. Works like a charm.

I've tried to keep this as simple as possible. check out this post for more info on grub in the forum: http://www.sidux.com/PNphpBB2-viewtopic-t-10702.html
And this for the manual: http://manual.sidux.com/en/sys-admin-gr ... -grub-boot Also just look through installation in the forum and you will find loads more. Hope this helps!

tuxracer - Jul 06, 2008 - 07:29 PM
Post subject: grub; dedicated grub partition?

This isn't exactly what you're saying but how does this idea compare to yours?:
If I have a dedicated grub partition, could I do this?:

-Use a grub command that lets me install it wherever I want: grub-install /dev/hda1 (to install to hda1 root for example)
That is step #1

Step #2: Copy the files: stage1, stage2, menu.lst and stage1_5 since I will be using file systems other than ext3 such as NTFS (Windows XP).

I can copy stage1 and stage2 from /boot/grub from any Linux LiveCD or installed/booted Linux OS?

Now I'd need stage1_5 files. I use the same source (so whatever distro I chose to use) and copy the stage1_5 files to the grub partition.

I'm not sure how to do this, though.

Step #3: create the menu.lst. I'm hazy on this part, too, unfortunately. In this example, create /mnt/test/boot/grub/menu.lst.

Get the boot info (the menu.lst from each particular distro) from the other distros and copy/write them into the new menu.lst of the grub partition.

Step #4: Once, I've made the menu.lst on the grub partition, with boot info from every distro on the drive, I need to make so the menu file is utilized when the drive boots up. I need to tell the hard drive's MBR to look at the grub partition when the drive boots up. If my grub partition is at /dev/hda1, I run these commands:

# grub
grub> root (hda0,0)
grub> setup (hd0)
grub> quit
# reboot

Step#5: To add new distros, I edit the grub partition's menu.lst. And add the boot info from the latest distro addition. I boot into the latest distro and sign in as root.

1. Mount /dev/hda1 /mnt/test
2. cd /mnt/test/boot/grub
3.cp -p menu.lst menu.lst.bup (bup???)

Edit menu.lst

In menu.lst, delete all 'global info' (what is 'global info?') and save/quit

Run Grub (# grub → grub> ) and do this:
1.grub > root (hd0, 0)
2.setup (hd0)

Reboot computer – menu.lst should include all boots (old and new)

What do you think? Is there anything there to modify or is anything not accurate or?

I'm getting my info/knowledge from the 'dedicated grub partition' page.

sleekmason - Jul 06, 2008 - 10:15 PM
Post subject: RE: grub; dedicated grub partition?

you are way over complicating things. If I understand correctly you have mepis installed already and have the mepis bootloader installed to the mbr. That is fine. When you install sidux you will be presented with an option to install the bootloader into the mbr or the root partition. You must use the root partition in order to leave your current (mepis) boot menu screen alone. From there you do what I listed above to your menu.lst IN MEPIS. Mepis currently owns the mbr so we access it through mepis's menu.lst. Does that help?

slh - Jul 06, 2008 - 10:37 PM
Post subject: RE: grub; dedicated grub partition?

Quote:

You must use the root partition in order to leave your current (mepis) boot menu screen alone.

While this is valid in theorie, you can't avoid updating the MBR if it doesn't support ext3 with 256 byte inodes yet (this bugfix has been added in 2008-01 Νυξ, Fedora 9, OpenSuSE 11.0, Ubuntu 8.04 Hardy Heron and cannot be expected in distros released before march 2008).

tuxracer - Jul 06, 2008 - 11:08 PM
Post subject: Re: RE: grub; dedicated grub partition?

sleekmason wrote:

Well, it does help but MEPIS *used to* be the main grub/boot loader. When I installed Debian - Lenny, the new Debian install now has the bootloader.

I suppose your post still applies, right? After installing sidux, I install grub to the root partition so it leaves the Debian boot menu alone? Then I edit /boot/grub/menu.lst with what you listed above? When I installed Lenny, I installed it to the MBR so it took over the mbr from Mepis. Right? I just want to make sure I understand things correctly.

Quote:

So, can I install Kubuntu 8.04 and Fedora 9 to root and do the same (as you described above)? That would be really convenient. I am not sure though as I heard/read that you have to do some extra editing/tweaking when you install Fedora.

Thanks for your help, sleekmason!

tuxracer - Jul 06, 2008 - 11:14 PM
Post subject: RE: Re: RE: grub; dedicated grub partition?

Here's my current menu.lst (I took out most of the comments #):

title Debian GNU/Linux, kernel 2.6.24-1-686
root (hd0,7)
kernel /boot/vmlinuz-2.6.24-1-686 root=/dev/sda8 ro quiet
initrd /boot/initrd.img-2.6.24-1-686

title Debian GNU/Linux, kernel 2.6.24-1-686 (single-user mode)
root (hd0,7)
kernel /boot/vmlinuz-2.6.24-1-686 root=/dev/sda8 ro single
initrd /boot/initrd.img-2.6.24-1-686

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title MEPIS at sda7, newest kernel (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 nomce quiet splash vga=791 resume=/dev/sda6
savedefault
boot

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title MEPIS at sda7, kernel 2.6.22-1-mepis-smp (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.22-1-mepis-smp root=/dev/sda7 nomce quiet splash vga=791 resume=/dev/sda6
savedefault
boot

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title MEMTEST (on /dev/sda7)
root (hd0,6)
kernel /boot/memtest86+.bin
savedefault
boot

sleekmason - Jul 07, 2008 - 01:57 AM
Post subject: RE: Re: RE: grub; dedicated grub partition?

Yes, basically the menu.lst in lenny would be what you want to change. It looks like you are already using a chainloader for windows so you can use that as an example as well (for the numbers to use i.e. hd0,2.) Good luck:)!

dptxp - Jul 11, 2008 - 07:12 PM
Post subject: RE: Re: RE: grub; dedicated grub partition?

chainloading is perhaps the simplest option.

check this thread-

http://sidux.com/PNphpBB2-viewtopic-t-1 ... art-0.html

tuxracer - Jul 14, 2008 - 01:37 PM
Post subject:

sleekmason wrote:

That it. Now when you reboot you will see a new entry for sidux in the grub menu, and when you click on it it will bring you to another grubmenu . . . for your new system. Works like a charm.

Hey, I understand way more what's happening here.

One question, though. When it boots again to show the sidux grub, is that all that the sidux grub menu will show?

There will be an extra step or showing of grub twice. But, it does sound simple to just chain load each additional operating system.

The alternative is one long list in menu.lst of the grub you install in the MBR, right?
The list will be long anyway but it will be even longer if you include entries for older kernels etc. Whereas, the chainloading method has grub entries for those somewhere else in grub of the other OS?

Chainloading is just having one grub hand over the boot to another grub or bootloader, I gather.

Hmmmm....

tuxracer - Jul 14, 2008 - 02:02 PM
Post subject:

Hey, sorry to post again but I think I have a good question. I am wondering how you would 'fix' this situation: if the distro you use as your main grub (i.e. it has the chainloader entries) is borked or you want to reinstall, how do you handle that?

I suppose a LiveCD can fix a 'broken' grub or if that particular OS is not booting properly. But, if you wanted to reinstall for some reason, that would wipe out the previous grub entries (i.e. the chainloader entries) so you would either have to redo or have a backup of the grub.conf (menu.lst) file? If you have a backup, you just copy it to the new file whenever you complete the new install? Or would they be effected at all?

dsmithhfx - Jul 14, 2008 - 02:47 PM
Post subject:

You'll find everything you need to know about how to create a basic grub floppy (that will get you to a grub command line), and how to use that to boot your system here:

http://www.troubleshooters.com/linux/grub/grub.htm

Otherwise, google on "grub" for all sorts of useful info.

I keep an up-to-date, full grub floppy (will all my bootable partitions tested working from it) on hand, along with an image of the floppy stored on other pcs, for just such an eventuality...

sleekmason - Jul 14, 2008 - 04:03 PM
Post subject:

Yes, I think you understand now.

The best thing to do is just make a copy of your menu.lst for future installs.

Hard to say which is best about either loading all into 1 menu.lst or using the chainloader, but with all the changes and probs with grub it just seems to be the easiest solution to me to use the chainloader. I have done both and even used lilo before(another boot loader) with satisfaction.

As far as how to reinstall grub you may look here: http://manual.sidux.com/en/sys-admin-gr ... -grub-boot and search the forums for more specific problems. I believe I asked the same thing about 1 year ago, and I think I've seen it several times since.

muchan - Jul 14, 2008 - 09:12 PM
Post subject:

The simplest solution is, say, just decide sidux be the main system, and install grub to MBR.

Then if you are kind of person who can't stand without trying other distro/os, just do it in vbox,
that is, always boot in sidux and do regular d-u. For me, multibootin is a trend of the past. Smile

When you try other distro for days/weeks with multibooting, you don't do regular d-u of sidux,
and your way back to sidux will be more difficult later. (of course, it's just my opinion.)

dsmithhfx - Jul 15, 2008 - 09:55 AM
Post subject:

Can't play nice with other distros is generally not considered a plus...

tuxracer - Jul 15, 2008 - 01:54 PM
Post subject:

sleekmason wrote:

The best thing to do is just make a copy of your menu.lst for future installs.

Hard to say which is best about either loading all into 1 menu.lst or using the chainloader, but with all the changes and probs with grub it just seems to be the easiest solution to me to use the chainloader. I have done both and even used lilo before(another boot loader) with satisfaction.

As far as how to reinstall grub you may look here: http://manual.sidux.com/en/sys-admin-gr ... -grub-boot and search the forums for more specific problems. I believe I asked the same thing about 1 year ago, and I think I've seen it several times since.

I agree with you! I think I will use the chainloader method when I do a new system. My new HD has just come in the mail and it's a larger 320GB WD 3200AAKS drive which will be faster than my previous generation drive. I also have more room to install multiple OS's. I think I will use the multi-boot method instead of a virtual box for now.

How do I make a copy of my menu.lst for when my grub is messed up and I want to 'fix' it? I mean, I was looking for all the steps. I've read the manual but I find most manuals are all over the place including steps I won't use or need (I don't need the floppy instructions or lilo etc. etc.).

I'll try to google this and read the related sidux content in the manual in the meantime.

I am considering to have a brand new install of both Linux and Windows on the new drive (I made a slipstreamed XP SP2 CD w/ SATA drivers and am curious to see if it will work aka if I did it correctly).

But, for now, I would like to experiment on my current (see: old) drive as it is mostly OS stuff and not much data on it to backup (could be done quickly). Therefore, I thought I'd try re-installing XP and then try to reinstall grub. Right now, Debian Lenny is pointing to the grub.conf file (is that how to explain it?) so my menu.lst is there. I would like to back it up and then repair it. Debian doesn't have a liveCD.

When I build with my new HDD, I'll probably install grub to the MBR using the sidux LiveCD.

EDIT: I thought of another idea: I have some space left on the old drive. I could re-install XP which will wipe out grub (right?). I have a sidux liveCD already so I could install (after XP) to the leftover disk space and install to the MBR. That should fix everything?

However, I am curious how I would solve the issue by repairing Debian's grub menu.lst (method without a liveCD), though. Okay, 'just thought I'd offer that idea up.

Thanks for more info/assistance and followups to my posts!

michaa - Jul 15, 2008 - 02:22 PM
Post subject:

tuxracer wrote:

How do I make a copy of my menu.lst for when my grub is messed up and I want to 'fix' it? I mean, I was looking for all the steps. I've read the manual but I find most manuals are all over the place including steps I won't use or need (I don't need the floppy instructions or lilo etc. etc.).

Quote:

# cp -a /boot/grub/menu.lst /path/to/backup/menu.lst

I think you'll have something like an archiv or a backup partition, if not copy it to ~/safe/menu.lst or the like. The folder you copy the menu.lst to shouldn't be on the "/" partition/disk Wink

dsmithhfx - Jul 15, 2008 - 02:27 PM
Post subject:

Quote:

How do I make a copy of my menu.lst for when my grub is messed up and I want to 'fix' it?

The trick is to make a copy before it's messed up...

In terminal:

Code:

su

cp /boot/grub/menu.lst /boot/grub/menu.lst_backup

To restore the backup, do it in reverse, eg:

Code:

su

cp /boot/grub/menu.lst_backup /boot/grub/menu.lst

Of course, it won't do much good if your pc is unbootable in the first place. For that contingency/eventuality, better copy the backup to another media such as a floppy disk. Then you can boot from a livecd and restore it from there.

My comment about maintaining a full grub floppy still stands. Understand, though, that you can't just copy the menu.lst from a hdd grub installation, since full grub from a floppy will map the drives differently.

tuxracer - Jul 15, 2008 - 02:59 PM
Post subject:

dsmithhfx wrote:

The trick is to make a copy before it's messed up...

In terminal:

Code:

su

cp /boot/grub/menu.lst /boot/grub/menu.lst_backup

To restore the backup, do it in reverse, eg:

Code:

su

cp /boot/grub/menu.lst_backup /boot/grub/menu.lst

Thanks so much! That is the info I'm looking for. That code looks familiar. I'm sure I've read that before.

Could I use a USB flash drive instead of a floppy? That would be more convenient than going out and buying a floppy and then hooking that up.

[quote="michaa"]

Quote:

Code:

cp -a /boot/grub/menu.lst /path/to/backup/menu.lst

I think you'll have something like an archiv or a backup partition, if not copy it to ~/safe/menu.lst or the like. The folder you copy the menu.lst to shouldn't be on the "/" partition/disk Wink

Yes, true! Wink

I'm trying to learn of my options.

muchan - Jul 15, 2008 - 09:01 PM
Post subject:

dsmithhfx wrote:

Can't play nice with other distros is generally not considered a plus...

but sidux is the most compatible to tomorrows distros. not with yesterdays... Wink

muchan

tuxracer - Jul 15, 2008 - 10:17 PM
Post subject:

dsmithhfx wrote:

In terminal:

Code:

su

cp /boot/grub/menu.lst /boot/grub/menu.lst_backup

To restore the backup, do it in reverse, eg:

Code:

su

cp /boot/grub/menu.lst_backup /boot/grub/menu.lst

I think I can use a usb flash drive for this?

I have read that they are often used to store a Linux OS but I just want to have a menu.lst file and any other related yet required files (if any).

That way, I could be using a liveCD to go into any distro's /boot/grub and use the menu.lst file on the usb flash drive to copy it over.... right?

The problem is I don't know linux enough to know how to do this and I was having problems with mounting/copying. I now have a 'menu.lst_backup' in my /boot/grub directory. Oops. I did manage to use the GUI way of copying (sorry, Windows) the file but I want to know how to do it the 'unix' terminal console or CL (command line?) method.

However, I am not sure whether I need to format the USB flash drive and to which format if I need to do this. I guess this topic should be in hardware now? I just thought it is a continuation of preparing an install and a 'safe fix' in case grub is ever "damaged.' I like to think I understand some part of what is going on but perhaps, someone can let me know whether this is a good strategy or not.

Btw, the usb flash drive is 8GB so I have much space to do this if it is a good option.

dsmithhfx - Jul 16, 2008 - 01:14 AM
Post subject:

muchan wrote:

but sidux is the most compatible to tomorrows distros. not with yesterdays... Wink

And... which do you suppose is more likely to be installed?

muchan - Jul 16, 2008 - 11:14 AM
Post subject:

Quote:

The problem is I don't know linux enough to know how to do this and I was having problems with mounting/copying. I now have a 'menu.lst_backup' in my /boot/grub directory. Oops. I did manage to use the GUI way of copying (sorry, Windows) the file but I want to know how to do it the 'unix' terminal console or CL (command line?) method.

unix/linux command for copying file is cp.
cp source_file distination_name
or see the detailed usage with
man cp
or even better, read through the documentation of GNU coreutils by
info coreutils
or search a website for command line... like sidux manuals gives you a link to
http://linuxcommand.org/

muchan - Jul 16, 2008 - 11:16 AM
Post subject:

Quote:

> but sidux is the most compatible to tomorrows distros. not with yesterdays... Wink
And... which do you suppose is more likely to be installed?

whatever... the current incompatibilty is simply a fact that sidux has newer version of Grub,
so tomorrow's distro/os that comes with newer Grub will be compatible with today's sidux.

slam - Jul 16, 2008 - 01:56 PM
Post subject:

sidux is intended to be installed as your primary operating system, and therefore defaults to installing it's newest Grub to MBR. If done so, it will automaticly add entries for booting all other operating systems found. This usually works fine, and is the supported way of doing it. We recommend to tell all other operating systems to install their boot loaders into their respective partitions, and you should easily be able to chainload into them (even if they upgrade the boot loader, the kernel, ....). As sidux upgrades it's kernels quite often for very good reasons, this is the most practical solution.

For all those who insist in controlling the MBR not with sidux, but with another operating system - well, we do not chain you and offer the options to do so, but you are on your own, and definitely not supported here (as we do not want to support other operating systems, obviously). You will have to live with the bugs outdated Grub versions contain, or - even worse - with incompatibilities/inabilities other boot loaders come with.

Your freedom of choice - and ours! Smile

Greetings,
Chris

tuxracer - Jul 17, 2008 - 04:42 AM
Post subject:

muchan, thanks for those instructions and advice. I will check those.

Quote:

Hmmmm... I think I just want to experiment and choose a method! lol... I plan on having data on another drive anyway. I might experiment with VirtualBox, too, and sidux might make a good host for that?

Anyway, in response to your post and comments, I would like some additional info. Are you saying that a siduxinstall of grub to MBR will automatically boot up future distros if you install the respective grubs for those to their partition, that sidux will edit the menu.lst with the chain load for those?

BelaLugosi - Jul 17, 2008 - 06:56 AM
Post subject:

Quote:

Are you saying that a siduxinstall of grub to MBR will automatically boot up future distros if you install the respective grubs for those to their partition, that sidux will edit the menu.lst with the chain load for those?

That would be very nice, but afaik not possible.
Every OS that is installed after sidux gains a manually chainload-entry in the sidux menu.lst

Grub only recognizes already present OS on installation.

slam - Jul 17, 2008 - 07:15 AM
Post subject:

The problem can be solved by creating a chainload entry for every partition where you plan to install other Linux distributions in your menu.list:

Code:

### END DEBIAN AUTOMAGIC KERNELS LIST

title testinstall (sda5)

chainloader (hd0,4)+1

title testinstall (sda6)

chainloader (hd0,5)+1

title testinstall (sda7)

chainloader (hd0,6)+1

title testinstall (sda8)

chainloader (hd0,7)+1

title testinstall (sda9)

chainloader (hd0,8)+1

That way you can boot all of them, even if they are installed later on. You may adapt the titles to better fit your needs.

Greetings,
Chris

piper - Jul 19, 2008 - 01:43 AM
Post subject:

** Some ** of my grub entries takin from that distro's grub, but, chainloading is easier, faster, Never have I had a problem with grub or adding distro's to it

Code:

### END DEBIAN AUTOMAGIC KERNELS LIST

title      Sidux64

root      (hd0,5)

kernel      /boot/vmlinuz-2.6.25-9.slh.1-sidux-amd64 root=UUID=2e168ca8-f88a-4490-8f89-0e9862f11ab6 ro quiet vga=791 

initrd      /boot/initrd.img-2.6.25-9.slh.1-sidux-amd64

### ISO boot

title sidux Live

kernel (hd2,9)/sidux/vmlinuz-2.6.25-7.slh.2-sidux-686  boot=fll quiet noeject vga=791 fromiso=/sidux/sidux.iso

initrd (hd2,9)/sidux/initrd.img-2.6.25-7.slh.2-sidux-686

title   Dreamlinux

root   (hd2,1)

kernel   /boot/vmlinuz-2.6.23.12-dream root=/dev/sdb2 ro quiet vga=791 splash resume=/dev/sda5

initrd   /boot/initrd.img-2.6.23.12-dream

title Mandriva

kernel (hd2,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=fe529c9c-eaaf-40fa-bab3-87191978d47b  resume=/dev/sda5 splash=silent vga=788

initrd (hd2,7)/boot/initrd.img

title=Sabayon

root (hd2,8)

kernel /boot/kernel-genkernel-x86-2.6.24-sabayon root=/dev/ram0 ramdisk=8192 real_root=/dev/sdb9  quiet  init=/linuxrc splash=silent,theme:sabayon vga=791 CONSOLE=/dev/tty1 dolvm 

initrd /boot/initramfs-genkernel-x86-2.6.24-sabayon

title Kanotix 

root (hd0,7)

kernel /boot/vmlinuz-2.6.22-10-kanotix root=UUID=cd8fe181-e4ef-4a63-83bb-a2cbc701c031 ro noapic noapm vga=791 quiet

initrd /boot/initrd.img-2.6.22-10-kanotix

title      Lenny-fvwm-crystal (no kde/gnome)

root      (hd2,2)

kernel      /boot/vmlinuz-2.6.21-2-486 root=/dev/sdb3 ro 

initrd      /boot/initrd.img-2.6.21-2-486

savedefault

title Bugnux

kernel (hd0,8)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda9  acpi=on resume=/dev/sda5 splash=silent vga=788

initrd (hd0,8)/boot/initrd.img

What I boot with at the moment besides the above

Code:

Kanotix

Kanotix CPX-Mini

Alien

Buffalo

Underground

Wolvix

Utopian

Elive16/17

Berry

Zenwalk

tuxracer - Jul 22, 2008 - 10:09 PM
Post subject:

Okay, I'm chainloading now but when I installed sidux, I had options which made me confused.

For e.g., when I am at the page for installing grub to either MBR or the root-partition, I have as choices:

mbr
partition
sda or sdb (I assume this means I have a choice of one of the drives)

Which should I choose for installing to the root partition?

I specified previously (in the page before which I could call the 'Partitioning' page) of /dev/sda10 (which is where sidux would install). So, if I select install to 'partition' in the next page (described scenario above), does that mean it will install grub to the root partition (if I choose 'partition')?

Btw, if I had selected sda (therefore, the 1st drive), for e.g., what would have happened? Would it 'remember' the selection of the previous page, sda10 and installed Grub there or would something else occur? Perhaps, 'partition' and 'sda' is the same thing (in this case), installing grub to the root partition since I chose to install (sidux OS) in sda10 (which is the 1st drive)?

Second question: concerning menu.lst
I noticed that there are only two entries. Doesn't sidux scan for other operating systems or did I select an option to 'disregard' other Linux OS's? It detected Windows XP so it's included.

It doesn't matter since I am using a dedicated/separate partition for Grub so I just had to install sidux's grub to the root partition.

Thanks for any answers and recommendations (for that matter).

lucky9 - Jul 22, 2008 - 11:45 PM
Post subject:

Partition means root partition in the installer.

Other operating systems usually have to be chainloaded. Or other special steps need to be taken.

aus9 - Aug 05, 2008 - 12:50 PM
Post subject:

I consider myself very experienced at grub so forgive me for telling you how to suck eggs.

1) your post 5 has this line in it.....For a live cd
# grub
grub> root (hda0,0)
grub> setup (hd0)
grub> quit
# reboot

Pretending you did not know that will fail for linux....try...if you have only one drive

Code:

su

grub

root (hd0,0)

setup (hd0)

quit

Grub counts from zero so change those numbers based on where your /boot folder or partition that contain /boot is.

Of course if grub is in mbr and you get some grub error message....grub can be used to trouble shoot you way out of the mess.

Most people put /boot as first partition or as a sub-folder to / and / as first partition.
But the above grub command will report ....succeeded....if it finds the balance of the booting files on your damaged system....and if not you know you have not got all the files or you used the wrong numbers.

I have written a tutorial elsewhere on the net....but there are plenty of tutorials on grub.

2) Forgive if I explain too much but...each drive has an mbr and not all are bootable. Your bios normally has a boot order to follow and when it finds a bootable drive....it jumps to that mbr....but the mbr is tiny so has only a very small code....that says....hey I am a bootloader...whether its ms or linux etc....and then tells the sytem to jump to the balance of the booting files.

In ms land those files are on C:/ or c root eg ntldr* boot.ini
In linux those files are always in /boot

In linux...some distro have a symbolic link to /etc/grub.conf....which is their choice but if you have grub....stuff should all be in /boot/grub

3) When installing....and you asked to install grub in mbr or root partition.....

it is best to install to mbr.....unless that partiton is a raid partition or a lvm partition.
and root is a confusing word....in context it means where is the /boot partition and is different context from the kernel line ....root=/dev/blah blah or root=label=blah blah or root=UUID=blah blah

I have moved from a rpm distro and I am currently in love with sidux so I hope you enjoy the ride as well

good luck

aus9 - Aug 05, 2008 - 01:26 PM
Post subject:

ohh forgot to add to prev post

if your format as ext2 or ext3....sidux uses a modified grub so to use a live cd....you need to use sidux.

I just did a test and I have a ext3 format for / and its all good.

Simpatico - Aug 07, 2008 - 08:05 PM
Post subject:

I've been happily running sidux for some time and I decided to also install Debian stable on the same machine, in case it was ever needed.

Stable included sidux in its grub, but the following error is given at boot when sidux is chosen:

Code:

kernel .. vga=791

Error 2: Bad file or directory type

Also, when using the sidux live CD,

Code:

grub-install /dev/sda

gives an error message. "No such block," I believe it said.

Is there a way I can modify Etch's grub and boot with it?

aus9 - Aug 07, 2008 - 11:49 PM
Post subject:

titan in another thread said

Code:

/usr/sbin/grub-install --recheck --no-floppy /dev/sda

was good....but of course you may have to verfiy sda is the correct target drive.

And that other thread is talking about the change in inode size. So you would use sidux as a live cd or live dvd to issue that command. With su or sudo su.

w

cheerio

Simpatico - Aug 08, 2008 - 02:55 AM
Post subject:

It was using sda. Thank you, aus. Very Happy