@Jbob said in Printer doesn't appear:
@ITSolutions , the FOG client is capable of upgrading from any version. Even the initial release, v0.7.0 can (or at least should) upgrade to 0.10 without issue.
Great information to know, thank you for confirming that. I wasn’t sure, just initial troubleshooting given the information present.
IF you log into your Pushbullet account go to settings and click on “Create Access Token”, Copy the code it gives you. Then go to FOG and click on “Link an Account” under the pushbullet management and copy the code. You should then start receiving notifications.
What version of FOG are you using? What version of windows are you deploying? If you are using FOG trunk are you using the new client?
@Matthieu-Jacquart It could be that the version on the machine is old enough that it doesn’t understand how to update correctly anymore. @jbob has made some major changes with 0.10.x as it is now cross platform. If this is a single machine I would just reinstall the client if it is more, than you may need to push an install some other way.
@jbob might have a better answer though.
What version of FOG are you using? What OS are you deploying to?
From your log it appears that you are using an old version of the client, so I am assuming you are using an old version of the trunk. I would recommend updating as I am pretty printers are something that has been worked on in the client in the 0.10.x version.
@phil_guy We need you to upload the actual file, so that it can be examined and find why the partition is not expanding.
@Wayne-Workman said in Storage Node with Multiple HDD's (no Raid) possible?:
I’d also recommend sticking the OS on RAID 1, in addition to the RAID 10 for images.
I would recommend that but the OP mentioned he was having issues with RAID setting up RAID to boot from. So I was addressing the possible solutions to avoid RAID. Otherwise getting a hardware RAID card would solve the issue all together.
@ITSolutions this is true, but is the storage combined?
No the storage shows as 2 different nodes, when you create an image definition you tell it what group, either backup or default.
I think @george1421’s suggestion is the best choice, especially if you may be needing to dynamically add more storage at anytime. This would also allow for easier rebuilds in case of OS corruption.
What version of FOG are you running and what OS?
Are you using a re-sizable image type?
@x23piracy said in Storage Node with Multiple HDD's (no Raid) possible?:
Hi,
in normal i would take Raid but this Computer can only do Software Raid an Ubuntu 14.04.4 doesnt like it, Raid10 unpossible get a lot of error trying to install and Raid 1 with only 2 of the 4 disks has problem installing grub because the softraid is using a virtual device mapper thing.
3 Years Ago with Ubuntu 12 i could manage that problem after reading a lot of stuff.
I need a real raid or sas controller for this i think.
Regards X23
Or the other choice could be, if you have a fifth drive and ability to hook it up to your MB, is install Ubuntu to the fifth drive (even if it is small 40+gb) and then raid the 4x1tb as the /images partition in the system. This would allow you to do the raid, and separate the OS from the storage. I recommend this setup when possible. If you ever need to blow away the OS you won’t lose your images.
@Wayne-Workman You don’t need to have raid to use multiple drives on a single node. But the storage won’t be a seamless 4 tb, you could configure it to have each drive configured as separate groups/nodes on your server. I actually have a similar setup right now. I have my internal SATA drive setup with my normal images for everyday use, for speed. But I have a 3tb USB drive that I have as a second storage group and node on the same machine. I use the USB drive to capture backups of the tech workstations in case of a crash.
@Sebastian-Roth I am not saying that you cannot upgrade from 1.2 to trunk. I just have seen it break things, mostly on Ubuntu, which is not surprising due to them changing everything in each major revision. That is who your thinking about changing the web root in 14.04. In this case the OP is using Ubuntu. In my opinion it is rather painless to back up the DB and images(granted that is if you have a location to hold them all) and then do a ground up rebuild of trunk. I also usually advise using a separate drive/partition for the images, so that would mostly rule out the need for baking up the images. I guess it all depends on what your preference is or what is possible in your environment.
@cemicolin The menu item should be fog.fullwipe instead of Full Wipe
@BedCruncher said in Mount and Extract files from images:
I know in the case of adding something I would have to go in and recompress the image and basically get it back to the proper directory and named the proper way at least according to what FOG expects for its own operation. Long term that isn’t what I was thinking about. It was more to be able to at least open an image in a read only format and be able to get access to the image and all files stored within without needing a host box to restore the image to. Espescially if the host box I have on hand is sufficiently different from the original and it BSOD’s on boot.
When you restore to another box, you don’t have to boot it. What I do is place a second drive in a machine, pull the image to that drive then boot from the first drive, you can then access the files with in the image as a second drive on the machine, never actually booting the image. Then just recapture if any changes are made. No need for having the same hardware.
@pmonstad It won’t hurt to reset all the hosts, even if they are not having the issue.
@rhekkers Can you check /opt/fog/.fogsettings and see if the following lines are in it
snmysqluser="root";
snmysqlpass="this may contain a password";
snmysqlhost="p:localhost";
If you left the password blank then the snmysqlpass should look like this,
snmysqlpass='';
If it isn’t try blanking it out and rerunning the installer to see if it fixes the issue.
@pmonstad On the Host management page at the top there will be a link “Reset Encryption Data”
@rhekkers Can you check to see if mysql is running?
sudo /etc/init.d/mysql status
If not then try starting it, sometimes the installer doesn’t start it correctly
sudo /etc/init.d/mysql start
When going from 1.2 to trunk it is best to do a clean install, trunk has changed quite a bit and I have seen going straight from 1.2 to trunk cause many issues, someone else this morning also had the same problem. I would recommend doing a clean install of trunk and restoring the DB and images to the new install.
