On 16/07/10 05:59 AM, Sunita Barve wrote:
> I have been using debian 5.0.3. I had changed disk and had connected on two
> different machines. Now I am getting the following error
I am in a similar situation.
> kinit: trying to resume from /dev/sda5
> kinit:No resume image, doing normal boot...
> Target filesystem doesnt have /sbin/init.
> run-init: /bin/sh: No such file or directory
>
> [ 5.449855] Kernel Panic - not syncing : Attempted to kill init!
>
> can anyone help me to sort out this error.
And I am getting similar errors. Can you post what are the grub lines
for the kernel you are trying to boot in? Also, what are the disc
partitions like in this machine (which is "/", "/boot")?
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: i1prvj$jp7$1@dough.gmane.org">http://lists.debian.org/i1prvj$jp7$1@dough.gmane.org
07-16-2010, 03:24 PM
"H.S."
kernel panic error
On 10-07-16 10:56 AM, H.S. wrote:
On 16/07/10 05:59 AM, Sunita Barve wrote:
I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error
I am in a similar situation.
kinit: trying to resume from /dev/sda5
kinit:No resume image, doing normal boot...
Target filesystem doesnt have /sbin/init.
run-init: /bin/sh: No such file or directory
[ 5.449855] Kernel Panic - not syncing : Attempted to kill init!
can anyone help me to sort out this error.
And I am getting similar errors. Can you post what are the grub lines
for the kernel you are trying to boot in? Also, what are the disc
partitions like in this machine (which is "/", "/boot")?
The solution in my case was to fix the grub's boot stanza for the
relevant kernel. The drives' names may change in different computers. My
solution was to put the UUIDs of the partitions for "/" and "/boot" (I
have these on different partitions), instead of their patition names
like /dev/sda2, in the boot stanza. If you want, I can post the stanza
from the /boot the machine as an example.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
On Fri, Jul 16, 2010 at 20:54, H.S. <hs.samix@gmail.com> wrote:
On 10-07-16 10:56 AM, H.S. wrote:
On 16/07/10 05:59 AM, Sunita Barve wrote:
I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error
I am in a similar situation.
kinit: trying to resume from /dev/sda5
kinit:No resume image, doing normal boot...
Target filesystem doesnt have /sbin/init.
run-init: /bin/sh: No such file *or directory
[ 5.449855] Kernel Panic - not syncing : Attempted to kill init!
can anyone help me to sort out this error.
And I am getting similar errors. Can you post what are the grub lines
for the kernel you are trying to boot in? Also, what are the disc
partitions like in this machine (which is "/", "/boot")?
The solution in my case was to fix the grub's boot stanza for the relevant kernel. The drives' names may change in different computers. My solution was to put the UUIDs of the partitions for "/" and "/boot" (I have these on different partitions), instead of their patition names like /dev/sda2, in the boot stanza. If you want, I can post the stanza from the /boot the machine as an example.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
It is necessary to use initrd image while using UUID.* So UUID method may not work with custom kernels where drivers are compiled in.* To find the uuids of of a non working system, first boot with a live/boot cd and issue either "blkid" or "ls -l /dev/disk/by-uuid"
Update grub accordingly.
07-17-2010, 06:53 AM
Andrei Popescu
kernel panic error
On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> >
> It is necessary to use initrd image while using UUID. So UUID method may
> not work with custom kernels where drivers are compiled in.
Could you please elaborate on that? How can UUID fail if you have
modules compiled in the kernel, since UUID is a property of the
filesystem?
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
07-17-2010, 05:40 PM
Anand Sivaram
kernel panic error
On Sat, Jul 17, 2010 at 12:23, Andrei Popescu <andreimpopescu@gmail.com> wrote:
On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> >
> It is necessary to use initrd image while using UUID. *So UUID method may
> not work with custom kernels where drivers are compiled in.
Could you please elaborate on that? How can UUID fail if you have
modules compiled in the kernel, since UUID is a property of the
filesystem?
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
Even if every driver is compiled into the kernel, an initrd may be required to
use root=UUID=....format.
That is what my experience too, finally I swithed to root=/dev/sda2
There are many suggestions that root=/dev/disk/by-uuid/....
could be used instead without an initrd.
See the link,
https://bbs.archlinux.org/viewtopic.php?id=61451
07-18-2010, 08:09 AM
Andrei Popescu
kernel panic error
On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> >
> > Could you please elaborate on that? How can UUID fail if you have
> > modules compiled in the kernel, since UUID is a property of the
> > filesystem?
>
> Even if every driver is compiled into the kernel, an initrd may be required
> to
> use root=UUID=....format.
> That is what my experience too, finally I swithed to root=/dev/sda2
> There are many suggestions that root=/dev/disk/by-uuid/....
> could be used instead without an initrd.
>
> See the link,
> https://bbs.archlinux.org/viewtopic.php?id=61451
The link only talks about /dev/disk/by-uuid/... which is correct. Those
are actually symlinks created by udev and I'm guessing they are not
present if you don't have an initrd. But passing root=UUID=... should
not require an initrd, because it doesn't rely on /dev being present.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
07-19-2010, 09:36 AM
Anand Sivaram
kernel panic error
On Sun, Jul 18, 2010 at 13:39, Andrei Popescu <andreimpopescu@gmail.com> wrote:
On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> >
> > Could you please elaborate on that? How can UUID fail if you have
> > modules compiled in the kernel, since UUID is a property of the
> > filesystem?
>
> Even if every driver is compiled into the kernel, an initrd may be required
> to
> use root=UUID=....format.
> That is what my experience too, finally I swithed to root=/dev/sda2
> There are many suggestions that root=/dev/disk/by-uuid/....
I am using a custom 2.6.34 kernel with every driver built in. *Currently it is booted with root=/dev/sda2 option.
Just to see how it works, I changed that to
1) *linux /boot/vmlinuz-2.6.34 root=UUID=ddc23ac8-37bf-4e89-a1cd-d77aefc011c8 ro *quietand2)*linux /boot/vmlinuz-2.6.34 root=/dev/disk/by-uuid/ddc23ac8-37bf-4e89-a1cd-d77aefc011c8
In both cases the system did not boot up. *The error was unable to mount root device.So finally, to use uuid option in either way, it is required to use initrd.
kernel panic error
