Posts made by xmute

@george1421 I downloaded a copy from the kernel directory on a different PC and copied it over. They were just called bzImage and bzImage32. I will get the version in the morning and report back.

I did run the test before I left and it did fail network. I also wasn’t able to see the mac address or IP through the menu.

EDIT:

Also, running Ubuntu 14-04 LTS
I get bzImage: x86 boot sector

And I got the bzImage from here https://fogproject.org/kernels/

EDIT 2: Not sure why the edit from my main post vanished. Let me put that here again.

I took a video of the newest message. From reading the blurry video, this is what I can read before the fog text logo comes up.

mmc0: Unknown controller version (3). You may experience problems.
usb 1-5: device descriptor read\64, error -71
EXT4-fs (read): couldn’t mount as ext3 due to feature incompatibles
Starting logging: OK
Populating /dev using udev: udev[2612]: error creating spell? fd: Function not implemented
done

EDIT 3: Took bzImage files and init files from a test fog machine I was messing with. 1.3.0 FOG on there. Copied the to the FOG 1.2.0 server.

The compatibility test comes back with disk and network passing.

Trying to register a host and I get:
Unable to register host: Invalid MAC Address (/bin/fog.man.reg)
Arg Passed:

I think I am making some progress here.

@x23piracy Nothing. I think Panasonic has some components wired internally to the board to look as USB.

All I have plugged in is a network cable.

On the newest bzImage/bzImage32, I thinks the xkci got resolved, I am still trying to grab what the message is being thrown before the FOG txtimage scrolls down.

Is there a way to pause or slow down the messages?

EDIT: Main post updated.

Notebook Spec

UEFI w/ CSM enabled. Secureboot Off
i5-6300U
NIC: Intel I219-LM

Staring off, I am running v1.2.0. Isolated network install.

Notebook SPEC
UEFI with CSM enabled. Secure boot off.
Intel Corre i5-6300U
Intel I219-LM

I am going to be getting a new batch of these notebooks and I am running into some issues.
The mk1 series worked fine. The mk2 is kinda screwy.
I am unable to inventory via PXE.

Leaving the bios as UEFI, I am not able to LAN boot.
Messing with having CSM on, no luck.

Moving on, I changed the BIOS to not use UEFI. I can get to the main FOG splash screen and select Full inventory.
The following is what I was able to capture before it scrolled on past everything to tell me it has an issue with inventory.

tsc: Fast TSC calibration failed.
usb 1-5: device descriptor read/64, error -71
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 1-5: hub failed to enable device, error -22

From here I deiced to update the bzimage and bzimage32 kernels manually.

It seems to go further, but I still can’t inventory. I see a message rush past (shorter than the above), but I am unable to capture what it reads.

Anyone know of any issues with this notebook? Or am I ahead of the curve here?

Found some software on the master for making recovery discs. Sorry for not looking for this sooner, I’m looking over the mountain instead of at the base.

If these work, I may remake the image quickly on the second to have an image.
Still wondering what Panasonic has on these causing fog to think the File Table is corrupt.

Thank you Tom.

Also, almost relevant for how I feel:
Quote from Simpsons, Ned Flander’s Mother:
[QUOTE]You gotta help us, Doc. We’ve tried nothin’ and we’re all out of ideas.[/QUOTE]

Update: Finished downloading the image with OS as Other with no avail.
It has tried startup repair and failed.

Something with the file table how Panasonic has set up needs to stay the same from time of taking image to deployment.
I have noticed fog looking at the file table and stating that it looks corrupt but the primary looks intact so it will use that.

Almost sounds like it is taking what looks like a file table from the reinstallation recovery partition and trying to reconfigure how it should be.

Would a dd Image be a good idea?

All software and drivers were already installed, would I have to go back and redo everything upon factory recovery and going into audit mode?

Throwing this out there, I have done HP desktops with OEM keys without having to go into audit mode and they image fine. They didn’t have full on recovery partitions though, they gave DVDs, which is nice.)
This has to be something with how the partitions are set up on these Panasonic laptops.

I am not seeing a way to try a fresh install while keeping the OEM key working. (Looks like Panasonic does not offer install DVDs for this model I have)

It would be nice if Panasonic gave installation DVDs.
I am missing the days when OEMs did this by default.

I was trying to figure out if there is a way to force fog to not check if the file table is correct upon deployment.

Reason I am looking into this is further testing from this original post: [url]http://fogproject.org/forum/threads/image-with-oem-recovery-partition.9920/[/url]

