[BlueOnyx:08213] Re: Same mess different BlueOnyx version, using scsi drives

[Gerald Waugh]

Michael Stauber wrote:
> Hi Gerald,
> 
> 
>> SL-6.1+BlueOnyx doesn't work
> 
>> SL-6.1 DVD works
> 
>>
> 
>> What happens when BlueOnyx is added that causes the install CD to barf
> 
>> nanging the drives
> 
> 
> I'm sorry to hear that, Gerald. I need some help troubleshooting this as
> I cannot cover all hardware variants during testing.
> 
> 
> Generally our SL-6.1+BlueOnyx CD should support any kind of drives:
> 
> 
> IDE, SCSI, SATA, SAS and SSD.
> 
> 
> However, *any* kind of hardware detection depends on the Kernel of the
> 1st stage installer and on the Anaconda installer within the 1st stage
> installer.
> 
> 
> Now if the "naked" SL-6.1 works for you, the problem could be with the
> custom kickstart.cfg file that we use on our version of the CD.
> 
> 
> To troubleshoot this, please do the following:
> 
> 
> Try to do another install using the most recent ISO:
> 
> 
> BlueOnyx-5107R-SL-6.1-20110811.iso (which you probably were using)
> 
> 
> Please let me know the exact error message you get.
> 
> 
> Additionally, when you get the error, press CTRL + ALT + F2 to get to
> the command prompt. Once you get the prompt, look inside the /tmp directory.
> 
> 
> There are some files in /tmp that greatly help with debugging of a
> failed install:
> 
> 
> /tmp/syslog
> 
> /tmp/anaconda.log
> 
> /tmp/include-parts
> 
> 
> Especially /tmp/include-parts is very important here, as it contains the
> automatically generated partition layout, which is generated by our
> kickstart script after it has detected your disk types and amount of disks.
> 
> 
> Please check your /tmp/include-parts and let me know what information it
> contains.
> 
> 
> Additionally, report back the output of the command "fdisk -l".
> Especially I need to know if any disks are found and if so, what their
> device identifiers are (i.e.: /dev/sda, /dev/hda or whatever).
> 
> 
> Based on that information I can then fix the CD so that it works for you
> (and others with the same issue).
> 
> 

I'll try and find time to work on this today.
When I fixed the 5.5 cd, I changed some of the rpms
using ones that worked from the standard CentOS cd.


-- 
Gerald