From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KROtz-0005ah-9z for mharc-grub-devel@gnu.org; Fri, 08 Aug 2008 06:08:55 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KROtt-0005ZW-QS for grub-devel@gnu.org; Fri, 08 Aug 2008 06:08:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KROtp-0005YB-03 for grub-devel@gnu.org; Fri, 08 Aug 2008 06:08:46 -0400 Received: from [199.232.76.173] (port=55260 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KROto-0005Xv-Cg for grub-devel@gnu.org; Fri, 08 Aug 2008 06:08:44 -0400 Received: from moutng.kundenserver.de ([212.227.126.171]:64548) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KROto-0005Tw-IV for grub-devel@gnu.org; Fri, 08 Aug 2008 06:08:44 -0400 Received: from [85.180.10.8] (e180010008.adsl.alicedsl.de [85.180.10.8]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1KROtm3ioH-0003Nu; Fri, 08 Aug 2008 12:08:43 +0200 From: Felix Zielcke To: The development of GRUB 2 In-Reply-To: <87sktfbzlu.fsf@xs4all.nl> References: <87myjoqtg3.fsf@xs4all.nl> <1218183250.4059.6.camel@fz.local> <87wsirc1d1.fsf@xs4all.nl> <1218187595.4059.33.camel@fz.local> <1218188069.4059.37.camel@fz.local> <87sktfbzlu.fsf@xs4all.nl> Content-Type: text/plain Date: Fri, 08 Aug 2008 12:08:42 +0200 Message-Id: <1218190122.4001.7.camel@fz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+6xm5AZslUPsxm66NyESCdg5rIJ4VYv2i69mc AG7V/5HKRMFbak/SFWIURvWkkldmllwZzCvz+YSXZgaSeLfWQd b/5mcDyWhGciFyIav32lqiVz9565PU9 X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) Subject: Re: ATA update X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2008 10:08:50 -0000 Am Freitag, den 08.08.2008, 11:55 +0200 schrieb Marco Gerards: > > Can't raid.mod be used for this, somehow? I had this talk already with Bean on IRC. At least the Nvidia nForce chipsets RAIDs have stored their 512 byte superblock in (end of disks) - 1024 bytes. The last 512 Bytes of both disks just contain zeroes. dmraid searches all disks for these superblocks it supports. So it is possible to implement this. Althoguh i don't know if raid.mod should be renamed to mdraid.mod and there should be a new dmraid.mod But that probable confuses people The raid.mod needs an overhaul anyway if the super 1.x format should be implemented, because the 1.x ones store there superblock at different positions of the disks not always at the same position where the current default 0.90 stores it.