September 18, 2019, 07:34:16 am


Have you visited the Allwinner Chipset wiki? -

cubian-nandistall 3 partition enhancement RC

Started by mzapa, June 02, 2014, 10:45:07 am

Previous topic - Next topic


Cubieplayer's latest version (v.1.1-4) of cubian-nandinstall works great!  Really nice to have the 2  clean partitions on nand but my current project requires 3 partitions so I modified cubian-nandinstall to suit my needs.  This version (v1.1-4CRC-1) is based off of Cubieplayer's v1.1-4 and is considered an "EXPERIMENTAL" custom release candidate.  This does not replace the repo cubian-nandinstall but is dependant on the repo version being installed.  This insures the current GA version of the bootloader and boot partition is used when running the CRC version.  The repo version (cubian-nandinstall) can be executed if a 2 partion nand is desired OR the CRC version (my-cubian-nandinstall) can be executed if a 3 partition nand is desired.

The CRC version can be placed anywhere on the SD such as /tmp.  If placed in /tmp, the script MUST be executed in /tmp/MY_NAND_INSTALL_DIST as your current working directory.  The accompanying exclude file MUST reside in the same directory as the script.  DO NOT OVERWRITE THE GA VERSION OF THE EXCLUDE FILE OR THE GA VERSION WILL FAIL.  An additional exclude entry is added that will not migrate swap files IF swapfiles located on the root directory are named swap* otherwise if you have swap files on your SD named differently, add them to the my-exclude.txt file.  This speeds up file transfer AND will not eat up space on the nand. Not fun running out of space installing to nand.

The nand partition layout will be:

   nanda bootloader
   nandb initrd (/boot)
   nandc linux (rootfs)

/boot is symlinked to nandb so you'll see /boot off the root as before.  If the symlink is not wanted, delete it and remove/comment out the entry in /etc/fstab.  Either umount /mnt/nandb OR on next reboot, the partition wont be mounted.  The symlink is not required to boot from nand.

Here's a snip from nand-part post execution:

3 partitions
partition  1: class =         DISK, name =   bootloader, partition start =    32768, partition size =     2048 user_type=0
partition  2: class =         DISK, name =       initrd, partition start =    34816, partition size =    20480 user_type=0
partition  3: class =         DISK, name =        linux, partition start =    55296, partition size =        0 user_type=0

Here's the directory layout on the root filesystem post execution:

drwxr-xr-x   2 root root  4096 May 31 01:48 bin
lrwxrwxrwx   1 root root    15 Jun  2 03:28 boot -> /mnt/nandb/boot
drwxr-xr-x  11 root root  3360 Jun  2 05:30 dev
drwxr-xr-x  92 root root  4096 Jun  2 05:43 etc
drwxr-xr-x   3 root root  4096 Feb  7 18:52 home
drwxr-xr-x  13 root root  4096 May 31 01:48 lib
drwx------   2 root root 16384 Feb  7 19:29 lost+found
drwxr-xr-x   2 root root  4096 Jun  2 00:41 media
drwxr-xr-x   3 root root  4096 Jun  2 03:28 mnt
drwxr-xr-x   2 root root  4096 Oct  7  2013 opt
dr-xr-xr-x 167 root root     0 Jan  1  1970 proc
drwx------  21 root root  4096 Jun  2 05:25 root
drwxr-xr-x  18 root root   740 Jun  2 07:46 run
drwxr-xr-x   2 root root  4096 May 31 01:48 sbin
drwxr-xr-x   2 root root  4096 Jun 10  2012 selinux
drwxr-xr-x   2 root root  4096 Oct  7  2013 srv
dr-xr-xr-x  12 root root     0 Jun  2 05:29 sys
drwxr-xr-x   3 root root  4096 Mar  8 00:14 system
drwxrwxrwt   4 root root  4096 Jun  2 14:30 tmp
drwxr-xr-x  10 root root  4096 Feb  7 18:52 usr
drwxr-xr-x  15 root root  4096 Mar  9 15:55 var


MD5 Checksum
826f675e3eb5107a3ed6d70c5d20d828  my-nandinstall.tar.gz