[quote=“Mark Pickard, post: 43751, member: 609”]… and how do I make sure it doesn’t happen on my latest VM install?[/quote]
Make sure you always have phpmyadmin installed and you’ll be back in the game…

Can you reproduce this again?? Install phpmyadmin (if not installed already), make changes to your settings till you get locked off. Let yourself in again and try again… We need to reproduce the error to be able to fin a fix!

Alright, I think I found it! It’s one single setting in the ‘globalSettings’ table…

Go to phpmyadmin, select ‘fog’ database, then ‘globalSettings’, find the value with ID ‘106’ and name ‘FOG_INACTIVITY_TIMEOUT’. I guess it is set to ‘fog’ (at least it was in the dump). Change it to ‘1’ (one) and you should be able to login again…

The rest is up to Tom I am afraid as I don’t know the web interface enough to see where this could happen. You said that it happended twice when you changed settings… Maybe Tom has an idea!?

But I am still wondering why this is only happening to you?! So many people out there using it and I’ve never seen anyone reporting this. How come??

Looks like this on my installation. But please be careful with this as I am not sure about what your offsite FOG nodes will do if the master is empty…

[CODE]# ls -alR /images/
/images/:
insgesamt 32
drwxrwxrwx 7 root root 4096 Feb 3 23:00 .
drwxr-xr-x 28 root root 4096 Feb 15 12:46 …
drwxrwxrwx 2 root root 4096 Mär 7 13:48 dev
-rwxrwxrwx 1 root root 0 Jan 17 10:11 .mntcheck
drwxrwxrwx 2 root root 4096 Jan 17 10:11 postdownloadscripts

/images/dev:
insgesamt 36
drwxrwxrwx 2 root root 4096 Mär 7 13:48 .
drwxrwxrwx 7 root root 4096 Feb 3 23:00 …
-rwxrwxrwx 1 root root 0 Jan 17 10:11 .mntcheck

/images/postdownloadscripts:
insgesamt 12
drwxrwxrwx 2 root root 4096 Jan 17 10:11 .
drwxrwxrwx 7 root root 4096 Feb 3 23:00 …
-rwxrwxrwx 1 root root 233 Jan 17 10:11 fog.postdownload[/CODE]

Which version(s) - old and new?

I can help you with the scripting. Do you prefer setting up a DHCP server (which you will need at some point anyway) or capturing the MAC addresses via tcpdump (you’d need a capture PC)??

Either way is a bit of extra work. DHCP pool setup or tcpdump capture, your choice… The good thing about the tcpdump solution is that you can use a laptop and walk from PC to PC, connect it straight to your laptop, capture boot it, wait for the DHCP request and off to the next…

On the other hand editing the boot menu and quick registrating all of them seems even less work. Which ever you choose it would be wise to follow some kind of order.

By the way, do you want to use random dynamic IPs (DHCP range) or static IPs assigned by your DHCP server?

What kind of PC do you try to run it on? Model? 32 or 64 bit CPU? Can you run memtest on other clients? Can FOG image/deploy this client??

Hmmm, interesting question! Concerning the default menu entry it depends on your FOG version. With 1.2.0 you’ll have to edit ‘/var/www/fog/lib/fog/BootMenu.class.php’. Find a like of code looking like this:
[CODE]$this->defaultChoice = “choose --default fog.local --timeout $timeout target && goto ${target}\n”;[/CODE]
Just change ‘fog.local’ to ‘fog.reginput’ (full registration) or ‘fog.reg’ (quick registration)… Save the file and boot your clients.

With never FOG versions you can just configure the default entry in the web interface (iPXE Menu).

I was thinking about automating your 150 new clients too. Do you buy them brand new? You probably will have to configure each and every client by hand to make it boot from network anyway, right?? If yes, you can just let it do the (quick registration) after you configured the BIOS settings…

If they are all configured to boot from network already then you could start them one at a time (in that order you want them to be). Have your DHCP server assign IPs from a Pool at this stage. You’ll see all MAC addresses in the log file on the DHCP server. Or if you don’t want to configure a DHCP server just yet you could also use ‘tcpdump’ to capture DHCP requests and get the MACs from there. A little shell scripting can then extract those MAC addresses and generate CVS to import into FOG. We should be able to help you with that if you need assistence…

