Uploading an image from partition layout: /dev/mmcblk0
-
Bump! :0
-
On the hosts with these particular devices, set the host device argument to:
[code]/dev/mmcblk[/code]Does this help?
-
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 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ā¦
-
I want to get these working, so fdisk -l doesnāt display the disk either?
-
Nope. I run fdisk -l and it just brings me to a new prompt.
Thanks a million for your help, Tom.
-
I hate asking, but can you get to a terminal prompt within clonezilla and get the contents of the information?
[code]lsusb[/code]
Iām under suspicion the FOG issues is likely related to the fact that eMMC is typically whatās kind of found in USB Flash sticks.
As I donāt have any drivers included in the kernel to support USB Disks (hence being able to keep a USB hdd connected without overwriting the wrong drive) I think this is where our problem lies.
-
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]
-
Okay
I am building mmc support into the kernel. I did a lot of research and hopefully the new kernels will, at the least, recognize the disk. -
[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 -
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.
-
Kernels are ready:
[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url] (64bit)
[url]https://mastacontorla.com/fogboot/kernel/bzImage32[/url] (32bit)I donāt know if it will work properly, but can you boot the system and see if it at least can recognize the disks now?
-
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] -
Getting closer! Iām gonna try various arguments and see if I can coax this any further.
-
What kernel did you try?
The bzImage32 should be the one you need and if you replaced your original bzImage32 with that, things should work.
-
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ā¦
-
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
-
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]
-
Can you remove the 0?
mmcblk should find mmcblk1 or mmcblk2 as needed.
-
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?
