root@fog:~/fogproject# git branch
* dev-branch
root@fog:~/fogproject#
Posts made by Shadow00Caster
-
RE: Unable to capture image, previously was able to
-
RE: Unable to capture image, previously was able to
@Tom-Elliott Did a git pull to latest, installfog.sh failing on Setting up and starting MySQL, nothing changed, worked with RC5.
-
Unable to capture image, previously was able to
Server
- FOG Version: 1.3.1-RC-5
- OS: Debian 7 32bit
Client
- Service Version:
- OS: Windows 8.1 64bit
Description
Trying to capture an image of a VM that I was previously able to, now getting:
Fatal Error, unable to find size data out on /dev/sda2. Cmd: ntfsresize -f -i -v -P /dev/sda2Image is setup as a single disk, resizable, all partitions. Disk has system reserved (default win install) and C partition.
Any help would be appreciated.
-
RE: Stuck at bg.png / Issues with Lenovo X1 Carbon (6th gen) & Lenovo Onelink+ dock (RTL8135 USB)
@Sebastian-Roth @george1421
I commented out the line and was able to get to the boot menu, as soon as I hit perform full registration its just a black screen with bzImage… 0% at the bottom.@Wayne-Workman
I tried a few of the different ROMs, mostly to the same conclusion :/.
Output of ls:
root@fog:~# ls -lat /var/www/fog/service/ipxe/
total 48684
-rwxr-xr-x 1 fog www-data 6995328 Aug 2 13:56 bzImage32
-rwxr-xr-x 1 fog www-data 7097776 Aug 2 13:56 bzImage
-rw-r–r-- 1 fog www-data 16501540 Aug 2 13:56 init_32.xz
-rw-r–r-- 1 fog www-data 18507592 Aug 2 13:56 init.xz
-rw-r–r-- 1 fog www-data 1221 Aug 2 13:55 advanced.php
-rw-r–r-- 1 fog www-data 21280 Aug 2 13:55 bg.png
-rw-r–r-- 1 fog www-data 719 Aug 2 13:55 boot.php
-rw-r–r-- 1 fog www-data 234697 Aug 2 13:55 grub.exe
-rw-r–r-- 1 fog www-data 25340 Aug 2 13:55 memdisk
-rw-r–r-- 1 fog www-data 1839104 Aug 2 13:55 memtest.bin
-rw-r–r-- 1 fog www-data 20958 Aug 2 13:55 refind.conf
-rw-r–r-- 1 fog www-data 205192 Aug 2 13:55 refind.efi
drwxr-xr-x 3 fog www-data 4096 Aug 2 13:55 .
drwxr-xr-x 3 www-data www-data 4096 Aug 2 13:55 …
drwxr-xr-x 2 fog www-data 4096 Aug 2 13:55 oldAt this point I think I am just going to old school this thing since it’s the only instance of this particular machine and every other machine that I image regularly has no issues.
-
RE: Stuck at bg.png / Issues with Lenovo X1 Carbon (6th gen) & Lenovo Onelink+ dock (RTL8135 USB)
@Wayne-Workman
Image: http://i.imgur.com/ipu55xH.jpgOutput from boot.php in browser:
#!ipxe
set fog-ip 10.1.1.254
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://10.1.1.254/fog/service/ipxe/ --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 5000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://10.1.1.254/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot -
RE: Stuck at bg.png / Issues with Lenovo X1 Carbon (6th gen) & Lenovo Onelink+ dock (RTL8135 USB)
@george1421 It’s set in legacy buis mode, uefi is “disabled”, secure boot is disabled, os defaults is disabled.
@Wayne-Workman I remove the bg.png file as suggested, however now after the boot.php… ok, it’s stuck at /fog/service/ipxe/… 80% -
Stuck at bg.png / Issues with Lenovo X1 Carbon (6th gen) & Lenovo Onelink+ dock (RTL8135 USB)
I have been trying to image a new Lenovo X1 Carbon (6th gen) using the Lenovo Onelink+ dock (as well as a Lenovo USB 3.0 eth adapter) and have not been able to get past initial loading; Adapter is Realtek RTL8135 USB.
Initially my DHCP option was set to undionly.kpxe and I was stuck and initializing devices, so a little searching led to switching to undionly.kkpxe which got me past that problem. The next issue was I was getting stuck at http://<ip>/fog/service/ipxe/boot.php (note that the tftp of default.ipxe prior to the http was “ok”) at 90%. After some more searching I found something that noted to turn off the ipxe menu options for hide and hide menu, I only had hide menu and advanced menu login enabled so I disabled both. With those disabled, I now got past boot.php stuck at 90% and get stuck at http://<ip>/fog/service/ipxe/bg.png at 12%.
My setup works with varying other systems through a wide range of dated hardware without issues, this is the only device giving me a boot problem.
I am running:
Debian 7
FOG version 1.3.0-RC-5 (git) / SVN Revision: 5943
bzImage version: 4.6.4
bzImage32 version: 4.6.4I have tried all the different kernel variants to no avail, undionly.kkpxe gets the furthest, any advice is greatly appreciated.
-
RE: Thinkpad e560
@Tom-Elliott So I did a few things along the lines of your suggestion.
- I took the drive from the laptop and threw it in the Dell workstation, imaged, no boot, put the drive back in laptop and still no boot (me thinks drive at this point)
- Grabbed an SSD from an old laptop which I had imaged with Fog previously but laptop died (drive is fine), threw that in laptop and it imaged and booted like normal.
The drive came with an operating system installed on it, but I suppose it could be bad. It’s a 512GB SanDisk X400.
@george1421 I just load necessary drivers after booting, the Dell drivers are all generic device drivers that exist within Windows Update and it works without issue, Lenovo has a Software Update utility that is a 1 click run and all necessary drivers are downloaded and installed.
Edit: Like I said I have an identical model coming this week which I will test on, could be an issue with the drive since I was able to image a different drive on the laptop, so it appears the laptop is functioning normally RE Fog compatibility.
-
RE: Thinkpad e560
@Tom-Elliott No, it’s a 7200RPM drive, I could throw in an SSD and test, do you think that would make a diff?
-
RE: Thinkpad e560
@Tom-Elliott Before updating to 1.3.0, should I create a new image of using 1.3.0? Note that I just deployed this same image to a Dell workstation without issue (on 1.3.0) pxe booted, partcloned, rebooted into Windows 8.1 Pro.
@george1421 I use a master image and then do drivers, never had any issue doing it this way and I have been using Fog for over 7 years. I will attempt the debug suggestion and reply with results.
-
RE: Thinkpad e560
@george1421 Questions answered in order:
- Yes it appears to image correctly, meaning it pxe boots and goes through the partclone processes just fine then exits and reboots.
- I have manually selected Windows Boot Manager and the drive, same result. I have also set the drive first and gotten the same result. All my other machines are set to network boot first, which loads fog, and then fog boots from disk, this has never had any issues.
- First time deploying to this model and device (I currently only have 1 device of this model but another arriving shortly which I will test with as well).
- Lenovo ThinkPad E560
- No, it’s a 500GB SanDisk SSD
- Windows 8.1 Pro
-
RE: Thinkpad e560
I am having the exact same problem.
I was using 1.2.0 and was getting the non-descriptive error “Unable to register due to these reasons:” (no reasons specified). Note that this 1.2.0 installation has been used successfully with many different Lenovo and Dell model workstations and laptops for Windows 7 and Window 8.1 for the past 2 years. I attempted first to update the kernel to the latest through the web interface, which just hung at transferring to TFTP so I downloaded it and manually put it on the server and ensured the kernel files owner, group and permissions were correct (both matching existing and per the documentation).
I have now upgraded to latest 1.3.0 from git following the documented installation/upgrade process, all worked flawlessly (props to that). I then proceeded to image the laptop with the now upgraded instance of Fog which worked normally, except upon booting from disk it just sits at the blinking cursor in the top left.
I have confirmed that UEFI is “disabled”, in that boot is set to legacy only, there is no drive configuration options (such as raid), secure boot disabled, and os defaults disabled (these are all the common bios factors).
Any assistance would be greatly appreciated.
I have taken screenshots and pictures of what I believe is all relevant information needed that can be viewed here: https://drive.google.com/folderview?id=0B9ZqDYezvotjenJRNnVyV2RVYW8&usp=sharing