Is the drive an Advanced Format Drive (4k)? It doesn’t make sense that it’s installed 32, but maybe 32 bit can’t support 4k byte sectors.
Can you set do a custom layout and make sure the drive formatting for Win 7x64 is setup for 2048?
Thanks,
Is the drive an Advanced Format Drive (4k)? It doesn’t make sense that it’s installed 32, but maybe 32 bit can’t support 4k byte sectors.
Can you set do a custom layout and make sure the drive formatting for Win 7x64 is setup for 2048?
Thanks,
Hello all,
I’m sure you’re all seeing the developer title under my name now, and I’m more than happy to develop for this.
For this reason, I think this post is appropriate and especially here than anywhere else.
I’m new to developing and I enjoy doing the work as I use FOG nearly everyday. I wanted all to know that, as I am new, I’m still learning how Blackout was building the system. I’m trying to maintain his code and add features I think are useful.
So I will be, slowly as it may be, adding features but I will not necessarily get to everybody’s stuff. If you have a feature request, please ask, but realize I’m brand new to the development of this project and need to learn the logic behind the new system so I may not be as quick as Blackout was. I’m doing the best I can and useful, and easy to implement, features I will attempt to add. Right now this is especially pertinent to the GUI as that’s the item, from what I can tell, mostly needing the work.
I hope I can please you for the most part, but am more focused on getting this completed as it has been quite a long time since a release happened.
I’m also working a full time position within a school district, which as many places (countries included) just started back up from the summer, so I’m working on this and busy at work. If I don’t make progress quickly enough, chances are I’m just busy at work. I try to help out on the forums as well, but I am human. I don’t know everything and will never claim to. I will give my help when possible. I make mistakes, and I have just a regular home with regular bills, etc…
This is all done completely in my free time (some of which my wife is starting to dislike, but excited for me as I enjoy this so much).
I’ve read through a few of the feature requests, and some of them I will try to add, some of them I won’t. I will try to post a Feature Add/Modded document, once complete, but again, my time is focused on coding/developing the system as a whole, so if I don’t get to full changelog documentation, I’m sorry. Maybe we can have the testers assist with that.
Thank you for the time on the soap box, and happy FOGing.
The only issue I for see with a backup like this is virus’. If you’re reimaging because of a virus this could potentially mean your imaging is useless for that machine. Just saying.
Also,
The fog user on the linux system may need the same password setup as in your config as ftp usually uses the local username for this purpose.
It most certainly does sound like, and very well could be, an issue with permissions.
Have you, since you received this error, tried uploading and x32 image?
Did your FTP, TFTP username password change recently?
It won’t have any problems mounting the /images directory as the mounted folder is actually:
/images/dev which is setup as rw across the board.
Where /images is mounted ro.
I’d check your GUI under Storage Management->All Storage Nodes->{YOUR STORAGE NODE} and verify the username and password are correct.
Then, check that Other Information->FOG Settings->TFTP Server that the [FONT=Ubuntu][COLOR=#333333] FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD are correct (from my knowledge these should match that of Storage Management).[/COLOR][/FONT]
So, it sounds like what ever is providing the dhcp address isn’t forwarding the boot request to your fog server. So everything is setup and, more or less, working.
On my router, this is done within the DNSMasq Options:
[CODE]dhcp-boot=pxelinux.0,HOSTNAME,IPADDRESS[/CODE]
Of course your results may vary, but you probably need something similar to this within your DHCP options.
I hope it helps as well. Are you using a custom init.gz as well? I’ve seen the skipping and even partial copies with my custom one. Though it’s still a work in progress. Uploads seem to work fine, but deploy’s don’t for some reason. That’s an area I’ll worry about later on though.
[CODE]mysql -u root -h <hostname> fog[/CODE]
If you have a root password for mysql:
[CODE]mysql -u root -pPASSWORD -h <hostname> fog[/CODE]
I certainly can, just need to figure out the best approach.
if rpm -qa|grep “maria” || rpm -qa|grep “mysql” or something along those lines.
Then I would say do the “from scratch” method you suggested as I haven’t any clue what else to try.
I don’t think CentOS is a problem. I run CentOS with no issues with fog. As I also performed my install with the same WIKI you did, it seems more like your system is just setup for noexec on the root filesystem which could be causing the issues you’re seeing. Essentially, the service FOGMulticastManager script is executing on a file, rather than a binary, it would cause the issues you’re seeing from what I can tell.
It’s almost as if you’ve got umasks turned on and/or the root filesystem is set as noexec within the fstab file.
I’d, still, highly recommend just logging in as root. Or sudo up to root with the command:
[CODE]sudo su -[/CODE]
Then run the installer.
You’ll be in as root and won’t need to append the sudo command to every statement.
Make sure you’re installing fog as user root.
Also, make sure you’re running the command chad’s stated as root.
If you’re logged in as another user, who has sudo privileges:
run the installfog.sh with:
[CODE]sudo ./installfog.sh[/CODE]
That’s what I was just going to say.
The reason it’s failing is because it can’t find the d1p1.img.001 file which, from the sounds of it, used to exist.
Update the image using another machine and then you should be good to go.
The next thing I Would check is that the images are actually pointing to that directory.
Under GUI, Image Management, Make sure the line for Image Files is pointing to your image name. So in your case it looks like it should contain:
[CODE]/images/1A3DellOptiplex360[/CODE]
and
[CODE]/images/755Athro[/CODE]
The other thing to check is that it’s of the correct type of image.
Based on the File you’re saying is failing it sounds like it’s a:
Multiple Partition, All Disk image.
I could be wrong.
Also, you said that the d1p1.img file exists.
Does d1p1.img.001 exist?
[quote=“Bill Arlofski, post: 10849, member: 1799”]Hi everyone. THANK YOU FOR FOG! Seriously.
Now that I realized there is a 0.33beta avail for testing, I am jumping in head-first.
Hope this is the correct place to report bugs or bug-like issues. If not, please direct me to the correct place.
I just grabbed 0.33beta today like so:
svn co [url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk[/url] freeghost
And ran the install script.
When the web UI updater ran on first logon I got the following errors:
[ATTACH]248[/ATTACH]
As I went through the menus, I cam across the following related errors:
[ATTACH]249[/ATTACH]
And on a host’s page:
[ATTACH]250[/ATTACH]
Google was of no help, and I also found nothing similar when searching the forums here.
Any help fixing this? Would love to get to putting 0.33beta through
Thanks! And thanks again for FOG!
edit: I have nightly dumps of the db, so I can easily restore a 0.32 fog db and run any tests requested if necessary.[/quote]
While I’m sure you’ve by and gone figured this out by now,
The reason you were seeing the OS field issue on the Image management page is because of the change From 0.32 to 0.33,
The OS type field is now assigned to the Image rather than per each host as was in the past. You’re seeing the error’s because the OS field on your images hasn’t been set. To fix the error’s, all you need to do is click on the image and assign the proper OS for it.
[url]http://www.fogproject.org/wiki/index.php/Moving_Between_Servers[/url]
[url]http://community.spiceworks.com/how_to/show/2631-moving-a-fog-server-to-new-hardware[/url]
[url]http://fogproject.org/forum/threads/moving-images.112/[/url]
I don’t know which will work best for you and your setup, but you should work.
Also,
Did the other server, by chance, get restarted before you started having the grey screen and such? Was tftpd-hpa service running? 12.04 has issues where tftp daemon starts before the NIC has an IP address, so it could potentially cause issues on the new server as well. Just a forewarning.
[url]http://fogproject.org/forum/threads/tftp-issues-but-fixable.779/[/url]