You are not logged in.

#1 2013-04-07 20:53:30

mask
Member
Registered: 2011-05-17
Posts: 16

"rERInd", duplicate windows entry

hello everyone,

I just installed a dual boot on my thinkpad t430s.
Everything work like a charm but the Widows entry is duplicated in rEFInd menu.
For information:
Windows 8 and Arch are installed on different disks (windows on a HDD and Arch on a SSD) both are GPT.
I had a problem with the rEFInd version available in the stable repo (freez during loading). I solved this using the "variant package" available on rEFInd website.
I found out that this problem should have been solved on version 0.6.6
Is the "variant package" outdated, is this a new bug or am I doing something wrong?

thx.

Last edited by mask (2013-04-08 22:13:06)

Offline

#2 2013-04-07 22:59:51

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

I'm not sure why you think the freezing problem should have been solved with rEFInd 0.6.6. Certainly no version of rEFInd has included an explicit bug fix for this problem, since as far as I can tell the ultimate cause is not with rEFInd. The "variant package" version of rEFInd to which you refer is a workaround that appears to work on many systems, but I'm not sure why it works -- at least not in detail. My suspicion is that the problem is in the EFI stub loader or in the way at least some Arch developers are compiling the binary kernel packages in the Arch repositories, but the bug clearly interacts with the EFI itself and with the programs that launch the kernel (rEFInd, gummiboot, the EFI shell, etc.).

As to your main question, my suspicion is that you have a duplicate copy of the Windows boot loader installed -- one on each disk. You may be able to verify this by checking the text that appears when you highlight an entry in rEFInd -- it should read "Boot Microsoft EFI boot from X", where X is a volume name or description. Those names or descriptions might be different if the entries are on different disks. If they're identical, then it could be you've got two identically-sized or identically-named ESPs, and if you give one or both of them unique filesystem names (using GParted, for example), you should see a difference.

If, OTOH, one of the icons has a name other than "Boot Microsoft EFI boot from X," then the name may provide a clue. For instance, if one reads "Boot EFI\Microsoft\bootmgfw.efi from X" and the other reads "Boot Microsoft EFI boot from X," then somebody or something has copied the bootmgfw.efi file from EFI/Microsoft/Boot to EFI/Microsoft.

In either case, once you've identified the duplicate boot loader file, you can do one of two things to rid yourself of the unwanted entry:

  • Edit the refind.conf file and use the dont_scan_dirs or dont_scan_volumes option to tell rEFInd to ignore one of the files. Which option you should use depends on where the duplicate file exists and what other files might exist in that location. You shouldn't use dont_scan_volumes if a Linux boot loader or kernel exists on that partition, for instance.

  • Delete the offending file, or at least rename it so that it no longer has a .efi extension.

Offline

#3 2013-04-08 02:26:34

mask
Member
Registered: 2011-05-17
Posts: 16

Re: "rERInd", duplicate windows entry

I thought the fix was:

rodsbooks.com/refind/revisions.html wrote:

The second new feature is that rEFInd now detects when the EFI/BOOT/bootx64.efi (or EFI/BOOT/bootia32.efi on 32-bit systems) boot loader is a duplicate of another boot loader, and automatically excludes it from the OS list

