In our local case, the deployment purchased a supposedly RHEL-compliant server which lacked a Linux driver for its built-in RAID controller.
This RAID controller created disk partitions which spanned the full size of each disk drive. These partitions appeared when the lower-level disk controller(s) were accessed directly after the RAID controller was turned off, and caused anaconda to die whenever it tried to figure out a partitioning scheme with already-full disks. Fdisk was used to delete these partitions from a Linux terminal console, and then anaconda was happy. The inverse situation also needs to be watched out for: If you are using a Linux-supported hardware RAID controller, the individual disks/controllers below it may still be accessible, and installing directly on those could make the RAID controller unhappy. On Fri, Mar 30, 2012 at 11:51 AM, Tim Moody <timmo...@sympatico.ca> wrote: > (btw installing straight from cd never worked for me as it failed on the >>> disk partitioning regardless of the options I chose) >>> >> >> From a kickstart file or by hand in the installer? >> > > using the cd and taking the kickstart option. > > >> Jerry >> >> >> ______________________________**_________________ > Server-devel mailing list > Server-devel@lists.laptop.org > http://lists.laptop.org/**listinfo/server-devel<http://lists.laptop.org/listinfo/server-devel> >
_______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
