Posts made by DarkEnergy

In order to make it work in the way I want I converted the fog directory into a sub directory and place your code in the directory above. Still I think it should be possible to create a virtualhost site within Apache with a conf file to be accessible directly without crashing because it cannot find the rest of the configuration. Is this possible?

Thank you for your response Wolfbane8653.

I don’t think the changes affected my system on a negative way as I noticed that FOG does not create a site in Apache. It is just in the directory which it is browsable by navigating to it by putting the path xxx.xxx.xxx/fog. If I am creating a site and a config file for FOG with the directive:
DocumentRoot /var/www/fog

Shouldn’t that place fog’s folder as the root for the directory and look down the tree? It seems as if there is a bug in the code. The site shouldn’t have to go out of its container to look down the tree.

I have being using FOG for about 2 months and everything was working fine until today. I need to deploy some images on the rush and I noticed an error on the dashboard:
Disk Information
Failed to connect to
DefaultMember
I also noticed that all the information for the dashboard is missing. I tried to boot one of the system to be image and the system could not find the boot image.I tried to removed the storage and adding it again, with the same result. I also tried rerunning installfog.sh with the same result. I do think I made a mistake somewhere when I deleted a folder under /var/www/fog.rev that was right beside of /var/www/fog. I also made changes to Apache2 by configuring FOG site to the default 80 instead of xxx.xxx.xxx/fog. I am not sure if any of this changes affected the system but, for what I can see if the storage is not found then, nothing will work.

I am also including images for a new system registration which just hangs and an image for an old systems that is already registered and need to boot to PXE to acquire the image.

If any one have an idea how to fix this please let me know.

[url=“/_imported_xf_attachments/1/1559_FOG_Dashboard.png?:”]FOG_Dashboard.png[/url][url=“/_imported_xf_attachments/1/1560_IMAG0309.jpg?:”]IMAG0309.jpg[/url][url=“/_imported_xf_attachments/1/1561_IMAG0310.jpg?:”]IMAG0310.jpg[/url]

Update:

Rescued the drive by going to Seagate and downloading SeaTools then performed a low level format. I got at least one of the drive back in business. Will try again to do image and deploy and see what give.

Here is an update, perhaps developer can look into it if they are monitoring this forum.

All the systems that are having the problem are using Seagate Barracuda ST380815AS 80 GB 7200.10 with firmware 3.CHH. It is killing the drives making them inoperative. So far I have three computers with dead drives. The drives are registered in the BIOS because the logic board is doing the connection but when installing Windows 7 manually, the installation is unable to see the drive. I also ran a live CD to see if the drive is there and it is not. Is there anyone that knows how to look a the logs in and for FOG? And if possible is there a way to bring the drives back working? Those system were working properly until the new image was deployed to them. I have replace the drive with a different one in the systems giving the issues and they are now working. It seems to be some kind of comparability issue, more like a bug that is killing the drives.

@PA317
I would recommend you try to install Windows manually and see if Windows finds the HDD. If not, then, you are on my boat with a dead drive in the bay. RPL the drive with a different one to see if that works.

[quote=“Julianh, post: 39299, member: 24986”]I had this, drove me nuts. Believe it or not the solution was to do a “fast wipe” of the disk before imaging down.[/quote]

That does not sound like that will fix the issue. I am able to restore the image to the same client but only that specific client. If the image is generalized then the image should be distributable to any other system which it is not the case. I will give it a go and see what happens.

Your problem seem very close to mine. After uploading the image to the server, the clients are unable to downloaded. The systems goes basically through the same process you showed in Youtube. Once it does the blinking, it just reboot to a missing operating system error. I am not sure what is the issue. Or at least I would like someone to point me in the right direction to see if there are any error logs somewhere in FOG. Kinda new to FOG too.