kernel panic error
in [Debian]
|
From: Sunita Barve on 16 Jul 2010 06:10 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 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. Thanks in advance, -- Sunita Barve, Ph. D. SIRC-In-Charge National Centre for Radio Astrophysics Post Bag No. 3, Pune Univ. Campus Pune 411 007, INDIA Phone : Office : 91-20-25719211 Residence : 91-020- 24470022 Mobile: 9922753827 Email : sunitab(a)ncra.tifr.res.in ; sunitabarve(a)gmail.com
From: H.S. on 16 Jul 2010 11:00 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(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/i1prvj$jp7$1(a)dough.gmane.org
From: H.S. on 16 Jul 2010 11:30 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(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/i1ptjm$r3d$1(a)dough.gmane.org
From: Anand Sivaram on 16 Jul 2010 23:40 On Fri, Jul 16, 2010 at 20:54, H.S. <hs.samix(a)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(a)lists.debian.org with a > subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org > Archive: http://lists.debian.org/i1ptjm$r3d$1(a)dough.gmane.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.
From: Andrei Popescu on 17 Jul 2010 03:00
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 |