Hi,
I had already tried --my-modules before, but I thought I'd try it again
with 3.7.6 before responding. My problem isn't that I'm not asking for
enough space in /dev/ram.
Here is the output from si_prepareclient (using --my-modules):
>> Evaluating initrd size to be added in the kernel boot options
>> (e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
>> suggested value -> ramdisk_size=36944
and my kernel boot options:
LABEL si-gwdd_mm
KERNEL gwdd_mm_kernel
APPEND vga=extended initrd=images/gwdd_mm_initrd.img
root=/dev/ram ramdisk_size=40000 SKIP_LOCAL_CFG=y MONITOR_SERVER=image3
MONITOR_CONSOLE=yes
and when I boot it up on a machine with identical hardware:
...
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found atblock0
input: AT Translated Set 2 keyboard as /class/input/input0
EXT2-fs: blocksize too small for device.
attempt to access beyond end of device
ram0: rw=0, want=18446744056529682440, limit=80000
isofs_fill_super: bread failed, dev=ram0, 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,0)
We DO have heterogeneous hardware, but I'm willing to have a separate
initrd for each hardware configuration if that's what it takes to get
this to work. As it stands, the default x86_64 boot image doesn't
detect the disk properly, and UYOK doesn't work for the reasons
described above.
Thanks for your assistance, and for your work on systemimager! It's a
great tool and your efforts are very much appreciated.
-Andrew
Andrea Righi wrote:
> It seems that your initrd is very big > 80MB, so you have to try at
> least with:
>
> ramdisk_size=100000
>
> or better use the size suggested in the output of si_prepareclient.
>
> Moreover you could try to optimize the size of the initrd removing some
> modules not used for the installation. You can do this automatically
> using the --my-modules option, or trying to exclude manually some
> modules via /etc/systemimager/UYOK.modules_to_exclude in your golden
> client... for example you could remove:
>
> kernel/drivers/net/wireless/*
> kernel/drivers/infiniband/*
>
> etc...
>
> If you have not heterogeneous hardware I suggest to use the --my-modules
> option, it's much simpler.
>
> Regards,
> -Andrea
>
> Andrew M. Lyons wrote:
>> I wanted to try 3.7.6 before I responded to this. the kernel and
>> initrd.img generated using 3.7.6 (UYOK, no --my-modules) are here:
>>
>> http://www.accre.vanderbilt.edu/si/
>>
>> The hardware I have doesn't work with the default x86_64boot for 3.7.5
>> or 3.7.6 (doesn't recognize the disk).
>>
>> I'll try some more of your suggestions and respond again...
>>
>>
>> Andrea Righi wrote:
>>> 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
> Sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
-------------------------------------------------------------------------
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
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
