Grub2 won't boot Win7 on hybrid msdos/ldm disk

[Ronni]

I hope the summary is correct.
Due to factory settings, the setup on my secondary disk is a bit special, see
https://bugs.launchpad.net/ubuntu/quantal/+source/grub2/+bug/1061255 post #57 and #58

This is the edited grub-cfg that will boot into WIndows http://paste.ubuntu.com/1404094/

fdisk -lu output http://paste.ubuntu.com/1417526/

Windows is on /dev/sdb.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: grub-pc 2.00-7ubuntu11
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Tue Dec 11 08:21:41 2012
InstallationDate: Installed on 2012-12-08 (2 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

[Phillip Susi (psusi)]

What is the unmodified config and what happens when you use it?

[Ronni (ronni-jensen)]

This is the current unmodified grub.cfg, when I try to boot from that I get "A Disk read error ocurred. Press Ctrl+Alt+Delete to restart"
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-085AFE3C5AFE265A' {
 insmod ldm
 insmod ntfs
 set root='ldm/24e38dab-ec38-11e1-99c0-642737cbe3d6/Volume1'
 if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root --hint-bios=hd1 --hint-efi=hd1 --hint-baremetal=ahci1 --hint='ldm/24e38dab-ec38-11e1-99c0-642737cbe3d6/Volume1' 085AFE3C5AFE265A
 else
   search --no-floppy --fs-uuid --set=root 085AFE3C5AFE265A
 fi
 chainloader +1
}

[Phillip Susi (psusi)]

Can you press 'c' to go to the grub console, and run insmod ldm, insmod ntfs, ls -l?

[Ronni (ronni-jensen)]

Why yes, yes I can.

Crappy cellphonepic of the result: http://imgur.com/Z3u50.

[Phillip Susi (psusi)]

That looks good so far, can you try:

set root=ldm/24e38dab-ec38-11e1-99c0-642737cbe3d6/Volume1
ls /

[Ronni (ronni-jensen)]

ls / on Volume1 gave me a directory-list for what I guess is recovery, ls / on Volume2 lists c: on the Windows-partition.

[Phillip Susi (psusi)]

Hrm... can you try the remaining commands:

search --no-floppy --fs-uuid --set=root 085AFE3C5AFE265A
chainloader +1

[Ronni (ronni-jensen)]

I tried going through the list three times, just to be sure. All the commands are accepted and then, after chainloader, nothing happens.

I'll post another picture if you want.

[Phillip Susi (psusi)]

By nothing you mean it is waiting for another command? I think you have to issue a boot command then when doing it manually.

[Ronni (ronni-jensen)]

Ah, makes sense, I of course didn't try and and enter the commands that does boot.
But yes, after the chainloader-command, the console is just waiting for more input.

[Phillip Susi (psusi)]

Did you ever try again with the boot command?

[Ronni (ronni-jensen)]

Oh, right, yeah I did, same result, "Disk Read Error".

[Phillip Susi (psusi)]

Before issuing the boot command can you run:

set debug=all

You should get a lot of output, if you could take a picture of it that might help.

[Phillip Susi (psusi)]

Oh, and were you doing the set root command, or the search command? You might try the other one and see if things change.

[Ronni (ronni-jensen)]

Result of debug-output http://imgur.com/iL1Vp
If you need more debug-output let me know, I can probably make a video.

I've been trying both set root and search, separately and together, the result is the same; "disk read error".

[Phillip Susi (psusi)]

I don't see the disk read error there?

[Ronni (ronni-jensen)]

The screen is cleared after debug-output, then "disk read error" is printed
on the screen.

On Sun, Dec 23, 2012 at 11:13 PM, Phillip Susi <email address hidden> wrote:

> I don't see the disk read error there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1088796
>
> Title:
> Grub2 won't boot Win7 on hybrid msdos/ldm disk
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1088796/+subscriptions
>

--
USED CARS — LAND — WHISKEY — MANURE — NAILS
     FLY SWATTERS — RACING FORMS — BONGOS

                       ENTERPRISES, Un-Ltd.
                       R. R. Jensen, President

[Phillip Susi (psusi)]

Ahh, you have two drives... try adding a drivemap (hd1) (hd0) command before boot.

[Ronni (ronni-jensen)]

That unfortunately makes no difference.

[Phillip Susi (psusi)]

The problem seems to be in the Windows boot loader. I thought it didn't like being booted from a drive other than hd0, and so the drivemap should work around that. I'm not sure what else to try if that doesn't do it, other than reconfiguring your machine to boot from the Windows drive.

Actually, I seem to remember reading somewhere that Windows does not support booting from dynamic disks ( ldm ), but maybe that changed?

[Ronni (ronni-jensen)]

Well, your guess is as good as mine. At least it boots up if I edit grub.cfg to boot it as an MSDOS disk, so it's not problem, just a bother if grub updates the config.

Whether Windows will boot from a dynamic disk; this is the way the disk has been setup from factory and when the disk is changed to the primary disk it boots up fine as well.

[Phillip Susi (psusi)]

I forgot you said it worked with the other config. This is odd. If you run ls /, do you get the same results with the modified config as with the regular one?

[Phillip Susi (psusi)]

Also can you run ls -l at the grub console with both configs?

[Ronni (ronni-jensen)]

As requested,
console with "regular" boot: http://imgur.com/0PVDa
console with Grub2 boot: http://imgur.com/Bq4yD

And now it gets weird, because now, it boots when I enter the new commands in console and when I select a modified grub2-bootloader.

However, I still have to edit grub.cfg to remove the 'if'-statement, like this: http://paste.ubuntu.com/1465140/

[Ronni (ronni-jensen)]

Correction: If I turn off my laptop and turn it on again, then Grub will give "Disk Read Error" if I try Windows 7 Loader.

If I then go to a Grub-console, type in the commands to do a regular MSDOS-boot, then subsequent LDM-boots work.

[Phillip Susi (psusi)]

Wow, that is very strange. So you boot with the msdos partition, windows comes up, you reboot, then the ldm one works? Something is very strange with your windows boot loader.

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]