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

Bug#488678: marked as done (linux-image-2.6.25-2-amd64: Boot fails: no tty)

Your message dated Fri, 4 Jul 2008 10:15:35 +0200
with message-id <20080704081535.GD2407@stro.at>
and subject line Re: Bug#488678: linux-image-2.6.25-2-amd64: Boot fails: no tty
has caused the Debian Bug report #488678,
regarding linux-image-2.6.25-2-amd64: Boot fails: no tty
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.)


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


Boot fails with the following messages:

 Target file system doesn't have /sbin/init
        No init found. Try passing init= bootarg.

        BusyBox v1.10.2 (Debian 1:1.10.2-1) built-in shell (ash)
        Enter 'help' for alist of built-in commands

        /bin/sh: can't access tty; job control off
        (initramfs)


I tried changing /etc/fstab to use UUID but this made no difference. I
also reinstalled the kernel a couple of times; no better.

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.23-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.22     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92b      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-25  Yet Another mkInitRD

linux-image-2.6.25-2-amd64 recommends no packages.

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

--- End Message ---
--- Begin Message --- 
On Tue, 01 Jul 2008, Anthony Campbell wrote:

> Well, I finally found the answer but it's very odd. I don't think it
> should work but it does. I put the "wrong" root entry in
> /boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this
> kernel seems to need /dev/hdb10. Here is the relevant section of the
> file:

newer grup uses UUID to pass the correct boot device to the linux image
that is recommended as device names are not stable.
mv /boot/grub/menu.lst to some backup place and recall
update-grub
 
 
closing as device names are userspace policy and not a kernel bug.
thanks for the feedback

-- 
maks

--- End Message ---
Reply to: