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

Bug#567590: marked as done (Strange bootable flag behavior with gpt disk label; RAID fails)

Your message dated Tue, 2 Feb 2010 10:19:31 +0100
with message-id <201002021019.31643.elendil@planet.nl>
and subject line Bug#567590: Strange bootable flag behavior with gpt disk label; RAID fails
has caused the Debian Bug report #567590,
regarding Strange bootable flag behavior with gpt disk label; RAID fails
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.)


-- 
567590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567590
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Severity: normal

I have a system containing two 2TB SATA drives which I have configured into a RAID1 and am using through LVM.  When using the Debian 5.03 amd64 installer, I was unable to use the partitioner provided in the menus to install.

When the partitioner started, I created new partition tables on the otherwise empty drives.  Because the drives are so large (2TB each), the installer wisely suggested that I use GPT rather than the traditional MBR partition table.  I created a new GPT on each drive with a single partition (named "RAID1-0" and "RAID1-1" respectively).

I then chose to configure software RAID; this is the point at which things broke down.  I received an error message indicating that there were no Linux RAID/Autodetect partitions available and that I should format one of my drives to create one.  It is my suspicion that the check to ensure that RAID partitions exist is assuming an MBR-style partition table.

I ran an mdadm --create command from the secondary terminal and restarted the partitioner.  When it rescanned the disks and discovered my RAID1 already in place, I was able to set up LVM without difficulty.

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Version: 64lenny1

Note that the fixed version will only become available at the next stable 
point release.

--- End Message ---
Reply to: