The fix may be released, but it doesn't fix the problem, see
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/896391
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403408
Title:
Grub 2 problem, e
Thanks to yet another complete failure in Ubuntu testing this has
occurred when I tried to do a standard network upgrade from 10.10 to
11.04. Now I cannot load Ubuntu, Windows 7 OR the recovery partition.
Laptop is essentially useless. Thanks!
--
You received this bug notification because you a
I suddenly began experiencing this problem this morning, after applying
an update to Ubuntu 10.10. I've reinstalled grub2 to no effect. I did a
complete re-install of my / partition. Same result. Error: no such
device.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I would just like to say that after about a year of having this head
ache with installing Ubuntu, I found out that the hard drive I bought
off the internet, which was supposed to be brand new, had the bios
changed in it, making it look like a 250 GB hdd that I paid for instead
of the 125 GB hdd tha
This bug occured for me today with a fresh install of 10.10 x64 on a
Thinkpad W700.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403408
Title:
Grub 2 problem, error: no such device
--
ubuntu-bugs
@karthik - 2 things: Firstly this problem does seem to have been fixed
some time ago, so you are right in some sense. Secondly XP bootloader
cannot boot Ubuntu! AFAIK Vista/7 bootloader can't either, so your steps
will fix Win boot. But you'll still need to fix GRUB2 so you can boot
Ubuntu.
--
Gr
This is Not A problem At all.
If you have Installed Ubuntu Along With Windows,
Windows Xp:
boot with windows xp cd,
go to repair screen,
choose your Windows and then Type
fixmbr
and
fixboot
then Reboot
Windows 7 And Vista
boot with windows cd,
After The Language Selection ,Click Repair Yo
This bug reappeared to me today after a kernel upgrade (after some weeks of
no problems), right after boot grub2 drops me to its shell. Booting manually
and removing the search line from grub.cfg fixed it. Maybe there is a
regression in grub2 ?
Thanks.
On Thu, May 13, 2010 at 2:38 AM, Adaptive w
Thanks Jed and PaulO for posts #89 and #90.
I've got an IBM Thinkpad T23, had the same problem and your posts got me up and
working on the first try.
I'm not a complete novice, but far from an expert.
Thanks for the concise and well-procedured responses.
Took me a little while to pick through th
Same bug is affecting me also, here is the number sequence it gave me
:eeaade90-1821-40e9-863a-8313c35b7031. How do i fix this, I'm not a
computer expert..
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member o
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: grub2 (Ubuntu)
Status: Fix Committed => Fix Released
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubu
Interesting thanks jhellen, I was hoping this might be the case, does
the nx7400 BIOS recognize the correct size of HDD above ~ 137GB? I
presume not however your confirmation would be appreciated.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this b
This problem went away with the latest beta of Lucid (10.04). At least
on my HP nx7400 :)
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I don't see any of the information required for a SRU request as stated
in the wiki page detailing the process. Unsubscribing the SRU team for
now.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
As far as I know, it is not necessary to relegate the remainder of the
disk space past 137GB to an extra or "archive" position. You can simply
create a separate partition for /boot, about 100MB or so should be fine,
and ensure that it is the first partition on the drive, or at least
within the firs
I would just like to make a correction to the second paragraph of my
previous post. You CAN use all of the space on your hard drive (YAY!).
However, you still must follow the guidelines set forth in the
directions above to avoid the "error: no such device $UUID" problem.
Note: you can use the prog
I believe I've figured this out. The problem occurs when your computer
doesn't recognize the total size of your hard drive. Look at the hard
drive information in the BIOS settings. Whatever the computer recognizes
is your limit. I replaced an 80 GB hard drive with a 180 GB hard drive.
When I enter
OK
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
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://lists.ubuntu.com/mailman/listinfo/ubuntu
I'd suggest posting on the forums (http://ubuntuforums.org/). Especially
as your problem may or may not be related to this bug.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Tried to install ubuntu 9.10 live cd today with existing Win XP SP3.
Asus A7N8X Deluxe, AMD Athlon XP 2800, 2G Ram, 640 GB HD. Hard drives
are two 320G drives striped together using Raid 0. Raid shows up as
scsi drive on mobo. XP on the first 200 GB. NTFS on the second 200 GB.
200 GB free. Ins
This worked! Thanks for the clear explanation.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
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
htt
You need to wait until Ubuntu has completely finished booting to the
desktop, then open the Terminal (Applications>>Accessories>>Terminal)
I would update grub-common before you do anything else (because
otherwise you'll have to do it twice - updating will break the repair).
So in the terminal win
1. From the grub bootmenu, press e to get to edit mode.
2. Erase the line starting with "search --nofloppy ..." and then press Ctrl+X
to boot.
3. When up and running you should run the command sudo update-grub.
I was able to perform steps 1 and 2 and boot successfully once but then
rebooting
I know that it's not good practice to post emotionally loaded responses.
So I will refrain from doing that. BUT, in 14 years of using linux
I have never ever ever ever ever ever ever ever ever ever ever ever ever
ever ever ever found an application that sucks so much as grub2!! Why?
I'll tell
Replaced the 60GB HD drive on an old gateway laptop, then installed 9.10 full
disk. Got this error. By deleting the search line in the grub (as explained
above) I was able to boot. I considered upgrading the BIOS, but since I don't
have windows on this machine it seemed t0o complicated for my si
I should mention that Win XP still loads fine (thank God for that).
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
This bug has just struck me.
I made an iso of Xubuntu today (latest), and tried installing it on an
old computer (P2 850, 256 Ram, etc). Install went fine, but I got
exactly the same messages as reported above (error: no such device).
This was a complete install on a small hard drive, using the w
Matthias et al: I am sure you are correct that installing a BIOS that
addresses the whole HDD is a solution - when those updated BIOS are
available.
Frequently I cannot find a sufficiently revised BIOS, which leaves one
looking for other solutions, that allow grub2 to cope with old BIOS.
If PC ma
Upgrading your Computer's BIOS most probably solves this problem as
well:
I had the same problem with an HP compaq nc4400 notebook which had been
upgraded to a 320 Gig HDD.
I was able to solve the problem by upgrading the BIOS.
This cured the BIOS' 128 GB HDD Bug and made the grub-Problem simply
Sorry for the long post everyone! I pondered whether to write this all
here or not - but decided it may be relevant to this bug for some Ubuntu
beginners.
@JimUSA - I know it can be frustrating but that is the nature of the
beast. All things considered (the breadth of different hardware, the
limit
I have just experienced this issue again (among others) trying to set up
XP/Ubuntu 9.10 dual boot on a desktop (DFI mobo with nForce4 chipset,
skt939 AMD X2 4400+, 320GB sda, 500GB sdb).
After sorting out my other issues, I again came to this bug, however the
behaviour is quite different to my lap
Thanks JedMeister, I'll be more careful to stay on topic.
Regarding Blocks vs Clusters? A user above mentioned that he expected
his LBA, large block addressing, might overcome the drive size problem.
It works by increasing the number of sectors that are grouped into one
disk writing unit so that
Glad you got your problems sorted Jim, but here is probably not the
ideal place to be fixing generic issues.
This is a list for discussion of a specific grub2 bug. I know you said
you have experienced this particular bug but a lot of your other posting
is irrelevant to this list. If you have other
Claude Heintz identified my problem. Thankyou Claude. I had noticed
the descrepancy between the size posted on the drive itself and the
reported size but I thought I was misinterpreting the HD label or that
there was high overhead.
I think I will try Claude's approach because I installed with a
I wonder if they will send replacement disks to replace these defective
ones they've sent out.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I miskeyed above, I was saying, they should change the name from Ubuntu
to TIME THIEF.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
It affected my old emachine that has a replaced drive that was running
XP before the partition and installation attempt. This is the first
emachine, a 900 Mhz screamer. I tried to install over and it wanted to
add an additional ubuntu 9.1 installation. Another oddity is that when
it allocated it
Somehow this seems to be fixed now?
I updated/upgraded the kernel a couple of days ago and I didn't need to
fix it this time! I'm not sure how they managed that because AFAIK grub2
wasn't updated (just the kernel) so perhaps I will still need to do it
again after a grub2 update? I hope not!
--
G
Post #35 worked for me using ThinkPad R31 with Ubuntu v9.10 (Karmic
Koala) fresh install.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I can confirm this bug. I Just installed Karmic with the 'use entire disk'
option, on a 250GB hdd and got the error:
...no such device. I did'nt try any of the fixes above. I reinstalled with
smaller /, /home, data partition, /swap. Other installs of Ubuntu on the same
250GB hdd went fine.
--
I have an HP Compact 8710p notebook with Vista. I did the plunge in Ubuntu 9.10
with the free CD but this "Grub loading error no such disk, grub rescue" is
preventing me from using my computer. I have spent at least 4-5 hours so far
trying to understand the instructions on how to install and how
Running an IBM T40, and after fresh install I got the problem described
above. Tried the solution in the first post, but when i try the sudo
update-grub i get" grub-probe: error: cannot find a device for /. And i
don't know what to do about it. any help would be appreciated.
--
Grub 2 problem, er
Cowboy, see http://ubuntuforums.org/showthread.php?p=8716254 for some
stuff that may well help you.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
It seems to me that I have a similar problem. When I was installing
Ubuntu 9.10 Server I answered to "Automatickly part the disk and
configure LVM". Installation finished succsessfully, but when I'm trying
to boot the system it says:"no such partition". I typed "set" at a gnome
resque panel and saw
Same bug hit me too, trying to install 9.10 after 10 Gb partition on 40 Gb
disk. Fiddling w/ partitions
showed critical point at 8 Gb, resulting in rescue mode if last install was
above that, or just an
unbootable menuitem (UUID mismatch) for an earlier install above 8 Gb.
8 Gb is one of many b
Am Sonntag, den 17.01.2010, 12:10 + schrieb Bogdan Mustiata:
> My suggestion is to add this module as default since it shouldn't impact
> the ones who have working bioses, and it should make the life of the
> guys with broken bioses (like me) a lot easier.
It can impact users with working a BI
@Philip
I've downloaded lucid alpha-2 iso yesterday and played around with it, so I can
tell for a fact that in the alpha-2 iso it's not fixed, or the fix doesn't
catches all corner cases.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug noti
I subscribed the ubuntu-sru team in case this is qualifies for an karmic
SRU.
@Bogdan: the bug that was fixed here was the issue identified in
http://savannah.gnu.org/bugs/?26834#comment1
Are you sure the issue you're having is the same as the one described there?
This bug was confirmed to be f
Setting to fix released in lucid as this was fixed in 1.98~20100101-1ubuntu1
or to be exact
grub2 (1.98~20091221-1) unstable; urgency=low
* New Bazaar snapshot.
- Fix search command failing on some broken BIOSes. (Closes: #530357)
[ Felix Zielcke ]
* Add Replaces:/Conflicts: grub-linux
Still happens in the latest alpha version (alpha-2, lucid). The fix from
comment #42 resolves it (adding --disk-module=ata to the grub-install
command).
My suggestion is to add this module as default since it shouldn't impact
the ones who have working bioses, and it should make the life of the
gu
Was having the same problem my girlfriend's Acer TravelMate 2301LC.
I had replaced the 40GB harddrive with a new 250GB one.
The larger harddrive seems to be a recurring factor in this bug.
So far I've been editing grub.cfg to remove the search line each time.
Anyway, I solved the problem by insta
Sorry I should have included this in my initial bug report.
Hardware: Dell Inspirion 600m (Pentium M 1.6Ghz, 512MB RAM - only
modification is new 140GB HDD).
OS environment: Dual boot - Win XP (original OS) & Ubuntu 9.10 (32 bit)
I upgraded the following grub2 packages:
grub-common (1.97~beta4-1
I just did apt-get update today and its broken again! Argh!
Now I know what to do it was easy to fix although now I have a grub
splash screen which is a dark image with black writing it was quite hard
to temporarily edit the the boot options so as to get in and fix it (I
just used post #1 above -
Newest grub from lucid ( 1.98~20100101-1ubuntu1 ) fixed this bug for
me.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I also had the same issue on a T41 laptop. Atm i have installed xp on
a 3gb partition and am installing linux as typing this hopefully that
helps, we shall see.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a m
I think that the information management in this thread is even worse
than the user experience caused by the above bug. Although I appreciate
the numerous hints to circumvent the problem, but only very little
information is provided about the nature and the cause of the bug. Is
the problem caused by
I had a working system with the fix in post #10. Then after running
updates today, (including a grub update that removed the fix) it failed
with "Out of Disk" and the fix in post 10 did not help. Also no access
to grub menu. I am trying a reinstall with a 10GB /boot partition.
Perhaps the "fix"
I am also having this problem. I have installed Ubunto on 4 computers. 2
worked fine right away.
#1) 160 gb toshiba only problem is having to figure out how to address the
built in wireless wireless. If i use the live edition it works but the
installed does not
#2) works fine but having a p
Hi guys, meant to post earlier, the issue was more basic, the Oct was older
than I thought and was a 32bit machine, got it reconfigured to 64 and do far
all seems to be working well. Thanks
Sent from my Magic
On 17 Dec 2009 00:36, "vdbergh" wrote:
I have some useful info to contribute I think.
My PPA has upstreams' bugfix for that included:
https://launchpad.net/~fzielcke/+archive/grub-ppa/
Note that this is the experimental branch and could have other bugs.
I also attach the fix which is in Bazaar revision 1924 in trunk.
Should apply cleanly to the karmic package.
** Attachment added:
I had the same issue and I was able to solve it by partitioning it
manually and putting /boot as first partition. I could not use the
'search' deletion trick because with lvm+encryption it doesn't even
reach the grub menu (but I had the same error message as in this bug
report when installing witho
I have some useful info to contribute I think.
I just got myself a 340Gb IDE drive. The bios claims it is only on a 139Gb
drive but the Karmic installer recognized the full
drive and the installer seemed to work fine. However when trying to boot into
my freshly installed sytem I got the error d
** Changed in: grub2 (Debian)
Status: Confirmed => Fix Released
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
@claudeheintz: my emachine (gateway) laptop also has a size limit
(learned this the hard way with winxp) but there is an easier solution
which doesnt have to waste any harddisk space. ALWAYS make your first
partition a boot partition. Make 1gb partition to host all the linux
kernels. And you could
I has this problem after installing Ubuntu on an older Gateway laptop
that I had installed a new 160gb hard drive. I installed Ubuntu after
restoring Windows XP. I did the fix by editing the config file which
worked for a little while until, after a few reboots, I could not get a
login from Grub.
On a fresh install Karmic 64-bit this still occurs. Removing the lines
in comment #10 made the system unbootable:
ubuntu karmic 2.6.31.16
Get the error now:
error: you need to load the kernel first
press any key to continue
and for the XP partition on a seperate harddisk
error: invalid signature
I decided to upgrade my old PVR to mythbuntu 9.10 and discovered the
hard way that this machine has the "no such device" problem. fwiw, it
has an AthlonXP-vintage MSI motherboard using ATA hard drives. After
much frustration I found this thread, and have been able to get the
machine to boot by remo
I can also confirm that I have this bug. Editing out the --search part
of the boot line gives me a working system. However... I just did some
updates and part of the update was a new kernel linux-2.6.31-16-generic.
After the updates my system reboots and instead of encountering the
error listed abo
http://lists.gnu.org/archive/html/grub-devel/2009-12/msg00095.html
Has a possible fix for this bug. If I understand the patch correctly it
doesn't actually get search by UUID to succeed but makes it no longer a
"fatal" error. So rather than the menu entry failing, the search --fs-
uuid --set comma
Jordan wrote:
> Since the upstream bug report mentions that this happens on BIOSs that
> can only read the first portion of large drives,...
I doubt this is the case. I am having this problem on a BIOSTAR K8M800
motherboard, and I have only a single data partition on an 80 gig IDE
drive. (Swap
Since the upstream bug report mentions that this happens on BIOSs that
can only read the first portion of large drives, can someone having this
problem and willing to risk possibly making the situation worse ( i.e.
not bootable even without the search line ) try "sudo grub-install
--disk-module=ata
same problem on Thinkpad T41 Felix (Comment #10) solved problem thank-
you
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Tried what was recommended in post #15. Success. I sure hope this ubuntu
was worth the time it took to sort this out.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hanno Böck wrote:
> Ubuntu-devs, can you please put a HIGH priority on this one and NOT release
> any more kernel or grub updates till this is fixed?
> I just got the problem on someones machine where I've worked around it
> recently. The new kernel update regeerated the grub config and the probl
Ubuntu-devs, can you please put a HIGH priority on this one and NOT release any
more kernel or grub updates till this is fixed?
I just got the problem on someones machine where I've worked around it
recently. The new kernel update regeerated the grub config and the problem was
back again.
--
G
Update, I installed xubuntu 9.10 on my ancient IBM thinkpad 600E and got
the "no such device" error. Removing the search line solved the problem
for this one
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a membe
I just tried to help somebody new to linux get through this bug. In the
end, we couldn't get it working and he's switching back to windows.
I doubt he'll be back anytime soon.
It's clear to me that grub2 was NOT ready for prime time.
--
Grub 2 problem, error: no such device
https://bugs.launch
Wow, thank you so much for the info on fixing the boot problem no floppy
etc.
I followed the instructions exactly EXCEPT, my lines were 173, 174 and
175. The edit of file grub-mkconfig_lib using the terminal command: sudo
gedit /usr/lib/grub/grub-mkconfig_lib worked flawlessly. I found it
easier t
This is my 4th clean install of Karmic, and I got bit. The bad part is
that this one was at a client, with a time crunch. The workaround in
the grub2 boot works, but I can't have a client do that. And I am
afraid to use the fix in post #10, as an upgrade means a service call
with "an emergency."
I encountered the same problem on a Dell laptop (I can't remember what model, I
guess from around 2005).
I edited /usr/lib/grub/grub-mkconfig_lib and commented out 3 lines as follows:
Before:
if fs_uuid="`${grub_probe} --device ${device} --target=fs_uuid 2> /dev/null`"
; then
echo "search
Is anything happening with this bug? I'm seeing more and more people on
the forums lately who have just decided to try 9.10 and are unable to
boot after installation due to this issue.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notificati
Anyone have any ideas how to do that?
I worry for all the people who might otherwise be so happy with
ubuntu
Duncan.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
It just happened to me. ACER Ferrari 3400 laptop, an old one running
8.04 before. I decided to install everything anew, just Ubuntu, no other
OS on the hard drive. I ended up editing /usr/lib/grub/grub-mkconfig_lib
as suggested in this thread to fix the problem.
This is a really annoying bug with
This should really be bumped to High importance, at the very least.
People are still running into this on fresh installs, and it's causing a
lot of frustration for new users. People who want to try Ubuntu are
being turned away.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/b
I'm new to Launchpad - does anyone how we can get this bug fixed, short
of taking a year out to learn programming and doing it ourselves?
Are the relevant people informed, and have it prioritised? I think it
is a critical bug as it renders your laptop completely useless!
I used the fix above and
I also confirm that the error appears after a clean install, no OS on
the disk. This is a awful experience for newcomers. I have three windows
machines, and two macs, and was hoping (and excited) about using Ubuntu,
specially 9.10 Karmic Koala. This bug/error is terribly frustrating and
even though
I can confirm that I also get the error message however i have no
problem booting. I have installed grub2 on a separate /boot partition on
the beginning of my disk. No problem booting win7 with grub2, just
linux. My partitions are ext3.
--
Grub 2 problem, error: no such device
https://bugs.launch
sjogro - what I did was to boot from the 'alternate cd' and that way I
could run a command prompt on the broken system and fix it.
See this post here:
http://ubuntuforums.org/showthread.php?t=1301144
There are other ways to get round this depicted above - maybe try them
first?
Duncan.
--
Grub
I can confirm this bug on a Fresh 9.10 install.
THIS FIX IS NOT RECOMMENDED --> editing: /usr/lib/grub/grub-mkconfig_lib
Some notes about the install.
500gb ide hd
Bios reports 136gb hd on bios boot screens. (Older PC)
Install goes fine, Reboot fails on "error: no such device"
Hold [shift] on bo
Just for the record, for people who get the repeated "no such device"
message and no boot menu:
If you turn on your computer and hold down the shift key, you will get
the Grub menu and can then use the instructions in comment #15 to boot
your system.
--
Grub 2 problem, error: no such device
http
@jon, "Rescue a broken system" is available in the "Alternate install
CD". If you have that ISO then you can boot using that also.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>From the grub bootmenu, press e to get to edit mode.
Erase the line starting with "search --nofloppy ..." and then press Ctrl+X to
boot.
When up and running you should run the command sudo update-grub.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received
I have had a similar problem with a fresh ubuntu 9.10 install on a
Thinkpad R40e.
On my system I was just getting "error: no such device" and "press any
key to continue" immediately without even seeing the grub menu. Pressing
a key just repeated the same message. Whats more, when booting from the
This is serious...hope it gets fixed soon. It was not good surprise
right after clean install you get can't find device!!!
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notifica
Managed to fix it on my T40 using the alternate installer and 'vi'
editor.
see this post...
http://ubuntuforums.org/showthread.php?t=1301144
and 4listers helpful reply.
Problem is the problem recurs on updating...
All best,
Duncan.
--
Grub 2 problem, error: no such device
https://bugs.laun
Felix:
You rock!
Everybody at Launchpad rocks!
This worked.
John
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Am Freitag, den 30.10.2009, 18:59 + schrieb John in SF:
> If I can get into this directory and file, I can do what is suggested
> but a list of the commands I should perform would really help since I
> am
> good at repetition and following direction. :)
sudo gedit /usr/lib/grub/grub-mkconfig_
Another approach but not full resolution:
I have been able to manually load the speciifc kernel following these
steps:
Boot to a Specific Kernel Manually
(https://help.ubuntu.com/community/Grub2)
However, when I re-start, I have to do the same thing again.
--
Grub 2 problem, error: no such dev
I also see this. My hardware : IBM x31, 1.7Ghz, 40GB hardrive, 1GB RAM.
Can someone provide explicit instruction on how to edit?
I see this comment below that was made previously but the problem I have
is how to actually edit the file.
"I edited /usr/lib/grub/grub-mkconfig_lib file . On line 147
Also happens on my T40, karmic 9.10 release install. After removing
search-line I can boot again.
--
Grub 2 problem, error: no such device
https://bugs.launchpad.net/bugs/403408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
1 - 100 of 110 matches
Mail list logo