[quote=“Tom Elliott, post: 43634, member: 7271”]Uncle Frank, cspence’s means no loops either![/quote]
Ohhhhh yes, now I see! Shouldn’t work till very late as I seem to overlook things too often then…

I’d vote for bash string manipulation…
[CODE]# Get All Active MAC Addresses
getMACAddresses()
{
macs=$(cat /sys/class/net/[^l][^o]*/address | tr ‘\n’ ‘|’)
echo -n ${macs%$‘|’}
}[/CODE]
Just make sure we use BASH (not SH) because the terrorist style (lol) shell glob does not work with SH…

sed, grep, tr and all the rest are very nice but we don’t really need them here, do we?
[CODE]… cat /sys/class/net/[^l][^o]*/address …[/CODE]

And still wondering about if ‘IFS’ is needed here. Sorry goto go now.

[CODE]… cat /sys/class/net/???*/address …[/CODE] kind of hackish but…

And I still wonder, why do we need the IFS here??

[quote=“Tom Elliott, post: 43626, member: 7271”]We have to know the exact path name, so it’s simpler to just use the tools that get that for us I think.[/quote]
I don’t think so…
[CODE]# Get All Active MAC Addresses
getMACAddresses()
{
IFS=$‘\n’
# Create a pipe-separated MAC List
for macline in $(cat /sys/class/net/*/address); do
# Add a pipe before adding more MACs
if [ -n “$mac” ]; then
mac=$mac|
fi
mac=${mac}${macline};
done
IFS=
echo $mac
}[/CODE]
No ip, no awk, no grep…

Not using any extra ip tools … /sys/class/net/*/address …

What do you mean by “boot to a VLAN”?? And what is a distorted registration window?

Screenshots? Error messages…?

Would it be possible to dump your whole FOG database and upload that dump file to this forum?? I’d love to push this data into my database to see if it looks me out as well… I hope there is no sensitive data in it. Please look through the file an delete password hashes before posting the file here!
[CODE]$ mysqldump --databases fog --user <your-db-user> -p > fog_dump.sql[/CODE]

[quote=“michieru, post: 43559, member: 3086”]Which version of FOG you are using? I am on 1.2.0 and I don’t see these options under image management.[/quote]
Hmmm that’s interesting. As you didn’t mentoin the FOG version in your first post I just searched the source of 1.2.0 and SVN version. FOG 1.2.0 doesn’t have any “Skipping partition” messages in the code as far as I could find. That’s why I suggested the setting.
Are you absolutely sure you use 1.2.0 on that server?? Maybe you updated kernel and initrd at some point??? Maybe check md5sums to see if you still use kernel/initrd coming with FOG 1.2.0
[CODE]$ md5sum fog_1.2.0/packages/web/service/ipxe/init*
27e9244f944ca596c0345f163f31cd22 fog_1.2.0/packages/web/service/ipxe/init_32.xz
87cb38f8f5d5636ca22a5bc6fa0d6684 fog_1.2.0/packages/web/service/ipxe/init.xz[/CODE]

[quote=“Clifford Raymond, post: 43552, member: 28730”]You are correct, I do see the same message. What does it mean when the file is corrupt? Do we have to reconfigure the whole server?[/quote]
What do you mean by “same message”??? Does the kernel image have the same md5sum??

I am sorry to say this but this forum is about FOG and things related to FOG. Don’t think a crashed hard drive should be discussed here.
That said I still try to give you a few hints that may be of help. [B]Be as carefully with this drive as possible![/B] Try connecting it to other computers (especially with different operating systems) to see if it comes up again. If not you might be able to disassemble it from its external case and try a different USB connector device or connect it straight to the normal ATA/SATA interface of a PC.
Depending on the outcome of all this you might end up having to recover data. ‘testdisk’ is definitely a great tool to look at… And lots of others. But this is a whole new (and way too complex) story. All the best with this!

Which partition setting? See here: [ATTACH]1776[/ATTACH]

If “Partition 9 only” is selected here that would be exactly what happens (skipping…)

[url=“/_imported_xf_attachments/1/1776_select_partitions.jpg?:”]select_partitions.jpg[/url]

Probably good to open a new thread for this and post your apache error logs (see Tom Elliot’s signature). I guess you’ve tried clearing browser caches??