Latest FOG 0.33b
-
Did you recently remove a location? It sounds like it’s throwing the error because it can’t find the location within the database anymore. I’m not seeing the same error though. I’ve added the location plugin, created a location, joined a system to the location, deleted that said location, and took a look at the host again. It just has a blank spot where the location dropdown should be.
Are you on the most current revision by chance?
-
I haven’t removed any location. I updated earlier today. I just now updated again to version 1415 and I am still having an issue. Also when I try to image it boots up to partclone and then exits without imaging.
-
I have a, sneaking, suspicion that the “partclone” issue you’re actually seeing is really a “partimage” problem. Chuck added a new flag a few revisions ago, and part of that “flagging” forced images currently on the system to be labeled as “legacy” images. This is so people can, more easily, upgrade from 0.32 to 0.33 without much issue. Its intent is to make a more seamless upgrade process, but for those of us already on 0.33b with partclone images, it forced all of those images to be “legacy.” We simply need to update our images to unflag them. This can be done by enabling “FOG_LEGACY_IN_GUI” under FOG Configuration->FOG Settings, then choose your image and change the PartImage parts to PartClone.
The location issue I’m looking into to try to replicate so I can help you better.
-
Here is what you really ask for. It seems that it does not see the second drive. Sorry for the confusion. I was trying to do to many thing at once. i really appreciate this.
[url=“/_imported_xf_attachments/0/630_IMAG0055.jpg?:”]IMAG0055.jpg[/url]
-
from that window, try running
[code]fdisk -l[/code] -
Here you go.
[url=“/_imported_xf_attachments/0/631_IMAG0056.jpg?:”]IMAG0056.jpg[/url]
-
Based on that Image, I am going to go with the 80GB drive is your SSD while the 1TB drive is the “extra storage” drive. Is this correct?
First things first, it’s recognizing the first drive (/dev/sda) as the 1TB drive, while the it’s recognizing the second drive (/dev/sdb) as 80GB. My guess is that channels these drives are connected to is the issue. It probably display’s similarly within the BIOS options as well. (First Drive as 1TB, second as 80GB).
-
The ssd is in SATA port one and the 1TB is in port two. I have a DVD drive in port zero.
-
[quote=“erod20, post: 24928, member: 23205”]The ssd is in SATA port one and the 1TB is in port two. I have a DVD drive in port zero.[/quote]
Personally, i’ve always put my boot drive on sata port 0, then data drive on sata 1 and dvd on sata 2. Try moving them around… -
r1417 released.
Remove HostMAC HostMACManager class files as there’s already something there (MACAddressAssociation.class.php). Other tweaks as well. FOG Core is using Class files now as well instead of direct calls to the DB. Add’s OUI and OUIManager class files for doling out the MAC manufacturer. Add’s some more documentation to the files. Looking pretty hard at the FOGCron class as it doesn’t appear, to me, anything actually is using it, nor do we really need to as ScheduledTasks are already done.
-
Hey Tom,
thanks for the great work you do. I installed FoG 0.33b for my projekt at work and have most issus that are describben here in this Forum. I read the you fix all of this issues that i have but tell me please how can i fix it on my FoG?? Do i have to download and replace some files or do i have to do it by myself?
Greetings
Andy -
[quote=“Andy783, post: 24937, member: 23069”]Hey Tom,
thanks for the great work you do. I installed FoG 0.33b for my projekt at work and have most issus that are describben here in this Forum. I read the you fix all of this issues that i have but tell me please how can i fix it on my FoG?? Do i have to download and replace some files or do i have to do it by myself?
Greetings
Andy[/quote]Andy,
I’m a little confused by what you’re asking. You state you’ve installed FOG 0.33b at work, but I’m not quite sure what “errors” you’re having. You said you have most issues that are described in this thread. That’s not really descriptive as I’ve been doing my best to fix the errors/issues that have cropped up.
When you installed FOG 0.33b, how did you install? Did you do it through SVN? Did you do it through a tarball file?
If you did it through SVN, all you need to do to update to the latest revision is cd into the directory containing the folder, usually trunk and run the svn update command:
[code]cd trunk
svn update[/code]If you did it through a tarball, download the latest from my website:
[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]. Extract the file and cd into the directory:
[code]wget --no-check-certificate https://mastacontrola.com/fog_0.33b.tar.bz2
tar -xjf fog_0.33b.tar.bz2
cd fog_0.33b[/code]Then re-run the installer:
[code]cd bin
./installfog.sh[/code]It will update your FOG installation.
-
r1418 released.
Set timezone in system.php if it’s not set in php.ini, set’s to UTC if it’s not specified.That’s it.
-
r1419 released.
Fixes Client Updater service so it can be disabled/enabled properly.
-
r1420 released.
Major change for this is Plugins…again.
I’ve removed the need for the run.php file as the initialization of the data should be the same. Right now the file assumes a plugin makes a schema change, but I don’t think there’s more than the two plugins we currently have (Capone and Location). So this revision moves the data necessary from the run.php files of both plugins and adds them directly into the plugin management page.
Also, this revisions adds the “image name” lookup feature to the Host search information. You can now search hosts by what groups they belong to, the image names, host names, serials, etc…
Hopefully all will enjoy.
-
I created a new image after I changed the ssd to port 0 and the mechanical drive to port 1. It restores the ssd but if the mechanical is bigger than the original it skips it. I have not tried a bigger ssd yet.
-
r1421 and 1422 released.
1421:
Changes FOG PXE Settings category to FOG Boot Settings. Fixes a reference to a deleted file (HostMACManager) so it points to the right place, sorry booting was broken for a little bit there. I only just found out.1422:
Just makes sure the reference label is done correctly for the MACAddressAssociation fields. -
Tom,
It looks like fog is looking for the wrong file names for the image of the second drive. Is my config wrong or is this a bug? In the pic you can see that it wants d1p2 and d1p5 but when I created the image it made d2p2 and d2p5.
Thanks
[url=“/_imported_xf_attachments/0/633_IMAG0057.jpg?:”]IMAG0057.jpg[/url]
-
d1 means disk one (the first disk it finds (/dev/sda))
d2 means disk two (the second disk it finds (/dev/sdb))
p# means the partition number’s it recognizes.From the picture you’re showing,
d1.mbr (the mbr backup for disk one.) is correct.
Disk one (from the pic) is only one partition on it: (d1p1)
Disk two has two partitions, /dev/sdb2 and /dev/sdb5 is my guess based on the labels of the image files.
Is this what you’re seeing when you run
[code]fdisk -l[/code] since changing ports? -
Disk two has sdb2 which is extended and sdb5 which is the Ntfs partition. That is correct.
