linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Info@quantum-sci.net
To: linux-raid@vger.kernel.org
Subject: Re: Help
Date: Sat, 22 Aug 2009 11:12:35 -0700	[thread overview]
Message-ID: <200908221112.35952.Info@quantum-sci.net> (raw)
In-Reply-To: <4A902134.2020009@anonymous.org.uk>

On Saturday 22 August 2009 09:47:48 John Robinson wrote:
> You should have mkinitrd (that's what it is on Fedora/RHEL/CentOS) or 
> something similar with which you can build initramfs images for any kernel.

OK once I changed the version to 0.90 it stopped just at the kernel banner on boot and hung.  I was about to give up on RAID when your message came through, and I created the initrd.img file.  I always compile my own kernels and don't depend on an initrd, but it now seems to be necessary.  So in Debian:
# update-initramfs -o /boot/initrd.img-2.6.30-5
... reboot, and voila it did what it was supposed to, for a change.  I'm now resyncing my 2TB drives, which will take a good while.

 
> > What partition type should I use rather than raid autodetect?  Or should I revert to 0.90 metadata?
> 
> Probably type DA, Non-FS data, though type FD will be fine even if 
> they're not auto-detected.

It simply found 'bad magick' with FD, so that doesn't work with the newer versions.  I tried to use both newer versions, but it's not possible.  You sound not quite sure of the partition type, so I'll stick with FD and 0.90.  Thanks though John.

Goswin says, "For scanning your videos raid10 with far layout is probably best with
a large read ahead."  I have the RAID10 blocksize set to 1024 for the video partition, but any idea how to set readahead?





  reply	other threads:[~2009-08-22 18:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 13:27 RAID10 Layouts Info
2009-08-21 16:43 ` Goswin von Brederlow
2009-08-21 18:02   ` Info
2009-08-21 19:20     ` Help Info
2009-08-21 19:38       ` Help John Robinson
2009-08-21 20:51         ` Help Info
2009-08-22  6:14       ` Help Info
2009-08-22  9:34         ` Help NeilBrown
2009-08-22 12:56           ` Help Info
2009-08-22 16:47             ` Help John Robinson
2009-08-22 18:12               ` Info [this message]
2009-08-22 20:45                 ` Help Info
2009-08-22 20:59                   ` Help Guy Watkins
     [not found]                     ` <200908230631.46865.Info@quantum-sci.net>
2009-08-24 23:08                       ` Help Info
2009-08-24 23:38                         ` Help NeilBrown
2009-08-25 13:18                           ` Help Info
2009-08-27 12:47                             ` Help Info
2009-08-23 20:28                 ` Help John Robinson
2009-08-22  6:31     ` RAID10 Layouts Goswin von Brederlow
2009-08-21 20:42   ` Keld Jørn Simonsen
2009-08-21 21:04     ` Info
2009-08-21 21:57     ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2006-08-23 19:21 help Archie Cotton
2006-02-04  2:21 Help Oren Ben-Menachem
2004-10-20  5:05 help Srinivasa S
2004-10-20  5:50 ` help Guy
2004-10-21  1:47 ` help Jon Lewis
2004-04-01 16:56 Help Jason C. Leach
2004-04-01 17:00 ` Help Måns Rullgård
2004-02-01 13:13 help Rami Addady

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=200908221112.35952.Info@quantum-sci.net \
    --to=info@quantum-sci.net \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).