I experienced the same problem on my Acer AS3810T, on Maverick. However,
it seems to be fixed in os-prober version = 1.40 (see last message in
the thread for this bug on debian.org, [1]).
I installed the .deb for os-prober (version 1.42) from natty, found here[2],
and ran the commands:
$ sudo
Here's a debdiff for a SRU to Maverick.
** Attachment added: Debdiff for os-prober, Maverick
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/476625/+attachment/1791117/+files/debdiff-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
#43 - delance, that version of os-prober is from before the fix,
explaining why you get the problem. A bit sad that this issue wasn't
fixed before releasing the Maverick CD.
Jérôme De Greef, #40 Thanks for I think that hivex is a good way to
check for what entries are present in the BCBD, but do
@Tom: I never reinstall Vista on my Packard Bell. For this brand, it
seems, as I'm the second one with this issue (see post#41) that the way
Vista and recovery is installed differ from usual way. Maverick CD (and
current one from depot) version of os-prober is 1.39.
--
Grub2 affected when
I'd reopen this one as it's obviously not fixed.
If I have time, I'll try to implement a solution using hives and BCD... if I
have time... I'm actually not in charge of os-prober but it seems that no
one care about fixing this for once and for all. This bug is more than one
year old now...
I also have the same problem on a Packard Bell with Windows Vista,
having just installed Ubuntu 10.10
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Windows Vista (loader) (on /dev/sda1) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set
Hi :)
I have helped people with the work-around a couple of times in the last
couple of months. Since it affects a Windows system and Windows is
often quirky it had not occurred to me to post a bug-report. Surely
everyone is moving away from Windows anyway ?? (sry, irony)
I don't know which
I installed os-prober 1.40 and now I get:
dela...@delance-desktop:~$ sudo os-prober
[sudo] password for delance:
/dev/sda1:Windows Vista (loader):Windows:chain
/dev/sda2:Windows Vista (loader):Windows1:chain
So sda2 is not seen as a recovery partition, which is better.
But sda1 is not yet seen
Packard Bell -
TJ#4
I get from 20microsoft:
/dev/sda1 /media/_OEMBP fuseblk
/dev/sda1:Windows Vista (loader):Windows:chain
/dev/sda2 /windows fuseblk
/dev/sda2:Windows Recovery Environment (loader):Windows1:chain
File systen is named _OEMBP.
In boot/BCD file of my recovery partition,
2010/11/21 delance 476...@bugs.launchpad.net
Packard Bell -
TJ#4
I get from 20microsoft:
/dev/sda1 /media/_OEMBP fuseblk
/dev/sda1:Windows Vista (loader):Windows:chain
/dev/sda2 /windows fuseblk
/dev/sda2:Windows Recovery Environment (loader):Windows1:chain
Is this correct or
It is not correct. sda1 is a small recovery partition and sda2 Vista
partition.
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same as https://launchpad.net/~intuitivenipple (TJ).
dela...@delance-desktop:~$ sudo fdisk -l
Périphérique Amorce DébutFin Blocs Id Système
/dev/sda1 1156712586896 27 Inconnu
/dev/sda2 *1568 39238 302592307+ 7 HPFS/NTFS
Can you please use TJ method using hives (BCD) to see what it gives on your
rescue partition (/dev/sda1) ?
Thanx
2010/11/13 delance 476...@bugs.launchpad.net
Same as
https://launchpad.net/~intuitivenipplehttps://launchpad.net/%7Eintuitivenipple(TJ).
dela...@delance-desktop:~$ sudo fdisk -l
This bug was fixed in the package os-prober - 1.40
---
os-prober (1.40) unstable; urgency=low
[ Christian Perrier ]
* Fix Windows Vista and Windows Recovery Environment partitions
recognition. (Thanks, Bouke Bunnik)
Closes: #589676, LP: #476625
* Allow recognition of
Ah, sorry, comment #7 is on the other bug report linked to this bug
report in launchpad.
Here is a quick link...
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/476625/comments/7
And I can confirm that using the hive method is the only way that
reliably works for me.
The reason why is in
This is the MAIN problem... assumption #2
2. The last entry in the /Boot/BCD file is related to the partition being probed
This is a false assumption in the case of my Toshiba Satellite system
and for many others also.
-Daniel
On Fri, Nov 12, 2010 at 7:37 AM, Daniel Bair dan...@danielbair.com
I complately agree with you.
I've used the hive method to clearly identify my windows partitions.
I fact we should stop to hardcode the partition names in
/usr/lib/os-probes/mounted/20microsoft.
Instead we should use the hive method and use it's result to identify
windows partitions. It's not a
** Branch linked: lp:debian/sid/os-prober
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can confirm it's fixed... until Microsoft or Windows distributors call
their recovery partition another name.
It's a temporary fix.
BTW, it's not very fair to not cite me in the changelog as you've used part
(if not all) of my patch.
Jérôme
--
Grub2 affected when os-prober incorrectly
And not fixed for me! Unless the solution of comment #7 is implemented
os-prober will not identify Recovery and Vista partitions correctly.
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Windows Vista (loader) (on /dev/sda2) {
insmod ntfs
set root='(hd0,2)'
search
God, as I said it was only a temporary fix and we already face a case where
it doens't work.
What's the BCD of your recovery partition ?
And btw what's comment #7 ? I don't see any number identifying the comments
here.
I assume this is not easy to fix as we depend on the way recovery partition
Just applied Bouke's modification, and it worked perfectly, recognizing
a Recovery intead of mislabeling it Windows Vista.
This should indeed be integrated upstream.
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
This is not a Ubuntu specific bug. Debian sid/unstable has the exact same issue.
See : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589676 (patch included).
I think this should be fixed upstream.
** Bug watch added: Debian Bug tracker #589676
On my comment #23, what actually happened with the curren version of Grub OS
Prober is that it identifiied correctly the
Windows 7 partition, which is at sda2, but it does not see the Dell Utility
Partition at sda1.
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
I've just been hit by this bug when installing Ubuntu Lucid 10.04 from
the alternate ISO image (64 bits) in a Dell Lattitude E6410. It came
with three primary partitions. Dell Utilities in sda1, Windows 7
Recovery in sda2 and Windows 7 in sda3. I created an extended partition
and install Ubuntu
Brian Doe, thanks for your attempt at fixing this. I suffer from this
issue, and I do have a recovery partition (well, suffer: I had to tell
my wife not to boot Vista but the recovery partition instead). Your
modification solves the misidentification of the Windows Vista
partition, so in that
RIght, now that Brian Doe provided a fix for the Vista identification, I
decided to see if my believe about the recovery partition not being
matched and thus being detected as the default of Windows Vista was
correct. Following the insructions from comment #7, I installed hivax,
and checked the
See the attached patch, combining the changes of bdoe and my added match
for the recovery partition Windows Setup, applies to version in Ubuntu
Lucid/10.04 (maybe it is different from others because I have a Dutch
version of Vista; Acer TravelMate 6292).
** Patch added: patch to the
** Tags added: patch
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have a fix for the problem. This affects those with Windows Vista
partitions being mis-identified as Windows Recovery Environment. The
problem is that os-prober is using /usr/lib/os-
probes/mounted/20microsoft to read specific attributes of the identified
Windows drive. One of these attributes
I had installed one of the later beta releases of Ubuntu 10.04 (latest
version available in early April), and my Vista partition was identified
correctly. Then, just yesterday, I finally noticed Update Manager trying
to get my attention, so I updated. Now, my Vista partition is mis-
identified as
I see the misidentification problem on a Lenovo ThinkPad T61.
The Windows Recovery Partition is identified as Windows Vista, the
Windows Vista Partition as Windows Recovery Environment.
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
Ditto.
Dell Inspiron 1720
Dual Boot: Windows Vista | Ubuntu 10.04
Prior to updating to Lucid Lynx I was running Ubuntu Karmic Koala 9.10.
No problems. Dual boot worked great.
After upgrade to 10.04, sda1 is being listed as the Windows Recovery
partition. Should be Windows Vista. Windows
Dell Vostro 410
Dual Boot: Windows Vista Business (32bit) | Ubuntu 10.04 (64bit)
Vista on /dev/sda3 is identified by OS-prober as Windows recovery environment,
recovery partition is not identified at all
Ubuntu boots fine, Windows stops with blinking cursor in the upper left corner
right after
I have the same problem on my acer laptop. The vista partition has been
incorrectly identified as windows recovery environment although windows
does run ok. This problem has only occurred after upgrading from KK to
LL.
--
Grub2 affected when os-prober incorrectly identifies Windows and
** Changed in: os-prober (Ubuntu)
Milestone: ubuntu-10.04-beta-2 = None
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This may be fixed permanently for 10.10 Maverick. I've now got hivex
ready for Debian which should make its way automatically into the Ubuntu
archives. *If* that happens os-prober can use my probe_bcd script to
correctly identify the Windows partitions.
For 10.04 Lucid I'm not sure how it could
Seeing the exact same problem as sergio on a Dell Studio 17 with two
internal hard drives after the upgrade from 9.10 to Lucid. Vista, which
lives on sda1, is misidentified as Windows Recovery Environment and the
recovery partition isn't seen at all. Had me a little freaked out first
time I saw
Same problem here. On a Dell laptop, Windows Vista is detected as a
Windows recovery environment. The dell recovery partition is not seen
at all.
Please _rise_ priority. This thing is driving _crazy_ people who try
linux for the first time and get the impression that lucid has wiped
their
In my case (Amilo Pi3514), the Amilo Vista recovery partiotion is
detected as Windows Vista (loader) while the real Windows is
detected as Windows Recovery Environment (loader):
redfo...@valhalla:/boot/grub$ sudo update-grub2
Generating grub.cfg ...
Found linux image:
I have a Sony Vaio VGN-FZ19VN where dev/sda1 is my recovery partition
and dev/sda2 is the Windows Vista partition. With karmic both were
identified as Windows Vista (loader). The following is the output from
grub2 in lucid beta 2:
l...@lars-laptop:~$ sudo update-grub
[sudo] password for lars:
I have two Toshiba Satellite laptops and grub misidentifies the Recovery versus
Vista partitions.
I can confirm that the script from comment #7 above does work correctly for me.
BCD store: /tmp/sda3/BOOT/BCD
Windows Setup
BCD store: /tmp/sda2/Boot/BCD
Microsoft Windows Vista
--
Grub2 affected
** Attachment added: Script to determine default boot entry name in Windows
BCD store
http://launchpadlibrarian.net/42837456/probe_bcd
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
You received this bug
** Attachment added: gawk script helper for probe_bcd
http://launchpadlibrarian.net/42838499/get_node_name.gawk
--
Grub2 affected when os-prober incorrectly identifies Windows and Recovery
partitions
https://bugs.launchpad.net/bugs/476625
You received this bug notification because you are a
I've written a POSIX shell script that can reliably identify the name of
the current default* BCD boot menu option in any bootable Windows
partition that uses a Boot Configuration Data store.
It is based on the fact that a BCD store is a standard Windows registry
hive, and there is now a LGPL
45 matches
Mail list logo
