Thank you, will see what I can do.;)
Posts made by cyberion1985
-
RE: New Kernel copies in raw mode
Hi Tom,
Unfortunately the TM does not have the option One can only change from legacy to UEFI mode Boot Mode, but in UEFI it will not allow to boot from Network. Legacy mode then we have the EFI partition problem
-
RE: New Kernel copies in raw mode
Thank you. Only seeing one disk with only one EFI GPT partition:
Device Boot Start End Blocks Id System
/dev/sda1 1 60802 488386583+ ee EFI GPT -
RE: New Kernel copies in raw mode
Ok, let me know what commands I should run (debug mode)
-
RE: New Kernel copies in raw mode
[CODE]# Created by FOG Imaging System
DEFAULT send
LABEL send
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.10.254 type=up img=testtest imgid=65 mac=2x:xx:xx:xx:xx:xx storage=192.168.10.254:/images/dev/ web=192.168.10.254/fog/ ignorepg=1 osid=5 pct=5 imgType=mps shutdown=on loglevel=4 consoleblank=0 fdrive= chkdsk=0[/CODE]
-
RE: New Kernel copies in raw mode
Hello Tom,
Many thanks for your help so far. Unfortunately, that Kernel made no difference. Would it be possible for you to send me the firmware of the tigon ? Or to give me a link where I can download / find it ? Thanks in advance
-
RE: New Kernel copies in raw mode
Well the TMP453 has that option. It has AHCI and IDE. Other Acer laptops even have the RAID option and the other two options. But this new TMP255 only has AHCI. I just updated the BIOS on this unit to see if it makes any difference ⊠and âŠit did not. Detects file system as raw and starts.
-
RE: New Kernel copies in raw mode
The TM255 sata setup is set up for AHCI , IDE mode is not available on this model , neither is RAID.
-
RE: New Kernel copies in raw mode
I just had an idea : What if , you would modify the Kernel of the one that was 12872000 bytes , the Kernel-3.8.8.core and insert the firmware for the tigon of the TM255 ?
-
RE: New Kernel copies in raw mode
Yes, we are using the stock init.gz and no one has modified it.
-
RE: New Kernel copies in raw mode
Hello again,
Yes, just checked the file and imgType=mps
-
RE: New Kernel copies in raw mode
Hello Tom,
The image is setup for âSecond is mps which is for Multi-part Single Disk Non-resizable.â
Like I said, if I upload it on the TMP453, then it works 100% and is NOT raw -
RE: New Kernel copies in raw mode
error message "[I][I]tg3 0000: eth0: Failed to load firmware âtigon/tg357766.bin[/I]â " [/I]disappeared
Everything else is the same. To clarify upload, it says âdetect file systemâŠrawâ which should say "âŠntfs. When I install this hard drive from the TMP255 into the TMP453, then it says ntfs and uploads the image flawlessly. Now it still tries to upload 465.76 GB on 1.08 GiB / min. [I]
[/I]I am now currently using acronis home, to deploy 1 machine per session, which takes 21 minutes -
RE: New Kernel copies in raw mode
Thanks a lot Tom, I will download and test the updated kernel now.
I have no raid setup. And I am using FOG 0.32.
-
RE: New Kernel copies in raw mode
So I tried that, with the work around. The image seems to upload and download fine on the TMP453, but not one the TMP255. When I download the image to the TMP255 with the new Kernel as described in the first post, then it just images the first partition and skips the other 4 partitions. Here are my error messages :
[I]esas2r driver will not be loaded because no ATTO esas2r devices were found 12c-parport-light: adapter type unspecified[/I]
[I]tg3 0000: eth0: Failed to load firmware âtigon/tg357766.binâ[/I]
[I]Warning: Error Fsyncing/closing /dev/md0: input/output error.[/I]
[ Please waitâŠ
Image restored ] x 4 (which does not deploy the image)
-
New Kernel copies in raw mode
So I had a similar issue to the post in :
âMore than 8 outputs detectedâ
[url]http://fogproject.org/forum/threads/lenovo-m93p-issue-after-init-gz-more-than-8-outputs-detected.9395[/url]So I [U]used the Kernel in that link[/U]. It works, BUT it uploads / downloads everything in RAW mode and it doesnât make a new file for each partition on the fog server. It makes one file and when it copies it, it somehow displays the FULL size of the partition (465 GB) in data to be copied. The original paritions are a total of about 45 - 50 GB. The fog upload makes a image of 37GB.
The machine I am using is a Acer TravelMate P255-M-54204G50, 500 GB SATA UEFI, W8, 64 BIT, BIOS InsydeH20 V2.06, Network BRCM HBA 0100 v15.4.2
Currently the deployment is slow or (36 GiB / 465 GiB). Will this speed up at one point ? It says 2 hours remaining All my previous images take 20 minutes or less to deploy.
What do I need to do to make this go as fast and good and reliable it used to ?
Do I need to run a program on the TM hard drive that someone flags the 0 bytes not to be used so the fog program only copies actual data blocks ?
How do I get it to copy the other partitions ?
How do I get it not to copy in ârawâ mode ? (as I specified , multiple partition single disk)
Quick help will be highly appreciated , as I need to image 150 and have them done by next week Thursday
[EDIT]
I am now busy working on a work around :I will install the HDD that I need to be imaged to the previous Acer model, the TMP453-M. This one worked before with my the older kernel I had.First, I will remove the new kernel and then copy back my backup old kernel. Then I will simply let it upload and then assign the Capone Association to the TMP255. Then I will re-copy the new kernel back and start deployment of the image onto the TMP255s over the network. Should work - hopefully
I also defragged my drive and ran chkdsk and also defrag on the the free space on it.
-
RE: GPT images fail deployment
Itâs running on 0.32
Will test with the RAW image upload. Since time will be a problem, I cannot use this option on 200 or 300 units - as this would delay the delivery date exponentially.
EDIT
I would need to know how I can update it with the update I downloaded :
1.) Update without overwriting the current settings, plugin configurationsâŠ
2.) If 1 fails then details on what files I should backup or where and what lines I must copy so I can restore the current configs to the 0.33b version
3.) There is no internet connection on the deployment server, so I canât do it onlineâŠ
EDIT 2
I ran the install file and it actually ran through fine⊠but nothing changed. The version in FOG still says itâs 0.32 âŠ
-
GPT images fail deployment
Hey
We use FOG for almost all our bigger image system deployments. If everything is straight-forward, then there are no problems and all works flawless. But what I noticed is that FOG doesnât like new hard drives that have no partitions on or hard drives that have been wiped clean.
I uploaded an image with FOG from a PC. This PC is running Windows 7 Pro 64 bit with a 500GB HDD. It has 4 partitions = EFI, MSR, Primary, Primary. The first partition os 100 MB, the second 128 MB, the third 451GB add the fourth 13GB. It had been âdowngradedâ from Windows 8, so the disk layout is GPT. The upload completed successfully and has valid file sizes on the upload location. It stores 4 images files.
When I deploy this image on a exact same model machine with the same original hard drive partition and disk layout, it deploys flawlessly.
Issues
1.) When I deploy this image on a exact same model machine, with a new hard drive (no partitions) it doesnât even start. When deploying, it says âtask completedâ and then shuts down or restarts (whichever I chose as a task completion option)
2.) I need to manually create the partitions on the new hard drive, and make the hard drive layout GPT. The partitions need to be the exact same sizes as the original. This starts the deployment, deploys onto partition 1,2 and 4 BUT it SKIPS the 2nd partition , the 451 GB one (which I actually need). I use diskpart for doing this.
I was in fact unable to deploy to ANY system with a unformatted, unpartitioned new hard drive running GPT. The thing is, I would need this to work as sometimes I replace the hard drive of a machine, which crashed and then need to restore it to factory default and thus I want to use the FOG images we created.
So what must I do, so that the deployment on new clean hard drives works just as well ?
The only workaround I have is to use Ghost or Acronis to make an image from a new original machine and deploy it onto a new hard drive and install that drive into the required machine.
Additionally, this all is no problem when working with a MBR image that was uploaded.