On Wed, 13 Oct 2010 22:46:26 +0200
"Dr.-Ing. Edgar Alwers" <[email protected]> wrote:

I would like to make a little report in between. 

At first, I realized, that the kernel of my host system was supporting ext4 
file systems but not ext2 and ext3. As grub.cfg asks for ext2, I thought, this 
could be the reason for my problems. So I decided to build linux-2.6.34 again 
with support for this file systems, and after that, to build grub2. OK. I did 
"grub-config". But as I am always a little afraid of touching MBR, I did not 
make  "grub-install". This tourned to be a catastrophe. I got a grub pront and 
nothing more. 

Well, with the help of my rescue disk, I tried to repair my error. No way. 
Rescue disks works with grub1, not grub2. chroot does also not help, as needed 
libraries are not accessible.

I then decided to install Fedora 13, in order to have a new basis. Now, I went 
into a new problem. I had an IDE disk and an SATA one. To my surprise, the 
denominations of the devices change as they like: sometimes thy are /dev/sdbx, 
but on the next reboot they may turn to be /dev/sdax and so on.
Like trying to fix a piece of soap. I could not install Fedora. The problem 
seems to be well known, as I now know, after googling a little.  It seems, that 
mixing two kinds of disks in one box, is problematic.

I took the IDE disk out of the PC, and installed Fedora 13. then I added my 
BLFS system to menu.lst, and now, everything is working.

"menu.lst", yes. Fedora 13 still works with grub1 , and it boots ext4 systems. 
As I wrote, I do not know, if it is worth to continue experimenting with grub2 
at this moment. I appreciate comments.

I wrote this in some extension, as I think that my experiences could be a help 
to others, working on the same field.

Regards and many thanks for all the comments and help,

Edgar


-- 
Dr.-Ing. Edgar Alwers <[email protected]>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to