Posts made by BedCruncher

@Quazz
Do you have a link showing how to do that with the new FOG 1.3 boot menus?

Don’t know why it isn’t putting the images in the reply correctly. to clarify the above.

Boot Menu Entry

Menu Item: 
HDT

Description: 
Hardware Detection Tool

Parameters: 
kernel ${boot_url}/hdt/isolinux/hdt.c32
boot

URL Directory Listing

backgnd.png
boot.cat
chain.c32
display.png
hdt.c32
isolinux.bin
isolinux.cfg
memtest.bin
menu.c32
modules.ali
pci.ids
red.png

Ran across another issue with a different piece of software that I was trying to add to the boot menu. It’s the HDT Tool project. What I currently have done is attempted to use an old config and files from a previous PXE server while modifying the relevant boot menu options.

I’ve also downloaded a bootable iso from the HDT site directly and mounted it in the same way as was done with the DBAN instructions. My current HDT boot configuration looks like.
with the url located at that address showing

Can anyone offer advice/help on this?

I had simply modeled it after the entry that I put in above for DBAN.

going to close this out now… helps when you specify

boot

as the last option.

Question regarding trying to get “WHDD” setup for the boot menu so that I can test hard drives as needed from the server. I’ve current got a directory shared off of /var/www/html/whdd with

whdd.bzi
initramfs

in that directory and my FOG Boot menu entry looks as follows.

Can anyone point me in the direction I need to go to make this work? Thanks in advance.

@ITSolutions @Tom-Elliot

Thanks for that info. I’ve been a few revisions behind in my prod and nonprod servers. Just got around to doing that today at the recommendation of Tom.

Noticed this new section in the install script and was wondering if someone could point me in the direction of something that explains more about it? I would like to understand in more depth what is going on with this change

########################################################################################
   FOG has adjusted to using a login system to protect what can/cannot be downloaded
   We have detected that you don't have credentials defined to perform the backup
   If you would like the database to be backed up during install please define
   in your /opt/fog/.fogsettings file

   fogguiuser='usernameOfFOGGUI'
   fogguipass='passwordOfFOGGUIUser'

   You can also re-run this installer as:

   fogguiuser='usernameOfFOGGUI' fogguipass='passwordOfFOGGUIUser' ././installfog.sh
 ########################################################################################

Thanks in advance.

@Tom-Elliott
Sorry about posting it in the wrong subforum. I hadn’t updated in a bit as at the time 7470 was fulfilling all of the things I had thrown at it. So far the new 1.3.0-RC seems to be working awesomely.Will definitely keep you posted if I see something else. Thanks again.

So far that seems to have sorted it. It’s no longer escaping the quotes. I will keep playing around to verify, but so far we’re good. Thanks @Tom-Elliott

When making any changes to the parameters section while trying to get DBAN working per the link at Fog-DBAN I noticed that while playing around with it, if I made any changes and didn’t pay attention that it would add slashes to escape the quotes. If I made a second change then another ‘\’ would be added. This would keep happening every time. I am running

Centos 7.2
Kernel = 3.10.0-327.22.2.el7.x86_64
Fog = 1.3 Release 7470

Any help would be apprecieated

@Sebastian-Roth
No worries there. I just knew that you were looking at it some. It’s no biggie. I’ll try to track it down and work with it, but at a slower pace, don’t want to roll something like that out and possibly mess up my prod server. Thanks for all your help with this manner.

@Sebastian-Roth
Did you ever get anywhere with the alternate client/project that you were looking at? Just curious.

@x23piracy
Wow, google for the Mangle Translation Win.

@x23piracy
Sorry, I didn’t perhaps explain what I was referencing. I was meaning the comment you had posted prior to this last series of images. The one that was authored by Thorsten F.

@x23piracy
Where did you find that link? I’d like to run it through a translator to be able to see what it says.

@Sebastian-Roth @george1421
OK, I’ve run it through all of the steps that I can think of to get imagemount working. I’ve not succeeded in this endeavor.

To generate the image I first tried

cat /images/W7Px64PreSysprep/d1p2.img | pigz -d -c > /tmp/test_img.img

I’ve also tried to restore it using

cat W7Px64PreSysprep/d1p2.img | gzip -d -c | partclone.ntfs -r -C --restore_raw_file -s - -O /tmp/test_img.img

and

cat /images/W7Px64PreSysprep/d1p2.img | pigz -d -c | partclone.restore -C -s - -O /tmp/test_img.img

and tried to mount the image using

imagemount -d /dev/nbd0 -f test_img.img -r

imagemount -d /dev/nbd0 -f test_img.img -r -m /mnt -t ntfs

imagemount -d /dev/nbd0 -f test_img.img -r -m /mnt -t ntfs -v verbose

Do either of you have a thought about how to do anything different?

EDIT:
I did get the nbd kernel module loaded with my current kernel 3.10.0-327.18.2.el7.x86_64

@Sebastian-Roth
I’ve got the module build and loaded properly and am starting the restore process to see the it from beginning to end and trying to mount the image using imagemount. Will update once I know more.

EDIT:
@george1421 @Sebastian-Roth
Ran into a slight hitch with the kernel module. Didn’t realize when I rebooted earlier this AM that I had a kernel update. Had to redownload and recompile the nbd module. Still in the testing part of getting the image restored and mounted.

@Sebastian-Roth
I’ve got the proper kernel source downloaded and am building according to the link you provided. Will update once I have any info to add.