Posts made by xburnerx00

This is the grub.cfg on the USB. Where do I put the line? Near the top with the lines that say set? Do I add ‘set’? before the lines you asked me to try? Are the lines two separate lines? Sorry, for all the questions.

set myfogip=192.168.10.200
set myimage=/boot/bzImage
set myinits=/boot/init.xz
set myloglevel=4
set timeout=-1
insmod all_video

menuentry "1. FOG Image Deploy/Capture" {
 echo loading the kernel
 linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

menuentry "2. Perform Full Host Registration and Inventory" {
 echo loading the kernel
 linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=manreg
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

menuentry "3. Quick Registration and Inventory" {
 echo loading the kernel
 linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=autoreg
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

menuentry "4. Client System Information (Compatibility)" {
 echo loading the kernel
 linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=sysinfo
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

menuentry "5. Run Memtest86+" {
 linux /boot/memdisk iso raw
 initrd /boot/memtest.bin
}

menuentry "6. FOG Debug Kernel" {
 echo loading the kernel
 linux  $myimage loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=275000 keymap= boottype=usb consoleblank=0 rootfstype=ext4 isdebug=yes
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

menuentry "7. FOG iPXE Jumpstart BIOS" {
 echo loading the kernel
 linux16  /boot/ipxe.krn
 echo booting iPXE...
}

menuentry "8. FOG iPXE Jumpstart EFI" {
 echo chain loading the kernel
 insmod chain 
 chainloader /boot/ipxe.efi
 echo booting iPXE-efi...
}

@Sebastian-Roth said in Problems after adding storage:

storage=192.168.10.200:/images2/ storageip=192.168.10.200

Thank you for the reply.

Where exactly do I add this line? On the grub.cfg file on my USB boot? That is the only place I remember making changes on the drive when I followed the instructions from here.

Server OS: CentOS 7
FOG Version: 1.5.9-RC1

I recently installed a new hard drive to expand storage for images on the master FOG node. I followed the instructions here: Adding additional image storage space to FOG server. Everything seems fine with the install so I did a test image.

FOG captured the image to the new storage node and the target machine restarted and booted normal. One problem is in the Tasks menu, the machine stayed “In-Progress” (No screen shot of that.) I cancel it and check Images and it shows…

I figured it is a bug so we’ll see when the image is deployed. I set the task to target machine, machine picks up task, but I get this error…

Tasks shows that the task is stuck in progress…

This is where I am stuck.

Deployment of another image that is stored on the original storage space deployed with no problems.

Thank you.

Yes, the Dell Latitude 3189 are laptops that do not have internet ports and we had to use USB adapters. At that time, the version of FOG didn’t like same MACs for multiple machines. So the way I got around that was deleting the hosts since it was tied to a MAC from a USB and I was more concerned with just getting them imaged. I guess I deleted them prematurely. Unless I just overlooked something completely and did something wrong.

As for the deploy task ones, I’m not sure why they were stuck in there. They may have been ones that seemed to be giving me imaging problems and I turned off the machine before canceling it in the task menu.

MariaDB [fog]> SELECT * FROM hosts WHERE hostID IN ( 515, 401, 513, 529, 532, 584 );
Empty set (0.00 sec)

MariaDB [fog]> SELECT * FROM images WHERE imageID IN ( 32, 33, 13 );
+---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+
| imageID | imageName          | imageDesc | imagePath        | imageProtect | imageMagnetUri | imageDateTime       | imageCreateBy | imageBuilding | imageSize                                                                                          | imageTypeID | imagePartitionTypeID | imageOSID | imageFormat | imageLastDeploy     | imageCompress | imageEnabled | imageReplicate | imageServerSize |
+---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+
|      13 | DellOP3050         |           | DellOP3050       |            0 |                | 2019-07-17 15:31:36 | fog           |             0 | 524283904.000000:204800.000000:104857600.000000:16777216.000000:9948450.000000:40748851200.000000: |           1 |                    1 |         9 | 0           | 2020-05-11 12:54:12 |             6 | 1            | 1              |     19663157396 |
|      32 | Dell Latitude 3189 |           | DellLatitude3189 |            0 |                | 2020-03-14 09:27:01 | fog           |             0 | 554692608.000000:104857600.000000:16777216.000000:25425911808.000000:                              |           1 |                    1 |         9 | 0           | 2020-03-14 11:52:34 |             6 | 1            | 1              |     14588521696 |
|      33 | HP 400 G1          |           | HP400G1          |            0 |                | 2020-05-13 07:39:14 | fog           |             0 | 554692608.000000:104857600.000000:16777216.000000:8306813.000000:34024706048.000000:               |           1 |                    1 |         9 | 5           | 2020-05-13 08:05:09 |             6 | 1            | 1              |     16054171954 |
+---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+
3 rows in set (0.00 sec)

@Tom-Elliott said in Storage Group Activity data displaying wrong information:

UPDATE tasks SET taskStateID = 4 WHERE taskID IN (‘756’,‘905’,‘754’,‘771’,‘777’,‘908’);

Yes, thank you, that worked.

Any idea on what may have caused this, and how to avoid in the future?

MariaDB [fog]> SELECT * FROM tasks WHERE taskStateID IN ( 0, 1, 2, 3 );
+--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+
| taskID | taskName                   | taskCreateTime      | taskCheckIn         | taskHostID | taskImageID | taskStateID | taskIsDebug | taskCreateBy | taskForce | taskScheduledStartTime | taskTypeID | taskPCT    | taskBPM  | taskTimeElapsed | taskTimeRemaining | taskDataCopied | taskPercentText | taskDataTotal | taskNFSGroupID | taskNFSMemberID | taskNFSFailures | taskLastMemberID | taskWOL | taskPassreset | taskShutdown |
+--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+
|    756 | AutoRegTask - IS-STU-SL-03 | 2020-03-14 13:15:35 | 2020-03-14 13:28:02 |        515 |          32 |           1 |           0 | fog          | 0         | 0000-00-00 00:00:00    |          1 | 0000000000 |          |                 |                   |                |                 |               |              1 |               1 |                 |                0 | 0       |               |              |
|    905 | Deploy Task - HS-103-SD-17 | 2020-05-13 12:30:18 | 0000-00-00 00:00:00 |        401 |          33 |           1 |           0 | fog          | 0         | 0000-00-00 00:00:00    |          1 | 0000000000 |          |                 |                   |                |                 |               |              1 |               1 |                 |                0 | 0       |               |              |
|    754 | Deploy Task - IS-STU-SL-16 | 2020-03-14 13:08:01 | 2020-03-14 13:12:05 |        513 |          32 |           3 |           0 | fog          | 0         | 0000-00-00 00:00:00    |          1 | 0000000014 |   4.20GB | 00:00:50        | 00:05:04          | 3.264 GiB      | 14.12           | 23.680 GiB    |              1 |               1 |                 |                0 | 0       |               |              |
|    771 | AutoRegTask - IS-STU-SL-21 | 2020-03-14 16:05:24 | 2020-03-14 16:07:06 |        529 |          32 |           3 |           0 | fog          | 0         | 0000-00-00 00:00:00    |          1 | 0000000074 |   1.85GB | 00:00:11        | 00:00:03          | 415.80 MiB     | 74.05           | 529.00 MiB    |              1 |               1 |                 |                0 | 0       |               |              |
|    777 | AutoRegTask - IS-STU-SL-18 | 2020-03-14 16:27:08 | 2020-03-14 16:28:24 |        532 |          32 |           3 |           0 | fog          | 0         | 0000-00-00 00:00:00    |          1 | 0000000061 |  25.17MB | 00:00:55        | 00:00:35          | 23.26 MiB      | 60.50           | 100.00 MiB    |              1 |               1 |                 |                0 | 0       |               |              |
|    908 | AutoRegTask - HS-104-SD-13 | 2020-05-13 12:49:04 | 2020-05-13 12:50:03 |        584 |          13 |           3 |           0 | fog          | 0         | 0000-00-00 00:00:00    |          1 | 0000000000 |          |                 |                   |                |                 |               |              1 |               1 |                 |                0 | 0       |               |              |
+--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+
6 rows in set (0.00 sec)

Hard to see for me, but I see tasks that were set back in March 14, 2020 and May 15, 2020.

MariaDB [fog]> SELECT * FROM multicastSessions WHERE msState IN ( 0, 1, 2, 3 );
Empty set (0.00 sec)

I’ve never done Multicast sessions so I would think this should be empty.

Updated 1.5.7 to 1.5.9-RC1

No tasks.

@xburnerx00
Forgot to add version.

Version 1.5.9-RC1

On the dash board it’s showing I have queued and active tasks but that’s not true. Is there a way to reset this and show correct information?

Great point on flexibility @george1421, any idea on how to get the ipxe jumpstarters working? I have been using the USB to capture and deploy but I think I may need them eventually and it would be nice to use all features available if needed.

Thanks @Sebastian-Roth, changing those settings worked. The FOS USB works now. I was able to register and capture a test image from a laptop that does not have ethernet ports. I tested 3 different USB Ethernet dongles and they were all recognized. Saves me headaches of working on two different models of laptops numbering into the 200’s without ethernet ports.

Concerning the iPXE jumpstarters, I have the machines I tested on set to Legacy BIOS. Unless I am missing something, I do not see the reason why to use those now that the USB is working. As long as I can register a machine and capture/deploy now, I think that’s all I need. Right?

I created a FOS USB using a CentOS7 server running FOG 1.5.7 following the instructions provided here. I followed the steps specifically for CentOS7.

I can boot into the menu and upon selection it starts the process and then it errors out.


I also get these errors when I choose FOG iPXE Jumpstart BIOS or FOG iPXE Jumpstart EFI

Some guidance would be appreciated.

Thank you.

Very true. I submitted a request for a few more hdd. I wanted ssd but people in charge dont think they’re worth it for old machines.

Thanks again.

Just an update.

I did get another laptop and created an image with no issues. I also imaged the one that was giving me problems, and that seems to be working fine. No idea it was giving me problems on creating the image but if it works, it works.

Thank you for the reply. I am thinking it might be a bad hard drive. These laptops have been used and abused over the years, but I installed windows and software with no problems. I will have to grab another and see what happens.

I have an HP Probook 655 G2 Laptop that has data not being compressed when imaging. The original problem was that it was not PXE booting and was getting a no “No configuration methods succeeded” error. Researched this a bit and decided to try a USB BIOS boot. I got the usb boot working after some trial and error and can boot into FOG imaging.

The problem is when FOG is doing its preimage processes, I noticed that it is not shrinking partitions saying that the disk is a fixed size. FOG continues through the imaging process and gets to 100% then it errors out eventually ending with a message saying there’s not enough space on on server.

I used the same usb boot on another laptop and it created an image successfully. I have created multiple images from different models before, using PXE boot, and this is the first time I have had this issue.

Any help would be great. Thanks.

FOG version 1.5.7

Thanks for the information. Relieves some of my worries.

Just a general question, but has anyone ever had any problems imaging to or from SSDs using FOG? Also, is it possible to make an image from a standard spinning disk drive and then image to an SSD? And vice-versa? I have mini PCs from last year that have the spinning disk drives and we ordered same model machines for this coming year, but they have SSDs. Just wanted to know what the experience was like for someone who has gone through this.

Thanks