I don't know if anyone looked at this, but I haven't received any answers yet on it. I have quite a few SuSE9.2 systems that have the identical problem with loading the initrd.
Even if the answer is "use 3.7.3", I would still appreciate an answer. --Carl Benson Carl J. Benson wrote: > Hello. > > I upgraded my S.I. server from 3.4.1 to 3.6.3, and I'm in the > process of upgrading all my clients to 3.6.3. I have many i386 > architecture clients that run SuSE9.2 and use the nvidia.ko > driver for graphics. > > On these systems, si_prepareclient adds all the modules for the > initrd, as in: > > Adding: /lib/modules/2.6.8-24.23-default/kernel/fs/reiserfs/reiserfs.ko > ... > Adding: /lib/modules/2.6.8-24.23-default/kernel/drivers/char/nvram.ko > >>> Filesystem for new initrd: ext2 > >>> Creating new initrd from: /tmp/.systemimager.0 > >>> New initrd mount point: /tmp/.systemimager.1 > >>> dd if=/dev/zero of=/etc/systemimager/boot/initrd bs=1024 count=24924 > 24924+0 records in > 24924+0 records out > > I see it making an ext2fs filesystem on /etc/systemimager/boot/initrd: > > >>> mke2fs -b 1024 -m 0 -N 14659 -F /etc/systemimager/boot/initrd > mke2fs 1.35 (28-Feb-2004) > warning: 347 blocks unused. > > Filesystem label= > OS type: Linux > Block size=1024 (log=0) > Fragment size=1024 (log=0) > 14664 inodes, 24577 blocks > 0 blocks (0.00%) reserved for the super user > First data block=1 > 3 block groups > 8192 blocks per group, 8192 fragments per group > 4888 inodes per group > Superblock backups stored on blocks: > 8193 > > Writing inode tables: done > Writing superblocks and filesystem accounting information: done > > This filesystem will be automatically checked every 35 mounts or > 180 days, whichever comes first. Use tune2fs -c or -i to override. > > >>> tune2fs -i 0 /etc/systemimager/boot/initrd > tune2fs 1.35 (28-Feb-2004) > Setting interval between check 0 seconds > > However, it looks like this filesystem is too small: > > >>> mount /etc/systemimager/boot/initrd /tmp/.systemimager.1 -o loop -t > ext2 > > >>> tar -C /tmp/.systemimager.0 -cf - . | tar -C /tmp/.systemimager.1 -xf - > tar: ./dev/log: socket ignored > tar: ./my_modules/nvidia.ko: Wrote only 3072 of 10240 bytes > tar: Unexpected EOF in archive > tar: Error is not recoverable: exiting now > > How can I work around this? > > Please & thanks. ------------------------------------------------------------------------- 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