This is basically a fresh Windows 7 SP1 x64 install. Besides the point where I work off of what what on the machine from factory (recovery partitions).
I am trying to stay away from doing a fresh install as we want to keep the key that came installed and not use up the few we have left.
-The OEM preinstalled a OEM key that only works with their installation partitions. Also, the slapped the Windows 8 sticker on it not giving a windows 7 key sticker.

If we do use Windows Backup and Recovery, everything works fine. I would love to use fog on this to keep an images not stored on random externals.

So far I have tried the following:
-Multi-Part, Single Disk
-Multi-Part, Multi-Disk
-OS as Windows 7
-OS as Other (Currently downloading to second PC to see what happens*)

Any ideas?

*Reason for posting: I noticed fog check and notify me that the table looks corrupt. before restoring the partitions)

sda2 has * boot marked.
sda2 is the 300mb part.

Stopped mid way.

Cannot read file d1p3.img.001

Going to try again with a backup of the first attempt ever tried.

Quick report

Was about to wipe a spare CF31S clean with an install and this was an odd sighting.
Still straight from OEM

Where do you want to install Windows?

Name | Total Size | Free Space | Type
Disk 0 Partition 1: Recovery | 17.7 GB | 3.3 GB | OEM (Reserved)
Disk 0 Partition 2: System | 300.0 MB | 258.0 MB | System
Disk 0 Partition 3 | 29.3 GB | 15.6 GB | Primary
Disk 0 Unallocated Space | 423.5 GB | 423.5 GB |

EDIT: For research sake, I will fdisk.
EDIT 2: Heard from coworker who started the image; they may have used a partition merging program to combo 2 partitions. This may be one of the issues with getting the image.

My small test failed.

[QUOTE]
This is first findings, before changing d#p#.img files around
It looked like it copied the partition correctly how they showed up in Disk Management.
Which was Recovery -> 100mb -> OS
sda1 took a while getting 12GB
sda2 breezes past
sda3 Takes longer being around 40GB+ anyway[/QUOTE]

Following your steps, I do not think that will work without changing other things. (Which I am not sure how)
What is now sda1 flys by too quickly. Almost failing (300mb if I saw it flash correctly?)
What is now sda2 tries to put what was in the 400GB+ part into 12GB
What is now sda3 tries to put the recovery partition into what is left over 400GB+
This leads to not even attempting to boot into Windows. Can’t find anything.

First one I tried was a Multi Part, Single Disk, NonResie.
Wouldn’t even let me try a Single part, Single Disk, Resize.

3 more minutes and I can try the Multi Part, Multi Disk I mentioned.

I apologize if my wall was hard to read.

EDIT: Now to wait until morning if it works.

Going to type out what I am done so far, tell me what I am missing. if anything.

Hardware: Panasonic CF-31S

I am assuming one HDD as I do not see room for more.

HDD: 500GB
[LIST]
[]Part 1: Recovery | 12GB
[]Part 2: 100mb
[*]Part 3: Windows 7 | Rest of the Disk
[/LIST]
Coworker finished installing custom applications on what is labeled Drive C, Partition 3 (Technically 2 for Win7 case)
Keeping First partition intact for time being, it is the OEMs Recovery Partition.

No SysPrep (For the time being, higher ups want to keep it that way)
No FogPrep (Am I reading this wrong or is it already implemented into 0.32 upon imaging?)
Taking an image: First trying Single Disk, Multi Part, NonResize.
Image get saved, pushed down to another.
Endless Startup Repair.

Go back into master hardware, do a defrag and error check.
Everything comes up fine.

Retake image, same problems.

Decide to use Windows 7 Backup to test other options.
I was able to clone another from using Backup. Works fine from what I can tell.

I am now going back to the master and re-uploading the image as a Mutli Disk, Multi Part, NonResize.
Let’s see where this leads me if anywhere.

Worse case: If nothing else, wiping disk, fresh Windows 7 install.

Am I missing something?

… Well, I hate when that happens. My freespace.php was pointing to the wrong location.

Never mind, sorry for bothering. Now to go look encase I didn’t make the same mistake in the other locations.

EDIT: Which I did, everywhere.

PROBLEM SOLVED

Just finished setting up a fog box on Ubuntu and added in additional hard drive to store my images.

Followed though steps on a few pages to get things rolling.

[url]https://help.ubuntu.com/community/InstallingANewHardDrive[/url]
and
[url]http://www.fogproject.org/wiki/index.php/Change_NFS_location[/url]

After “Edit your storage-node definition” on the second link, the chart that usually shows how much storage is left, all it reports back to me is

“No error, but no data was return”

Did I follow something wrong?