Hi,
On 05/07/2015 02:24 PM, Fred Smith wrote:
On Thu, May 07, 2015 at 01:52:58PM -0400, Tom Horsley wrote:
On Thu, 07 May 2015 13:42:01 -0400
Alex Regan wrote:
Thanks for any ideas.
I also had big problems when trying to boot after adding a
new raid (which shouldn't have been involved in the boot
process at all). I never figured out exactly what the
problem was for sure, but at some point I booted the
system on a live CD, chrooted into the actual root,
and did a yum update which installed (among other things)
a new kernel, and I was able to boot OK after that.
Either the initramfs was missing a module it needed
to talk to the raid, or maybe the grub.cfg was missing
a load of a module it needed. Not sure which, but the
installing of a new kernel fixed whatever it was.
new kernel would enforce the building of a new initrd,
wouldn't it?
perhaps that's all the OP needs to do to solve his problem...
Yes, that's certainly a possibility, but nothing new was introduced.
RAID1 was already there because the root is RAID1.
The server is back in the colo, so I wonder if I could reproduce it
locally here before making the drive (no pun intended, lol).
Thanks,
Alex
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
