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)
-
bump
-
cyberion,
Is the filesystem you have setup in a software raid setup? I ask because of the /dev/md0 being created. This may explain why it’s loading as raw. The file systems aren’t syncing together to give you the accurate file information you’re needing.
Also, it’s not the kernel that’s causing it to go to RAW mode directly. What version of FOG are you using?
I will rebuild my kernel with the tigon/tg357766.bin file if I can find it within the linux-firmware directory so you should have access to that network adapter.
-
[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url] should contain the tigon firmware your system is requesting.
-
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.
-
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
-
The image for the TMP255, what type of image is it set up for?
I’m guessing it’s setup for raw, which would be why it’s trying to upload as raw.
I’d check it because the kernel doesn’t determine image type for upload operations.
There are 4 types:
First is n which is for Single Disk-Resizable.
Second is mps which is for Multi-part Single Disk Non-resizable.
Third is mpa which is for Multi-Part Multi Disk non-resizable.
Fourth is dd (raw) transfer. -
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 -
Changing the Drives isn’t going to help out at all. If you were to take the drive from the TMP453 and put it into the TMP255, I’ll bet it also loads as raw.
If you can check the /tftpboot/pxelinux.cfg/01-XX-XX-XX-XX-XX-XX file and check the imgType= to verify that it’s truly set for mps.
-
Hello again,
Yes, just checked the file and imgType=mps
-
Are you using the stock init.gz file from 0.32 or did you or somebody use (and/or) build a custom init.gz?
-
Yes, we are using the stock init.gz and no one has modified it.
-
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 ?
-
I can’t really modify the 3.8.8 kernel stuff. However, I can remove the “RAID” part of the 3.13.3. What bothers me though, is that it shouldn’t be trying to build a RAID if one hasn’t been setup. Is the TM255 sata setup for RAID, AHCI, or IDE?
-
The TM255 sata setup is set up for AHCI , IDE mode is not available on this model , neither is RAID.
-
That doesn’t make any sense that you can change the “mode” of the sata controller. It defeats the purpose of even displaying the option.
Let me do some research.
-
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.
-
Just built 3.13.4 kernel. Removed “raid” modes.
Please give this one a shot on your TM 255 machine and let me know if you can.
-
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
-
Cyberion,
While I’ve been trying kernels, I don’t think that’s what’s causing the issue in your particular case. I think this because if it was the kernel, you’d be seeing the SAME results on the TMP453 system. The kernel doesn’t determine the imaging type, the image type does.
Can you create a task, don’t start the system, and take a look at the file created for the task?
The file should be located in /tftpboot/pxelinux.cfg/
It will follow suit as:
[code]01-XX-XX-XX-XX-XX-XX[/code] Where the X’s represent the system’s MAC Address. If you can past the contents of the file here (less the mac address if you want) so I can take a look at the build of it.
