mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory

[Stein Olav Aske]

I want to start out by saying that I'm a noob, so please bear with me

I've been having problems booting "post" Hoary Hedgehog releases, that is both
with Breezy and now Dapper after fresh installs. The boot process starts just
fine, and continues until a few steps after detecting my usb ports. The console
prints something about io errors, the screen clears, and prints the following:

...
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
mount: Mounting /dev on /root/dev failed: No such file or directory
Target filesystem doesn't have /sbin/init

/bin/sh: can't access tty; Job control turned off
#
...

The problem is nonexistent if I boot Breezy or Dapper using the kernel provided
with Horay, so I'm guessing it's related to some change/ patch made in the
kernel after Horay.

[Stein Olav Aske (stein-aske)]

My problem is simular to the one described in #18934.
The only difference is that I'm trying to install Ubuntu
on a internal harddrive.

[Ben Collins (ben-collins)]

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

[Stein Olav Aske (stein-aske)]

I'm sorry to say that the problem is present in Dapper Flight 2.
But, I was able to see the IO errors more clearly. It's something to
do with my windows raid array and ubuntu trying to read from those discs.
I've had simular problems with Mandriva, but worked around that problem by
telling Mandriva
not to try mounting those discs. Maby you added sata raid support to the kernel
after Horay, and that's
why I'm not getting the error in that release? If so, then this would be more of an
install issue rather than a kernel issue.

[Stein Olav Aske (stein-aske)]

Oh, I'm not having any problems with the Live version of Dapper...

[Ben Collins (ben-collins)]

Can you look at dmesg output once it fails to mount, and send me any relevant
information regarding the drives? Hand written, or digital photo of the exact
output would be appreciated.

Thanks

[Stein Olav Aske (stein-aske)]

Created an attachment (id=5352)
A digital photo of the dmesg output

[Stein Olav Aske (stein-aske)]

My motherboard is MSI K8N Neo2 (Nforce 3 chipset) and I'm using the
on board SATA Raid controller. The discs are 2 Western Digital Raptor 73,4 GB
running in
raid 0, and formatted with NTFS.

[Ben Collins (ben-collins)]

So your system is on hda or hdb? What is being passed for the root= option to
the kernel?

[Stein Olav Aske (stein-aske)]

[lilo.conf]
boot=/dev/hdb
root=/dev/hdb1

map=/boot/map
default=Linux

image=/vmlinuz
      label=Linux
      read-only
      initrd=/initrd.img

My Ubuntu system is located on hdb, the root partition is /dev/hdb1. I've
mounted it on the live distro just to be sure. My lilo.conf was generated by the
Ubuntu install process. Vmlinuz and initrd.img is located at both / and /boot/
when I mount /dev/dhb1 on the live distro.

[Ben Collins (ben-collins)]

(In reply to comment #9)
> [lilo.conf]
> boot=/dev/hdb
> root=/dev/hdb1

Is your computer actually booting from hdb? Also, why are you not using grub?

[Stein Olav Aske (stein-aske)]

Whenever I try using Grub as a boot manager I get the following error:

Booting 'Ubuntu, kernel ...'
root (hd1,0)
     Filesystem type unknown, partition type 0x7

I've never bothered trying to fix this as I've always known lilo to work. I had
the same error while using Mandriva and Grub as bootloader. As for if I'm sure
that my computer is booting from hdb, fairly. I keep separate bootloaders for
Linux and Windows, so I have to specify which device I want to boot from (I've
had some bad experience using the same bootloader for both windows and linux).

[Ben Collins (ben-collins)]

Does /dev/hdb1 exist while you are in the busybox prompt?

[Stein Olav Aske (stein-aske)]

Yes, /dev/hdb1 exists while I'm in the busybox prompt, and I was able to mount
the partition manualy.

[Ben Collins (ben-collins)]

Ok, then this isn't a kernel bug (the hoary kernel is booting a different
initrd), so I am kicking this over the initramfs-tools. Please run this command,
since I know you'll be asked to (also update to latest dapper completely first)

sudo update-initramfs -u

Then reboot again.

[Stein Olav Aske (stein-aske)]

Created an attachment (id=5473)
dmesg after running "sudo update-initramfs -u"

[Stein Olav Aske (stein-aske)]

I tried running sudo update-initramfs -u and rebooting, but I still ended up in
busybox prompt.

[Tormod Volden (tormodvolden)]

Is this still a problem with for instance dapper flight 5? Is your linux boot disk also on the raid? You said the raid disks were ntfs... Exactly which RAID controller chip do you have?

Anyway, hdb sounds like an IDE disk and not S-ATA. It is also possible that grub uses another ordering of the disks than expected. For lilo I don't know.

For support of fakeraid boot disks in dapper, see bug #22107.

[RunDMC (s-bonn)]

I'm a noob too.

I experienced same problem triying to run the Ubuntu 6.10 Edgy cd live.

First i recive the message "/bin/sh:can't access tty; job control turned off
(initramfs)".

Triyin to resolve this problem, i found this hint in a Ubuntus spanish official forum : edit start line in the grub with F6 > changing "splash" for "break=bottom" y then CRTL+D to continue boot, but the result is the same. When CRTL+D again, the message is:

mounting /root/sys failed: no such file or directory
mounting /proc on /root/proc failed: no such file or directory
Target filesystem doesn't have /sbin/init

Hardware:

- Mobo: Desktop Board Intel® DP965LT
- Micro: Intel core2duo E6300 1,86Ghz
- Graphic: nVidia GeForce 7950 GX2
- Hard drive: Maxtor 6v200E0
- Optical:LG: HL-DT-ST-DVDRAM GSA H10N
              LG: HL-DT-ST-DVDROM GDR8164B
- RAM: 2GB DDR2 533 on double channel

[Recalcitrante (ignaciovicario)]

I have added a report of a problem like this in this opened bug: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/106063 But now I see that this is the right place. I have this problem in Ubuntu Feisty with its generic kernel 2.6.20-15.27. But no problem with a self compiled 2.6.17.14

Here is the copy and paste of my report in bug 106063:

2.6.20-15.27 fails and entering busybox in the ram disk
When appears the line below, it stays almost three minutes an then follows and enters in busybox.
 [ 9.024000] Time: acpi-pm clocksource has been installed
After about 3 minutes (in a PIII 450 MHz) it shows more lines, some of them with errors. here are the last ones:
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
 mount: Mounting /sys on /root/sys failed: No such a file or directory
 mount: Mounting /proc on /root/proc failed: No such a file or directory
 Busybox (...)
 /bin/sh: can't access tty; job control turned off
      (initramfs)

[grasshopper (blackwolf-franken-online)]

This problem was lately fixed with dapper 6.06.2.

[jcoates (jcoatz)]

So I have just got this issue in Maverick 10.10

I can't boot into ubuntu, I just get to the busybox promt, with initramfs displayed, and then it hangs.

Any thoughts?!