Dapper failed to mount disks after upgrade

[Jolinhama]

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.

[Jolinhama (jolinhama)]

I installed dapper again and applied the latest patches successfully.
Anyhow, my machine is working fine now.

[Jason Westerkon (web250)]

I have the same problem with my desktop.

This thread seems to show others too with the problem:
http://ubuntuforums.org/showthread.php?t=185396

[Jason Westerkon (web250)]

Moved to confirmed...clearly this bug has many people scratching their heads and reinstalling, this needs to be fixed stat

[saffari (saffari)]

I have the same issue, I tried all the ideas potsed to ubuntuforums, didn't help.

So what now? :)

[Ben Collins (ben-collins)]

Please test against latest dapper kernel.

[Jolinhama (jolinhama)]

I have not found any specific steps to reproduce this situation so it's somewhat difficult.
Anyhow, I've tried to install dapper twice yesterday and there has been no problem at all.
It looks OK.

So, Do I need to close this ticket? Can I? What should I do? Please advise me.
Thanks!

[anonym (launch-mailinator)]

I have the same problem. My fstab looks like this:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda5 / ext3 defaults,errors=remount-ro 0 1
/dev/hda7 /home ext3 defaults 0 2
/dev/hda1 /media/win_c vfat defaults,utf8,umask=007,gid=46 0 1
/dev/hda2 /media/win_d vfat defaults,utf8,umask=007,gid=46 0 1
/dev/hda6 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0

I have always had hda5 and hda7. I boot to Windows and back to Dapper, and it says at startup those same errors as above. I boot back to Windows and check with explore2fs are these partitions ok. They are, but now they are named hda3 and hda5. Pretty interesting how their names could change without touching hardware or anything. And now I have to find out how to fix it. :(

[anonym (launch-mailinator)]

And I forgot to say that I have used Dapper for 2 months by now, working fine since now.

[Erik Andrén (erik-andren)]

Could this bug be a duplicate of 65711?

[Sebastian Rode (sebastian-ro-deactivatedaccount)]

I think this issue is fixed, or?
Thank you again for taking the time to report this bug and helping to make Ubuntu better.