Making "snapshot"

busybee

Hi tedd77, I've revised the instructions a bit. Please do a mkfs.ext4 before mounting it.

Afer the loop mount, please use a "df -h" command to see if the free space is big enough to hold your Linux rootfs files.

It's best to use rkflashkit to backup in your case.

Here's my output of rkflashkit:

-----------------------8<-------------------8<--------------------------

$ sudo rkflashkit part
Found devices:
0x2207:0x320a

============= 2014-12-22 11:03:55 ============


Loading partition information

PARMxFIRMWARE_VER:4.4.2
MACHINE_MODEL:rk30sdk
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x62008000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.hardware=rk30board androidboot.console=ttyFIQ0 board.ap_has_alsa=0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x00180000@0x00092000(system),0x00002000@0x00212000(metadata),0x00200000@0x00214000(userdata),0x00620000@0x00414000(linuxroot),-@0x00a34000(user)

Partitions:
uboot        (0x00002000 @ 0x00002000)    4 MiB
misc         (0x00002000 @ 0x00004000)    4 MiB
resource     (0x00008000 @ 0x00006000)   16 MiB
kernel       (0x00008000 @ 0x0000e000)   16 MiB
boot         (0x00010000 @ 0x00016000)   32 MiB
recovery     (0x00010000 @ 0x00026000)   32 MiB
backup       (0x0001a000 @ 0x00036000)   52 MiB
cache        (0x00040000 @ 0x00050000)  128 MiB
kpanic       (0x00002000 @ 0x00090000)    4 MiB
system       (0x00180000 @ 0x00092000)  768 MiB
metadata     (0x00002000 @ 0x00212000)    4 MiB
userdata     (0x00200000 @ 0x00214000) 1024 MiB
linuxroot    (0x00620000 @ 0x00414000) 3136 MiB

-----------------------8<-------------------8<--------------------------

You can see the linuxroot partition above, right ? Then you can backup it by issueing command:

    $ sudo rkflashkit backup @linuxroot  mylinuxroot.img

tedd77

hello busybee,

thank you, I will try again to do the image using your method.

as for the rkflashkit the only partitions I can see are resource, boot, misc, and backup.

============= 2014-12-22 10:11:54 ============


    Loading partition information

    PARM FIRMWARE_VER:4.4.2
    MACHINE_MODEL:rk30sdk
    MACHINE_ID:007
    MANUFACTURER:RK30SDK
    MAGIC: 0x5041524B
    ATAG: 0x60000800
    MACHINE: 3066
    CHECK_MASK: 0x80
    PWR_HLD: 0,0,A,0,1
    #KERNEL_IMG: 0x62008000
    #FDT_NAME: rk-kernel.dtb
    #RECOVER_KEY: 1,1,0,20,0
    CMDLINE:console=ttyFIQ0,115200 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(resource),0x00008000@0x0000A000(boot),0x00002000@0x00012000(misc),0x0001a000@0x00014000(backup),-@0x0002e000(linuxroot)

Partitions:
resource     (0x00008000 @ 0x00002000)   16 MiB
boot         (0x00008000 @ 0x0000a000)   16 MiB
misc         (0x00002000 @ 0x00012000)    4 MiB
backup       (0x0001a000 @ 0x00014000)   52 MiB

-----------------------

Although the linuxroot is stated in the CMDLINE however I cannot see in the form of a partition in order to be able to backup.

I am using the rkflashkit present under the git clone https://github.com/linuxerwang/rkflashkit

Best regards

tedd77

hello busybee,




I did the image as per your instructions, when trying to flash with androidtool I get loading firmware failed.

Unless there is another tool to flash back to the board the image we created it not suitable .




I hope my experience will benefit other members.

Please look into it and advise with proper remedie.

busybee

Woud you please post the AndroidTool snapshot with failure message?




I personally like to flash individual image with rkflashkit:




sudo rkflashkit flash @linuxroot ?your_linux_root.img




or launch its friendly GUI:

sudo rkflashkit

select the partition and image file and flash.

busybee

For rkflashkit alike tools to work, the device must be set to "upgrade mode".?

?
http://wiki.t-firefly.com/index.php/Fir ... h_image/en
?has the detail.

tedd77

Hello busybee,

Thank you for the instructions.

The results of sudo du -hxs / is 3.2G

I am stuck a the following point : $ sudo mount -o loop new_ubuntu.img /mnt/new

Getting error ?mount: block device /media/firefly/sd31g/new_ubuntu.img is write-protected, mounting read-only
mount: you must specify the filesystem type


The sd card was formatted as file system type=fat32




could you please advice if the command is correct?

tedd77

Hello,

I was able to make the rkflashkit see my device, I can see the following partitions:

resource, boot, misc, backup

I did backup all of them, but re-flashing them to the other board did not seem to make it identical. actually nothing has changed at all.

tedd77

Hello busybee,

If Firefly support cannot help, where from can we get it ?

Please let me know if you are willing to support or not! that way I can decide which way to go. Thank you

jas-rk

If it helps you can make a backup of the individual partitions on the eMMC using rkflashkit, some instructions on the wiki . ?It's not exactly the same as making a complete image of the eMMC but you should be able to restore them.

tedd77

jas-rk ,?Thank you, unfortunately the rkflashkit is not detecting my firefly board therefore I am unable to test what you suggested.