Thank you Michael, Am I doing something wrong, or missing the obvious? fai subroutines did not like what I did.
Kernel parameters: initrd=initrd.img-2.6.32-5-686-bigmem libata.force=noncq ip=dhcp root=/dev/nfs nfsroot=/app/fai/nfsroot boot=live FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install SERVER=mg006 hostname=c-fs1qa.qa01.groupee-inc.net BOOT_IMAGE=vmlinuz-2.6.32-5-686-bigmem /usr/lib/fai/subroutines: line 683: libata.force=noncq: command not found /usr/lib/fai/subroutines: line 684: export: `libata.force': not a valid identifier Below is my pxelinux conf file, which is where I assumed that the parameter needed to be inserted. Was this an incorrect assumption on my part? label fai-generated kernel vmlinuz-2.6.32-5-686-bigmem append initrd=initrd.img-2.6.32-5-686-bigmem libata.force=noncq ip=dhcp root=/dev/nfs nfsroot=/app/fai/nfsroot boot=live FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install SERVER=mg006 hostname=c-fs1qa.qa01.groupee-inc.net David Dreezer On Apr 15, 2011, at 12:40 PM, Michael Tautschnig wrote: > Hi David, > >> The machine came to life eventually. I've attached the system messages as I >> think it may be helpful >> > [...] > > I've looked at your log file and it seems that there might be help in using > > libata.force=noncq > > on the kernel command line. I've taken that from > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892 > > Maybe you can take a look at that bug report, it also includes references to > other bug reports. That would fit with the situation that you have a different > controller in this host. > > Hope this helps, > Michael >
