Network naming has been troublesome for a bit. If you want to keep the
classic names, your boot string needs to contain:
net.ifnames=0 biosdevname=0
On Thu, Aug 4, 2016 at 10:09 AM, Alexander Thomas <
alexander.tho...@esaturnus.com> wrote:
> There was a discussion titled “example network scrip
When installing on a regular disk without raid use the partition number.
e.g. /dev/sda1. When installing on an array use the array number /dev/md/0
On Wed, Oct 30, 2013 at 8:16 AM, o...@v-brinkmann.de wrote:
> **
> > Markus Koeberl hat am 30. Oktober 2013 um
> 13:42 geschrieben:
> >
> > #inst
Another post-script I run checks the status of the MD sync. If the drive
isn't synced the boot sectors may not be on all member disks. I have a
LAST script that waits for arrays to sync before rebooting (good idea
regardless).
If you have multiple arrays you can loop this. I actually just have
I use a script to bypass partitioning since we have servers with 1-6 disks.
Anything with more than 1 disk gets raided, so I have to pass the
following to /tmp/fai/disk_var.sh which is read in by the grub setup. Make
sure you are using 1.2 metadata for your array. You don't have to bypass
partiti
>From memory. Fix for reality.
Partition and format your USB (if you are using an old fdisk, start at
sector 8 or later). Format as ext3.
Mounting as something like '/mnt/fai_usb' and the iso as '/mnt/fai_cd'.
Assuming /dev/sdb1 as your formatted USB device
mount -o loop /path/to/iso /mnt/fai_
Sounds to me like you have a network issue, NFS timeouts shouldn't occur
unless there are lost packets -- if the disk is stuck in I/O wait the NFS
process can still respond. Check your interfaces and switches for
dropped/errored packets. You should be able to host hundreds of clients
off a 1G, it
Increase the amount of nfs processes in /etc/default/nfs-kernel-server. Or
your disk is saturated (unlikely). I install dozens at a time with no slow
down.
RPCNFSDCOUNT=512
Increasing the count arbitrarily high will not affect performance.
However, over 1100 or so it starts to mess up the NFS
Add this varaible to your .var file in /srv/fai/config/class/ for whatever
class you want to inherit this variable.
# default values for installation. You can override them in your *.var files
MAXPACKAGES=2000
On Fri, Sep 21, 2012 at 10:49 AM, Katarzyna Myrek wrote:
> Hi
>
> I remember that I
tel wrote:
> Le 14/06/2012 19:00, Michael Senizaiz a écrit :
>
> What kernel are you using? Are you using 'boot=live'? The boot= tells
>> it what script in scripts/ to run after init, and only live and nfs will
>> use the rootserver variable.
>>
>
> Y
What kernel are you using? Are you using 'boot=live'? The boot= tells it
what script in scripts/ to run after init, and only live and nfs will use
the rootserver variable.
On Thu, Jun 14, 2012 at 11:43 AM, Nicolas Courtel wrote:
> Le 14/06/2012 17:28, Michael Senizaiz a écrit
This is occuring because the DHCP server isn't sending over ROOTSERVER, or
you are configuring with a static IP so rootserver doesn't get set by the
DHCP server.
Some of the networking bits must have changed in the debian kernel since
the documentation was written.
I got around this for USB/CD boo
I've read the documentation as well as the source code. It appears FAI
does not support Static network booting to the NFS root when a DHCP server
isn't available on that subnet. Additionally the documentation is wrong
for setting static IP's, as well as inconsistent with other parts of the
code.
12 matches
Mail list logo
