Still toying around. Ran into a couple things I did not expect, but nothing show stopping yet. The biggest thing on my mind immediately was knowing that Robert was using an UUID for the root mount of the eMMC. Which turned out to be a non issue so far.
I had considered backing up the eMMC as it is now - WIth Debian Jessie on it and one single partition. But I do not like what all is running on this image, and I'm not 100% how to deal with the things I'm not liking. So . . . I think I'll skip that. Now, time to boot back into the development image, and see what hackery I can engage . . . On Wed, Jul 27, 2016 at 4:18 PM, William Hermans <[email protected]> wrote: > I think I will experiment with this in a bit. What I'll do is grab one of > the latest Jessie flasher images. Flash it to eMMC, and then replace the > rootfs with an older Wheezy rootfs. I do not have any of this ready, so > setup will take me a while. Which will include backing up the eMMC as it > sits( factory image ). > > Got some other things to do first though. . . > > On Wed, Jul 27, 2016 at 4:14 PM, William Hermans <[email protected]> > wrote: > >> Ok, so once you have a working eMMC. You'll probably want to make the >> partition as small as possible, while still being big enough for the >> rootfs. Then dd backyp the entire eMMC block device. That way, when you dd >> back to replicate, it'll take less time. Then, if you need, or want to >> resize the rootfs partition. You do that afterwards. It should make the >> whole process much quicker. Instead of copying over needed data, and then >> filling the rest of the eMMC with zero's through dd . . . >> >> On Wed, Jul 27, 2016 at 3:48 PM, Matt99eo < >> [email protected]> wrote: >> >>> I am noob+ so I'll give'r it a whirl :) >>> >>> On Wednesday, July 27, 2016 at 3:36:26 PM UTC-7, William Hermans wrote: >>>> >>>> One thing that does come to mind that you can try. Would be to get one >>>> of the latest Jessie flasher images. Then flash that to eMMC. Afterwords, >>>> wipe the rootfs, create a tar backup of the rootfs you want on the eMMC, >>>> then tar that over to the eMMC. But as a Linux newb that might be easier >>>> said than done. >>>> >>>> Perhaps I'll experiment with that sometime this evening if I find the >>>> time. >>>> >>>> On Wed, Jul 27, 2016 at 3:31 PM, William Hermans <[email protected]> >>>> wrote: >>>> >>>>> Same method you're using, but if= needs to point to a suitable MLO >>>>> file. That is: I'm guessing based on the count and bs of that particular >>>>> dd >>>>> line. I only say I would probably never use Robert's script to do this as >>>>> I >>>>> do not know what he script does, and I am very particular in how my >>>>> beaglebones are setup. SO instead of reading through his script, I would >>>>> write my own script. Since I know what needs being done. >>>>> >>>>> As to other methods I'd use. Well technically I've never written to an >>>>> eMMC yet. Others here probably have more hands on than I in regards to the >>>>> eMMC. However, as I mention above. I know what needs doing, and how to do >>>>> it. Which is something really too complex to just tell someone without >>>>> experience how to do. Unless I've tested it first. Which won't happen any >>>>> time soon. >>>>> >>>>> So we're back to square 1. >>>>> >>>>> On Wed, Jul 27, 2016 at 3:23 PM, Matt99eo <[email protected] >>>>> > wrote: >>>>> >>>>>> OK could could you reccomend another way to accomplish my objective >>>>>> that does work? >>>>>> >>>>>> Thanks for your input! >>>>>> >>>>>> On Wednesday, July 27, 2016 at 3:18:19 PM UTC-7, William Hermans >>>>>> wrote: >>>>>>> >>>>>>> I know nothing of Robert's eMMC flasher script. I would probably >>>>>>> never use it. But thus far have not used it. However, the reason why dd >>>>>>> error'd out is as I said in my last post. It needs an input file in >>>>>>> order >>>>>>> to work. >>>>>>> >>>>>>> On Wed, Jul 27, 2016 at 3:13 PM, Matt99eo < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> But isn't the script >>>>>>>> -- beaglebone-black-make-microSD-flasher-from-eMMC.sh -- supposed do do >>>>>>>> that? >>>>>>>> >>>>>>>> Do I need to manually add this in? Sorry noob here I don't >>>>>>>> understand. I see the problem. But I don't know how to solve it, >>>>>>>> hence >>>>>>>> asking for help :) >>>>>>>> >>>>>>>> On Wednesday, July 27, 2016 at 3:10:48 PM UTC-7, William Hermans >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> dd: failed to open '': No such file or directory[ 35.897114] >>>>>>>>>> Kernel panic - not syncing: Attempted to kill init! >>>>>>>>>> exitcode=0x00000100 >>>>>>>>>> >>>>>>>>> >>>>>>>>> That's why. It can't find a file or directory. And here is why: >>>>>>>>> >>>>>>>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >>>>>>>>>> >>>>>>>>> >>>>>>>>> See the problem ? Where's the input file ? " " ? >>>>>>>>> >>>>>>>>> On Wed, Jul 27, 2016 at 2:51 PM, Matt99eo < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> I mean why isn't the boot loader getting on the uSD I've created >>>>>>>>>> using the script? I know why it needs to be there... >>>>>>>>>> >>>>>>>>>> How do I solve this such that I can slam the created uSD into a >>>>>>>>>> new BBB and have flash eMMC? >>>>>>>>>> >>>>>>>>>> On Wednesday, July 27, 2016 at 2:46:30 PM UTC-7, William Hermans >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> The line I've highlighed in yellow seams to be the problem. >>>>>>>>>>>> Why is the cloning script getting a bootloader in here? >>>>>>>>>>>> >>>>>>>>>>>> Any help much appreciated! >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> What do you mean "why?" ? Short answer is that a bootloader( >>>>>>>>>>> actually two - first and second stage ) is required to boot from >>>>>>>>>>> eMMC. >>>>>>>>>>> >>>>>>>>>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k is in reference >>>>>>>>>>> to MLO I believe. uboot.img is roughly 348k as I recall. >>>>>>>>>>> >>>>>>>>>>> On Wed, Jul 27, 2016 at 2:26 PM, Matt99eo < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> Been trying to clone a debian 8.4 running kernel 4.1.x using >>>>>>>>>>>> the RC Nelson script >>>>>>>>>>>> beaglebone-black-make-microSD-flasher-from-eMMC.sh >>>>>>>>>>>> >>>>>>>>>>>> I have ensured that I have the latest script (git pull when in >>>>>>>>>>>> /opt/scripts/tools) >>>>>>>>>>>> I have ensured the BBB I am cloning has a network connection >>>>>>>>>>>> during the process. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> When I insert he new uSD card into a new BBB to flash it it >>>>>>>>>>>> ends quickly with a kernel panic. >>>>>>>>>>>> >>>>>>>>>>>> Here is the serial debug output: >>>>>>>>>>>> >>>>>>>>>>>> Starting eMMC Flasher from microSD media >>>>>>>>>>>> Version: [1.20160718: mkfs.ext4 1.43...] >>>>>>>>>>>> ----------------------------- >>>>>>>>>>>> Checking for Valid bbb-eeprom header >>>>>>>>>>>> Valid bbb-eeprom header found [335] >>>>>>>>>>>> ----------------------------- >>>>>>>>>>>> copying: [/dev/mmcblk0] -> [/dev/mmcblk1] >>>>>>>>>>>> lsblk: >>>>>>>>>>>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>>>>>>>>>>> mmcblk1boot0 179:16 0 1M 1 disk >>>>>>>>>>>> mmcblk1boot1 179:24 0 1M 1 disk >>>>>>>>>>>> mmcblk0 179:0 0 7.2G 0 disk >>>>>>>>>>>> `-mmcblk0p1 179:1 0 7.2G 0 part / >>>>>>>>>>>> mmcblk1 179:8 0 3.7G 0 disk >>>>>>>>>>>> ----------------------------- >>>>>>>>>>>> df -h | grep rootfs: >>>>>>>>>>>> ----------------------------- >>>>>>>>>>>> Erasing: /dev/mmcblk1 >>>>>>>>>>>> 108+0 records in >>>>>>>>>>>> 108+0 records out >>>>>>>>>>>> 113246208 bytes (113 MB) copied, 17.7061 s, 6.4 MB/s >>>>>>>>>>>> [ 34.099130] random: nonblocking pool is initialized >>>>>>>>>>>> 108+0 records in >>>>>>>>>>>> 108+0 records out >>>>>>>>>>>> 113246208 bytes (113 MB) copied, 4.35786 s, 26.0 MB/s >>>>>>>>>>>> Erasing: /dev/mmcblk1 complete >>>>>>>>>>>> ----------------------------- >>>>>>>>>>>> Writing bootloader to [/dev/mmcblk1] >>>>>>>>>>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >>>>>>>>>>>> ----------------------------- >>>>>>>>>>>> dd: failed to open '': No such file or directory[ 35.897114] >>>>>>>>>>>> Kernel panic - not syncing: Attempted to kill init! >>>>>>>>>>>> exitcode=0x00000100 >>>>>>>>>>>> [ 35.897114] >>>>>>>>>>>> [ 35.911129] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted >>>>>>>>>>>> 4.1.21-bone-rt-r20 #1 >>>>>>>>>>>> [ 35.918639] Hardware name: Generic AM33XX (Flattened Device >>>>>>>>>>>> Tree) >>>>>>>>>>>> [ 35.924801] [<c0012e01>] (unwind_backtrace) from >>>>>>>>>>>> [<c0010fe9>] (show_stack+0x11/0x14) >>>>>>>>>>>> [ 35.932590] [<c0010fe9>] (show_stack) from [<c05e2049>] >>>>>>>>>>>> (panic+0x6d/0x188) >>>>>>>>>>>> [ 35.939500] [<c05e2049>] (panic) from [<c002fea9>] >>>>>>>>>>>> (complete_and_exit+0x1/0x18) >>>>>>>>>>>> [ 35.946844] [<c002fea9>] (complete_and_exit) from >>>>>>>>>>>> [<c00372c1>] (sigprocmask+0x59/0x88) >>>>>>>>>>>> [ 35.954801] [<c00372c1>] (sigprocmask) from [<00000001>] >>>>>>>>>>>> (0x1) >>>>>>>>>>>> [ 35.960665] ---[ end Kernel panic - not syncing: Attempted >>>>>>>>>>>> to kill init! exitcode=0x00000100 >>>>>>>>>>>> [ 35.960665] >>>>>>>>>>>> >>>>>>>>>>>> The line I've highlighed in yellow seams to be the problem. >>>>>>>>>>>> Why is the cloning script getting a bootloader in here? >>>>>>>>>>>> >>>>>>>>>>>> Any help much appreciated! >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> For more options, visit http://beagleboard.org/discuss >>>>>>>>>>>> --- >>>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>>> Google Groups "BeagleBoard" group. >>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>>> it, send an email to [email protected]. >>>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>> https://groups.google.com/d/msgid/beagleboard/f7f021f7-98e5-4ae8-88d7-311f83b8d32b%40googlegroups.com >>>>>>>>>>>> <https://groups.google.com/d/msgid/beagleboard/f7f021f7-98e5-4ae8-88d7-311f83b8d32b%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>>> . >>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>> For more options, visit http://beagleboard.org/discuss >>>>>>>>>> --- >>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>> Google Groups "BeagleBoard" group. >>>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>>> send an email to [email protected]. >>>>>>>>>> To view this discussion on the web visit >>>>>>>>>> https://groups.google.com/d/msgid/beagleboard/3acf56a9-1173-4ca1-a8e5-38e86c62c21e%40googlegroups.com >>>>>>>>>> <https://groups.google.com/d/msgid/beagleboard/3acf56a9-1173-4ca1-a8e5-38e86c62c21e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>> . >>>>>>>>>> >>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>> For more options, visit http://beagleboard.org/discuss >>>>>>>> --- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "BeagleBoard" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/beagleboard/8980903e-7beb-44f9-b020-e8c2abedb712%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/beagleboard/8980903e-7beb-44f9-b020-e8c2abedb712%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>> For more options, visit http://beagleboard.org/discuss >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "BeagleBoard" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/beagleboard/cdb14054-5e99-4842-9b4c-3e6ee423a3c1%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/beagleboard/cdb14054-5e99-4842-9b4c-3e6ee423a3c1%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> >>>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/6d2c65aa-9fbf-4839-b432-9fa07fdd66d9%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/6d2c65aa-9fbf-4839-b432-9fa07fdd66d9%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORp7sgpTuW9jfCkiA31AG-xK1hdmRc05h_5aYoUKBgk%3D5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
