| Autor |
Nachricht |
|
|
Titel: Cannot install grub to partition
 Verfasst am: 15.08.2006, 03:45 Uhr
|
|
Anmeldung: 16. Apr 2006
Beiträge: 207
Wohnort: England
|
|
I have suse's grub as my bootloader using chainloader entries to boot my other os's so my kanotix grub is normally installed to it's own partition (hda1).
I have been making some changes to my partitions and I temporarily installed my kanotix grub to the mbr and at that point it was still working fine.
I've finished messing with partitions and now reinstalled suse's grub to mbr but I cannot get my kanotix grub to install back to it's own partition.
I used grub-install /dev/hda1 and it ran without errors but when I tried to boot it from suse's grub I simply got a grub command prompt.
In the middle of all this I did notice that grub-gfxboot was upgraded so I tried removing and reinstalling that then doing grub-install /dev/hda1 again but now it doesn't even get to the grub prompt, it says grub loading... then goes back to the main grub menu again.
Just to confirm, kanotix is on /dev/hda1 and I installed it to partion with grub-install /dev/hda1.
The entry for kanotix in suse's grub is like this -
Code:
title Kanotix
root (hd0,0)
chainloader +1
I can't see any reason why it shouldn't be working. |
_________________
sidux 32 & 64 | PCLinuxOS | PC-BSD
repository of shame - compiz fusion & beryl repo for debian Sid/Lenny/Etch | 32-bit | 64-bit
|
| |
|
|
|
 |
|
|
|
Titel:
Verfasst am: 15.08.2006, 08:34 Uhr
|
|
Anmeldung: 02. Mai 2004
Beiträge: 471
Wohnort: Portland, OR, USA
|
|
I'm a bit mystified as to why you'd want to set grub (in the MBR) to start another instance of grub (on the partition). (Matter of fact, I'm going to go see if that works, out of curiosity.)
<edit> Yep, works fine (as you posted) from a grub prompt. (I've got "grub for Windows" installed.)
Why don't you just set Suse's grub to boot Kanotix? |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 15.08.2006, 09:55 Uhr
|
|
Anmeldung: 16. Apr 2006
Beiträge: 207
Wohnort: England
|
|
I use suse's grub to boot my other os's using chainloader entries because the other distros I'm currently using are all development versions (ubuntu edgy, fedora core devel and kanotix/debian sid and so kernels from one or the other are being updated fairly frequently so it means I would otherwise have to keep changing suse's grub entries every time a kernel is updated.
This way I never have to change menu.lst on any distro.
I have been doing it like this for as long as I can remember with no problems til now. |
_________________
sidux 32 & 64 | PCLinuxOS | PC-BSD
repository of shame - compiz fusion & beryl repo for debian Sid/Lenny/Etch | 32-bit | 64-bit
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 15.08.2006, 13:44 Uhr
|
|
Anmeldung: 10. Dez 2004
Beiträge: 489
Wohnort: Stuttgart / Kulmbach
|
|
perhaps this helps
title kanotix
root (hd0,0)
savedefault
makeactive
chainloader +1
which filesystem are you using on your kanotix? don't know exactly but i think there are some problems with xfs/reiser4 and grub
or try to install lilo to your kanotix / |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 15.08.2006, 17:29 Uhr
|
|
Anmeldung: 02. Mai 2004
Beiträge: 471
Wohnort: Portland, OR, USA
|
|
Perhaps grub itself is borked somehow on your Kanotix installation, in which case you can always run Kanotix off the live CD and follow the instructions in this Wiki entry to restore grub to your hda1 partition.
Regarding changing Kanotix kernels often, unless you like to have more than one kernel on hand, be advised that the Kanotix kernel install script always creates symlinks (/boot/vmlinuz and /boot/initrd.img) to the current kernel. So you don't actually have to edit Suse's menu.lst each time you install a new Kanotix kernel if you reference the symlinks. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 16.08.2006, 03:23 Uhr
|
|
Anmeldung: 16. Apr 2006
Beiträge: 207
Wohnort: England
|
|
@ John
You suggestion for a grub entry produced the same result, I'm using reiserfs, by the way.
@ eco2geek
I don't use kanotix kernels at all, I use debian sid ones because my modem crashes with every kanotix kernel. For some reason the vmlinuz/initrd synlinks aren't being setup correctly with the debian kernels, though it wouldn't be much hassle to just create them myself of course.
Nothing in the wiki link helped I'm afraid.
Doing everything the way I mentioned has always worked perfectly fine for as long as I've been using multiple distros, up until now. |
_________________
sidux 32 & 64 | PCLinuxOS | PC-BSD
repository of shame - compiz fusion & beryl repo for debian Sid/Lenny/Etch | 32-bit | 64-bit
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 16.08.2006, 06:34 Uhr
|
|
Anmeldung: 10. Dez 2004
Beiträge: 489
Wohnort: Stuttgart / Kulmbach
|
|
how do you install grub?
grub-install --root-directory=/ /dev/hda1 when you're in your kanotix installation, otherwise you got to chance --root-directoy to /media/hda1 |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 16.08.2006, 13:12 Uhr
|
|
Anmeldung: 16. Apr 2006
Beiträge: 207
Wohnort: England
|
|
Yes I did try installing that way also but still the same.
However, I'm pleased to say I've sorted the problem out now.
I managed to find the previous version of grub-gfxboot and installed that and kanotix is booting fine again with the chainloader entry so the problem was obviously with the upgraded version of grub-gfxboot as I suspected.
Incidentally, I've also solved the problem of my modem crashing with kanotix kernels so I can now use them and point suse's grub to the kanotix kernel vmlinuz/initrd symlinks as well which would probably take a second or 2 off the boot time. |
_________________
sidux 32 & 64 | PCLinuxOS | PC-BSD
repository of shame - compiz fusion & beryl repo for debian Sid/Lenny/Etch | 32-bit | 64-bit
|
| |
|
|
|
|
|
|
