bjoernvold.com

Hey guys I really suck at grub. So after a Mandriva cooker update I have got this lovely black screen with:
Grub loading, please wait......
Error 22

Hmm this is strange: When I put in an USB-pen made with mandriva seed the boot goes just fine (no fixing no nothing). I I remove it = grub error again.
Looks like the disk detection is fubared.
Looks like this when booted from the USB-pen

Got an error here dunno if it is rellevant tho...



/boot/grub/menu.lst

Gimme a tip

Ut ooh. Last time I got that, I had to rebuild the initrd. Sigh. Have forgotten how to do it, sorry. This one's rolf's lol.

Edit: here is the grub manual. In it, is a list of errors. Maybe you can find something from that?

22 : No such partition
This error is returned if a partition is requested in the device part of a device- or full file name which isn't on the selected disk.

Thanks! I'll dive into it. And I think we safely can say the disk detection is fubared. Edit:
It must have been a Kernel update here (I did not pay attention). It is not a good idea to have to many USB-disks connected when doing a kernel update - and that I had.
After having played around with it a bit I managed to get to the start menu. but it now gives me an error after entering the normal Mandriva:
Error 11: Unrecognized device string ( I kind of suspect that this could be because of my manual fiddling with /boot/grub/menu.lst)
A 2.6.33.1 (previous)kernel boot goes just fine. The thing is: I dont think that is a previous Kernel so I might just set that as the normal boot.

How do I copy the lines when editing this stuff? Or better put: How do I make a previous kernel boot in the startup menu my default boot?
Well I fixed it - sort off. I am now booting automatically a kernel alternative in the menu list.

viking60 wrote:It must have been a Kernel update here (I did not pay attention). It is not a good idea to have to many USB-disks connected when doing a kernel update - and that I had.

What I used to do with Cooker was run first:

That would let me know if a kernel update was coming in, and if things will be fubarred or not in general. If they were, I knew not to update in real-time mode. Also, if I saw a kernel update in the list, it gave me one last chance to unplug all my usb drives. As you said, it's not a good idea at all, especially with Cooker, to have usb drives plugged in during a kernel update. As well, if I suspected that an update to the kernel was coming in, I'd run:

That way I made absolute sure the previous kernel would be kept if the new one fubarred.

It also assurred that I kept KDE3 in Cooker LOL.

viking60 wrote:How do I copy the lines when editing this stuff? Or better put: How do I make a previous kernel boot in the startup menu my default boot?
Well I fixed it - sort off. I am now booting automatically a kernel alternative in the menu list.

Looks like you found a way. I edit in vi, calling, as root,


In vi in konsole, I can drag text to copy, middle-click to paste, with some quirk sometimes leaving off a few characters at the beginning, I don't know why. Other editors would work. The default can be set in the boot module of MCC or setting the entry you want, counting from the top entry as 0, in the default statement line at the top of menu.lst, fyi, some, at least, of which it seems you have figured out.

Thanks rolf - I figured out the counting bit After I started installing Gentoo I tell you this is nothing Man talk about frustrations. I am getting there tho...

I tried Gentoo a long time ago. It's ok but I think I'd rather spend my time on other things, not building the whole distribution from source.

Funny. That's the part I like lol. It's what I appreciated about FreeBSD, Arch, and Gentoo all three.

rolf wrote:I tried Gentoo a long time ago. It's ok but I think I'd rather spend my time on other things, not building the whole distribution from source.

You know what - I totally agree with you now (I have learned). No one has time for that sh.. in a production environment. It is a good education tho. But I'll set up the server now and never touch it again. Spending three days on that is not worth it. Hell the gnome compilation alone toke 3 hours.

From time to time, I enjoy going through the steps and seeing if everything is in line so that the machine builds some software. Not long ago, I managed to follow the directions to get a 64-bit build of Seamonkey, which wasn't otherwise forthcoming. It's gratifying when it works, can take a lot of time if it doesn't. I appreciate all the work the Mandriva and community devels put into creating a distro that, for the most part, just works.

Yeah - although cooker is going a bit bananas these days. I Just had a kernel panic - and a box that refused to boot. rebooted and it kind of works - but this thing is far from being ready for a release.
I have managed to make the Gentoo install but the GUI bit just PMO so I gave that up- No problem since I started out to build a server anyway.