Slackware failed to boot from GRUB due to new ext3
Hello guys,
A simple one, but I'm posting because I don't see the forest because of the trees... So, I've installed a Slackware 13 on the same disk with a Centos (and Freebsd but this doesn't matter too much). As boot loader I use Centos' grub. My partitions looks like: Code:
fdisk -l I modified the grub to include it: Code:
title Slackware 13.0 But, at restart, the well known GRUB error: File not found. What is wrong here? Should these messages from fdisk (cylinder boundary, disk order) to have some influence? Thanks for replies. |
by the following method you can install any number of OS on a single machine, booted with one grub
install lilo to the root partition of slack. you can do this by running liloconfig as root. Hint: boot to slackware partition using the install cd then go back to centos and add an entry to centos grub-menu.list like Quote:
GRUB> rootnoverify(hd0,6) GRUB> chainloader +1 GRUB> boot regards rkrishna |
Looks broadly similar to mine except for lack of space between "root" and "(" in "root(hd0,6)".
EDIT: What does your Centos boot stanza look like in menu.lst (for comparison)? |
My menu.lst
Code:
# grub.conf generated by anaconda |
Quote:
|
Quote:
one advantage is you can see the `cool lilo screen' of slackware with slackware boot logo. :) i always does this, install the boot managers of various linux to its own root partition and call it from a common grub. so tht individual settings to each will remain untouched and various kernel options will also remain untouched. anyway this worked very well for me anyway there is nothing wrong in installing lilo to ur root partion of slack, so that you can atleast try from the grub prompt. regards rkrishna |
Ok, what I did:
- insert the space at root(hd0,6) as catkin correctly pointed to - changed the /boot/vmlinuz to /boot/vmlinuz-huge-smp-2.6.29.6-smp (this is the default) Rebooted, and another kind of errors: Code:
root (hd0,6) rkrishna - even if your solution seems to be one step +, I think it's the best solution in terms of safety. I'll check it later, but for my knowledge, I want to fix the grub too :) |
I guess I found the problem:
it seems that "e2fsprogs ≥ 1.40.5 creates ext3 filesystems with 256 byte large inodes by default (in contrast to 128 byte used before), to accommodate for further ext4 related changes... Using any of these new features requires updating the bootsector of your system. Bootsectors written by "grub or earlier versions of "grub-gfxboot" are not able to boot or even access partitions using any of these new features! " (more here) Slackware 13 has e2fsprogs 1.41.8. Using dumpe2fs I find out that: Code:
dumpe2fs /dev/sda7 | grep "Inode size" Thanks guys, I think this will solved the problem. |
All times are GMT -5. The time now is 11:23 AM. |