Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: uniqsys on March 02, 2006, 03:09:50 AM
-
I recently installed 7.0pre3 on a Compaq proliant 1600 which already has hardware RAID. I was wondering if anyone could tell me of a way to turn off the RAID configuration of 7.x since it is already covered by the hardware. I didn't see an option for this during install as with 6.0.
Thanks.
-
I recently installed 7.0pre3 on a Compaq proliant 1600 which already has hardware RAID. I was wondering if anyone could tell me of a way to turn off the RAID configuration of 7.x since it is already covered by the hardware.
The only way to disable it is to use a custom kickstart file. See RedHat documentation for details about kickstart.
The software RAID is not doing you any harm. There's no need for you to disable it.
-
Thanks. I'll look into the Redhat Doc.
I suspected that running the RAID software wouldn't do any harm except use some minor amount of resources, but confirmation on this always is reassuring. BTW why the force to software RAID in 7.x as opposed to choice as in 6.0? Just curious.
Thanks for the help.
-
BTW why the force to software RAID in 7.x as opposed to choice as in 6.0?
So that it is possible to add RAID redundancy without re-installing.
-
I see. That makes a lot of sense.
I'm glad to see even more flexibility being built into SME server. Great work!
-
If you pass the keyword "partition" to the boot line then you will be presented with the partition screen. From there you can remove the partitions and partition the way you want to.
You can remove the software raid in this way but you won't be able to add the LVM back into the mix. So you will be stuck with just ext3 partitions. If you want more complicated then you will have to use a kickstart method like Charlie stated.
-
I'm working on the same "problem", this is an interesting info i already found reading smeinstallclass.py and so on, but the iso install doesn't let the time to append "partition" to the kernel commandline, as the prompt is set to 0 in isolinux.cfg. You must re-roll your iso, adding an entry to isolinux.cfg and setting another value for prompt in order to partition manually the hard disk.
Maybe a bug, or is it normal ????
And i'm deseperately looking for the anaconda-ks.cfg which was created in SME6 by the installer, apparently not in SME7..
You advice everyone wanting to custom the install process to create a kickstart file, but there is not a lot more info about it on contribs.org.
I definitely agree that there is documentation for anaconda and kickstart on RHEL/Fedora knowledge base, but this would be a good idea to add info about it on contribs.
If you want, i can share the informations i gathered in my customisation of SME install process.. i know this would NOT be supported for future updates, but it might be useful for some advanced users :)
Landry
-
... but the iso install doesn't let the time to append "partition" to the kernel commandline, as the prompt is set to 0 in isolinux.cfg.
Hold down the shift key at boot time.
-
You advice everyone wanting to custom the install process to create a kickstart file, but there is not a lot more info about it on contribs.org.
I definitely agree that there is documentation for anaconda and kickstart on RHEL/Fedora knowledge base, but this would be a good idea to add info about it on contribs.
There is a wiki here - you can add any documentation you feel is necessary.
-
... but the iso install doesn't let the time to append "partition" to the kernel commandline, as the prompt is set to 0 in isolinux.cfg.
Hold down the shift key at boot time.
Great, i didn't know that... shame on me !
There is a wiki here - you can add any documentation you feel is necessary
I just wanted to be sure it was not going 'against' official position of contrib's team to just support the standard install on the entire disk.
I'll make a page to gather all the informations i've found about this subject.
Charlie, thanks for your reply.. your work on SME is unvaluable ;-)
Landry