Could you post the errors you're receiving, or, if you want, could you post your kernel and initrd somewhere on the web? Have you tried to check if the initrd fs is not corrupted (see my previous email). Moreover are you using a fs for the initrd that is statically built into the kernel? (for example if you're using cramfs you should see a CONFIG_CRAMFS=y in your kernel config, but the correct filesystem to be used should be automatically detected by si_prepareclient).
Regards, -Andrea Andrew M. Lyons wrote: > We're experiencing the same problem (with UYOK RHEL5beta2 on a box with > 2 dual-core opterons) > > Topher Fischer wrote: >> Increasing the "ramdisk_size" parameter doesn't fix the problem, there's >> something weird with the kernel that I'm using. This doesn't make sense: >> >> ram1: rw=0, want=18446744056529682440, limit=32768 >> >> If nobody has any ideas of what might be causing this, does anybody have >> a kernel and initrd.img I can have? I need it for a x86_64 machine with >> the e1000 network driver. >> >> Andrea Righi wrote: >>> Look in the troubleshooting section on wiki: >>> >>> http://wiki.systemimager.org/index.php/Troubleshooting#Ramdisk_too_small.3F_Getting_errors.3F >>> >>> Regards, >>> -Andrea >>> >>> Topher Fischer wrote: >>> >>>> I'm trying to get some new HP desktops (Core 2 Duo) to boot up and start >>>> imaging. I'm using Fedora Core 6 for the image and RHEL 3 for the >>>> server. I started with the rpms I got using the standard 'install' >>>> script, but it didn't work, so I got the "unstable" rpms off sourceforge >>>> (3.7.5) and still got the same problem. Working with the image seems to >>>> be going fine, but when I actually try and PXE boot a machine, it pulls >>>> down the kernel and initrd.img files, starts loading the kernel, then >>>> gives me this: >>>> ############################## >>>> RAMDISK: Compressed image found at block 0 >>>> RAMDISK: incomplete write (-28 != 32768) 16777216 >>>> attempt to access beyond end of device >>>> ram1: rw=0, want=18446744056529682440, limit=32768 >>>> isofs_fill_super: bread failed, dev=ram1, iso_blknum=17, block=-2147483648 >>>> No filesystem could mount root, tried: ext2 iso9660 >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>> unknown-block(1,1) >>>> ############################### >>>> >>>> I get the same thing using both the files in /etc/systemimager/boot, and >>>> using 'mkbootpackage'. Does anybody have any suggestions on how to go >>>> about resolving this, or maybe some kernel and initrd.img files to share? >>>> >>>> Thanks in advance, >>>> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
