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

Bug#645210: marked as done (debian-installer: grub2 setup for a new drive misses a Windows boot choice from the original drive)

Your message dated Mon, 2 Sep 2013 15:53:07 +0200
with message-id <201309021553.23982.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #645210,
regarding debian-installer: grub2 setup for a new drive misses a Windows boot choice from the original drive
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
645210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645210
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Version: i386 netinst as of October 5, 2011
Severity: important
Tags: d-i

Dear Maintainer,

   * What led up to the situation?

   I decided to install Debian on a new disk drive and preserve the Windows
installation on the original drive.

   I downloaded the latest i386 netinst ISO image of Debian Installer, burned
it on a DVD and booted off it.

   * What exactly did you do (or not do) that was effective (or ineffective)?

   I chose the new drive for simple partitioning.  I chose to install Grub2 in
MBR of the original drive.

   * What was the outcome of this action?

   I did not see Windows as a boot option.  (This took a worse turn when the
udev in the initial RAM disk image loaded a kernel module "radeon" for my video
card ATI Radeon HD 3600, apparently in an attempt to provide a frame buffer for
the text mode, and the video card showed garbage.  It took a while to add an
option "blacklist=radeon" to the kernel command line at boot time and add a
line "blacklist radeon" to a file in /etc/modprobe.d).

   * What outcome did you expect instead?

   I expected to see a boot option to start from a partition in the original
disk drive.


Here is how I worked around the issue.

   I booted off the netinst DVD into a rescue mode.  Ran update-grub and it did
not show the Windows partition of the original drive.  Inspected the output of
os-prober.  I believe it did not show Windows either.  I then ran fdisk -l and
I think I saw my original disk drive with its Windows partition.  After
inspecting os-prober I figured it depended on the list of mounted partitions.
I added the Windows partition to /etc/fstab,

        /dev/sda1       /c      ntfs    auto    0       0

   Unfortunately, "mount /c" failed because the target root partition where I
chrooted did not have modules of the rescue kernel.  I cannot remember how I
succeeded in mounting the partition before re-running update-grub.  Perhaps, I
returned or rebooted to the dialogs of the rescue mode of Debian Installer and
chose to re-configure Grub2 in the dialogs.

  I could see my Windows partition of the original drive in the bootloader's
list at boot time.  I could successfully start Windows.

Here is my opinion on a possible root cause.

  It seems that Debian Installer does not attempt to mount partitions on drives
other than the one selected for partitioning.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
reassign 619236 debian-installer
severity 619236 normal
reassign 705484 debian-installer
thanks

Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: