Posts made by d4rk3

I was able to clone partition 1 (mmcblk0p1) successfully, but beyond that it fails to recognize the remaining partitions.

I was only able to clone p1 by running Debug, creating /images, mounting it on my FOG server and running partclone.dd manually.

I figured the kernel was probably the main issue here.

And you are correct with running fdisk -l. Even after using your new kernel as well, unfortunately.

Same error, only saying “clone: open /dev/mmcblk error” instead.

I tried a bunch of kernel arguments yesterday…to no avail.

Do you think using Partclone v0.2.73 would help at all?

Tom, if you or anyone knows where I should go from here I’d appreciate it!

[url=“/_imported_xf_attachments/1/1427_Partclone Error.jpg?:”]Partclone Error.jpg[/url]

Good news: I was able to hit the PartClone screen while trying to upload! I just had to set the primary disk to /dev/mmcblk0.

It then threw an error about not being able to open /dev/mmcblk0 and reboots, but that’s ok because I’m so close now! It seems I just need to find the right disk/argument and these will be FOG compatible

I used the bzImage32. I was able to launch a debug task by setting argument /dev/mmcblk. Still can’t see anything with fdisk, gdisk, etc.

Gonna continue trying…

Getting closer! I’m gonna try various arguments and see if I can coax this any further.

First off, sorry for my delayed response. I didn’t receive an email notification of a response to my thread.

The kernel panics, but, it then spits out two lines before locking up:

[B]VFS: Mounted root (ext2 filesystem) on device 1:0.[/B]
[B]devtmpfs: mounted[/B]

Awesome, thank you! I will test it once you’ve made it.

Also, it looks like I forgot to mention that these are 32-bit devices.

[FONT=Consolas]lsusb[/FONT]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 154b:0053 PNY (Flash drive used to load Clonezilla into my RAM)
Bus 001 Device 003: ID 0b05:17e0 ASUSTek Computer, Inc.
Bus 001 Device 002: ID 0b05:17e4 ASUSTek Computer, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Yep, give me just a bit and I’ll do that.

In the meantime, here are my disk reports from when I’ve captured an image with Clonezilla.

[url=“/_imported_xf_attachments/1/1422_mmcblk0.zip?:”]mmcblk0.zip[/url]

Nope. I run fdisk -l and it just brings me to a new prompt.

Thanks a million for your help, Tom.

I should also mention that even though I can easily send inventory on these now, FOG still has yet to recognize the hard drive in the inventory report.

I can deploy a debug task to one of these and I cannot get anything from fdisk, gdisk, etc. However, the latest builds of Clonezilla properly recognize the partition layout…I’m wondering if getting one of the disk utilities working with these hard drives would be all it would take to get these to upload an image…

Unfortunately, no I tried on SVN 2389 and now on 2411.

I will be continuing on my quest this evening and into the weekend…

I’ve made several custom kernels, tried every disk/kernel argument related to mmcblk partitions I can think of…nothing. But so close, nonetheless…

I’ve seen this myself on fourish 755’s in our district. I haven’t had much time to look into it…I tried a couple different kernels to no avail.

Workaround is to simply deploy onto a working hard drive, shut the station down upon completion and then pop the hard drive into the problematic 755. Then Windows will start setting up devices as usual.

Bump! :0

Go here: [url]https://rom-o-matic.eu/[/url]

Click Advanced, at the bottom choose “EFI PXE Bootstrap 32-bit (.efi)”

These are the options I always check:

[SIZE=12px][FONT=Arial][COLOR=#000000]CPUID_SETTINGS[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]DOWNLOAD_PROTO_NFS[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]IMAGE_PNG[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]PARAM_CMD[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]CONSOLE_CMD[/COLOR][/FONT][/SIZE]

Finally, plop this script in the iPXE script box (remember to change the last line to match your FOG server’s IP or hostname:
(the colour and cpair lines are optional, I use these for my menu colors. Simply remove them if desired.)

#!ipxe

colour --basic 2 7
cpair --foreground 7 --background 9 1
cpair --foreground 0 --background 9 2
dhcp
set arch i386 ||
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain [url]http://x.x.x.x/fog/service/ipxe/boot.php##params[/url]

Note: With the 32-bit tablets I UEFI PXE boot with, I have to manually set the arch to i386 in this script because they are technically 64-bit capable and FOG detects this and gives them bzImage/init.xz, but they only work with bzImage32/init_32.xz.

It’s very possible, I haven’t even tried that route due to lack of time over the summer when I just had to put the legacy/UEFI boot file issue to rest.

Specific MAC’s, sorry…tedious I know, but you only have to enter them once and then update the policy as needed.

On our Server 2012 R2 DHCP Server I set up a policy for EFI boot files for matching MAC addresses of our UEFI-only PXE boot stations. It works great