I'm sorry that this bug did not receive attention to get it fixed in the
dapper release; but dapper is now end-of-life, and the issue described
here should not occur in supported Ubuntu releases. If you encounter
other bugs in Ubuntu 8.04 and later, please file new bug reports for
those issues.
Everybody! Just close this bug, and file your own. Better to merge
duplicates than to argue over every single bootup problem possible. A
bug report is made for 1(ONE!) bug, not 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: initramfs-tools
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Try a diagnostic of your partitions.
Get GParted:
http://gparted.sourceforge.net/download.php
Uses ubuntu-like Gnome UI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/47768
Title:
Mount Root Files
I wish I understood all this lingo--new to u
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Well Yes I just got hit bad,, I got a new update on a semi stable version of
10.04 beta2 and then got an update released today 4/22/10 of Intrafms and it
appeared to install fine then crashed on reboot have filed bug here
https://bugs.launchpad.net/ubuntu/+bug/568580
Re: Intrmfs New update
Move the status back to New since it was changed by an currently
inactivated user that doesn't seem to be working on this bug.
it has been a long while since this bug was reported and Ubuntu has
evolved dramatically since Ubuntu 6.10 Dapper Drake. Can anyone actually
still reproduce this bug?
**
** Also affects: initramfs-tools
Importance: Undecided
Status: New
** Changed in: initramfs-tools
Status: New = In Progress
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
I have found similar hang in Hardy when installed on dual-boot mode with XP on
Sony Vaio desktop.
Only occurs after first major update. If I re-install from CD it works fine.
I have since discovered same on Acer Aspire 1 with 8.10 after replacing
Linpus. Ubuntu is sole OS this time. Workaround
This bug is not a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/262588
This bug has probably something to do with USB stuff while the so called
duplicate is a DKMS issue.
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug
This thread on the forums seems related (29 pages long):
http://ubuntuforums.org/showthread.php?t=765195
Near the end of the thread the suggested work around becomes 'use Fedora
10', so it seems like something that needs to be dealt with.
I was stung with a very similar issue with Hardy, and
similar bug in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/262588
i had same issue.
i typed down what bootup says:
after choosing kernel 2.6.27.1,
after pages of scrolldown,
usbhid: V2.6: USB HID core driver
(waits a bit here..)
Gave up waiting for root device. Common Problems:
-
Well I got my email about this bug, what I wrote and so I realised, that
my fix wasn't for the first bug reported, but for the bugs reported by
brett: https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/47768/comments/12
and
richard hau:
I have found this to occur in Feisty.
I attempted to update the kernel to that in Gutsy - added Gutsy to the
repository list.
On rebooting, the boot stops at the point where it tries to mount the hard disc
(inferred from symptoms).
After many minutes, I get a prompt from busybox.
When I check
My comments about this post actually refer to bug #32123 which
describes one of the issues mentioned in this bug. Please excuse my
error.
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Hello! First of all let me say I am truly regretting doing this. This is
a spam message sent to all critical bug message lists. It's purpose:
making this (https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/59695) bug critical too. This is a long standing bug and
has a very serious impact
Hello! First of all let me say I am truly regretting doing this. This is
a spam message sent to all critical bug message lists. It's purpose:
making this (https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/59695) bug critical too. This is a long standing bug and
has a very serious impact
I report same issue in Gutsy beta (up to date).
Machine: Acer Aspire 1600
Kernel: 2.6.22-12.30
Initramfs-tools: 0.85eubuntu19
Kernel stop booting on line Root System File. The log is similar to
the one on first post.
Thank you
--
Mount Root Files System Failed
Please close this bug!!! There are at least 4 different issues from
various people described here. The bug report spans at least 3
versions and it's almost a year and half old. The Confirmed status is
falsely stated, no issue has been conclusively found. This bug report
has little ability to
Unsetting dapper.2 milestone since this problem is not understood at all
at the moment.
** Changed in: initramfs-tools (Ubuntu)
Target: ubuntu-6.06.2 = None
** Changed in: initramfs-tools (Ubuntu)
Target: None = dapper-updates
--
Mount Root Files System Failed
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
Status: Incomplete = Confirmed
Target: None = ubuntu-6.06.2
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug notification because you are a member
I ran into a similar problem - the system wouldn't boot, but stop at some USB
HID message, or it would drop me into
busybox (similar to Arthur's case here). Turned out it was because I had
edited /etc/initramfs-tools/initramfs.conf,
and set BOOT=nfs instead of BOOT=local (for building an
I've exactly the same problem as Martyn Russell.
I've upgraded my distro to Feisty, and now when i try to reboot i get :
Loading essential drivers ... OK
Running /scripts/init-premount... OK
Mounting root file system ...
Running /scripts/local-top ... OK
Waiting for root file system ...
And
Some additional info...
My sata controller is a sata_nv
[EMAIL PROTECTED]:~$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: HDS728080PLA380 Rev: PF2O
Type: Direct-AccessANSI SCSI revision: 05
Host: scsi2 Channel:
aedwards, I agree with you, this ticket does not seem to be capable to
trigger any actions. If an of the mentioned Issues still exist in feisty
a new bug should be filed (imho).
--
Mount Root Files System Failed
https://bugs.launchpad.net/bugs/47768
You received this bug notification because you
I just updated on Feisty to kernel 2.6.20-14 and when I try to reboot (with
-quiet removed from the grub config) I get the following:
--
Loading essential drivers ... OK
Running /scripts/init-premount... OK
Mounting root file system ...
Running /scripts/local-top ... OK
Waiting for root file
I am not convinced anyone else here is having the exact same issue as
I was. It almost looks to me as if there are at least 3 separate
issues expressed in this bug. The machine that was affected by this
bug is a production machine, I can't really install feisty until it's
official release. I am
The recent daily build works great for me now. Loving feisty, and the
live cd works great.
--
Mount Root Files System Failed
https://launchpad.net/bugs/47768
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have a similar problem on edgy.
initramfs stops and produces a prompt on boot because it can't find the
root filesystem (root=/dev/md1)
typing 'mdadm -As' from initramfs gives errors as the /etc/mdadm.conf
file built into initramfs contains only the UUID numbers of my RAID
sets. No keywords or
Please guys answer Robert Collins questions.
As he mentioned, we would like to know if this problem is still
happening with a daily image of Feisty (http://cdimage.ubuntu.com/).
Thank you.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Needs Info
--
Mount Root Files System
try adding irqpoll to grub :
e (edit)
go to the ligne kernel /boot/...
e (edit)
add irqpoll
b (boot)
Not sure if it could work, but cost nothing to try !
If it works, you will have to modify your /boot/grub/menu.lst
--
Mount Root Files System Failed
https://launchpad.net/bugs/47768
--
Arthur, do you have any reason to believe that this bug is the problem
you are experiencing ? If not, please file a new bug for your problem,
as they are almost certainly unrelated.
Michael, we need to fix the root cause of the problem : do you know what
yaird does differently to initramfstools -
Under Feisty, I get the error
/bin/sh : can't access tty : job control turned off
(initramfs)
It then awaits user input. I'm using 01-11-07 live-cd on an Inspiron
6000D with an ATI x300 64MB and 512MB RAM.
--
Mount Root Files System Failed
https://launchpad.net/bugs/47768
--
ubuntu-bugs
The problem is in fact with initramfs-tools, but you can work around
this problem by using yaird to generate your initrd. Had this problem
quite often lately and searched for an alternative. yaird is a quite
good one (at least for me ; and I',m using raid + lvm ; bootloader is
lilo).
You cannot
I have the same problem in a HP laptop with Ubuntu 'Feisty'.
The problem becomes after updating initramfs-tools to version 0.85dubuntu5.
My system is not able to boot with initrd images generated with this version,
but dowgrading to 0.69ubuntu20, I can generate valid images for kernel 2.6.19
and
I think I have found the cause of the issue. It seems that the udev
persistent storage rules that should be found in the initrd under the
directory {initrd}/etc/udev/rules.d/65-persistent-storage.rules don't
exist for some unknown reason. It is my belief that since grub only
passes a UUID to
I installed and booted Ubuntu 6.06 Dapper Drake - Beta with no problem in
my laptop asus w3v.
Then, I installed all the updates with the Update Manager.
After that, I rebooted and apeared in the grub menu a new kernel.
kernel 2.6.15-25-386 - the new one
kernel 2.6.15-20-386 - the one that comes
on one test machine i have the same problem, it seems to be a problem with some
chipsets and newer kernel ? -hal? (hoary, breezy and demudi (sarge) had no
problems on that machine).
If there is anything connected to any USB port at boot time, i get a freeze at
Mounting root filesystem (without
I do have a built in USB hub on the ACER that will not install. It sits on
top of the pc and you press down to expose four usb ports. This may be the
problem. I will have to try and install with the the hub discontected from
the mother board.
On 6/15/06, Brett [EMAIL PROTECTED] wrote:
I tried
That's exactly the same symptoms on my system. (bug# 43950)
I solved the problem removing USB2 support in bios.
But the bug still exists!
I expected a solution today updating the kernel to 2.6.15-25-386.
But the bug still alive!
--
Mount Root Files System Failed
https://launchpad.net/bugs/47768
I tried installing Dapper a week ago and had a problem because it would
stop at the Root File System Portion of the boot (The second OK) on
the LiveCD. For unrelated reasons I reformatted and reinstalled Windows
on the same machine. During this I detached everything but the monitor,
mouse and
42 matches
Mail list logo
