Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries



Links

Issociate
Impressum

#1: No init found

Posted on 2004-10-29 08:58:19 by heisspf

Hi,

Slackware 10.

I am trying to change my hard drive. I duly copied all partitions and
files to the new drive with 'tar -C "$1" -cOl . | tar -C "$2" -xpf - '. Now
when I boot I get:

.....
Freeing unused kernel memory: 120 K freed.
Warning unable to open an initial console.
Kernel panic: no init found. Try passing init= option to kernel.

When I boot using the rescue disk after

.....
Freeing unused kernel memory: 120 K freed.

it continues with
INIT: version 2.84 booting ...

to fully boot and I can use the installation flawlessly.

init is at /sbin/init.

Where is the hang-up ?

Thanks & regards

--
Peter



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Report this message

Mr Ad

Google

#2: Re: No init found

Posted on 2004-10-29 11:30:14 by Jim Nelson

Peter H. wrote:
> Hi,
>
> Slackware 10.
>
> I am trying to change my hard drive. I duly copied all partitions and
> files to the new drive with 'tar -C "$1" -cOl . | tar -C "$2" -xpf - '. Now
> when I boot I get:
>
> ....
> Freeing unused kernel memory: 120 K freed.
> Warning unable to open an initial console.
> Kernel panic: no init found. Try passing init= option to kernel.
>
> When I boot using the rescue disk after
>
> ....
> Freeing unused kernel memory: 120 K freed.
>
> it continues with
> INIT: version 2.84 booting ...
>
> to fully boot and I can use the installation flawlessly.
>
> init is at /sbin/init.
>
> Where is the hang-up ?
>
> Thanks & regards
>

Is the new hard drive in the same location as the old one? i.e. on IDE drives,
both the old and new hard drives were master drives on the primary interface, and
for SCSI drives, does the new hard drive have the same SCSI ID on the same adapter
card in the same PCI slot as the old one?

If not, you will have to modify lilo.conf to reflect the location of the new hard
drive. "man lilo.conf" and "info lilo.conf" have a great deal of information about
how to set the root partition configuration in lilo. Make sure you run the "lilo"
command as root before rebooting, since just modifying lilo.conf will not change
the configuration in the boot sector.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Report this message

#3: Re: No init found

Posted on 2004-10-29 13:39:49 by chuck gelm net

Peter H. wrote:

>Hi,
>
>Slackware 10.
>
>I am trying to change my hard drive. I duly copied all partitions and
>files to the new drive with 'tar -C "$1" -cOl . | tar -C "$2" -xpf - '. Now
>when I boot I get:
>
>....
>Freeing unused kernel memory: 120 K freed.
>Warning unable to open an initial console.
>Kernel panic: no init found. Try passing init= option to kernel.
>
>When I boot using the rescue disk after
>
>....
>Freeing unused kernel memory: 120 K freed.
>
>it continues with
>INIT: version 2.84 booting ...
>
>to fully boot and I can use the installation flawlessly.
>
>init is at /sbin/init.
>
>Where is the hang-up ?
>
>Thanks & regards
>
Looks like Jim is on the correct item; lilo.conf.

Here is an except from a web page containing a hint at your error message:
from: http://linux.omnipotent.net/article.php?article_id=12464
<snip>


Kernel will not Boot

You have created a new Custom Linux Kernel, made an entry in
/etc/lilo.conf and then rebooted the computer system. But, your new
Kernel won't boot, and instead you get:

|Warning: unable to open an initial console Kernel panic: no init found.
Try passing init= option to kernel |

The most likely problem is that you didn't set the "root=" parameter in
/etc/lilo.conf properly. For example, on my system, I have
root=/dev/hdc5, which is sets the root partition: "/". The Kernel looks
for the init command is located in /sbin/init and the /sbin directory
resides on /. Thus, when the / is not set correctly, the Kernel cannot
initiate the init process, and as a result we get a "Kernel panic".
<end snip>

HTH, Chuck


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Report this message

#4: Re: No init found

Posted on 2004-10-30 05:43:53 by heisspf

Thanks Jim and Chuck.

james4765@verizon.net said:
> If not, you will have to modify lilo.conf to reflect the location of the new
> hard drive.


Shame on me, I should have known but it just didn't click. It eventually
dawned me last night too late to hold the mail.

Regards

Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Report this message