[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#412139: marked as done (linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root)

Your message dated Sun, 29 Jun 2008 18:10:55 +0200
with message-id <20080629161055.GU11284@stro.at>
and subject line Re: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root
has caused the Debian Bug report #412139,
regarding linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
412139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412139
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: grave
Justification: renders package unusable

After latest upgrade of 2.6.18-4-686 my machine stops booting when reasing to the message: Waiting for root.

The disk is found but just before finding disk on system I see this error message from udev: udevd[411]: Illegal subsystem (or something like that). Then complains of an error in /etc/udev/rules.d/udev.rules on line 61

I have tried to run update-initramfs -u -t -k 2.6.18-4-686 without any luck.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils                     5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0]         1.5.11     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e      tools for generating an initramfs
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.18-4-686 recommends:
ii  libc6-i686                  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false
  linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false
  linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true
* linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/kimage-is-a-directory:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true

--- End Message ---
--- Begin Message --- 
closing as no real info beside that ordering of the modules changed.
this is quite expected and thus UUID usage is recommended.

best regards

-- 
maks

--- End Message ---
Reply to: