> Hi Ralf, > > >>> damn! I think I killed my GRUB and MBR with installing a windows version >>> (I know, i shouldn't do that, but i had to try some thing with windows). >>> Unfortunately even that windows install did not succeed... now, i am up >>> without a bootloader. I think, windows changed the MBR, so only windows >>> has been tried to start. So i inserted a knoppix and did a grub-install. >>> >>> Now, grub is back... and it has got the old entries in it ... fine ... >>> but >>> it won't start. The error is: >>> >>> - Filesystem type is ext2fs, partition type 0x83 >>> - The boot entry (kernel /boot/vmlinuz... root=UID=... >>> - Error 15: File not found >>> >>> Any ideas to fix that? Maybe the grub-install command from Knoppix has >>> been too old? (Knoppix detected my hd as hda instead of sda (when >>> boooting >>> 64studio). I also tried the 64studio installer to get me to the shell. >>> But >>> that doesn't work as the 64studio didn't include the grub installer >>> commands. >>> >>> Any hints Or am I lost? (If yes, i think i should try to get the okay >>> for >>> a investment into a mac... as that might be a linux, just more >>> userfriendly, and therefore much too expensive) >>> >>> >> Grub doesn't care about the hda-sda-module-issue, it just cares about >> the sequence, e.g. one Linux call it hda and sda, but for another Linux >> the same disks are sda and sdb, that's the way you could correct it, but >> it's just important that "root (hdx,y)" is set to the correct number of >> the disk sequence, 0 for the first disk, 1 for the second one etc.. >> Because you're using "root=UUID", it should be the same like it's for >> "root=/dev/disk/by-label/", you only need to take care because of "root >> (hdx,y)". >> > > Okay .... i will check that. > What i don't understand at the moment. Where does grub get the list of > kernels and partitions from? Is it stored in MBR and installed with > update-grub or is it read from /boot/...? So, if i change the menu enries, > i think i have to do a update-grub afterwards? >
It's not stored in the MBR. It might be, that the GRUB installer takes a look at existing file systems. Maybe it just takes a look at directories called /boot to see what kernels there are, in addition there somewhere is a place were the Linux version is stored and it also takes a look to this file. Maybe it takes a look at all /boot/grub/menu.lst files. Maybe it also takes a look at all /etc/fstab files. But it's not written to the MBR and it's not GRUB doing this, but the GRUB installer. >> There still could be some other issues, but I guess you could fix your >> problem by correcting "root (hdx,y)". >> >> You should have copied the MBR by the dd command, but don't panic, even >> if Windows should have partitioned something there are tools to restore >> the old partition table. >> > > no panic yet. When i run knoppix i can mount both partitions (/ and /home) > so i could a least do a backup ... for a fresh install... After doing a backup there still would be no working GRUB ;). But the error you get is harmless, this will be fixed very easy. _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
