I would like more confirmations that the patch in #90 actually works.
Your feedback is appreciated.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I replaced C:\wubildr with the file attached in #90 and that fixes the problem
for me.
Thanks.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Agostino
In the link I provided before another user confirm that this patch fixes the
issue.
** Tags added: verification-done
** Tags removed: verification-needed
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification
Wiped and reinstalled 9.10 before your patch became available. I did
not use the LiveCD, but downloaded then current Wubi.exe and let it
fetch all needed modules of 9.10. This installed Grub 1.97~B4, which
appears to function without any glitch.
Have kept your mail and patch against the
** Changed in: grub2 (Ubuntu)
Status: Triaged = Fix Committed
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: grub2 (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: grub2 (Ubuntu)
Status: Fix Released = Fix Committed
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Triaged
** Description changed:
Binary package hint: grub
Installed ubuntu 9.10 using Wubi.
Performed upgrades.
After a grub update could not boot.
Get screen:
Try (hd0,0) : NTFS5:
and then
-
Bug is in Launchpad :
https://bugs.edge.launchpad.net/ubuntu/+source/grub2/+bug/477104
There i instruction to boot and to repair.
I was having the same bug.
If you need more help, ask me.
2009/12/18 Sergio Zanchetta prime...@ubuntu.com:
** Changed in: grub2 (Ubuntu)
Status: Confirmed =
@Agostino
As you can see here
https://answers.edge.launchpad.net/ubuntu/+source/grub2/+question/91579
this patch fixes the problem.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of
I have applied the grub patch proposed by phcoder (comment #77) and
regenerated wubildr
Please try to replace C:\wubildr with the file attached and report
whether this fixes the problem
** Attachment added: wubildr
http://launchpadlibrarian.net/36920146/wubildr
--
After 9.10 grub update can
Please make sure that when you boot the line insmod ntfs is commented
out or disable it by pressing e at the grub boot menu and edit the
entry before proceeding.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification
** Changed in: grub2 (Ubuntu)
Assignee: hyungt1024 (hyungt1024) = Lakshmanan (lak89)
** Changed in: grub2 (Ubuntu)
Assignee: Lakshmanan (lak89) = (unassigned)
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug
#22 -
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/477104/comments/22
fixed it for me. But, that blew away a couple more hours...
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member
Re: Post #5: Mr. Russo; On my machine C:\wubildr and
H:\ubuntu\winboot\wubildr match exactly as to Byte size and MD5Sum, as
do C:\wubildr.mbr and H:\ubuntu\winboot\wubildr.mbr, where Win 2K is
installed on C:\ (or Disc 1-1) and Ubuntu 9.10 is(was) installed on H:\
(or Disc 2-1). Disc 1-1 is the
The problem magically rectified itself , the last time.
I updated my system last night, after being unable to access it for a week. I
noticed an upgrade for grub, and it broke it again. Now I can't boot again.
This is doing ubuntu's reputation as a stable operating system, no good at all.
I
Andy and Jim,
I had this problem on a computer at work a couple of weeks ago. I messed
around with it for a few days, and then decided that I could not afford to
spend weeks trying to make my computer boot properly. I reformatted the hard
drive and installed Ubuntu as the only OS, and it's worked
Amen, Peter Brook.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
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
I've been having this problem for months...MONTHS!! I either install the
update (2.6.31-16), reboot and get the kernel panic issue or actually
use the (2.6.31-16) update, install and configure my applications, get
in a few reboots that actually took me back to my desktop until that
unlucky time it
what is upstream? where will be propagated the fix? how to patch with
in an already installed wubi?
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It's the same bug of the kernel panic error ?
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/477169?comments=all
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which
Am Samstag, den 12.12.2009, 14:27 + schrieb meow81:
It's the same bug of the kernel panic error ?
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/477169?comments=a
ll
It can't be. GRUB has nothing to do with the kernel being unable to
mount it.
At least if the root= linux parameter
Am Samstag, den 12.12.2009, 14:03 + schrieb meow81:
what is upstream? where will be propagated the fix? how to patch with
in an already installed wubi?
In the context of Vladimirb (phcoder) it means the GNU project, where
GRUB is officially developed/maintained.
I don't know the internals
Hi,
I described my symptoms (kernel panic etc) in #58
None of the proposed fixes worked for me (e.g. post #65, or I didn't execute
everything properly, but I think I did).
However, this worked like a charm:
http://ubuntuforums.org/showpost.php?p=8361928postcount=38
(replace /dev/sda1 with your
Having reinstalled 9.10 once already, upgraded Grub twice, and sifted
through all 82 foregoing posts, plus more linked struggling, I suddenly
recognize I could be dealing with this Schweinerei for five more months.
However engrossing a hobby Ubuntu might prove, I have remunerating work
to finish.
It's a bug in ntfs.mod for which I committed the fix upstream yesterday.
Use upstream or wait for Colin Watson to propagate the fix
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of
Type the next script in order to find the Y:
grubls (hdX,Y)
where Y=1 in most of Wubi cases, hence
...root=/dev/sda1
--
grubls
grubls (hdX,Y) #find ubuntu partition
grubinsmod ntfs #load ntfs module
grubset root=(hdX,Y)
grubls $Boot #find BOOT
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) = hyungt1024 (hyungt1024)
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Greetings all, I recently updated my system and was surprised to find
that on reboot that grub could not load the kernel, offing a message:
file not found. After exploring the grub shell for a bit I found that
the mounted boot partition was loaded into the /boot directory. Thus in
the beginning of
Same issue here with 9.10 x64 in Wubi.
Mine seems to be an issue with the kernel though. When I enter:
linux /boot/vmlinuz-2.6.31-15-generic root=/dev/sda3
loop=/ubuntu/disks/root.disk
I get a grub error reading file. However if I specify -14-generic
instead, it works fine. I have
OK Joe I have got the same issue.
This is an issue with kernel patch 15 magic number
try
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda3
loop=/ubuntu/disks/root.disk
instead of
linux /boot/vmlinuz-2.6.31-15-generic root=/dev/sda3
loop=/ubuntu/disks/root.disk
And don't forget to initrd
Hello!
Also have this problem and tried all the suggested solutions - nothing
works. Though, I can boot from grub's shell manually.
After this crash, I've completely reinstalled Ubuntu and now I have two images
- the working one and the broken one.
I am wondering, what if I just copy everything
I think I've found a solution for me.
Steps:
1. Completely remove grub, grub2, grub-pc and grub-common packages.
2. Delete all files in the /boot/grub directory
3. Delete packages cache, so they'll be downloaded once more (don't know
whether it is necessray)
4. Install grub-pc and grub-common
You need to be following bug #477169 for the most up to date info on
this problem, as well as a workaround solution.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same problem.
The issue is that the new kernel has a bad magic number.
So it is unloadable.
But return to grub prompt instead of grub boot menu is very unpleasant.
The following sequence save me:
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1
loop=/ubuntu/disks/root.disk
initrd
(Warning: English ISN'T my native lenguaje, so, please, be patient)
I'm affected by this bug too, but, in my particular case it appears
when, before I install the grub2-splashimages package, I *also* make a
modification of the /etc/grub.d/05_debian_theme in order to activate a
splashimage, and
@800xlman:
I used to have that problem in Jaunty (wubi) too. Its a problem of
configuration in the boot.ini file (well, that WAS in my specific case,
maybe it is the same situation for you). I solved via 'test error' or
in other words, testing all the posible entrys on the boot.ini file.
In the
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Critical
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which
Forgive me I am new to ubuntu 9.10 this is my problem. I did my updates
and the computer got stuck at sh:grub prompt now I typed this in
sh:grubinsmod ntfs
sh:grubset root=(hd0,1)
sh:grubloopback loop0 /ubuntu/disks/root.disk
sh:grubset root=(loop0)
sh:grublinux /boot/vmlinuz-2.6.31-14-generic
Hello all,
Experiencing the same problems as above. Have
- single hardisk (2 paritions) with WinXP and Ubuntu(on C:\)
- Ubuntu 9.10 Kernel 2.6.31.14 was installed first and grub worked fine
- Update generated new version 2.6.31-15
- restarted system and falls into grub shell.
Followed the
As was already commented on, go to bug report 477169, and read #69 and #70.
Complete workaround solution to the problem.
If it doesn't work, go read it again.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification
Kudos to Mark Abene. Mark, using this trick I was finally able to boot
my wubi install. Thanks!!! See my post in bug
https://bugs.lauchpad.net/wubi/+bug/477169 #69. I typed all the
commands from the grub prompt, now I'll modify the appropriate files to
make this automatic.
--
After 9.10 grub
Following situation here:
Karmic Installation with wubi
Kernel is 2.6.31-14 (no other installed)
After booting grub says error: file not found
grub.cfg looked like garbage
Booted Ubuntu from Live-CD
Grup.cfg looks fine here. I tried to rewrite it anyway by doing the following
steps:
- Mounted
Getting 'ALERT! /dev/hda2 does not exist. Dropping to a shell!' after trying
some of the workarounds mentioned in this thread.
It seems that some people have managed to go over this or over the whole
mess... any suggestion on what I should try at this stage?
(grub.cfg also shows some grabage
I got the same error with the latest kernel update:from 2.6.31-14 to
2.6.31-15
When booting it ended up in the minimal grub shell.
HOWEVER, I could recover to a certain extent:
Noticed that there was already a (loop0) device listed, thus the grub could
create the loop device from the root.disk
It isn't the kernel update that broke anything, it's grub2 losing the
ability to see the new kernel file. In all my tests (I've been able to
reproduce every single error everyone has gotten), grub2 was always the
root cause.
As a test, I created a complete duplicate of my Wubi install as ext3
In brief - same behaviour as #44.
Installed kubuntu 9.10 with wubi, was running fine this morning. Then I updated
it and since then it won't boot up giving the
Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block (8,2)
message
I tried manually booting like in #1 (tried all
Ok, it's definitely messed up.
I tried the update without the grub update, it seems that some stuff in
the update list caused the kernel not to find the hard disk.
I am now seeing the error like in #37
Kernel Panic - not syncing: VFS:unable to mount root fs on unknown
block
even though i can
@ Comment #52 and #53
try for hd0,1 sda1 or for hd1,3 sdb3 and so on. Please remember this
thread isn't for support! Next time you should use google for answering
questions like that.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received
I have the same problem as described in comments #44 and #37, and I'm
quite sure I'm typing the correct parameters for root and loop. I get a
kernel panic after manually booting following the instructions above.
What to do in this case?
OBS: My Ubuntu is 64-bit
--
After 9.10 grub update can not
I have the same problem that mohdyusuf (comment #52). When I try to
recreate the grub, the system says that there are no 'mount point in
/dev/ /mnt/dev' where I write 'sudo mount --bind /dev/ /mnt/dev'.
And alsoi, I'm unable to load ubuntu with the suggestion of comment #1
or #17.
I have the
Same problem here, since nothing worked i've had to reinstall Wubi i'm
really pissed this bug should be listed as high.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: grub (Ubuntu)
Status: New = Confirmed
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
My Bug #482195 was marked as a duplicate of this one, but I'm not sure
if it is. It is a specific edge case when using the AMD64 version of
Ubuntu and specifying installation size to 30G. If I use 32bit Ubuntu
or if I specify 29G installation size and below then everything went
fine.
--
After
This bug affected me too. However, none of the workaround to manually
boot the system failed for the fact that no hard disks were listed under
/dev/
I have no idea why.
when i do
sh:grub ls
i get something like
(loop0) (hd 0) (hd 0,1) (hd 0,2) (hd 1) (hd 1,1) (hd 0,2)
but there is no
Same problem here, running 9.10 wubi from the c:\drive on win7. In order to get
going again, i tried basically all tips in this thread, with no luck. As a last
resort i renamed my c:\ubuntu folder to ubuntu.old, and installed a new wubi
instance. Then after restarting, esc out of grub to the
Fresh Ubuntu 9.10 wubi install here. And here's the deal:
After updating and regenerating /boot/grub/grub.cfg (which is the same as
original), a fresh boot drops me to the grub prompt. Grub2 is unable to read
any text files at all now, which is the obvious reason for being dumped to the
grub
A few more observations:
I mentioned that running grub-install modifies c:\wubildr and deposits a tons
of files into /boot/grub on the linux side.
The files are being copied from /usr/lib/grub/i386-pc. I have no idea why
they're being copied, as a stock install does not locate these files in
Adding bug #477169 as a duplicate, because it is. That's exactly what
happened to my first install if initrd is updated. If the kernel is
updated, it's invalid magic number. In fact it looks like any file
which is updated from the original stock install reads as garbage from
within grub2. For
After the newest update (yesterday), i can't even boot ubuntu manually
using steps i stated before.
it hangs half way through booting, Some of what is written on the
screen:
RAMDISK: Couldn't find valid RAM disk image starting at 0
No file system could mount root, tried: ext3 ext2 ext4 fuseblk
In desperation I ran 'update-grub', tried to reboot and failed.
I ran 'upgrade-grub2' to put everything back as before, and ran a single
update to my 'gCDEmu' virtual CD system, before rebooting. It all works
fine for me, now!?!
--
After 9.10 grub update can not boot into Wubi install
Have the same error, Karmic, x86_64 (grub prompt, grub fails to execute
grub.cfg).
Here are a few (possibly new) symptoms:
* grub.cfg looks fine when editing using vim after booting the system using
grub shell commands
* however: when using cat /boot/grub/grub.cfg from the grub shell, it shows
Hi Agostino,
I also get a load of 0's when catting the loop0/boot/grub/grub.cnf
before setting the loopback...
I also tried to figure out what is going wrong, it seems not to be
related to grub, but rahter to what happens before/how grub is loaded...
Here is why I think this:
I moved my broken
Yes that seems to be the case, but I cannot reproduce this bug, and there isn't
anything obvious in the code.
So it's a matter of narrowing it down a bit.
If you follow the instructions in #39 it might help. Hopefully this is
reproducible on your side.
If it is an update-grub problem, it might
Hi Agostino,
Thanks for the help, it was sda2.
I've now booted and opened grub.cfg, its perfectly readable, see
below...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN
I have 2 update-grub commands, update-grub and update-grub2
After running the first:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s
After typing:
linux /boot/vml... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
initrd /boot/init...
boot
and getting:
ALERT! /hosts/ubuntu/disks/root.disk does not exist. Dropping into a shell!
I can't find root.disk or even 'Ubuntu' folder. 'Hosts' folder exists,
but there's no 'Ubuntu'
I have exactly the same problem. After the grub update, i restarted the
next day (today) and am suck in the same place starting at sh:grub
Did what you said Augostino. Here's what I got:
ls delivered:
(loop0) (hd 0) (hd 0,5) (hd 0,3) (hd 0,2) (hd 0,1)
root delivered:
Filesystem is ext2
then
Whoops, sorry for the sp on your name Agostino. I typed it from someone
else's sp error. Thanks in advance for any help.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs,
If you have ALERT! /hosts/ubuntu/disks/root.disk does not exist. it is
because when you run the command
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1
loop=/ubuntu/disks/root.disk ro quiet splash
you need to replace /dev/sda1 with the appropriate partition, /dev/sda1
means that wubi is to
A fresh install of Wubi 9.10, also failed to reboot after the initial
configuration boot.
results of above commands are:
ls
(loop0) (hd0) (hd0,2) (hd0,1) (hd1) (hd1,1) (fd0)
root
(loop0): Filesystem is ext2.
cat (loop0)/boot/grub/grub.cfg
(pages of garbage, eg. cbce8aaF[Ta4bbRc3)
So it seems that (loop0)/boot/grub/grub.cfg is corrupted, can the others
confirm?
You can also check the file if you boot manually as explained above and then
open /boot/grub/grub.cfg
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received
ls:
(loop0) (hd0) (hd0,5) (hd0,1)
root:
Filesystem is ext2. --- why its not ext4?
cat (loop0)/boot/grub/grub.cfg:
Fullscreen of 0 --- Inverted colors,
background white, text black
configfile
Tried to boot manually using:
linux /boot/vml... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
initrd /boot/init...
boot
got:
ALERT! /hosts/ubuntu/disks/root.disk does not exist. Dropping into a shell!
the path exists in windows, but there is no ubuntu in hosts in BusyBox,
although hosts
Augostino,
I also got the errors:
sh:grubconfigfile (loop0) /boot/grub/grub.cfg
error: unknown command a...@??!?$'Ao?T%'
error: unknown command D?1%
error: unknown command e?h??l9...@??
@ looked like a smiley face :)
% looked like clubs ie deck of cards
--
After 9.10 grub update can not
Andy,
I've had:
ALERT! /hosts/ubuntu/disks/root.disk does not exist. Dropping into a
shell!
but I had syntax wrong.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs,
Agostino, I took the grub.cnf entry from a clean wubi 9.10 install, so
that's why the insmod is there :)
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks for everybody's posts to this issue -- they solved the problem
for me. Here's a brief account:
I installed 9.10 AMD64 under Windows XP MCE using wubi, and got stranded at the
grub2 prompt during the first reboot.
As described by others, I entered only:
linux /boot/vml... root=/dev/sda1
The sudo update-grub2 broke my system :o
I earlier replaced the grub.cfg in /boot/grub, but the update-grub2
replaced that one by a new one?
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a
McKraught what is the output of
cat (loop0)/boot/grub/grub.cfg
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Augostino,
here it is:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set
McKraught, that looks fine, can't you boot with that config.cfg?
I.e. can you do
configfile (loop0)/boot/grub/grub.cfg
then select the first option?
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you
Please note, I only need reports for people who have the problem, if
somehow you fixed the issue, please do not reply or you will be make
debugging more complex. If it does NOT work for you, please post the
output of the following grub commands:
ls
root
cat (loop0)/boot/grub/grub.cfg
configfile
** Changed in: grub (Ubuntu)
Status: New = Confirmed
** Changed in: grub (Ubuntu)
Status: Confirmed = New
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs,
Hmm, comment #11 shows that loop0 is already mounted,
which means that the steps in #19 up to `set root-(loop0)` are not needed.
What happens if you type `root` in the grub terminal (without entering
any other command)?
I am particularly interested in why you are using `insmod ntfs`, since ntfs
This works if you add the boot command.
After the system booted, I ran update-grub2 in terminal.
This fixed the boot problem.
thanks
On Sat, Nov 7, 2009 at 2:14 PM, robau r...@audenaerde.org wrote:
ok so I found out how to restart by hand:
insmod ntfs
set root=(hd0,1)
loopback loop0
I ran update-grub2 after system boot in terminal as root and this did
not fix my problem.
Agostino Russo when I keyed root at the prompt I got:
(loop0): File system is ext2
As far as why I used `insmod ntfs` I have no reason for using. (is my face red?)
what I used is:
sh:grubset root=(loop0)
I installed 9.10 using wubi on xp I also updated grub with update
manager. I have to manual boot with:
sh:grubinsmod ntfs
sh:grubset root=(hd0,1)
sh:grubloopback loop0 /ubuntu/disks/root.disk
sh:grubset root=(loop0)
sh:grublinux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1
Same here... I guess that when the upgrader asked whether we wanted to
overwrite the current grub2 configuration file or not we should have
said YES instead of KEEP CURRENT VERSION (or something like that).
I'm running grub in a second stage after rEFIt (this is an Intel MAC),
and my situation is
Same problem here. After a clean shutdown, I treid to reboot this
morning, getting the same problem..
(Also, when booting to Windows, windows was running a chkdsk.. so maybe
something else went wrong too.. :S)
--
After 9.10 grub update can not boot into Wubi install
This is how I fixed it:
1) Boot from a Live CD
2) Reinstall grub as explained here:
https://wiki.ubuntu.com/Grub2#Recover%20Grub%202%20via%20LiveCD
Just in case the link above stops working, this is what I did:
# sudo mount /dev/sda4 /mnt
(/dev/sda4 is where my linux data partition
Try to replace C:\wubildr and C:\wubildr.mbr with the respective files in
C:\ubuntu\winboot\wubildr*
Please let me know if that works
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of
Also please post the grub configuration file that does not work
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This does not help :(
Also the fix suggested by Fernando does not work, as I use a root.disk
file and no direct partition.
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs,
Replaced the files.
No change.
Still get the sh:grub prompt.
Dieter
On Sat, Nov 7, 2009 at 7:31 AM, Agostino Russo agostino.ru...@gmail.comwrote:
Try to replace C:\wubildr and C:\wubildr.mbr with the respective files in
C:\ubuntu\winboot\wubildr*
Please let me know if that works
--
After
Do you get any file printout with?
cat (loop0)/boot/grub/grub.cfg
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
What is the grub.cfg inside of root.disk? root.disk /boot/grub/grub.cfg
What is the output in the grub console of?
ls
ls (loop0)
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this bug notification because you are a member of Ubuntu
From the sh:grub ls (loop0) I get
Device loop0: Filesystem type ext2,
Last modification time 2009-11-06 00:53:47 Friday,
UUID bd548a62-c679-41f3-8c33-1854ff6ae498
Dieter
On Sat, Nov 7, 2009 at 9:04 AM, Agostino Russo
agostino.ru...@gmail.comwrote:
What is the grub.cfg inside of root.disk?
I get a screen full of 00 ...
On Sat, Nov 7, 2009 at 9:06 AM, Agostino Russo
agostino.ru...@gmail.comwrote:
Do you get any file printout with?
cat (loop0)/boot/grub/grub.cfg
--
After 9.10 grub update can not boot into Wubi install
https://bugs.launchpad.net/bugs/477104
You received this
Same here
On Sat, Nov 7, 2009 at 8:31 AM, robau r...@audenaerde.org wrote:
This does not help :(
Also the fix suggested by Fernando does not work, as I use a root.disk
file and no direct partition.
--
After 9.10 grub update can not boot into Wubi install
i try to istall ubuntu 9.10 on my acer aspire with windows xp sp3
with wuby i selected an empty parition on my hd and i continued the
installation..
but when i restart the pc to complete the istallation and i selected ubuntu it
has appeared
Try (hd0,0) : NTFS5:
and then
101 - 200 of 205 matches
Mail list logo
