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

Bug#502896: marked as done (11: system fail to boot)

Your message dated Tue, 21 Oct 2008 11:09:08 +0200
with message-id <20081021090908.GC10015@baikonur.stro.at>
and subject line Re: Bug#502896: 11: system fail to boot
has caused the Debian Bug report #502896,
regarding 11: system fail to boot
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.)


-- 
502896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502896
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: 11
Version: linux-image
Severity: critical
Justification: breaks the whole system

It is reported a lot of times before. But as it still occure i guess
it still need to be reported.

The cure at the moment is to press the reset button and try reboot until it
boots correctly.

The system is installed with debian-40r4a-i386-netinst.iso. It is right out
of the box. Nothing fiddled with. And the system is using Reiserfs. It is a
dual cpu machine if it matters.

I am about to compile a custom kernel to see if it will solve anything.

It starts booting as usual, when the boot process comes to...

Begin: Mounting root file system...
Begin: Runnung /scripts/local-top...
Done.

/init: /init: 1: Cannot open /dev/root: No such device or address
Begin: Running /scripts/local-premount...
resume: libcrypt version 1.2.3
resume: Could not stat the resume device file. Please type in the file name
to try again or press ENTER to boot the system

<snip, inline comment>
*** And then if ENTER is pressed ***
*** messages like this apear     ***
<snip>

Done.
Usage modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] -o
  <modulename>] [--dump-moduleversions] [ <modname> [parameters...] 
modprobe -r [-n] [-i] [-v] [ <modulename> ...]
modprobe -l -t <dirname> [-a <modulename> ...]
mount: Cannot read /etc/fstab: No such file or directory
Begin: Running /scripts/local-bottom...
Done.
Done.
Begin: Running /scripts/init-bottom...
mount: Mounting /root/dev on /dev, static/dev failed: No such file or
derectory
Done.
mount: Mounting /proc on /root/proc failed: No such file or derectory.
Target system doesn't have /sbin/init
BusyBix v1.1.3 (Debian 1.1.3-4) Built-in shell (ash). Enter 'help' for a
list of built-in commands.
/bin/sh: Can't access tty; job control turned off (initramfs)

(initramfs)

This is where the boot ends. Time to hit the reset button.



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message --- 
On Mon, Oct 20, 2008 at 08:12:13PM +0200, Bo Forslund wrote:
> Package: 11
> Version: linux-image
> Severity: critical
> Justification: breaks the whole system
> 
> It is reported a lot of times before. But as it still occure i guess
> it still need to be reported.
> 
> The cure at the moment is to press the reset button and try reboot until it
> boots correctly.
> 
> The system is installed with debian-40r4a-i386-netinst.iso. It is right out
> of the box. Nothing fiddled with. And the system is using Reiserfs. It is a
> dual cpu machine if it matters.
> 
> I am about to compile a custom kernel to see if it will solve anything.
> 
> It starts booting as usual, when the boot process comes to...
> 
> Begin: Mounting root file system...
> Begin: Runnung /scripts/local-top...
> Done.
> 
> /init: /init: 1: Cannot open /dev/root: No such device or address
> Begin: Running /scripts/local-premount...
> resume: libcrypt version 1.2.3
> resume: Could not stat the resume device file. Please type in the file name
> to try again or press ENTER to boot the system
> 
> <snip, inline comment>
> *** And then if ENTER is pressed ***
> *** messages like this apear     ***
> <snip>
> 
> Done.
> Usage modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] -o
>   <modulename>] [--dump-moduleversions] [ <modname> [parameters...] 
> modprobe -r [-n] [-i] [-v] [ <modulename> ...]
> modprobe -l -t <dirname> [-a <modulename> ...]
> mount: Cannot read /etc/fstab: No such file or directory
> Begin: Running /scripts/local-bottom...
> Done.
> Done.
> Begin: Running /scripts/init-bottom...
> mount: Mounting /root/dev on /dev, static/dev failed: No such file or
> derectory
> Done.
> mount: Mounting /proc on /root/proc failed: No such file or derectory.
> Target system doesn't have /sbin/init
> BusyBix v1.1.3 (Debian 1.1.3-4) Built-in shell (ash). Enter 'help' for a
> list of built-in commands.
> /bin/sh: Can't access tty; job control turned off (initramfs)
> 
> (initramfs)
> 
> This is where the boot ends. Time to hit the reset button.
> 
use UUID

there is *no* gurantee on stable device names.

--- End Message ---
Reply to: