linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Moshe Yudkowsky <moshe@pobox.com>,
	maximilian attems <max@stro.at>,
	linux raid <linux-raid@vger.kernel.org>
Subject: Re: using update-initramfs: how to get new mdadm.conf into the /boot? Or is it XFS?
Date: Thu, 07 Feb 2008 16:48:16 -0500	[thread overview]
Message-ID: <47AB7CA0.9010407@tmr.com> (raw)
In-Reply-To: <47AB7714.50608@tmr.com>

Bill Davidsen wrote:
> Moshe Yudkowsky wrote:
>> maximilian attems wrote:
>>
>>> error 15 is an *grub* error.
>>>
>>> grub is known for it's dislike of xfs, so with this whole setup use 
>>> ext3
>>> rerun grub-install and you should be fine.
>>
>> I should mention that something *did* change. When attempting to use 
>> XFS, grub would give me a note about "18 partitions used" (I forget 
>> the exact language). This was different than I'd remembered; when I 
>> switched back to using reiserfs, grub reports using 19 partitions.
>>
>> So there's something definitely interesting about XFS and booting.
>>
>> As an additional note, if I use the grub boot-time commands to edit 
>> root to read, e.g., root=/dev/sda2 or root=/dev/sdb2, I get the same 
>> Error 15 error message.
>>
>> It may be that grub is complaining about grub and resiserfs, but I 
>> suspect that it has a true complain about the file system and what's 
>> on the partitions.
>>
> I think you have two choices, convert /boot to ext2 and be sure you 
> are going down the best-tested code path, or fight and debug, read 
> code, learn grub source, play with the init parts of the boot 
> sequence, and then convert /boot to ext2 anyway. No matter how 
> "better" something else might be, /boot has nothing I use except at 
> boot, I don't need features or performance, I just want it to work.
>
> Unless you are so frustrated you have entered "I am going to make this 
> *work* if it takes forever" mode, I would try the easy solution first. 
> Just my take on it.
>
Or you can get lucky and someone will have seen this before and hand you 
a solution...  ;-)

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  reply	other threads:[~2008-02-07 21:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 20:59 using update-initramfs: how to get new mdadm.conf into the /boot? Or is it XFS? Moshe Yudkowsky
2008-02-04 21:08 ` Robin Hill
2008-02-04 21:09 ` maximilian attems
2008-02-04 21:53   ` Moshe Yudkowsky
2008-02-07 21:24     ` Bill Davidsen
2008-02-07 21:48       ` Bill Davidsen [this message]
2008-02-04 22:25 ` Robin Hill
2008-02-04 22:59   ` Moshe Yudkowsky
2008-02-05  1:23     ` Moshe Yudkowsky

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=47AB7CA0.9010407@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=max@stro.at \
    --cc=moshe@pobox.com \
    /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).