Sorry, can't seem to change my posts here.
noacpi made the busybox thing happen less often, but it still did. With
rootdelay=10 irqpoll I started the computer 11 times in a row without
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Nevermind.. Just forgot to update-grub after editing /etc/default/grub.
*stupid* Looks like noacpi fixes the problem, I can live without ACPI on
a Pentium III.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Forgot to note: typing "exit" always works immediately. "irqpoll" option
also does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360378
Title:
Gave up waiting for root device after upgrade
I just installed an old box with Asus CUSL2-C (i815) and Lubuntu 14.04
(trusty). Occasionally get the busybootblows, but not always. Just
randomly, 2 times out of 3 maybe.
Turning "plug and play OS" in BIOS on or off makes no difference
Adding "noapic" after quiet splash in /etc/default/grub makes
I am using a few of different JumpBoxes, and after migrating them from
ESXi4.0 to ESXi4.1 I went to boot them back up, & in 2 of them have
received the error message saying:
Segmentation fault
Gave up waiting for root device
I have already tried switching the OS Type in vSphere device manager
fro
Yes, so now all the people who has the same problem has to re-vote there.
And issue there should be set as not duplicate,, if this can't be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360378
I already did file a separate bug. (bug #460914) It is marked as a
duplicate of this one. I'm not having boot issues anymore because of the
upgrade to Lucid. Lucid has its own share of boot issues, but gets past
that point. As we can see in the comments here, some people still
experience these symp
Alvin, kenorb - Most boot issues are unique to a specific platform and
BIOS. BrianL's issues are against a kernel that has gone out of support
and against HW that he never described. If y'all are still having boot
problems, then you should start your own bug report using 'ubuntu-bug
linux' (assumin
importance: High → Undecided ?
status: Confirmed → Won't Fix
How you can simple close High Confirmed bug with no any solution provided?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360378
Title:
G
For sure!
I was using Ubuntu at my work. After upgrade it was completely broke. I've
completely removed Ubuntu and installed FreeBSD, because I can't wait for
solution or follow the workarounds which will break my systems even more.
If I were the reporter, for sure after one year I would remove U
No offense, but would you keep a system that does not boot in order to
follow up a bug if a system doesn't boot after a fresh installation? I
can understand that the original reported doesn't respond anymore. He's
probably using another version/distribution by now.
--
You received this bug notifi
No response fro the original reporter
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
oli z, I'm glad the grub change worked for you, but I've had this
problem with both grub 1 and grub 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360378
Title:
Gave up waiting for root device aft
@zeeshaan
please stop spamming wrong informations. your "fix" has absolutly nothing to do
with the problems here reported.
just encountered the same problem on one of my servers. i checked on some of my
other servers and noticed that they hadnt installed grub2, they used grub
make sure you have
Here's a 100% working solution.
Zee's 6 step Ubuntu fix!
http://zeeis.me/ubuntu-boot-error-si...r-root-device/
If you wanna share it with anyone or post it on your website, please mention a
linkback as credit.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.lau
I just encountered this performing 'aptitude safe-upgrade' from 2.6.32-22.36
to 2.6.32-24.43 (generic)
Had two similar machines upgrade fine.
The previous 2.6.32-22.36 grub (v0.97) menu entry continued to boot fine.
After reading these comments I tried, after booting the previous kernel:
update-
Found this:
http://ubuntuforums.org/showthread.php?t=1195275
I had in /etc/default/grub default settings:
GRUB_HIDDEN_TIMEOUT_QUIET=true
'The user may force displaying the menu as the computer boots by holding down
the SHIFT key.'
Nice.
I'll try to boot with the older kernel.
--
Gave up waiting
I had as well 2.15.2, I did the downgrade to 2.14, but still the same error
Compare the difference:
http://launchpadlibrarian.net/55230468/mountall_2.14_2.15.2.diff.gz
There is already 2.17, but not any new fixes.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs
accidentally did an apt-get update, mountall 2.15.2 was installed ->
same behavior -> downgraded to 2.14 -> boots again
Cheers
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member
Solved the problem by booting recover kernel (had to add i915.modeset=1
to grub entry). After the error message type:
mountall
then a blue menu appeared
typed sudo gdm to start gnome
Had a look at the latest updated packages. With Synaptic removed current
version of mountall (mountall 2.15.1).
In the end I just reinstalled and it is now running fine. Perhaps that can
work for you too.
Cheers,
Danny
***
Log Off and Live!
www.ishouldlogoff.com
US Phone: 843-LOG-8OFF
On Sun, Aug 8, 2010 at 16:05, Mark Myers <360...@bugs.launchpad.net> wrote:
> I am
I am having the same problem. I loaded Ubuntu 10.04 into my laptop with no
problem whatsoever. I bought a new PC and installed Ubuntu 10.04 64 bit version
with double boot of Windows 7 which was pre-installed on the desktop.
I am too new to Ubuntu and Linux to know how to edit the config files or
It seems like I'm the only one still suffering from this problem. I got
a new laptop a couple of weeks ago and I installed Ubuntu 10.4 (netbook
edition) on it. I've been saddled with the problem described above ever
since! Tried changing the delay and replacing the UUID in grub with
'root=/dev/sda1
For those of you encountering this with VirtualBox, moving the system
drive(s) to a virtual IDE controller instead of a virtual SATA
controller fixes it.
I had the same issue after installing 10.04 to two virtual SATA drives
(1 sys + 1 swap), I then tried an expert install using LILO instead of
GR
Ah, got it. Thanks for the help. Now I see the interface indicating that
as well. Makes sense that it was moved to "linux" anyways, at it sounds
like a kernel issue.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug
I believe it was marked invalid against the initramfs-tools package, but
confirmed against "linux", if I'm understanding the launchpad interface
correctly.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notificati
Could someone comment on why this is in fact Invalid? Why was it not
marked a duplicate of another bug?
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Perhaps Rick Silva's fix in #26 is also an option? Or is that really
for the older bug
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This problem appeared for me this week after some recent updates on my
Karmic 9.10 package. This leads me to believe its closer to the
Maverick issue discussed in #32-34 above but does that mean I need to
execute the code in #33 to fix? or should I look at #6 to fix? Either
way I'm a newbie and
Colin Watson, can you pls clarify the reason for this bug having been
marked invalid on 6/17 ? Is it superseded by 577353? The experiences
described by several people above do seem to indicate that this problem
does [still] exist in Lucid. I am able to reliably reproduce this
problem, whenever upg
Thanks for the update, Colin.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Noel, you do not have this bug (360378). This bug was introduced
briefly in initramfs-tools 0.96.1ubuntu3, and has since been fixed;
since it was introduced for the first time on 16 June 2010, it can't be
the same as this bug which was filed on 13 April 2009. It just happens
to have similar sympt
Confirmed. The workaround is to run:
dpkg --set-selections
initramfs-tools hold
initramfs-tools-bin hold
^D
before upgrading.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
Gave up waiting fo
This is reproducible with Maverick today. I did a clean reinstall,
reboot, update, reboot and BOOM!
The complaint appears to be that during init, "wait-for-root" cannot be
found. It is NOT kernel related, since I was able to use the kernel
earlier. From what I remember of today's updates, this
same here...
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
I just had this happen with Maverick during today's updates.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
The problem also occurs with VirtualBox. Using a kubuntu 10.4 64bit
host, I installed the proprietary version of VirtualBox (downloaded
virtualbox-3.2_3.2.2-62298~Ubuntu~lucid_amd64.deb from
http://www.virtualbox.org/wiki/Linux_Downloads) and made a ubuntu 10.4
32bit server image (from ubuntu-10.0
@John D Marsden
I have seen this bug on several machines, where I couldn't boot different
versions of the kernel, and it wasn't 100% reproducible. (rootdelay fixes
nothing)
However, the problem you have with kernel 2.6.32-22 seems to be
reproducible. I have experienced the same on one pc and fil
I had the same problem on my wife's Netbook (Toshiba NB200) after
upgrading from Ubuntu Netbook Remix 9.10 to Lucid using the standard
upgrade procedure.
I tried the extending the "rootdelay" altering the Grub instructions to
look for /dev/sdax instead of the UUID but neither worked.
However afte
Found a new fix...
Had ried a couple of the solutions above:
- added root delay to grub.conf / kernel boot options
- changed grub to reference the root drive directly instead of by UUID
- copied "initrd.img-2.6.32-21-generic" from another machine running Lucid
... but neither of those worked
Howe
tuc821!! your #6 response was magic! fixed a problem i've had for a
month! many thanks
martin b
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1st reinstall didn't work for me either, hard drive not found on first
boot. I replaced the drive and it installed fine the second time.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are
I tried that too, but on first boot, the hard drive wasn't found. I also
tried another install on another hard drive without progress. Reinstall
is not the solution.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug
I gave up and did a fresh install of ubuntu 9.10
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
I now have this on a server that previously did not showed this behaviour.
(Most others do)
It didn't show up until after the upgrade to linux-image-2.6.31-20.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notif
I found an outer half solve (the first?),
half because when we can change storages, or we can install Ubuntu to a
pendrive.
December 31, 2009 (-> ancient bug)
Solving the BusyBox black screen problem in grub2/Ubuntu9.10
http://computergyan.wordpress.com/2009/12/31/solving-the-busybox-black
After upgrading to grub2, I am able to successfully boot into 2.6.28-18.
This is a workaround, not a fix, as I would still like to be able to
boot into 2.6.31-20, and that kernel still gives the uuid no device
exists error.
--
Gave up waiting for root device after upgrade then busybox console
htt
More info as I continue to work this problem:
I have 6 different kernels on this box, as I never removed any.
The following kernels boot to a maintenance login:
2.6.24-19
2.6.24-24
2.6.24-25
2.6.24-27
They all display this error:
"init readahead main process terminated with status 5
mountall:/proc
Also experiencing this bug, after upgrading my fileserver from jaunty to
karmic, get error message:
"Gave up waiting for root device. Common problems:
- Boot args
- check rootdelay= ...
- check root= ...
- missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/ does not
Craig,
I followed your suggested procedure in the above post, but still I
have the same problem. Finally I am ending in a console login where my
screen is continuously flashing so I couldn't even log into my account.
While loading the grub I verified that my grub is pointing to kernel
2.5.31
Here is my path to fixing the problem on my Ubuntu 9.10 that was set-up
by System76. I am not really a sysadmin type, so take my remarks
cautiously.
- Booted up from a Live USB (Ubuntu 9.10)
- First needed to mount my root partition (sda1 is mine):
sudo mkdir /media/sda1
sudo mount -t ext3 /dev/s
Are we sure it's a bug in the kernel, and not grub2?
These are the things I know:
- The problem does not always occur (In my case, it's 80% of all boots)
- LVM is irrelevant
- Hardware is irrelevant
- changing to acpi=off kernel option helps in some cases
- changing UUID to full path in grub.cfg h
I switched the harddive on an affected server and reinstalled karmic.
Same problem. Won't boot after install.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Added tag iso-testing because this happend on fresh karmic installations
Added tag ubuntu-boot-experience because it affects the Ubuntu boot experience
** Tags added: iso-testing ubuntu-boot-experience
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.n
Bug #343919 may also be a cause of this
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
http://zfranciscus.wordpress.com/2009/11/01/ubuntu-karmic-upgrade-series-1-upgrading-jaunty-to-karmic-koala/
Also makes mention that loading by UUID and found that loading with actual
device name worked better:
<>
--
Gave up waiting for root device after upgrade then busybox console
https://bug
Other reports: http://ubuntuforums.org/showthread.php?t=1319976 Some
work-arounds appear to be discussed there.
I also found this posted out in the wild:
<>
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
Gave up waiting for root device after upgrade then busybox console
ht
i confirm this bug as well. I'm running a Thinkpad T61p, core 2 duo,
nividia gt8600. Got the "Gave up waiting for root device" then it drops
to initramfs using ash. Bad bug.
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received t
Ok, again did a new Ubuntu 9.10 AMD64 install and upgrade on another PC, now
this problem does not occur..
So it seems not to occur on every install (and if it does, I know the fix, see
previous post ;)
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad
finally.. this fixed it for me too, thanx!!
After a clean install and upgrade on my new (Ubuntu) PC my harddisk suddenly
was not found an more.
Booted from Life CD, everything, disk, labels seemed ok, but no boot until I
did put it the direct reference to my Linux partition.
To make myrand new
Having same problem, was hoping for a resolution ... :)
Details:
Was applying updates/upgrades - saw a message about needing to run lilo ...
lilo said something like (IIRC) /etc/lilo.conf does not exist ... machine ended
up getting rebooted (was fine until then!) ... and now --> Boot menu == "U
This is not a bug in the linux-meta package, moving to the linux
package.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a me
Exactly the same happening for me after upgrade to Jaunty. BusyBox
returns every time. The known rootdelay=90 workaround doesn't work. Grub
recognizes the partitions correctly right from the start, and the UUIDs
are proper, but kernel fails to find the root drive.
I am using a laptop with a SATA h
** Description changed:
Binary package hint: linux-image-generic
- After upgrade via synaptic on 4/12/09 system is now not booting
- correctly was working with previous kernel 2.6.28.11 but the changes to
- this package after 4/12/09 may have caused my system to not longer boot
- and fall bac
64 matches
Mail list logo
