Your message dated Sat, 29 Sep 2007 17:17:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Yaird-devel] Bug#337293: Kernel panic on changing partition 
numbers
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.14-1-k7
Version: 2.6.14-2
Severity: important



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.14-1-k7 depends on:
ii  initramfs-tools [linux-initra 0.37       tools for generating an initramfs
ii  module-init-tools             3.2-pre9-3 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.11-10  Yet Another mkInitRD

linux-image-2.6.14-1-k7 recommends no packages.

-- no debconf information

Hello!

i installed the kernel through dselect, when i reboot the whole things
comes to a grinding halt with:
Switching root
/usr/lib/yaird/exec/run_init: opening console: No such file or directory
Kernel panic _ not syncing: Attempted to kill init

i have not the faintest idea on what i could do to change this...
i had allready a very similar error when i wanted to migrate to
2.6.12... this was solved by reinstalling a debian on that machine, but
i wont reinstall the whole thing each time there's a new kernel...


--- End Message ---
--- Begin Message ---
ingo wagener skrev:

> while changing my partitions around on Lenny (2.6.18-5-k7) this old stuff 
> came 
> back to haunt me - apparently it is not totally sorted. 
> 
> My root partition is on sda11 while home is on sda5. sda6 was empty so I 
> deleted and grew sda5 into it, making root now sda10.
> 
> I adjusted grub and the fstab to reflect these changes.
> 
> On reboot I was greeted with :
> 
> /usr/lib/yaird/exec/run_init: opening console: No such file or directory
> Kernel panic _ not syncing: Attempted to kill init
> 
> Any attempts to chroot into sda10 from knoppix to rebuild yaird failed and 
> the 
> only way to get the system back up was to create a new sda6 to reinstate the 
> old partition order.

Thanks for your bugreport!

If you change the root partition, you need to rebuild the ramdisk
*before* rebooting.

This is not really a bug, but rather a limitation in the core design of
yaird: Modules and routines needed to establish a root fs is resolved at
ramdisk *build* time, not (as with the alternative, initramfs-tools) at
*boot* time.

If you need a rescue environment, I recommend using a development
snapshot of debian-installer. Knoppix is derived from Debian but has
drifted some so might do some things different these days.

Possibly what caused problems in your rescue attempt was that you need
to chroot into the environment you need to boot into, you need to be
booting off of a kernel similar (but not necessarily identical) to the
one within the chroot, and you need access to /proc and /sys and other
virtual filesystems within the chroot.


Closing this as a non-bug.

If you insist, then please elaborate on what you consider buggy - or if
you agree but suspect that yaird can somehow be extended to handle these
kinds of situations better, then file a "wishlist" bugreport elaborating
on that.


Kind regards,

 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to