[Bug 46189] Dapper failed to mount disks after upgrade

[Jolinhama]

Public bug reported:

Hi,

I am using Dapper and I have applied every patches once a day using
"Update Manager". Today (05/23/2006 10:00 EST), I applied patches and
rebooted my machine and it failed to boot up.

When I booted my notebook up, Ubuntu image was displayed for a while and
it disappeared and following messages are displayed.

----------------------------------------
mount: Mounting /dev/hda1 on /root failed: No such device
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: NO such file or directory
Target filesystem doesn't have /sbin/init

BusyBox v1.01 (Debian 1:1.01-4ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
#
----------------------------------------

1. My machine information:
Dell Latitude C640 (Notebook)
Hitachi Dk23EB-40 40GB harddisk
ATI Radeon 7500 (32MB)
Intel Mobile Pentium 4 (2GHz)
CD-ROM

2. Ubuntu version
I am not sure what version I am using now.
>From GRUB menu, I could find following information.

----------------------------------------
Ubuntu, kernel 2.6.15-23-386
Ubuntu, kernel 2.6.15-23-386 (recovery mode)
Ubuntu, kernel 2.6.15-22-386
Ubuntu, kernel 2.6.15-22-386 (recovery mode)
Ubuntu, kernel 2.6.15-21-386
Ubuntu, kernel 2.6.15-21-386 (recovery mode)
Ubuntu, kernel 2.6.15-20-386
Ubuntu, kernel 2.6.15-20-386 (recovery mode)
Ubuntu, memtest86+
----------------------------------------

I tried every options above (all version and all of recovery mode) and
it failed.

3. Is my hard disk working fine?
I am not sure it is working or not. I am going to reinstall dapper again.
If I could install dapper successfully, then it would mean hard disk is fine.

** Affects: linux-meta (Ubuntu)
       Severity: Normal
       Priority: (none set)
         Status: Unconfirmed

-- 
Dapper failed to mount disks after upgrade
https://launchpad.net/bugs/46189