From: John Robinson <john.robinson@anonymous.org.uk>
To: Arun Khan <knura9@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
Date: Sun, 07 Oct 2012 10:06:42 +0100 [thread overview]
Message-ID: <50714622.4020903@anonymous.org.uk> (raw)
In-Reply-To: <CAHhM8gAOfUXwPet1EY3gBa_9--K2opvEYFmOxBh9KJnHSCr_Hw@mail.gmail.com>
On 07/10/2012 07:24, Arun Khan wrote:
> Hi John,
>
> I posted the requested info to the list.
>
> I was wondering if you had a chance to go through it.
>
> Either way do let me know. I am anxious to get this solved if possible.
Sorry, I was distracted by $realjob...
The only thing that occurs to me is:
>> # cat /boot/grub/grub.conf
>> # grub.conf generated by anaconda
>> #
>> # Note that you do not have to rerun grub after making changes to this file
>> # NOTICE: You do not have a /boot partition. This means that
>> # all kernel and initrd paths are relative to /, eg.
>> # root (hd0,0)
>> # kernel /boot/vmlinuz-version ro root=/dev/sda1
>> # initrd /boot/initrd-[generic-]version.img
>> #boot=/dev/sda
this. Uncomment it, and change to boot=/dev/md_d0p1, and re-run
`grub-install`.
Also, just to be sure, if you haven't installed a new kernel since
migrating to RAID, update your initrd - something like `mkinitrd -f
/boot/initramfs-2.6.32-220.el6.x86_64.img 2.6.32-220.el6`.
I can't think of anything else.
Cheers,
John.
next prev parent reply other threads:[~2012-10-07 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 11:17 CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present Arun Khan
2012-10-03 14:23 ` John Robinson
2012-10-03 16:48 ` Arun Khan
[not found] ` <CAHhM8gAOfUXwPet1EY3gBa_9--K2opvEYFmOxBh9KJnHSCr_Hw@mail.gmail.com>
2012-10-07 9:06 ` John Robinson [this message]
2012-10-07 16:13 ` Arun Khan
2012-10-09 15:24 ` Arun Khan
2012-10-15 10:40 ` Arun Khan
2012-10-03 17:45 ` Keith Keller
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=50714622.4020903@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=knura9@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.