How to skip repository upgrade in 'fai-setup -v'
I'm setting up a FAI server on a Linux box without Internet access.
When I execute 'fai-setup -v' the script first finishes installing the
base system ("I: Base system installed successfully. Creating
base.tgz"). Then the script tries to upgrade the new repository
("Upgrading /srv/fai/nfsroot/live/filesystem.dir").
As the server is not in the Internet this takes a whole lot of time for
all the timeouts to be completed for each request. Can this be skipped
somehow? There don't seem to be command line parameters for fai-setup to
achieve this. :-(
Thanks for any suggestions,
Cheers, Peter
Re: How to skip repository upgrade in 'fai-setup -v'
Peter Bittner wrote:
> When I execute 'fai-setup -v' the script first finishes installing the
> base system ("I: Base system installed successfully. Creating
> base.tgz"). Then the script tries to upgrade the new repository
> ("Upgrading /srv/fai/nfsroot/live/filesystem.dir").
>
> As the server is not in the Internet
If that's the case, how can the base.tgz be correctly created?
Henning
Re: How to skip repository upgrade in 'fai-setup -v'
Henning,
can you explain your answer? Is it necessary for a FAISERVER system to
be on the Internet to complete the setup successfully?
Peter
On Mon, 2009-08-31 at 16:59 +0200, Henning Sprang wrote:
> Peter Bittner wrote:
> > When I execute 'fai-setup -v' the script first finishes installing the
> > base system ("I: Base system installed successfully. Creating
> > base.tgz"). Then the script tries to upgrade the new repository
> > ("Upgrading /srv/fai/nfsroot/live/filesystem.dir").
> >
> > As the server is not in the Internet
>
> If that's the case, how can the base.tgz be correctly created?
>
> Henning
Re: How to skip repository upgrade in 'fai-setup -v'
Peter Bittner wrote: > Henning, > > can you explain your answer? Is it necessary for a FAISERVER system to > be on the Internet to complete the setup successfully? The base.tgz is a packaged NFSROOT (plus some additional packages, minus some tweaks only needed for the NFSROOT), and it's usually built from scratch with each fai-setup run - or, better, it is created from scratch with each make-fai-nfsroot, which is called by fai-setup. The NFSROOT is created by calling deboostrap, which needs a debian mirror usually. It is entirely possible that the "finished successfully" statement is wrong - you could check your nfsroot and base.tgz if they really contain anything useful. Henning
Problem with Intel igb network driver on client
Hello, we are running Debian Lenny with FAI without any problems. Now, we got a new cluster client with a new Intel network chipset which is not supported by Lenny. Therefore, the igb driver has to be compiled manually. The motherbord of the client (and the FAI server) is a Supermicro X8DTU. Sorry, but I could not find the exact network chipset description. On the server everything is running fine. In the nfsroot, the module igb.ko is present. Probably, it was copied by make-fai-nfsroot from the server (same architecture, kernel etc. on the server and the new client). Inside the nfsroot, the module is listed in the file /usr/share/initramfs-tools/hook-functions in the function auto_add_modules(), too. Booting the client, the PXE boot process begins, the initrd is loaded followed by: Monting root file system ... ... Uniform multi-platform E-ide-driver ... ide0 ... ... ide1 ... Kernel panic - not syncing: Attempt to kill init! I do not know, why the igb driver is obviously not found. IMHO, the testing of the ide modules (to find the root file system) is caused by the file (inside the nfsroot) /usr/share/initramfs-tools/scripts/live-premount/modules which contains: modprobe -q ide-generic modprobe -q esp I've tried to add the igb module here, but nothing happened. Has the initrd to be rebuild? Thanks in advance, Gordon -- Compilerwarnungen von heute sind die Programmierfehler von morgen. (Quelle unbekannt)
Re: Problem with Intel igb network driver on client
Hi this is just from memory - so please take it with a grain of salt: On Tuesday 01 September 2009 07:49:22 Gordon Grubert wrote: > I've tried to add the igb module here, but nothing happened. > Has the initrd to be rebuild? Essentially yes. I think you need to chroot into your NFS-root where the new kernel was installed (or the module copied to). In there you need to run update-initramfs -k -u -v -v should tell you if the module made it into the initrd. If not you might need to tinker with the modules file of initramdfs. HTH Carsten
Re: Problem with Intel igb network driver on client
> On Tue, 01 Sep 2009 07:49:22 +0200, Gordon Grubert > said: > Supermicro X8DTU. Sorry, but I could not find the exact > network chipset description. On the server everything is > running fine. Run lspci (maybe from a live CD like grml) and you should see which network card this is. > In the nfsroot, the module igb.ko is present. Probably, it > was copied by make-fai-nfsroot from the server (same > architecture, kernel etc. on the server and the new client). > Inside the nfsroot, the module is listed in the file > /usr/share/initramfs-tools/hook-functions in the > function auto_add_modules(), too. Yes, in my initrd the igb driver is also available. It seems to be available by default. > Booting the client, the PXE boot process begins, the > initrd is loaded followed by: > Monting root file system ... ... > Uniform multi-platform E-ide-driver > ... ide0 ... > ... ide1 ... > Kernel panic - not syncing: Attempt to kill init! Mmm, did you spacify boot-live in your pxelinux/cfg config file? > I do not know, why the igb driver is obviously not found. > IMHO, the testing of the ide modules (to find the root file > system) is caused by the file (inside the nfsroot) Why should IDE modules be needed when trying to mount the nfsroot? Do you boot from network or from CD? -- regards Thomas
