From: "Alok K. Dhir" <alok@dhir.net>
To: "'Jakob Østergaard'" <jakob@unthought.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Autostart RAID 1+0 (root)
Date: Tue, 22 Jan 2002 13:07:32 -0500 [thread overview]
Message-ID: <003801c1a36f$a9a27c20$9865fea9@pcsn630778> (raw)
In-Reply-To: <20020122184600.C11697@unthought.net>
> > >
> > > Does the kernel support autostarting nested RAID partitions?
> > >
>
> Yes it does. If you have persistent superblocks on all arrays, they
> *should* autostart.
>
> If you boot from the 4G disk, does the array start properly ?
> Does it start properly even if you remove your /etc/raidtab ?
>
> Please check that you have the correct RAID levels either
> compiled into your kernel, or on an initrd.
1. I have persistent superblocks on all arrays.
2. Booting from the 4G does allow the arrays to start properly.
3. The first two arrays (md0 and md1, the mirrors) start properly
without raidtab. The third, the stripe between md0 and md1, does not.
4. All raid levels are compiled as modules, along with reiserfs, and my
scsi card driver in an initrd. I also tried compiling a monolithic
kernel with all of these without success.
I did, in fact, get it working. The only way I was able to do boot with
my nested array autostarted and mounted as root was to create an initrd
with a statically compiled raidstart and a copy of my raidtab in the
initrd's etc dir. I then issue "raidstart mdx" commands for each of the
arrays in linuxrc. I actually just modified the mkinitrd genereated
initrd image.
I can only conclude that autostarting nested arrays either doesn't work,
or is broken in RH-2.4.9-13. I have not tried a more recent kernel with
this machine.
Thanks
Al
next prev parent reply other threads:[~2002-01-22 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 16:40 Alok K. Dhir
2002-01-19 0:11 ` Tim Moore
2002-01-22 17:15 ` Bill Davidsen
2002-01-22 17:46 ` Jakob Østergaard
2002-01-22 18:07 ` Alok K. Dhir [this message]
2002-01-22 20:12 ` Bill Davidsen
2002-01-22 21:52 ` Jakob Østergaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003801c1a36f$a9a27c20$9865fea9@pcsn630778' \
--to=alok@dhir.net \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®