Failed vista image upload help
-
[quote=“the_duke, post: 26741, member: 23777”]I have fog 0.32 and am using a custom kernel. I did a full disk check and came back good. A friend told me to try this, not sure if it will work or not:“[FONT=arial][COLOR=#222222]saw some links that list NCQ compatibility. Also, just turning off NCQ can solve a lot of issues. Apparently, that’s turned off with a kernel parameter of:[/COLOR][/FONT]
[FONT=arial][COLOR=#222222]libata.force=noncq”. [/COLOR][/FONT][/quote]I don’t know if this has helped anybody else, but I tried it just for testing purposes and it seems that this argument is not correct. That doesn’t mean it won’t work for your scenerio as it could just mean I don’t have libata.force to actually send arguments loaded at my system’s boot time. This could also, if you have one, only be valid for SSD drives, and I don’t have any SSD’s that I can test with.
-
So what it sounds like is that since the full disk check came back good to go that these laptops just dont seem to want to work right??
-
I’ll go ahead and apologize before hand if I needed to create a new post here. I know that this is a really old post, but I have come back to these laptops and trying to deploy a vista image to them now that I have updated fog versions. I am using fog 1.2.0 on ubuntu 12.04. I have been successful at deploying linux mint 17, ubuntu 12.04 and 14.04 to these laptops. When I try to do a clean install of vista it seems to upload just fine, but on deployment, it starts going through the process;
checking os…windows vista
checking cpu cores…2
send method…nfs
attempting to send inventory…done
etc, etcgoes all the way down to changing hostname…done
updating computer database status
database updated
task is completed, computer will now restart, but it never actually deploys. Computer will reboot and black screen with missing OS.Any ideas or suggestions.
Again these are Lenovo SL500s
-
Vista is known NOT to work on 1.2.0.
If you want, update to SVN revision 2096 (1.2.0 was SVN revision 2094) and it should be fixed.
-
@Tom-Elliott oh ok, does it matter which method that I use to update to trunk?
-
@the_duke for that particular revision I’d say use svn.
-
@Tom-Elliott Ok, it got to the restarting apache2 for fog vhost and failed. Should I try to install again or is there something else I need to look at?
-
@Tom-Elliott Here is what came out in the terminal
- Starting web server apache2 *
- The apache2 configtest failed.
Output of config test was:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/authz_default.load: Cannot load /usr/lib/apache2/modules/mod_authz_default.so into server: /usr/lib/apache2/modules/mod_authz_default.so: cannot open shared object file: No such file or directory
Action ‘configtest’ failed.
The Apache error log may have more information.
-
@the_duke said:
@Tom-Elliott Ok, it got to the restarting apache2 for fog vhost and failed. Should I try to install again or is there something else I need to look at?
Well I’m glad it failed as it could’ve been disasterous. You svnd to the latest didn’t you? You need to checkout a specific revision. Use the command
svn co -r 2096 https://svn.code.sf.net/p/freeghost/code/trunk
If you want to try the latest you’ll most likely need to update your current Linux os.
-
@Tom-Elliott Yes I did, I’ll do this now
-
@the_duke
To fix those issues run:sudo a2dismod authz_default authz_default mem_cached; sudo a2enmod authz_core;sudo apache2 restart;
-
@Tom-Elliott Ok, installed revision 2096 and apache2 still failed. I then ran the commands that you posted and here is what came out:
Module authz_default already disabled
Module authz_default already disabled
ERROR: Module mem_cached does not exist!
jcsadmin@jcstest69:~$ sudo a2enmod authz_core
Module authz_core already enabled
jcsadmin@jcstest69:~$ sudo apache2 restart
Usage: apache2 [-D name] [-d directory] [-f file]
[-C “directive”] [-c “directive”]
[-k start|restart|graceful|graceful-stop|stop]
[-v] [-V] [-h] [-l] [-L] [-t] [-T] [-S] [-X]
Options:
-D name : define a name for use in <IfDefine name> directives
-d directory : specify an alternate initial ServerRoot
-f file : specify an alternate ServerConfigFile
-C “directive” : process directive before reading config files
-c “directive” : process directive after reading config files
-e level : show startup errors of level (see LogLevel)
-E file : log startup errors to file
-v : show version number
-V : show compile settings
-h : list available command line options (this page)
-l : list compiled in modules
-L : list available configuration directives
-t -D DUMP_VHOSTS : show parsed vhost settings
-t -D DUMP_RUN_CFG : show parsed run settings
-S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
-t -D DUMP_MODULES : show all loaded modules
-M : a synonym for -t -D DUMP_MODULES
-t : run syntax check for config files
-T : start without DocumentRoot(s) check
-X : debug mode (only one worker, do not detach) -
@Tom-Elliott sorry the sudo apache2 restart should’ve been sudo service apache2 restart
-
@Tom-Elliott Tried that too, here’s the output of that:
jcsadmin@jcstest69:~$ sudo service apache2 restart
- Restarting web server apache2 [fail]
- There are processes named ‘apache2’ running which do not match your pid file which are left untouched in the name of safety, Please review the situation by hand.
-
@the_duke can you reboot?
-
@Tom-Elliott Here is what it it is saying now:
Restarting web server apache2 [fail]
- The apache2 configtest failed.
Output of config test was:
AH00526: Syntax error on line 12 of /etc/apache2/sites-enabled/001-fog.conf:
SSLCertificateFile: file ‘/var/www/fog/management/other/ssl/srvpublic.crt’ does not exist or is empty
Action ‘configtest’ failed.
The Apache error log may have more information.
- The apache2 configtest failed.
-
@the_duke now run
sudo a2dissite 001-fog
. Then rerunsudo service apache2 restart
-
@Tom-Elliott Ok, now it restarted the apache2, but when I go to my web gui to update/install database schema, I get the update/installed failed
-
@the_duke please rerun the installer in whole. My guess is the Config file is not present as it failed to even restart Apache before.
-
@Tom-Elliott same thing