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

Bug#542912: marked as done (linux-image-2.6.30-1-amd64: 2.6.30 only boots when I sacrifice a goat - waiting for root dev)



Your message dated Sat, 22 Aug 2009 10:57:00 +0200
with message-id <20090822085700.GA2505@wavehammer.waldi.eu.org>
and subject line Re: Bug#542912: linux-image-2.6.30-1-amd64: 2.6.30 only boots when I sacrifice a goat - waiting for root dev
has caused the Debian Bug report #542912,
regarding linux-image-2.6.30-1-amd64: 2.6.30 only boots when I sacrifice a goat - waiting for root dev
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.)


-- 
542912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542912
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-5                  
Severity: important                

linux-image-2.6.26-2-amd64 boots fine.

In linux-image-2.6.30-1-amd64 somehow the device discovery at boot time is 
messed up:

I have
/dev/sda: 750.2 GB, 750155292160 bytes
/dev/sdb: 1000.2 GB, 1000204886016 bytes
/dev/hda: 400.1 GB, 400088457216 bytes  
+ a sata dvd burner.                    

2.6.30 now finds most of the time, that /dev/hda
should be /dev/sda and /dev/sda -> /dev/sdb.... 
and therefore booting fails with "waiting for root dev"

00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port 
SATA AHCI Controller (rev 02)                                                                                           

04:00.1 IDE interface: JMicron Technology Corp. 20360/20363 Serial ATA 
Controller (rev 02)

AHCI is enabled. If you need any additional info, please tell me.


-- Package-specific info:

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

Kernel: Linux 2.6.26-2-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/dash                            

Versions of packages linux-image-2.6.30-1-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.27     Debian configuration management 
sy
ii  initramfs-tools [linux-initra 0.93.4     tools for generating an initramfs
ii  module-init-tools             3.9-2      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-55    GRand Unified Bootloader (dummy 
pa
ii  grub-legacy [grub]            0.97-55    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:
  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/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/preinst/elilo-initrd-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/old-system-map-link-2.6.30-1-amd64: true
  shared/kernel-image/really-run-bootloader: true
  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/prerm/would-invalidate-boot-loader-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-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:




--- End Message ---
--- Begin Message ---
On Sat, Aug 22, 2009 at 10:18:24AM +0200, Dirk Mast wrote:
> In linux-image-2.6.30-1-amd64 somehow the device discovery at boot time is 
> messed up:
> 2.6.30 now finds most of the time, that /dev/hda
> should be /dev/sda and /dev/sda -> /dev/sdb.... 
> and therefore booting fails with "waiting for root dev"

None of this devicenames are stable. They are assigned in order of
detection. Use /dev/disk/*, LABEL= or UUID= (see fstab(5) for more
information).

Bastian

-- 
There is an order of things in this universe.
		-- Apollo, "Who Mourns for Adonais?" stardate 3468.1


--- End Message ---

Reply to: