Asus EEE PC Imaging Errors
-
Ok awesome sounds good. I am testing that theory now. I am trying to upload the same image i just downloaded. The image works fine. I am getting an error when it goes through it’s checks. It just reboots and removes the task. Testing now.
Is there a way to put a pause in it so that i can see the errors before it reboots?
-
@EAHarvey said:
Is there a way to put a pause in it so that i can see the errors before it reboots?
before i can answer that, i need to know what version of fog are you running
-
Version \1.2.0
-
@EAHarvey said:
Version \1.2.0
When you choose to upload, on the confirmation page - choose “Debug” instead of instant.
This will prompt you to hit enter at every step of the upload process to continue.
-
Sweet. I’m testing now to see what’s up. You guys are all Amazing BTW!! Thank you so much.
-
These are my options.
-
I see something about setting up a debug task. I’m going to try this to test also.
-
@EAHarvey I didn’t know that 1.2.0 didn’t have debug tasks… I apologize.
Can you consider upgrading to FOG Trunk, please? You might even find that your problem goes away.
-
I guess I’m not familiar with trunk. Different version than 1.2.0/? Where do i download it?
Forgive me for not knowing this, i was unaware of another version.
-
@EAHarvey https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
I recommend the SVN method. You should fully update your system before doing this, and backup your data beforehand also. There are steps in the article at the bottom for backing up your data.
-
Ahh ok, so this is like the currently developing version of FOG. More like a beta.
-
@EAHarvey Yup. But, it’s referred to in historical threads and sites abroad as “FOG Trunk”, so I call it that in order to keep those historical references accurate. But yeah, it’s beta. It’s all I use at work and at home. It’s MOST safely used with virtualization, but three of my organization’s fog servers are not virtualized and they are doing fine - we just don’t update those as often.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman beta implies that it has reached a point where it is being tested to be considered a release candidate, trunk is simply the development trunk. the central repo of all changes that have been brought into the mainline. while we try to keep the development trunk stable, it is not a finalized form and hasn’t necessarily been tested much at all, depending on how much has been committed to it on a given day.
I prefer to recommend upgrades to specific versions of the trunk if I can. an upgrade from 1.2.0 to svn revision 3652 should be pretty painless and has most of the new features that most users would notice. -
Ok awesome. I have it installed and running. Going to start some testing. I’ll let you guys know. Thanks so much for the great help.
-
lol now that i have updated my tftp sever is timing out,… Oh my.
-
what distro and version of Linux are you running fog on?
-
Ubuntu Server 14.04. I think it has to do with these eee pc netbooks. They have the atheros boot stuff. It seems to work on all my others. I’m going to keep testing. I have a working setup going so I’m not down production wise.
-
Everything is working properly so far except these little Asus EEE PC. I have also ran the single disk option for uploading and it works great. I guess i am going to have to figure out a sort of external imaging for the EEE PC. I don’t want to mess up my production server just for a few old netbooks. Thank you all for all your help.
-
I don’t believe you’ve mentioned what network boot file you’re using, but I’m going to assume it’s the default undionly.kpxe
sometimes the undionly.kkpxe works better, especially on buggy bios/pxe implementations. I’d give that a try before giving up on it. -
@Junkhacker said:
I don’t believe you’ve mentioned what network boot file you’re using, but I’m going to assume it’s the default undionly.kpxe
sometimes the undionly.kkpxe works better, especially on buggy bios/pxe implementations. I’d give that a try before giving up on it.@EAHarvey I would have suggested the exact same thing.
