Ok - there is no real easy way to do this. If you remember what partition the root file system is, you can try this:Aron Smith wrote:
On Wednesday 05 January 2005 05:28 pm, Aron Smith wrote:The problem looks like the root directory is not on the device specified during installation. Let me guess - when you did the install, this drive was not /dev/hda, and now it is. You are going to have to make a couple of changes to make it work. Unless someone has the answers handy, I will have to do a bit of research in the monring, but basicly what you have to do is change the root devices passed to the kernel from /dev/hd?# to /dev/hda# where # is the partition number, and stays the same - only the drive "letter" changes. You will also want to specify "init=/bin/bash" for this boot, untill you can edit /etc/fstab to reflect the changed drive. You will also have to edit /etc/lilo.conf and change the root drive specified there. Make sure you run lilo after making the change, so that the changes take effect. There is a way to do it by putting the drive back in the other machne, but that probably would be just as hard.
I have an old Compaq Armada here with no CD-ROM by removing the HDD (6Gb)
and u7sing an adapter I was able to install ? Mdk 10.1 on the drive.
After reinstalling the drive I find that I have a problem
Kernel panic : No init found Try passingi nit= optionn to kernel
So what do I do now (oboviously I have reached my level of incompentance
One other way would be to get one of the floppy distributions, boot off of it, and go in and make the changes.
Mikkel
Hit the Esc key when you get the boot screen.
at the "Boot:" prompt, type "linux root=/dev/hda# init=/bin/bash" where # is the root partition number.
If all goes well, you are now at the # prompt. From here, you can edit /etc/fstab and /etc/lilo.conf as described above. I like to use mcedit or joe for this, but the editor is your choice.
Now, if this doesn't work, then we can try other options. There is one thing that may cause problems. And because lilo works, I think this may be the case. If your laptop is old enough that it doesn't use LBA, and the ither system used LBA, or the two systems see the hard drive as different configurations, then the partition table may not reflect how the laptop sees the drive. But I would have expected to see some error messages before it got to the point of trying to mount the root file system.
When you had the drive in the other system, were there other drives, besides the CD-ROM drive in the system? Knowing the install system configuration would help with knowing what MDK thinks it is installed on.
Before you give up on MDK, and go to a floppy based system, you may want to look at doing a network install. I have not done one with MDK yet, but it used to be fairly easy with RedHat. You do need a network card for the laptop though.
Mikkel --
Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
