@sebastian-roth said in The initial storage node is much smaller than the disk space I gave my VM?:

sudo resize2fs -p /dev/mapper/ubuntu–vg-ubuntu–lv

That all did the trick, VM is now showing the full allocated disk space!

Thank you so, so much for your help, and also for giving me a little homework! I’ll read up on LVM as you said.

Thank you again for your help, I can’t thank you enough!

@chris_unit said in Controlling exit:

That way we can book to windows using exit to refind, and exit to GRUB UEFI for ubuntu.

You are on the right track on the other thread. The two refind options are what you need. This way you can target where refind looks for the boot files. You can include and exclude file paths to get what you need.

The grub4win implementation inside fog is bios only. BUT that’s not to say you couldn’t use a similar concept to the dual refind hack to leverage grub too. There are a few ways to go about it. I don’t have to deal with dual boot so I’ve never looked into streamlining that flow.

Hi @Sebastian-Roth,

Now works fine the FOG client 🙂

Thanks for your fast reply

@sebastian-roth The error with chkconfig is still here and I dnd’t found any topic about it in the forum, is any alternativ possible to this package ?

@jc35
mount /dev/sda1 /mnt
mount --bind /sys /mnt/sys
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts

chroot /mnt ./usr/sbin/grub-install /dev/sda

@chris_unit said in Intel NUC UEFI PXE menu:

and set the vendor class to PXEClient:Arch:00007
is that the right vendor class for an intel nuc?

I can’t answer that. I can tell you it will either be type 7 or 9 for 64 bit uefi computers.

If you want to find out what type the nucs are setup wireshark on a witness computer (second computer on the same subnet). Run a capture filter of port 67 or port 68 PXE boot the target computer. In the Discover packet sent out by the target computer, in the dhcp option 93 or 94 (sorry can’t remember at the moment) the target computer tells the dhcp server what type it is.

@sebastian-roth
I completed the upgrade without any major problems.
I had to reinstall some php packages that had been removed during the upgrade
(the comparison between the packages installed on the old version and the new one allowed me to reinstall them easily)

I also had to re-run installfog.sh because I had the same problem as here:
https://forums.fogproject.org/topic/15254/503-service-unavailable-after-debian-upgrade.

Also, unrelated to fog, I had to review the configuration of mariadb and more particularly the authentication mode of the “root@localhost” user.
Indeed the user “root@localhost” was still using authentication with a password, but the new method is to use auth_socket :

+-----------+------------------+-----------------------+-------------------------------------------+ | Host | User | plugin | authentication_string | +-----------+------------------+-----------------------+-------------------------------------------+ | localhost | root | mysql_native_password | XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | +-----------+------------------+-----------------------+-------------------------------------------+ | Host | User | plugin | authentication_string | +-----------+------------------+-----------------------+-------------------------------------------+ | localhost | root | unix_socket |

this is all I can say

@george1421 Well I’m kind of answering my own question here.

php -m | grep -e gettext -e mysqli

If they are installed on the OPs system then they should be visible with the php -m command.

@JasonNaughton As we had another person run into a similar looking issue I had a closer look at the code and might have found why this happens. Please find all the details here: https://forums.fogproject.org/post/144691

Hi,

It was my firewall, I have rebooting a rule and now all is fine.

Thank u

@chris_unit With some solid Linux knowledge you surely can convert an LVM install to a plain one but probably re-installing is a lot faster if the system is not highly customized.

@chris_unit said in mysql not starting when trying to install 2nd time:

did you install on 7.2?

I haven’t. Somehow thought this was a typo when you first mentioned version 7.2. Quoting from: https://mirrors.xtom.de/centos/7.2.1511/readme

This directory (and version of CentOS) is deprecated. For normal users,
you should use /7/ and not /7.2.1511/ in your path. Please see this FAQ
concerning the CentOS release scheme:

https://wiki.centos.org/FAQ/General

If you know what you are doing, and absolutely want to remain at the 7.2.1511
level, go to http://vault.centos.org/ for packages.

Please keep in mind that 7.2.1511 no longer gets any updates, nor
any security fix’s.

Sorry but we don’t have enough people to work on FOG for it to support officially deprecated OS versions.

@Sebastian-Roth you put me on the track!

The bios was configured in legacy bios first, I switched to uefi first and it works!

Thank you!

@julio said in démarrer une machine via le réseau:

@george1421 désolé george pour le dérangement, j’ai trouvé le problème à ma solution tout seul ne prend pas en compte mes messages et mes images stp. merci bien

C’est bien aussi de donner la solution au problème. Cela peut servir à d’autres personnes. Merci.

@sebastian-roth That solved the issue for me. Thanks!

@kyl Could just be a PATH issue then. Try /bin/touch instead of touch on your next test.

@Generalcanada Not exactly sure but maybe this post might help you: https://forums.fogproject.org/post/143080

@OmegaXis Strange error. Have never seen this before.

@tom-elliott salut tom et ici ca veut dire quoi et comment je pourrais resoudre cela??? merci bien

@george1421 said in dnsmasq won't start automatically. [SOLVED]:

@fog_newb Well there are really two commands you need to use.

Enable the service to start every reboot systemctl enable dnsmasq To start the service now systemctl start dnsmasq

These are two distinct actions and one doesn’t depend on the other.

@george1421

Thanks. I have used both of those commands before trying to get it to autostart on boot. I haven’t used them since running sudo systemctl enable dnsmasq , which was the one that got dnsmasq starting on boot for me. Perhaps since I used those commands prior it is all good?

I went through my bash history and saw I almost used sudo systemctl enable dnsmasq I had the syntax messed up though. I used sudo systemctl dnsmasq enable

I am really starting to like Linux. I digress, I am mostly a casual so I doubt I will ever have it on my daily driver but I am thinking about trying it on a laptop. I don’t know though, sometimes, I just like to point and click. 🙂