Sorry if I sounded a little aggressive here... it was three days of frustration and then someone pointing me at promise disk controllers and I was going way way way down the wrong route.
Anyway, I think most of what you have said will help... but... Samuel Flory wrote:
Bill Dossett wrote:
snip.
If I can't figure out how to get the module loaded ... correctly... viaIf I build my own kernel, then I will continue to have problems every time I run up2date and I'll have to constantly build new kernels and while I don't mind building a kernel, I used to do it all the time, I am trying to make things easier to maintain around here.. not harder.
Why do you need to build a custom kernel. Red Hat always compiles the raid driver as a module. If you install a kernel it should create an initrd for you. (At least it has for me for years.) Also if you just install a kernel instead of upgrading you should still have your old config.
initrd, which I have tried numerous ways so far and though I see it load, I still get the dreaded failure during pivotroot and the system
won't boot.
Basically, I was hoping to write a howto, that would take into account
grub, bootable softare raid, modules and converting from non-raid to
raid without having to reload.
I've worked on this for most of last week and pretty much came up
against the wall that I am apparently not loading up my initrd the
same way that redhat does... so I would really like to know how that
is done... hopefully, I can write some documentation about it then,
which I am fairly good at.
So... why, then, does the Redhat install default to grub, when I amCan anyone point me in the right direction to any documents about how to do this?Look and the linux documentation project.
And secondly.... is there any further info on bootable sofware
raid and what I do if one of the disk fails? I pulled one of the
disks the other day while the system was powered down, and it wouldn't
boot at all while it was out... that certainly is _not_ the way
my hardware RAID systems work. I am using the GRUB boot loader
and I assumed that each disk was bootable, but no go here, I had
to put the disk back in before it would boot up again.. if they
are going to offer us software raid, then I think they should follow
thru and tell us how to use it.
On older releases of Redhat lilo/grub was installed on only the 1st drive. You can manually install lilo on both disks fairly easily. (I don't use grub.)
doing a bootable software raid install? Seems a bit silly to load up a system that won't work... with no suggestions etc on how to fix it.
Thanks, I'm afraid I'm getting a little disillusioned with RedHat these
days... seems like there is the Linux way of doing things and the Redhat
way of doing things and they are getting further apart all the time, and
as that happens, I wonder more and more about hitching my horse to the
Redhat wagon or not...
Bill Dossett
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
