[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#800639: os-prober: corrupts windows 7 loader/header

Hi Shirish,

Apologies for the delayed follow-up, things have been hectic
here... :-/

On Sat, Oct 03, 2015 at 08:26:47AM +0530, shirish शिरीष wrote:
>in-line :-
>On 10/3/15, Steve McIntyre <steve@einval.com> wrote:
>> On Fri, Oct 02, 2015 at 05:54:20AM +0530, shirish शिरीष wrote:
>>>Package: os-prober
>>>Version: 1.67
>>>Severity: important
>> Hi Shirish,
>Hi Steve,
>> Could you explain in a little more detail what you've seen please?
>> What exactly do you mean when you say that it's corrupting the Windows
>> 7 loader? What's the setup you're using on your machines (hardware,
>> disk layout etc.)?
>Thank you for taking time to respond to this bug.
>What do I mean by it's corrupting the Windows 7 loader is that it
>doesn't boot into MS-Windows. I had installed MS-Windows after
>installing Debian (I know that is the wrong way to do it).
>Of course, once MS-Windows comes in, it hogs the boot-loader and grub
>is nowhere to be found
>So then I used a live usb using GRML as a rescue option.
>I used lsblk to see how all the partitions were.
>Figured out that /dev/sda2 is the one which has the GNU/Linux
>partition (I had mapped it before but still was good to know it still
>was showing the same.)
>Then mounted /dev/sda2 to a mount point
># mount /dev/sda2 /mnt
>and then installed grub to the MBR
>#grub-install --root-directory= /mnt /dev/sda
>got the familiar boot screen with the correct version of grub showing
>on the grub screen but no MS-Windows 7
>Then installed os-prober . While it did find Windows 7 and put the
>menu entry, trying to use it is worthless, I get some corrupting image
>and then it fails to find some files.
>$ df -h
>Filesystem      Size  Used Avail Use% Mounted on
>udev             10M     0   10M   0% /dev
>tmpfs           1.6G  9.4M  1.5G   1% /run
>/dev/sda2        92G   18G   70G  20% /
>tmpfs           3.8G  152K  3.8G   1% /dev/shm
>tmpfs           5.0M  4.0K  5.0M   1% /run/lock
>tmpfs           3.8G     0  3.8G   0% /sys/fs/cgroup
>/dev/sda3       110G   89G   17G  85% /home
>tmpfs           769M  4.0K  769M   1% /run/user/119
>tmpfs           769M   32K  769M   1% /run/user/1000
>/dev/sda4       260G   38G  222G  15% /media/shirish/alphanumeric-label
>This is on a Thinkpad T-440, 500 GB , 8 GB RAM

OK, that's useful information. I've got a sneaky suspicion on that
T440 machine that it may be expecting to boot via UEFI, and you've now
installed a Debian system that's booting in BIOS mode. If the system's
firmware (aka BIOS) is configured to look for BIOS boot first, that
would explain why it's no longer seeing the Windows install. What
happens if you go into the firmware setup? Can you change the boot
options to try UEFI first, or UEFI only?

Steve McIntyre, Cambridge, UK.                                steve@einval.com
Who needs computer imagery when you've got Brian Blessed?

Reply to: