openSUSE starting aid

dvice, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received

AW: openSUSE starting aid

! Frank P.S.: > Hope this helps. Do not hesitate to also ask on irc. Would love to. But currently the company firewall is between me and IRC... -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not

fcopy and /dev/null

.and this twice. After dropping into the half-installed system, /dev/null is there. Best regards, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy

AW: fcopy and /dev/null

tory”. Nevertheless, /target/dev/null now is present, with the same attributes as /dev/null . Best, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy t

AW: AW: fcopy and /dev/null

>You have to use >mknod --mode=666 $target/dev/null c 1 3 That was the key, now the error message is gone. Thanks! Frank -- Frank Morawietz IT Systems Administrator Global Computational Chemistry & Biology Healthcare | Discovery Development Technologies Merck Merck Healt

PXE boot with UEFI

an this be true? BTW: The very same configuration booted with PXE in legacy mode works perfectly. It starts fine and the whole installation runs through until the system is installed completely. Of course, it installed a legacy system, not UEFI, then. Thanks for any experience/advice/help, Frank --

AW: PXE boot with UEFI

s not accept options" does not express a problem. This message also appears when the install boot is successful (in legacy BIOS mode). Best regards, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you a

AW: PXE boot with UEFI

onnection refused error happened where ldlinux should be transferred. Is there anything else I could examine to diagnose further? Regards, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intend

Forgotten home dir

fore this point downloading and installing packages work. At this point it fails. Any ideas? Anybody else experienced this? Regards, Frank -- Frank Morawietz

AW: AW: PXE boot with UEFI

d successfully get every single file from the server in /srv/tftp/fai/ . Worked without any issue and on server side no refused nor any other error. So it does not seem to be a problem with the tftp server, right? Regards, Frank -- Frank Morawietz This message and any attachment are confi

AW: AW: PXE boot with UEFI

forward. (UEFI installation provides more issues - there is more to come...) Thanks to all who provided input and ideas! Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you

AW: AW: AW: PXE boot with UEFI

l workstations delivered that I plan to install with FAI... >The one similar set of symptoms I have run across in looking on the web >also worked in legacy but not uefi... turned out to be a >hardware/firmware issue on the client box. >Past this, unfortunately, I got nothing. Thanks a

AW: get-boot-info

N-IP’ when installing a two NIC workstation with only the primary one connected to the network. Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy th

AW: get-boot-info

> You issue is now fixed Great, thank you Thomas! -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents

fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

k with "dpkg -c" that it does not contain it. How do I get the livenet module for Dracut? Is this a FAI topic at all or is it a Debian problem? Sounds similar to the mail I am replying to, but any versions involved are more recent. Thanks for any advice, Frank -- Frank Morawietz

AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

terested what I did to cope with the errors in above log so far. Regards, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attac

AW: AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

dev/null >if [ $? -eq 0 ]; then >pkgs+=" dracut-live dracut-squash" >fi Are dracut-live and dracut-squash part of the newer FAI release? I can't find them in the Debian standard repos. Regards, Frank -- Frank Morawietz This message and any attachment are conf

RE: AW: AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

Thanks for your advice, Thomas. With the fai-project.org repos added on the install server followed by an update of fai to 5.9.4 "fai-setup -v -f" went fine and completed without errors! Regards, Frank -- Frank Morawietz This message and any attachment are confidential and may be

AW: dracut error during nfsroot update

%2F2017-June%2F011735.html>). > The solution then was to include curl in the nfsroot. Curl is installed in > our nfsroot, we are using the NFSROOT list shipped with the current version. > > Any ideas how to find out what is missing? Updating to FAI 5.9.4 fixed this for me. HTH, Frank

AW: Driver replacement

Hello Pasquale, if your compute nodes are identical and all of them need the Nvidia driver, you can use a basefile that already has Nouveau removed and Nvidia installed. Then there is no need for a Nvidia installation script at all. Just as an unconventional idea… Best, Frank -- Frank