On Fri, Jul 16, 2010 at 20:54, H.S. <hs.sa...@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-requ...@lists.debian.org with a > subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/i1ptjm$r3...@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.
