Bugs item #1068036, was opened at 2004-11-17 06:19 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=1068036&group_id=9368
Category: Installation Group: 4.0 Status: Open Resolution: None Priority: 9 Submitted By: Thomas Naughton (naughtont) Assigned to: Bernard Li (bernardli) Summary: Fedora (FC2) - scsi HD bug Initial Comment: When testing with oscar-4.0 material on Fedora Core 2 (x86) with a SCSI HD I had problems after the node reboots. The node seems to build properly (step6) but on the next reboot after the SI install you get a Kernel PANIC can't find root (sda6). The sda6 partition exists and appears to have the correct data, ie. it is mountable by hand from a rescue disk. I/we tried playing with a few Grub options to no avail. Bernard had similar issues (kernel panic can't mount root) on some of his systems and it seemed to be due to missing entries (apparently un-needed) in modules.conf (2.4 kernel) and therefore were missing in the new modprobe.conf (2.6 kernel). I do not have the test system available to confirm this portion for our issue. Note, the headnode had FC2/SCSI but was built by hand from CD's and worked just fine. REPRODUCE PROBLEM: + use oscar-4.0beta tarball on Fedora Core 2 system with SCSI harddrives. + After building nodes, upon reboot, node(s) should have kernel panic ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-02 05:08 Message: Logged In: NO I think this is related to the same errors seen under the pvfs bug. I had to copy over a working initrd to my systemimager image directory in order to get the image to boot. It looks like something is haveing a problem building the initrd properly. The initrd that was built by default did not have the scsi modules in it. Jason [EMAIL PROTECTED] ---------------------------------------------------------------------- Comment By: Bernard Li (bernardli) Date: 2004-11-30 11:13 Message: Logged In: YES user_id=879102 - code checked into SVN - release notes will be updated - SVN r2764 ---------------------------------------------------------------------- Comment By: Bernard Li (bernardli) Date: 2004-11-26 14:15 Message: Logged In: YES user_id=879102 - I think I have working solution which is to run systemconfigurator after /etc/modprobe.conf is generated - I will perform some more testing before commiting it - The user will still be able to copy over a working modprobe.conf if they choose to ---------------------------------------------------------------------- Comment By: Bernard Li (bernardli) Date: 2004-11-23 15:18 Message: Logged In: YES user_id=879102 - the fix is, if the headnode has SCSI HD, simply copy /etc/modprobe.conf to /var/lib/systemimager/images/oscarimage/etc (on the headnode) and delete the script /var/lib/systemimager/scripts/post- install/22all.generate_modprobe_script - this worked on a cluster that I tested on during SC04 - I will look into an alternative solution which is to hardcode the necessary SCSI module(s) to /etc/modprobe.conf after it's generated from /etc/modules.conf - this may work as I have noticed that the necessary module is 'generic' - this setup should work for both SCSI and IDE drives - ultimately I believe this has to be fixed for SIS... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-11-22 12:37 Message: Logged In: NO Bernard please explain your fix, then we'll determine if this is a 4.0 item (ie. before moving to level=9). ---------------------------------------------------------------------- Comment By: Ed Hill (edhill) Date: 2004-11-17 08:08 Message: Logged In: YES user_id=79627 We also had this problem and it was because the SCSI drivers we needed were missing from the initrd. And I *think* this happened because our compute nodes are SCSI while the head node is IDE. The ways to fix it are to either build a custom kernel that has the needed SCSI drivers compiled in or to make sure that OSCAR has an initrd that has the necessary SCSI drivers. So how can we specify a spicific initrd for a node or a set of nodes (say, if some nodes are SCSI and some aren't)? Ed <[EMAIL PROTECTED]> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=1068036&group_id=9368 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
