Package: fai-client Version: 3.3.2 First, I want to clarify that this bug is NOT directly fault of fai, it is again due to other key packages and changes in fundamental behavior that drive me NUTS when it is changed with so little consideration, but it seems you may still wish to change things on your end to stay up with the curve.
mdadm 3.1.1(-1?) changes the DEFAULT metadata flag from the prior 0.90, to 1.x; which effectively translates to 1.1 as the default/stable 1.x metadata format. This chokes up ALL attempts to use these raid devices as either boot or root in my testing at least. All of this behavior manifests itself when building a standard sid system using fai and the current tree, and I fear it will propagate down sooner or later, at least to squeeze if it's not already there too. Further evidence of this issue and 'reasons' as to why it's not fixed can be found in these bug reports: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569107 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492897 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554500 Long story short, since you control the mdadm calls in your fai build scripts, if you add the option -e 0.90 (or long tag --metadata=0.90) To the create/partition script when creating the mdadm raid arrays, specifically for boot/root partitions, I think we all win and you beat this for the long-term until mdadm/bootloader people get their crap straight and take the full user base into consideration. Right now, netinst is broken using raid1 and I'm having to manually destroy and re-create the partitions to boot any new software raid system setups.... grrrr. If you care about my stress levels please be sure to modify setup-storage as well as the old standard as I use setup-storage. Not sure if the old method even supports software raid, I forget =) Thanks, you guys maintain a great piece of software doing an amazing thing that linux enjoys making very difficult! - jmd __________ Information from ESET NOD32 Antivirus, version of virus signature database 4871 (20100216) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9fd4262651d33f43b846af30e876e18a018e0...@matrixdc01.ad.matrix.msu.edu
