<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>We have a group of older servers that for whatever reason require the flag libata.force=noncq to be inserted in the kernel command line.</div><div><br></div><div>See message 15 of <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607285">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607285</a> for the exact file we're using. That's actually my config file quoted.</div><div><br></div><div>My question isn't related to this bug exactly, but actually what I've run into at the next step in the process. There seems to be no mechanism in FAI at the present that will take that exported kernel option and add it into grub2. So, while we can apply the kernel option to our kernel, mount NFSROOT and install our server we can't actually apply the kernel options to the installed system, which means once FAI tells it to reboot....... it never comes back up.</div><div><br></div><div>My workaround has been to remove the reboot flag as you see in the config that I linked to. I will then manually go in, edit /etc/default/grub/GRUB_CMDLINE_LINUX_DEFAULT then reboot the machine, but that's not exactly automatic. I could put a script into /scripts/LAST for this server class that will sed that into the file for me I suppose, but is there a better way? Is there a mechanism in FAI that would do this for me, but that I am not seeing? </div><div><br></div><div>Am I the only one that has faced a need to make a kernel flag permanent?</div><div><br></div><div>Thanks,</div><div><br><div>
David Dreezer<br>Customer Advocate, Social Strata, Inc.<br><br><br>
</div>
<br></div></body></html>