Testing Netinst AMD64 CD fails to create MD devices for RAID1
There seems to be a bug with software RAID1 in the 06/21/2011 version
of the Testing Netinst AMD64 CD image. Separate partitions can be linked to create the md devices, but then one or the other of the two md devices fails after the initial sync is attempted. So the failure is occurring before the resulting raid partitions are used. They fail without being formated, labeled, etc. It is not possible to proceed with the rest of the Debian installation. I uploaded installation log copies with the following bug reports on http://bugs.debian.org: Bug#631331 installation-report Bug#631338 installation-report The hardware composition of the failing target machine is as follows: Motherboard ASUS P6X58D Premium P6X58D Premium Socket 1366 X58 ATX Intel Motherboard Intel Core i7-950 3.06 GHz Corsair Dominator 6GB DDR3-1600 Western Digital Black Caviar ATA WDC WD1002FAEX-0 Anyone have a good work around? Thanks, Marc -- -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 874o3ersqw.fsf@cadence.glidepath.invalid">http://lists.debian.org/874o3ersqw.fsf@cadence.glidepath.invalid |
Testing Netinst AMD64 CD fails to create MD devices for RAID1
On Sat, 25 Jun 2011 08:38:15 -0400, Marc D Ronell wrote:
> There seems to be a bug with software RAID1 in the 06/21/2011 version > of the Testing Netinst AMD64 CD image. Separate partitions can be > linked to create the md devices, but then one or the other of the two > md devices fails after the initial sync is attempted. So the failure > is occurring before the resulting raid partitions are used. They fail > without being formated, labeled, etc. It is not possible to proceed > with the rest of the Debian installation. (...) > Anyone have a good work around? How about making the raid before installing Debian? Or maybe trying with another netinst image? This one is from 2011-06-25: http://cdimage.debian.org/cdimage/daily-builds/wheezy_d-i/current/amd64/iso-cd/ And this one uses sid's installer: http://cdimage.debian.org/cdimage/daily-builds/daily.new/current/amd64/iso-cd/ Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: pan.2011.06.25.15.17.32@gmail.com">http://lists.debian.org/pan.2011.06.25.15.17.32@gmail.com |
Testing Netinst AMD64 CD fails to create MD devices for RAID1
>>>>> "Camaleón" == Camaleón <noelamac@gmail.com> writes:
Camaleón> On Sat, 25 Jun 2011 08:38:15 -0400, Marc D Ronell wrote: >> There seems to be a bug with software RAID1 in the 06/21/2011 >> version of the Testing Netinst AMD64 CD image. Separate >> partitions can be linked to create the md devices, but then one >> or the other of the two md devices fails after the initial sync >> is attempted. So the failure is occurring before the resulting >> raid partitions are used. They fail without being formated, >> labeled, etc. It is not possible to proceed with the rest of >> the Debian installation. Camaleón> (...) >> Anyone have a good work around? Camaleón> How about making the raid before installing Debian? Camaleón> Or maybe trying with another netinst image? This one is Camaleón> from 2011-06-25: Camaleón> http://cdimage.debian.org/cdimage/daily-builds/wheezy_d-i/current/amd64/iso-cd/ Camaleón> And this one uses sid's installer: Camaleón> http://cdimage.debian.org/cdimage/daily-builds/daily.new/current/amd64/iso-cd/ Camaleon, Thanks for the pointer to the image with the sid installer above. That basically worked. I found a couple of issues, I think, which might be useful to change on the installer. One is that the md devices took a long time to sync as each was DELAYED. Installing an internal bitmap on each device sped up the sync process and allowed the devices to be usable: # mdadm -G /dev/md1 --bitmap=internal After each md device synced, I installed the internal bitmap and that might have helped to stabilize the devices. From there I was able to format the md devices with xfs. A second issue is that the /etc/lilo.conf file did not specify the initrd image which was put in the /boot directory by the Debian installer. Once that configuration line was added to lilo.conf, the boot loader installed and worked, the only other issue was to be sure that the md device selected for the lilo install had to be version 0.90 as opposed to version 1.2. Hope that helps someone and thanks for the suggestion of using the image with the sid installer. Marc -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 87boxgxh9h.fsf@cadence.glidepath.invalid">http://lists.debian.org/87boxgxh9h.fsf@cadence.glidepath.invalid |
| All times are GMT. The time now is 03:48 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.