In the rEFInd menu I have 3 entries:
- Arch(I'm using the option "scan_all_linux_kernels" so, no .efi extension)
-Windows => Boot Microsoft EFI boot from 96 Mib FAT volume
-Windows(duplicate) => Boot EFI\Boot\bootx64.efi from 96 Mib FAT volume

Both menu entry for Windows are working.
I tried to use the option "dont_scan_dirs" wih different syntaxes:
ESP:/EFI/Boot,ESP:/EFI/boot,ESP:\EFI\Boot,ESP:\EFI\boot
but none of them worked. Worse, using the dont_scan_dirs ESP:/EFI/boot option makes my entry for Arch disapear while the two entries for Windows are still there...

edit :
when I said

mask wrote:

I found out that this problem should have been solved on version 0.6.6

I meant the duplicate entry problem, not the freezing problem, sorry for the confusion.

Last edited by mask (2013-04-08 02:30:11)

Offline

#4 2013-04-08 16:48:10

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

mask wrote:

I thought the fix was:

rodsbooks.com/refind/revisions.html wrote:

The second new feature is that rEFInd now detects when the EFI/BOOT/bootx64.efi (or EFI/BOOT/bootia32.efi on 32-bit systems) boot loader is a duplicate of another boot loader, and automatically excludes it from the OS list

In the rEFInd menu I have 3 entries:
- Arch(I'm using the option "scan_all_linux_kernels" so, no .efi extension)
-Windows => Boot Microsoft EFI boot from 96 Mib FAT volume
-Windows(duplicate) => Boot EFI\Boot\bootx64.efi from 96 Mib FAT volume

I've just checked, and that seems to be a new bug. (It wasn't technically a bug before, but since it's now supposed to be fixed, it now is.) I'll look into it....

Offline

#5 2013-04-08 16:57:09

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: "rERInd", duplicate windows entry

@ mask, please edit the thread title to "rEFInd", I was confused there for a second.

Offline

#6 2013-04-08 17:48:45

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

Upon review, rEFInd 0.6.8 is doing what I'd expect on my own test system; however, I did find another case where a duplicate could creep in and fixed it. A test version is here:

http://www.rodsbooks.com/refind-bin-0.6.8.1.zip

If that does not fix your problem, please check to see if the two files are identical with "diff". For instance, if your ESP is mounted at /boot/efi:

diff /boot/efi/EFI/BOOT/bootx64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi

If "diff" returns with no messages, that means the files are identical and there may be a bug in rEFInd; but if "diff" reports there are differences, then the files are not identical and there's no rEFInd bug. In the latter case, to remove the duplicate you'll need to delete the offending file or use "dont_scan_files" or "dont_scan_dirs".

Another thought: Users sometimes report bugs because they think they're running newer versions than they are. Please check your rEFInd version number in the information screen. If it's old, make sure you upgrade the rEFInd binary that you're actually running (from the ESP, normally).

One more comment: At least one EFI (Gigabyte's "Hybrid EFI") has a case-sensitivity bug in its built-in libraries, upon which rEFInd relies for certain operations. On such a firmware, it's conceivable that rEFInd's check for a duplicate fallback boot loader will fail if the fallback filename varies in case from "EFI/BOOT/bootx64.efi". Thus, you could try changing the case of any directories or the filename if they aren't precisely this. (To change case only, you'll need to use "mv" twice, once to change the name completely and again to change it to the desired case.)

Offline

#7 2013-04-08 21:59:13

mask
Member
Registered: 2011-05-17
Posts: 16

Re: "rERInd", duplicate windows entry

I just tried the test version you sent and it solved the duplicate entry issue but the freezing problem reappeared.
The entry for Windows works(I even have a nice logo now) but the Arch entry freeze!

Offline

#8 2013-04-09 16:13:27

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

Offline

#9 2013-04-09 17:06:12

mask
Member
Registered: 2011-05-17
Posts: 16

Re: "rERInd", duplicate windows entry

I replaced "/boot/efi/EFI/refind/refind_x64.efi" and "/usr/lib/refind/refind_x64.efi" by the latest version you provided.
Now, the freezing problem is gone but the duplicate Windows entry issue is back!

By the way, /EFI/BOOT/bootx64.efi and /EFI/Microsoft/Boot/bootmgfw.efi are exactly the same.

Offline

#10 2013-04-09 18:55:54

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

Then that sounds like there's a bug in GNU-EFI that's manifesting in the rEFInd code. I'll look into it....

Offline

#11 2013-04-09 19:11:22

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

Mask,

I couldn't replicate the problem locally. I've got a debug version for you to try:

http://www.rodsbooks.com/refind_x64.efi

This one pauses during each comparison and displays some information, like this:

Checking for duplicate of 'EFI\BOOT\bootx64.efi' with 'EFI\Microsoft\Boot\bootmgfw.efi'
Doing full check
Files are identical

* Hit any key to continue *

Please post what this version displays on the check for whatever boot loader is being duplicated (with EFI\Microsoft\Boot\bootmgfw.efi, presumably). Feel free to take a screen shot with a digital camera if you like; or copy it manually but precisely!

Offline

#12 2013-04-10 20:07:09

mask
Member
Registered: 2011-05-17
Posts: 16

Re: "rERInd", duplicate windows entry

Here is a picture of my screen during boot. Hope it can help.

242sgzs.jpg

Offline

#13 2013-04-10 22:29:20

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: "rERInd", duplicate windows entry

That looks like filesystem damage, although why it should show up with the GNU-EFI build and not with the TianoCore build puzzles me. What size is your ESP, and what filesystem do you use on it (FAT32 or FAT16)? Some users have reported problems with flaky FAT32 behavior on partitions that are under 512MiB in size, so if your ESP is smaller than that, I recommend either increasing its size (if that's practical) or switching to FAT16 on the ESP (despite the fact that the EFI spec calls for FAT32 on the ESP).

Offline

#14 2013-04-10 23:22:52

mask
Member
Registered: 2011-05-17
Posts: 16

Re: "rERInd", duplicate windows entry

I have two esp , one on each disk, they are both Fat32, the one containing rEFInd is 1024Mib and the one created by the Windows installer is 100Mib...
I kept one esp on each disk so I can boot on a disk without the one containing rEFInd.

Offline

Board footer

Powered by FluxBB