Re: fai 4.1 can't boot with multi ethernet box

2014-02-07 Diskussionsfäden Alex Mestiashvili

On 02/07/2014 02:08 PM, Thomas Lange wrote:

On Fri, 07 Feb 2014 13:56:15 +0100, Alex Mestiashvili 
 said:

 > Just tried the new FAI 4.1 installed on a wheezy box.
 > nfsroot has FAI4.1 packages installed.

 > It seems that dracut fails to detect the correct interface on a multi
 > ethernet server.
See https://lists.uni-koeln.de/pipermail/linux-fai/2013-March/010022.html
 From man dracut.cmdline:

ip=:_{dhcp|on|any|dhcp6|auto6}_[:[][:__]]

You can say: ip=eth1:dhcp
or even specify the MAC address with dracut.


yes, worked like a charm!, I start to like dracut :)



 > dracut: Mounted root filesystem 192.168.0.40:/srv/fai/nfsroot
 > aufs 3.2.x
 > warning can't open /etc/fstab: No such file or directory
 > dracut: Switching root
 > switch_root: failed to execute /sbin/init: Not a directory
 > Kernel panic - not syncing ...
This can also happen if it tires to do a NFS v4 mount. So, first check
if you see a mount request on the FAI install server. If yes, you may
have this NFSv4 problem. See these hints

https://lists.uni-koeln.de/pipermail/linux-fai/2013-January/009899.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676883#10



That was it, after fixing nfs options on the server side all works as 
expected.


Thank you a lot,
Alex



Re: fai 4.1 can't boot with multi ethernet box

2014-02-07 Diskussionsfäden Thomas Lange
> On Fri, 07 Feb 2014 13:56:15 +0100, Alex Mestiashvili 
>  said:

> Just tried the new FAI 4.1 installed on a wheezy box.
> nfsroot has FAI4.1 packages installed.

> It seems that dracut fails to detect the correct interface on a multi 
> ethernet server.
See https://lists.uni-koeln.de/pipermail/linux-fai/2013-March/010022.html
>From man dracut.cmdline:

   ip=:_{dhcp|on|any|dhcp6|auto6}_[:[][:__]]

You can say: ip=eth1:dhcp
or even specify the MAC address with dracut.


> dracut: Mounted root filesystem 192.168.0.40:/srv/fai/nfsroot
> aufs 3.2.x
> warning can't open /etc/fstab: No such file or directory
> dracut: Switching root
> switch_root: failed to execute /sbin/init: Not a directory
> Kernel panic - not syncing ...
This can also happen if it tires to do a NFS v4 mount. So, first check
if you see a mount request on the FAI install server. If yes, you may
have this NFSv4 problem. See these hints

https://lists.uni-koeln.de/pipermail/linux-fai/2013-January/009899.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676883#10

-- 

P.S.: I'm always very interested in user experiences with FAI. Can you
  please fill out the FAI questionnaire
  http://fai-project.org/questionnaire and send it back to me when
  you finished a project with fai.

regards Thomas


fai 4.1 can't boot with multi ethernet box

2014-02-07 Diskussionsfäden Alex Mestiashvili

Hi All,

Just tried the new FAI 4.1 installed on a wheezy box.
nfsroot has FAI4.1 packages installed.

It seems that dracut fails to detect the correct interface on a multi 
ethernet server.


in the past I could solve the issue by defining in the 
/etc/initramfs-tools/initramfs.conf the following:


 DEVICE=eth0


Is there a way to do the same with dracut ?

That's what happening during boot:

kernel is loaded via pxe, all fine

than I get the following

starting dhcp for interface eth0
...
links becomes ready,
dhcp failed

and so on till eth3,

after that I get the following:

dracut: Mounted root filesystem 192.168.0.40:/srv/fai/nfsroot
aufs 3.2.x
warning can't open /etc/fstab: No such file or directory
dracut: Switching root
switch_root: failed to execute /sbin/init: Not a directory
Kernel panic - not syncing ...


if I try with live nfsroot ( make-fai-nfsroot -l )

than at the end I am getting a shell and can see that faiserver is 
actually mounted to the client


and the very last line in /run/initramfs/idsosreport.txt is:

 dracut Warning: Could not boot.


any hint ?

thanks,
Alex










Re: UEFI boot

2014-02-07 Diskussionsfäden Thomas Lange
> On Mon, 3 Feb 2014 19:10:54 +0100, Meik Hellmund 
>  said:

> I tried a FAI installation with UEFI clients. 
> What I did in the end is surely not optimal. But perhaps 
> it's interesting for some people on this list 
> or you can give me some advice when I didn't do things 
> the "fai way".
Instead of trying PXE and grub efi I would ask the ipxe project what
kind of EFI support ipxe currently has.

-- 
regards Thomas