Dell Latitude E7240 hangs during imaging
-
What version fog? Which bzImage have you tried?
What is the Network card on that system?
-
[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] -
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=“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.
-
what is the status of:
fdisk -l -
[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/NTFSPartition 1 does not end on cylinder boundary
/dev/sda2 45 15566 124674048 7 HPFS/NTFSThis is an SSD.
-
In the debug mode, can you give the results of gdisk -l /dev/sda please?
-
[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 -
So the problem is NOT because of kernel or driver issue. It’s also NOT because of the disk being SSD. It’s because the disk is formatted with GPT.
-
Is there a way to fix this on FOG or will I have to format each disk before running an image?
-
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=“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.
-
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=“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.
-
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=“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.
