From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Timothy D. Lenz" Subject: Re: Converting system to raid Date: Fri, 10 Apr 2009 12:43:01 -0700 Message-ID: <008a01c9ba14$955074c0$0a00a8c0@vorg> References: <003801c9b96d$21a0f420$0a00a8c0@vorg> <49DF0D06.8030705@musmo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Sender: linux-raid-owner@vger.kernel.org To: linux-raid@vger.kernel.org List-Id: linux-raid.ids Is that /etc/mdadm/mdadm.conf or /mnt/md0/etc/mdadm/mdadm.conf Both are the same in his case, but of chroot moves the root point to the array, shouldn't it look at that conf? ----- Original Message ----- From: "CoolCold" To: Cc: "Timothy D. Lenz" ; Sent: Friday, April 10, 2009 2:55 AM Subject: Re: Converting system to raid Yes, he should provide correct /etc/mdadm/mdadm.conf and update-initramfs -u on md boot, smth like chroot /mnt/md0 update-initramfs -u On Fri, Apr 10, 2009 at 1:10 PM, KwangErn Liew wrote: > > Timothy D. Lenz wrote: >> >> Ended with warning: unable to open an initial console. I was able to >> scroll back and didn't really see any errors. Don't know if I >> missed a change to some config file or something else that should be built >> into the kernel. I have gone over a lot of "guides" and >> don't see what is missing. > > FYI, I've never been successful in booting RAID without initrd even though > all necessary modules are built-in. I guess mdadm.conf requires initrd to > kick start? > > > KwangErn > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- -- Best regards, [COOLCOLD-RIPN]