Doug LaRue

On these tablets were is only the onboard EMMC flash drive so as long as using "all" will trigger something to 'fix' the defaults in the backup it should work. I've been able to work through this with my 2 different backup images so my posting of this error is only somewhat for me and more so for figuring out a way to fix it so others don't end up here. I can see why the kernel devs are doing this but it looks like magic stuff happening when tools like Clonezilla start hiccuping on the side-effects...

I have another backup/restore image which I ran cnvt-ocs-dev on to convert mmcblk0 to mmcblk1 and THAT is the 2nd gub.cfg menu item I use when I first get the error trying to install to mmcblk0. I guess the "4 times" explanation didn't come across as I had intended. The main problem is how random the kernel is at assigning device names. Like I said, on that one system it would go from mmcblk0 to mmcblk1 to mmcblk0 to mmcblk1. It switched back and forth 4 times. Here are my 2 grub entries: menuentry...

just happened. see display pics. I rebooted and ran the same restore option(mmcblk0) and it's happily cloning. Seems odd it would be so random on the same hardware.

just happened. see display pics.

Hmm, pretty sure it was terminating the run. It might have to do with mmcblk0 being assigned to SDIO but with no disk installed there literally is no /dev/mmcblk0 and there only exists a /dev/mmcblk1 and at that point it gives me a description and says terminate hit enter or something dumping me to a prompt where I type reboot. I have modified grub.cfg so that I have 2 entries, one for mmcblk0 and one for mmcblk1 since I copied the backup image and ran the converter on the copy. I've not tried "ask_user"...

That makes it a bit difficult to use clonezilla when it wants device lists and not UUID or something which does not change. I just had a crazy tablet where this happened: I used the mmcblk0 backup and it complained saying mmcblk1 was found so I restarted using the backup which I'd setup mmcblk1 and it complained saying mmcblk0 was found I used the mmcblk0 backup and it complained saying mmcblk1 was found the forth time I restarted again with mmcblk0 and voila I got ahead of it and it cloned. Is there...

I'm imaging a bunch of tablets and running into this problem where my "gold" image system had installed to mmcblk0 but sometimes clonezilla is enumerating the device as /dev/mmcblk1. I've heard older versions of clonezilla don't do this. So why is this happening? I'm not a fan of having systems which will now have different device configurations and this will likely effect when uSD cards are used and students will be seeing different locations for the storage device. I have worked around the installation...

That's impressive, I wonder how this has not become a more popular project. I miss the WPS and all the wonderful things SOM brought to it.