|
Andrea, I tried your first suggestion, but still got the same failure. I guess I will try the post-install thing, but that seems kinda hackish... I'm also having to re-run grub-install on my systems now to get them to boot. I swear I didn't have to do that when I reported this, but I could have just mixed up my tests. So to recap: I kickstart a rhel3 update 4 system I take an image I drop the same image back on the box kernel panics after getting this "crc error<6>". I can boot the box up in rescue mode, uncompress the initrd and recompress, reinstall grub with grub-install. The system boots normally. Also, I kickstarted a system with LILO rather than Grub, and it worked normally after taking an image and dropping back on the same box. On Monday 07 August 2006 09:08, Andrea Righi wrote: > Have you tried to uncompress and recompress the initrd directly in your > image (in /var/lib/systemimager/images)? > > Moreover have you tried to run a post-install script to re-create the > initrd after the imaging, just before the first reboot? I mean the > post-install script should look like: > > #!/bin/sh > /sbin/mkinitrd <options_for_rhel3> > > -Andrea > > Matt Jamison wrote: > > No errors reported anywhere. Has anyone else actually tested successfully > > with RHEL3 and 3.7.3+? > > > > On Sunday 06 August 2006 20:42, Bernard Li wrote: > >> SystemImager keeps rsync logs in /var/log/systemimager/rsyncd - you might > > want to check that. > >> > >> Cheers, > >> > >> Bernard > >> > >> ________________________________ > >> > >> From: Matt Jamison [mailto:[EMAIL PROTECTED] > >> Sent: Sun 06/08/2006 16:32 > >> To: [email protected] > >> Cc: Bernard Li > >> Subject: Re: [Sisuite-users] crc error booting imaged system > >> > >> > >> > >> Yes, I used UYOK when imaging, but this error is actually occuring after the > >> system "successfully" images, on the first boot of the fresh image. > >> > >> I actually made a little progress on this right after sending the post, in > >> that I found a way to fix the problem once in rescue mode. I still haven't > >> figured out what is causing it during imaging though... > >> > >> If i just boot into rescue mode and uncompress and recompress the initrd > > with > >> gzip, the system can boot fine... I thought maybe rsync was somehow messing > >> up the compressed initrds, but even after upgrade the server, client and > >> initrd templates all to rsync 2.6.8, I still have the same error... > >> > >> Thanks, > >> > >> Matt > >> > >> Since I've been submitting these 2.4 kernel problems and fixes, I've got > > them > >> in my test environment :) > >> > >> On Sunday 06 August 2006 15:34, Bernard Li wrote: > >>> Did you use UYOK to generate your ramdisk? Did you set an appropriate > >> number for the kernel APPEND line for ramdisk_size > > like "ramdisk_size=80000"? > >>> Also, can you post your node's /boot/grub/menu.lst? > >>> > >>> Cheers, > >>> > >>> Bernard > >>> > >>> P.S. It would probably be better if you test the code from trunk rather > > than > >> 3.7.3 since Andrea fixed a lot of 2.4 kernel related issues in trunk. > >>> ________________________________ > >>> > >>> From: [EMAIL PROTECTED] on behalf of Matt > > Jamison > >>> Sent: Sun 06/08/2006 12:03 > >>> To: [email protected] > >>> Subject: [Sisuite-users] crc error booting imaged system > >>> > >>> > >>> > >>> Just in case someone else has already dealt with this issue, I want to > >> describe my latest problem with 2.4 kernel/RHEL3 and si 3.7.3 (maybe > >> systemconfigurator?) > >>> Here is the scenario: > >>> > >>> Kickstart RHEL3 system, everything working perfectly > >>> > >>> Take an image of the system with 3.7.3 > >>> > >>> Drop new image on system > >>> > >>> Everything seems to finally be working in systemimager with the 2.4 > > kernel, > >> (all the data is getting copied), but the system is not bootable after > >> imaging. It fails with: > >>> RAMDISK: Compressed image found at block 0 > >>> > >>> crc error<6>Freeing intird memory: 277k freed > >>> > >>> VFS: Cannot open root device "LABEL=/" or 00:00 > >>> > >>> Please append a correct "root=" boot option > >>> > >>> I have no idea what is causing this crc error, but something has to be > >> getting corrupted during imaging. It seems to be a problem with > > decompressing > >> the initrd, but the strange thing is I've verified the initrd md5sum on the > >> imaged system matches the file after kickstarting (by booting into rescue > >> mode). > >>> Also, I've verified this problem on several systems, so I'm sure it's not > > a > >> hardware thing. > >>> Running out of ideas, > >>> > >>> Matt > >>> > >>> > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Sisuite-users mailing list > https://lists.sourceforge.net/lists/listinfo/sisuite-users > |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
