Description of problem: Every time I do mkinitrd to create a RAM disk image I get error from tar: ./bin/insmod: Wrote only 2560 of 10240 bytes Version-Release number of selected component (if applicable): mkinitrd version 2.2.5-15 How reproducible: Every time Steps to Reproduce: [root@ia64-l82bi189 root]# ./doboot > mkinitrdErr.txt + alias 'rm=rm -i' + alias 'cp=cp -i' + alias 'mv=mv -i' + '[' -f /etc/bashrc ']' + . /etc/bashrc +++ id -gn +++ id -un +++ id -u ++ '[' root = root -a 0 -gt 99 ']' ++ umask 022 ++ '[' '' ']' + cd /usr/src/linux + gzip -c vmlinux > /boot/efi/vmlinuz-2.4.18-e.31smp + cp vmlinux /boot/efi/vmlinux-2.4.18-e.31smp + cp System.map /boot/System.map-2.4.18-e.31smp + cd /boot + ln -sf efi/vmlinuz-2.4.18-e.31smp vmlinuz-2.4.18-e.31smp + rm System.map + ln -sf System.map-2.4.18-e.31smp System.map + ln -sf efi/initrd-2.4.18-e.31smp.img initrd-2.4.18-e.31smp.img + cd efi + mkinitrd -f initrd-2.4.18-e.31smp.img 2.4.18-e.31smp tar: ./bin/insmod: Wrote only 2560 of 10240 bytes tar: Error exit delayed from previous errors Actual results: Expected results: Additional info:
How big is your initrd? What modules are being included in it? The simple workaround is to change IMAGESIZE as defined at the top of mkinitrd (this is done in newer versions because it became a problem with the Red Hat Enterprise Linux 3 beta, but I never saw or heard of it being a problem with 2.1)
My initrd is 1259160 bytes Modules being added are: eth0 e1000 eth1 e1000 scsi_hostadapter mptbase scsi_hostadapter1 mptscsih scsi_hostadapter2 qla2300 scsi_hostadapter3 mptscsih scsi_hostadapter4 mptscsih scsi_hostadapter5 qla2300 scsi_hostadapter6 qla2300 usb-controller usb-uhci
Yeah, you're probably hitting the imagesize. If you bump the number does it work?
Sorry Jeremy, I am a little new to this (I do not want to be called a Linux Newbie :) I tried looking for mkinitrd.c or .h without any success. How do I change the imagesize?
mkinitrd is just a simple shell script... look at /sbin/mkinitrd and you should find IMAGESIZE=4000 pretty quickly. Change the 4000 to an 8000 and that should do it.
Your work-around works! Thanks. Does this qualify as a REAL bug?
Yep, it's fixed in newer versions, though.