Package: cdrom Followup-For: Bug #583200 Dear Maintainer,
Using the Debian 7.0 AMD64 network install CDROM. Attempted to create a Debian Wheezy system on /dev/sdd of a system which already contains a Debian Squeeze installation on /dev/sda. Two other drives in the system. All are 3-Terabyte SATA drives which contain encrypted LVM2 partitions. No changes to Grub templates etc. from the defaults. Installation proceeded as expected on /dev/sdd right up to the point where it said it was installing grub onto the MBR of /dev/sda. I was too slow to reach the power switch before it had done it. :( I had hoped that (1) Unless otherwise directed, the MBR to be written will be the MBR of the drive on which the system is being installed. (2) If the MBR of any drive is to be overwritten, a backup of the original MBR would be made and would not overwrite any other MBR backup which might exist anywhere on the system. (3) If the MBR of any drive other than the install drive is to be overwritten, at least a prompt for confirmation will be issued. It took more than 24 hours to recover the trashed system. -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org