Skip to main content

Install RHEL using software RAID

Issue: I was sorely disappointed when I was exposed to how poor "RAID" is on commodity motherboards (like ASUS and Gigabyte).  I had not put much thought into exactly what it meant when they claimed they had SATA RAID.  This whole epiphany was the result of when I had installed RHEL (or Fedora, I can't recall) on a system with a 1TB drive. Fortunately the drive that was headed for certain doom, failed shortly after the install.  No big deal, right? I'll just throw another drive in and it should take off... somehow?  Well, not even close, actually.

fakeRAID is the term I see used in referencing this setup.  There most likely is some benefit to this approach when using Windows and the overlying fakeRAID software components.  It would seem that you could boot the system from one of the 2 mirrors and start the fakeRAID software and inform it that a replacement drive was installed. There may also be some sort of performance improvement using this stack.  I'm not interested in all that mess though...

I configured my SATA controller back to AHCI with 2 "basic" drives and started the install.
The installation is a bit cumbersome. I will say, in it's defense, to be able to create a software RAID device, or devices... with LVM, during a GUI installation, is pretty impressive.

Steps:
Boot from installation media, of course
Select the drives you wish to use - I also indicate that I would like to "Use All Space" and check the "review" button towards the bottom.  You will be removing any suggestions the installer makes anyhow.
Remove all LVM and partitions currently present on your drives (that you didn't want to preserve)
<INSERT FINISH STEPS HERE>



Labels:

Comments

Post a Comment

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more