On Mon, 2005-01-17 at 13:38 -0500, Christopher Alexander Stein wrote:> Hi, > > I am trying to get Lustre working on a Debian system using the > RPM packages. > > Has anyone successfully booted up the pre-built kernel on a > Debian machine? The pre-built kernel needs an initrd.img file, > but the initrd.img file generated by Debian''s mkinitrd script is > too big for the boot loader (I am using GRUB). I get: > > RAMDISK: cramfs filesystem found at block 0 > RAMDISK: image too big! (17444/8192 blocks) > ... > Kernel panic: VFS: Unable to mount root fs on 00:09I don''t have this problem, but perhaps there are modules in your initrd which could be removed? On my Debian machines I simply alien''d the pre-built kernels and booted them. I had no problem except one machine needed modules which aren''t in that package, and I had to rebuild the kernel and initrd. Still, it boots fine. 19820544 2004-12-07 17:26 initrd.img-2.6.5-SLES9_SP1_BRANCH_2004111114454891_lustre.1.4.0smp -jwb
Hi, The biggest module stuffed into my initrd.img file is Lustre itself, and that can''t be removed, I assume. Your initrd.img file is larger than the one I''m using, yet my bootup fails, claiming that my initrd.img is too big. I find this odd. Did you start with this RPM ?: kernel-bigsmp-2.6.5-SLES9_SP1_BRANCH_2004111114454891_lustre.1.4.0.i686.rpm How did you figure out which modules were needed that weren''t in the package? Could you please send me your /etc/mkinitrd/mkinitrd.conf file ? Thank you, Lex On Tue, 18 Jan 2005, Jeffrey W. Baker wrote:> > RAMDISK: cramfs filesystem found at block 0 > > RAMDISK: image too big! (17444/8192 blocks) > > ... > > Kernel panic: VFS: Unable to mount root fs on 00:09 > > I don''t have this problem, but perhaps there are modules in your initrd > which could be removed? On my Debian machines I simply alien''d the > pre-built kernels and booted them. I had no problem except one machine > needed modules which aren''t in that package, and I had to rebuild the > kernel and initrd. Still, it boots fine. > > 19820544 2004-12-07 17:26 initrd.img-2.6.5-SLES9_SP1_BRANCH_2004111114454891_lustre.1.4.0smp
On Tue, 2005-01-18 at 15:24 -0500, Christopher Alexander Stein wrote:> OK, thanks. That (as well as the approach of MODULES=dep) allowed > me to load the initrd.img file. It''s no longer too big. > > The system gets 2 lines farther in bootup then panics because it > can''t mount root; > > Freeing initrd memory: 1112k freed > Kernel panic: VFS: Unable to mount root fs on 08:01 > > I figure I must be missing some module (perhaps a SCSI module); > that''s neither built into the stock kernel nor exists in its > /lib/modules/ subdirectory. > > What is the best approach to finding out what module I am > missing?I found the SuSE kernel unable to boot my SATA-based machines. I had to rebuild the kernel with the SATA drivers built-in. In general I find the SuSE kernel very unreliable on amd64 (in ways unrelated to Lustre) and I can hardly imagine why anyone has the nerve to actually charge money for what may be the worst Linux anyone ever put in a box. And I have even more difficulty trying to imagine why SuSE is worth supporting when Debian isn''t, when Debian is by far the most widely used Linux among self-described open source developers. But, that''s why I don''t get the venture capital, I guess. Oh, getting back to the point. Rebuild the kernel with the necessary drivers built-in, not modules. -jwb
--=-FeBE2Lt7m585F6/H2CbB Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi Cris, Change /etc/mkinitrd/mkinitrd.conf and set MODULES=dep The kernel supplied does not appear to support cramfs so you will have to make in ext2 image Change MKIMAGE=''/usr/local/sbin/mkext2fs %s %s > /dev/null'' (mkext2fs attached) On Mon, 2005-01-17 at 13:38 -0500, Christopher Alexander Stein wrote:> Hi, > > I am trying to get Lustre working on a Debian system using the > RPM packages. > > Has anyone successfully booted up the pre-built kernel on a > Debian machine? The pre-built kernel needs an initrd.img file, > but the initrd.img file generated by Debian''s mkinitrd script is > too big for the boot loader (I am using GRUB). I get: > > RAMDISK: cramfs filesystem found at block 0 > RAMDISK: image too big! (17444/8192 blocks) > ... > Kernel panic: VFS: Unable to mount root fs on 00:09 > > Has anyone successfully got Lustre up on a Debian system with a > clusterfs pre-built kernel. > > Thanks, > > Lex > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss@lists.clusterfs.com > https://lists.clusterfs.com/mailman/listinfo/lustre-discuss >-- Adam Cassar ICT Manager NetRegistry Pty Ltd ______________________________________________ http://www.netregistry.com.au Tel: 02 9699 6099 Fax: 02 9699 6088 PO Box 270 Broadway NSW 2007 Domains |Business Email|Web Hosting|E-Commerce Trusted by 10,000s of businesses since 1997 ______________________________________________ --=-FeBE2Lt7m585F6/H2CbB Content-Disposition: attachment; filename=mkext2fs Content-Type: application/x-shellscript; name=mkext2fs Content-Transfer-Encoding: 7bit #!/bin/bash # similar to mkcramfs (for use with debian mkinitrd) # mkext2fs dirname outfile # # no options are parsed # # Written by: Fabian Franz <mkext2fs@fabian-franz.de> # GPL v.2 - See: `locate gpl.txt` if [ $# -lt 2 ] then echo "Usage: $(basename $0) dirname outfile" exit 1 fi TMPDIR=/tmp/$(basename $0).$$ mkdir $TMPDIR function clean_exit { umount $TMPDIR 2>/dev/null rm -rf $TMPDIR } trap clean_exit EXIT COUNT=$[$(du -s $1 | awk ''{ print $1 }'' )*2+1000] dd if=/dev/zero of=$TMPDIR/image count=$COUNT mke2fs -F $TMPDIR/image mount -o loop $TMPDIR/image $TMPDIR cp -a $1/* $TMPDIR umount $TMPDIR cat $TMPDIR/image | gzip - > $2 --=-FeBE2Lt7m585F6/H2CbB--
On 1/18/2005 14:08, Christopher Alexander Stein wrote:> > The biggest module stuffed into my initrd.img file is Lustre > itself, and that can''t be removed, I assume.You don''t need it in your initrd unless you''re planning to run Lustre as your root file system -- which is possible, but probably not your intention. -Phil
OK, thanks. That (as well as the approach of MODULES=dep) allowed me to load the initrd.img file. It''s no longer too big. The system gets 2 lines farther in bootup then panics because it can''t mount root; Freeing initrd memory: 1112k freed Kernel panic: VFS: Unable to mount root fs on 08:01 I figure I must be missing some module (perhaps a SCSI module); that''s neither built into the stock kernel nor exists in its /lib/modules/ subdirectory. What is the best approach to finding out what module I am missing? Thanks Lex On Tue, 18 Jan 2005, Phil Schwan wrote:> On 1/18/2005 14:08, Christopher Alexander Stein wrote: > > > > The biggest module stuffed into my initrd.img file is Lustre > > itself, and that can''t be removed, I assume. > > You don''t need it in your initrd unless you''re planning to run Lustre as > your root file system -- which is possible, but probably not your intention. > > -Phil > >-- "The English know only one sauce; melted butter." -- Voltaire
Hi, I am trying to get Lustre working on a Debian system using the RPM packages. Has anyone successfully booted up the pre-built kernel on a Debian machine? The pre-built kernel needs an initrd.img file, but the initrd.img file generated by Debian''s mkinitrd script is too big for the boot loader (I am using GRUB). I get: RAMDISK: cramfs filesystem found at block 0 RAMDISK: image too big! (17444/8192 blocks) ... Kernel panic: VFS: Unable to mount root fs on 00:09 Has anyone successfully got Lustre up on a Debian system with a clusterfs pre-built kernel. Thanks, Lex