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

Bug#434710: marked as done (Boot stopped.)



Your message dated Sat, 4 Aug 2007 10:42:09 +0200
with message-id <20070804084209.GG6261@stro.at>
and subject line Boot stopped.
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6

I installed Debian 4.0 on my VMWare Workstation 5.5.4 build-44386.
It worked fine.
(Kernel is "linux-image-2.6.18-4-686 2.6.18.dfsg.1-12etch2".)

Next I tried "testing" by "apt-get upgrade" and "apt-get dist-upgrade".
Kernel package "linux-image-2.6.21-2-686 2.6.21-6" was installed.
But when I reseted Virturl Machine, boot sequence stopped.
Here is a console.
=========
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
=========(stopped)

So I tried to boot on signle-user-mode.
Here is a console.
=========
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
ALERT!  /dev/sda1 does not exist.  Dropping to a shell!
        Check your root= boot argument (cat /proc/cmdline)
Check for missing modules (cat /proc/modules), or device files (ls /dev)


BusyBox v1.1.3 (Debian 1: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) 
=========

Thank you.




--- End Message ---
--- Begin Message ---
see
http://bugzilla.kernel.org/show_bug.cgi?id=8492

closing as known vmware bug,
and has been fixed in version 6 of VMWare Workstation.


-- 
maks

--- End Message ---

Reply to: