Posts made by jackley

[quote=“ianabc, post: 30865, member: 24548”]Hi Jackley, Toms response was to Chuck Sites above, there was too much going on in this thread :). Do you see anything in the ipxe directory (e.g. /var/www/html/fog/service/ipxe - you might have a slightly different web root). The Add Kernel function should drop the file you are uploading in there I think.[/quote]

There is a bzImage there, but it’s from 9:17 AM today. I just tried to install a new kernel, it doesn’t appear to be updating. Below is the stat output for bzImage:

[CODE]/var/www/fog/service/ipxe$ stat bzImage
File: ‘bzImage’
Size: 6090592 Blocks: 11896 IO Block: 4096 regular file
Device: 801h/2049d Inode: 786936 Links: 1
Access: (0644/-rw-r–r–) Uid: ( 1000/ fog) Gid: ( 33/www-data)
Access: 2014-06-19 09:14:09.555283765 -0400
Modify: 2014-06-19 09:14:09.611283767 -0400
Change: 2014-06-19 09:14:27.151284163 -0400
Birth: -
[/CODE]

[quote=“Tom Elliott, post: 30860, member: 7271”]This sounds like it’s not exiting to the HD properly. Perchance, is your SATA Controller setup for IDE, AHCI, or RAID? I’ve heard reports (other’s please confirm if you can) that the Controller type can play into the “exit” mode options and use.[/quote]

I believe I got this to work by updating the DHCP, thanks all. Now I’m having a new issue.

When I go to install a new kernel, the progress hangs at “Starting Process…” with a spinning gear.

[quote=“Fhajad, post: 30800, member: 24675”]Do you have your DHCP server options set correctly?[/quote]

Where can I verify these settings?

Where can I find the dhcp sever settings?

What should be under [FONT=Ubuntu][COLOR=#555555]FOG_PXE_IMAGE_DNSADDRESS, if anything? That field is blank. [/COLOR][/FONT]

Running Ubuntu 13.10. Upgraded from a FOG beta to 1.1. When I go to boot a laptop from the FOG server, I get:

“TFTP.
PXE-M0F: Exiting Intel Boot Agent
Selected Boot Device Failed.”

I was able to tftp into the server and get undionly.pxe. Verified the username/password are correct under the FOG System Settings > FOG Settings > TFTP Server.

[quote=“Tom Elliott, post: 23051, member: 7271”]Try changing the image type to multi-part non-resizable.

The reason it’s not working for you, is resizable is expecting only two partitions. The first partition it creates/searches for is the 100MB partition naturally created on a fully fresh install.[/quote]

Thanks, I’ll try that.

[quote=“Tom Elliott, post: 22873, member: 7271”]From looking at your partitioning table, it appears your /dev/sda1 is not the normal 100mb partition but rather a 350mb partition. Are you trying multipart image or resizable?[/quote]

Re-sizable.

[quote=“Tom Elliott, post: 22821, member: 7271”]I’m working on getting GPT support working in 0.33, but 0.32 does not support it. So yes, unfortunately, you will need to have an image that is created under MBR style.[/quote]

Does our image need to be created using MBR or does the destination need to be formatted with MBR? I formatted the disk with MBR, but the issue isn’t resolved. Our image is Windows 7 that was created using MBR.

Is there a way to fix this on FOG or will I have to format each disk before running an image?

[quote=“Tom Elliott, post: 22808, member: 7271”]In the debug mode, can you give the results of gdisk -l /dev/sda please?[/quote]

Disk /dev/sda: 250069680 sectors, 119.2 GB
Logical sector size: 512 bytes
Disk identifier (GUID): (GUID goes here)
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 250069646.
Partitions will be aligned on 2048-sector boundaries
Total free space is 4147 sectors (2.3 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 718847 350.0 MiB 0700 Linux/Windows data
2 718848 250066943 118.9 GiB 0700 Linux/Windows data

[quote=“Tom Elliott, post: 22791, member: 7271”]what is the status of:
fdisk -l[/quote]

Device Boot Start End Blocks ID System
/dev/sda1 * 1 45 358400 7 HPFS/NTFS

Partition 1 does not end on cylinder boundary
/dev/sda2 45 15566 124674048 7 HPFS/NTFS

This is an SSD.

[quote=“Tom Elliott, post: 22737, member: 7271”]Can you try booting the system with my kernel in debug mode? I just want to see if it’s network or hard drive you’re having issues with.[/quote]

Booted into debug mode and got to a prompt. I have network connectivity.

[quote=“Tom Elliott, post: 22675, member: 7271”]What version fog? Which bzImage have you tried?

What is the Network card on that system?[/quote]
FOG 0.32. I tried your “all-net” bzImage that you linked to the post I referenced.

I booted into Ubuntu 13.10 and got this info on the NIC:

[CODE]Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-LM [8086:155a] (rev 04)
Subsystem: Dell Device [1028:05ca]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 57
Region 0: Memory at f7e00000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f7e3c000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at f080 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
[/CODE]

I’m trying to image a Latitude E7240. It proceeds to the imaging process and then throws up errors that seem to be related to the network card. The problem is the same one described in [URL=‘http://fogproject.org/forum/threads/dell-latitude-e7240-imaging-problem.8006/#post-17755’]this [/URL]thread. Installing the bzImage linked to in that thread does not resolve the issue. Bios is version A07 and we’re running the latest version of FOG. Any suggestions?