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

Bug#535270: marked as done (linux-image-2.6.30-1-amd64: Waiting for root file system)

Your message dated Sat, 13 Feb 2010 12:20:00 +0100
with message-id <20100213112000.GR2821@stro.at>
and subject line Re: Bug#535270: Waiting for root file system [FIXED]
has caused the Debian Bug report #535270,
regarding linux-image-2.6.30-1-amd64: Waiting for root file system
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.)


-- 
535270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535270
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-1
Severity: normal


Hi.

The consequence of this problem seems similar to the report #532861.
My current kernel (2.6.26-1) behaves fine, while following an upgrade,
the newly installed is stuck just after printing "Waiting for root [...]".

The root file system was installed (using the Debian netinst from about
two years ago) on reiserfs on LVM on RAID1.

[To add to the annoyance, the upgrade process updated some X library,
and, although X starts up, no other graphical program does, so my
machine is now mainly unusable even with this working kernel.]

-- Package-specific info:

-- System Information:
Debian Release: squeeze/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.30-1-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93       tools for generating an initramfs
ii  module-init-tools             3.7-pre5-1 tools for managing Linux kernel mo

linux-image-2.6.30-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.30-1-amd64 suggests:
ii  grub                       0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30           <none>        (no description available)

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

--- End Message ---
--- Begin Message --- 
On Wed, 01 Jul 2009, Gilles Sadowski wrote:

> Hi.
> 
> After a "dist-upgrade" with aptitude, the problem magically disappeared.
> [I could neither do a "safe-upgrade" nor an "upgrade" because of one conflict
> which those 2 actions wouldn't resolve...]
> 
> Best,
> Gilles

thanks for the feedbac, thus closing.

--- End Message ---
Reply to: