• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Issue moving Mandrake 10 box to different machine

Red Squirrel

No Lifer
I'm trying to move a Mandrake 10 box from one vm server to another (vmware server to ESX). I get a kernel panic right when it boots. I used a rescue CD to ch ange hda to sda where required. It uses lilo and not grub, and I can't seem to find the /boot partition. There is a /boot folder on the main partition but it's not really what i would expect to see on a typical system.

I also found a /etc/lilo.conf file and it says to ru n lilo after editing the file, so is there another step i need to do? I tried to actually type lilo but nothing happened. I tried lilo /dev/sda and it crapped the mbr.

Any help would be appreciated.
 
I can't seem to find the /boot partition. There is a /boot folder on the main partition but it's not really what i would expect to see on a typical system.

Why? There's no problems with /boot being part of the / filesystem as long as you don't need anything special to get to it like LVM, software RAID, etc.

I also found a /etc/lilo.conf file and it says to ru n lilo after editing the file, so is there another step i need to do? I tried to actually type lilo but nothing happened. I tried lilo /dev/sda and it crapped the mbr

You need to run lilo as root after editing /etc/lilo.conf so it can remap the kernels and initrds. It's been a long time since I've seen lilo but I believe it should print out the kernel names when you run it.
 
When I run lilo think it tries to run the one that's on the live CD so it fails. How do I go about doing a chroot? I did it before and it was just "chroot foldername" or "chroot foldername path/to/shell" but it's not working. I just get "/bin/zsh" no such file or directory" if I specify the shell I get a segfault. I'm using System Rescue CD. I tried knopix but it wont boot. Just sits at a black screen.
 
Originally posted by: RedSquirrel
When I run lilo think it tries to run the one that's on the live CD so it fails. How do I go about doing a chroot? I did it before and it was just "chroot foldername" or "chroot foldername path/to/shell" but it's not working. I just get "/bin/zsh" no such file or directory" if I specify the shell I get a segfault. I'm using System Rescue CD. I tried knopix but it wont boot. Just sits at a black screen.

man 8 chroot
 
Says No entry in manual for section 8. From what I recall though just using chroot [foldername] should work. So I really don't know why it's not working. But if I can manage to chroot think I may be able to get some stuff to work.

This is mandrake 10 so it's hard to find given it's age, but I think I may of found an ISO, downloading now. I'll check to see if it has a repair option.
 
Originally posted by: RedSquirrel
Says No entry in manual for section 8. From what I recall though just using chroot [foldername] should work. So I really don't know why it's not working. But if I can manage to chroot think I may be able to get some stuff to work.

This is mandrake 10 so it's hard to find given it's age, but I think I may of found an ISO, downloading now. I'll check to see if it has a repair option.

Maybe your linux puts it in the wrong section. Try man 1 chroot (where it is on Centos 😕 ). Reading through that man page it's pretty useless though.

If you weren't using the Mandrake disk in the first place, I'm not surprised you get segfaults when running it correctly.
 
chroot probably tries to use your current shell by default, which sounds like it's zsh and that's not installed in the other installation. chroot <directory> /bin/bash should work, if it's giving you a segfault then you might have other problems to deal with first.
 
Yeah tried all of that. And chroot does not seem any more complicated based on the doc I did find.

Turns out we don't need that VM moved anymore so I just deleted it.
 
Back
Top