Hi, I'm still unable to understand why I get a wrong initrd after reboot. my /var/lib/systemimager/images/oscarimage/etc/systemconfig/systemconfig.conf contains CONFIGRD = YES so it should rebuild the initdrd before rebooting (systemconfigurator --configrd)
The ahci.ko is not a module in the kernel used for PXE deployment, but it is a module in the installed kernel. Would it be a cause for wrong initrd? Should I add a CONFIGHW = YES in systemconfig.conf and add a line for ahci.ko in hardware.lst? Must it be of type scsi despite it is sata? Would updating kernel in systemimager-x86_64boot-standard-4.2.0-0.2svn5510.el5 and systemimager-x86_64initrd_template-4.2.0-0.2svn5510.el5 fix this issue without doing tricks aside? Many thanks for any help..... Le lundi 07 mars 2011 16:37:19 Olivier LAHAYE a écrit : > Hi, > > >From an OSCAR server that have a CCISS disk array (no SATA3 > >disk/controler), > > I'm trying to deploy a node image on some new hardware HPDL165G7 with > SATA3(ahci.ko) disk using latest systemimager svn revision (which works fine > for all my other hardwares). > > The problem is that after deploying the image without any trouble, the node > fails to reboot (kernel panic, no disk found). > The cause is that the node initrd.img lacks the ahci.ko module (and uselesly > includes cciss.ko). > > How is the initrd.img built? Would it be built on the server? Not in the > postinstall stage of the image deployment? > > digging into OSCAR I was able to understand that the following things are > done to create the image: > > # Create the image > mksiimage -A --name oscarimage --filename > /usr/share/oscar/oscarsamples/centos-5-x86_64.rpmlist --arch x86_64 --path > /var/lib/systemimager/images/oscarimage --distro centos-5-x86_64 --verbose > > # Create the disk layout (this produces): > /var/lib/systemimager/images/oscarimage/etc/systemconfig/systemconfig.conf > et > /var/lib/systemimager/images/oscarimage/etc/systemimager/autoinstallscript. > conf # I'm using scsi.disk as it's the same dev names as sata. (/dev/sd*) > mksidisk -A --name oscarimage --file > /usr/share/oscar/oscarsamples/scsi.disk > > # autoinstall script. I though that using autodetect-disk would regenerate > the initrd before the reboot during the image deployment (but I'm > apparently wrong). > /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image oscarimage > - force -ip-assignment static -post-install reboot > > # Unfortunately, If I deploy the image now, the node won't reboot and I'm > forced to manualy generate the initrd in the image like this: > /usr/sbin/chroot /var/lib/systemimager/images/oscarimage /sbin/mkinitrd -v > -f --fstab=/etc/fstab.fake --allow-missing --with=ahci > /boot/initrd-2.6.18-164.el5.img 2.6.18-164.el5 > > Doing so will make things work, but it's a dirty hack IMHO... > > Any clean way to do without using UYOK (as the current kernel is ok, the > driver is there, it's just missing in the initrd image). > > Many thanks for any help understanding this. > > PS: I've attached the si_monitor.log just in case.... -- Olivier LAHAYE Responsable calcul scientifique CEA DRT/LIST +33 1 69 08 13 25 ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
