Re: [SSI-users] Debian Mkinitrd problems, was: (no subject)

[drag s. <lin...@co...>]

On Sun, 2004-12-19 at 14:01 +0530, Aneesh Kumar K.V wrote:
> drag sidious wrote:
> >>ormation: done
> >  
> >  This filesystem will be automatically checked every 26 mounts or
> >  180 days, whichever comes first.  Use tune2fs -c or -i to override.
> >  Copying files.....
> >  cpio: ./dev/cciss: No such file or directory
> >  cpio: ./dev/ide: No such file or directory
> >  cpio: ./dev/mapper: No such file or directory
> >  cpio: ./dev/md: No such file or directory
> >  cpio: ./dev/scsi: No such file or directory
> >  cpio: write error: No space left on device
> >  initrd:  68.6% -- replaced with initrd.gz
> >  Finished building ramdisk
> >  spock:~/tmp# ls -l initrd
> >  -rw-r--r--  1 root root 0 Dec 18 06:56 initrd
> >  spock:~/tmp#
> 
> 
> There is not space on your ramdisk i guess. I guess  you have added 
> MODULE=all in our /etc/mkinitrd/mkinitrd.conf file. You can make in 
> MODULES=dep and see if it works.
> 
> -aneesh
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Ssic-linux-users mailing list
> Ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users

No that wasn't it. I had it set on the defaults, the only change that I
made was eliminating the > /dev/null for the output of the mkinitrd
script so that I could see what was going on a bit more.

There is a bug with the scripts.. Either in the mkinitrd script or the
mkramdisk.

I actually have it working now, I think. At least cluster -v reports
that 2 nodes are up. Haven't done any testing on it yet.

What I did to make it work was run mkinitrd with the -k option so that
it didn't delete the temporary directory. Then I manually built a
loopback ext2 file system and copied the directory contents
of /tmp/mkinitrd.XXXXX/initrd/ to it. Then used that as the build my
initrd.

Seems to work. I'll play around with the scripts for a bit to see were
they are getting the size wrong, but I am not a horrid programmer so I
can't promise anything.

One question though, when it builds the ./initrd/ filing system is it
suppose to have a compressed loopback file system of it's own on it? Not
sure what is going on.

(I copied the directory to my root's own ~/tmp directory for safe
keeping, btw)

spock:~/tmp# ls mkinitrd.69449/initrd/
bin      dev    etc     linuxrc       mnt   script   tmp
bin2     dev2   initrd  linuxrc.conf  proc  scripts  usr
cluster  devfs  lib     loadmodules   sbin  sys      var

spock:~/tmp# ls -lh mkinitrd.69449/initrd/initrd
-rw-r--r--  1 root root 1.7M Dec 19 07:12 mkinitrd.69449/initrd/initrd

spock:~/tmp# file mkinitrd.69449/initrd/initrd
mkinitrd.69449/initrd/initrd: gzip compressed data, was "initrd", from
Unix, max compression

spock:~/tmp# du -h mkinitrd.69449/initrd/
*snip*
6.8M    ./mkinitrd.69449/initrd
*snip*

Is that suppose to be there?

In order to make the initrd it has to end up being nearly 7 megs, and
the only module that I have in there is e1000. 

Thank You very much for your time, btw. Having everything aviable thru
apt-get makes this thing very nice, other then this everything seems to
be working great.