We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

board reset failure



  • root@Omega-BEA9:/etc/opkg# oupgrade -v

    Device Firmware Version: 0.1.10 b160
    this is my initial version.

    root@Omega-BEA9:~# df -h
    Filesystem            	Size  	Used   Available   Use% Mounted on
    /dev/root             	5.5M  	5.5M   	0        100%   /rom
    tmpfs                	61.4M 	96.0K 	61.3M   0%      /tmp
    /dev/mtdblock6          25.1M  	3.1M 	22.0M   12%    /overlay
    overlayfs:/overlay   	25.1M  	3.1M 	22.0M   12%    /
    tmpfs               	512.0K     0	512.0K   0%    /dev
    
    

    i have upgraded to
    root@Omega-BEA9:~# oupgrade -v

    Device Firmware Version: 0.3.2 b233

    root@Omega-BEA9:~# df -h
    Filesystem            	Size  	Used Available Use% Mounted on
    /dev/root             	7.8M  	7.8M     	0   100%   /rom
    tmpfs                	60.9M	228.0K 	60.7M   0% /tmp
    /dev/mtdblock6       	22.1M 	22.1M   0 100% /overlay
    tmpfs                	60.9M	116.0K 	60.8M   0% /tmp/root
    overlayfs:/tmp/root  	60.9M	116.0K 	60.8M   0% /
    tmpfs               	512.0K     0	512.0K   0% /dev
    /dev/mtdblock7      	512.0K	196.0K	316.0K  38% /mnt/mtdblock7
    /dev/mmcblk0p1       	14.8G 	96.0K 	14.8G   0% /mnt/mmcblk0p1
    
    

    16 GB SD card is connected to the board
    now whatever I install it shows 0 remaining in overlay, so i am trying to reset the board to the initial b160 version,
    I have tried both firstboot cmd method and the button reset method, but it does not revert back to b160.

    and also I am facing an issue with booting from sd card.


  • administrators

    @Balajiembd factory reset will erase the overlay partition. So you will start with a clean slate of the last installed firmware. It will not take you back to b160.

    See this recent discussion on the forum and the factory reset documentation page for more information.



  • thanks @Lazar-Demin ,

    it seems overlay is full ( 22.1M 22.M available -0 )

    so not able to install anything (i need to install jool NAT64)

    when i try to boot from SDCARD (16GB) i am facing issue .

    https://docs.onion.io/omega2-docs/boot-from-external-storage.html

    after doing all steps overlay size is not changed (SDcard is mounting as storage only)

    root@Omega-BEA9:~# df -h
    Filesystem            	Size  	Used Available Use% Mounted on
    /dev/root             	7.8M  	7.8M     0   100%    /rom
    tmpfs                	60.9M	228.0K 	60.7M   0%   /tmp
    /dev/mtdblock6       	22.1M 	22.1M   0     100%   /overlay
    tmpfs                	60.9M	116.0K 	60.8M   0%   /tmp/root
    overlayfs:/tmp/root  	60.9M	116.0K 	60.8M   0%   /
    tmpfs               	512.0K     0	512.0K   0%   /dev
    /dev/mtdblock7      	512.0K	196.0K	316.0K  38%   /mnt/mtdblock7
    /dev/mmcblk0p1       	14.8G 	96.0K 	14.8G   0%    /mnt/mmcblk0p1
    
    

  • administrators

    @Balajiembd yeah, it looks like the overlay partition is still on the flash and has not been moved to the external storage.
    Have you followed all the steps from the documentation page? The procedure should work.



  • Yes i have followed all the step given in the procedure
    https://docs.onion.io/omega2-docs/boot-from-external-storage.html

    do you have any other page link or doc only for SSD ,
    i tried many times , kindly help



  • steps used... kindly let me know did i miss something ...

    Filesystem                Size      Used Available Use% Mounted on
    /dev/root                 7.8M      7.8M         0 100% /rom
    tmpfs                    60.9M    100.0K     60.8M   0% /tmp
    /dev/mtdblock6           22.1M     22.1M         0 100% /overlay
    tmpfs                    60.9M    128.0K     60.8M   0% /tmp/root
    overlayfs:/tmp/root      60.9M    128.0K     60.8M   0% /
    tmpfs                   512.0K         0    512.0K   0% /dev
    /dev/mtdblock7          512.0K    196.0K    316.0K  38% /mnt/mtdblock7
    /dev/mmcblk0p1           14.5G     61.7M     13.7G   0% /mnt/mmcblk0p1
    root@Omega-BEA9:~# umount /dev/mmcblk0p1
    root@Omega-BEA9:~# mkfs.ext4 /dev/mmcblk0p1
    mke2fs 1.44.1 (24-Mar-2018)
    /dev/mmcblk0p1 contains a ext4 file system
    	last mounted on /mnt on Fri Dec  6 16:28:18 2019
    Proceed anyway? (y,N) y
    Creating filesystem with 3888512 4k blocks and 972944 inodes
    Filesystem UUID: 29c73378-a1f5-4b40-9c73-93da09f3e53e
    Superblock backups stored on blocks: 
    	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
    
    Allocating group tables: done                            
    Writing inode tables: done                            
    Creating journal (16384 blocks): done
    Writing superblocks and filesystem accounting information: done 
    
    root@Omega-BEA9:~# cd /mnt/
    root@Omega-BEA9:/mnt# ls
    mmcblk0p1  mtdblock7
    root@Omega-BEA9:/mnt# mount /dev/mmcblk0p1 /mnt/ ; tar -C /overlay -cvf - . | ta
    r -C /mnt/ -xf - ; umount /mnt/
    ./
    ./sysupgrade.tgz
    
    root@Omega-BEA9:/mnt# opkg install block-mount
    Package block-mount (2018-04-16-e2436836-1) installed in root is up to date.
    root@Omega-BEA9:/mnt# block detect > /etc/config/fstab
    root@Omega-BEA9:/mnt# vi /etc/config/fstab
    root@Omega-BEA9:/mnt# cat /etc/config/fstab
    config 'global'
    	option	anon_swap	'0'
    	option	anon_mount	'0'
    	option	auto_swap	'1'
    	option	auto_mount	'1'
    	option	delay_root	'5'
    	option	check_fs	'0'
    
    config 'mount'
    	option	target	'/overlay'
    	option	uuid	'29c73378-a1f5-4b40-9c73-93da09f3e53e'
    	option	enabled	'1'
    
    
    

  • administrators

    @Balajiembd as a general aside: I would recommend making a new topic in the forum since the conversation doesn't relate to factory reset.

    It also looks like you're using b233 firmware which is the stable version.
    I would recommend upgrading the firmware to the latest version (b256) and trying again. See this docs page for more details: http://docs.onion.io/omega2-docs/using-the-omega-updating.html#upgrading-to-the-latest-version

    It would also be helpful for debugging if, after the mount /dev/mmcblk0p1 /mnt/ ; tar -C /overlay -cvf - . | ta r -C /mnt/ -xf - ; umount /mnt/ command, you did a ls /mnt to confirm the overlay partition was indeed copied to the external storage.

    Another avenue you can explore (also after updating to the latest firmware): try doing this procedure using the script that does this procedure for the omega2 pro device: https://github.com/OnionIoT/OpenWRT-Packages/blob/openwrt-18.06/omega2pro/files/o2-pro-init.sh



  • thanks i have upgraded version to b256 version .

    now i can able to do use

    sd card as bootable

    root@Omega-BEA9:~# df -h
    Filesystem                Size      Used Available Use% Mounted on
    /dev/root                 7.8M      7.8M         0 100% /rom
    tmpfs                    60.9M     96.0K     60.8M   0% /tmp
    /dev/mmcblk0p1           14.5G     40.3M     13.7G   0% /overlay
    overlayfs:/overlay       14.5G     40.3M     13.7G   0% /
    tmpfs                   512.0K         0    512.0K   0% /dev
    /dev/mmcblk0p1           14.5G     40.3M     13.7G   0% /mnt/mmcblk0p1
    /dev/mtdblock6           22.1M    708.0K     21.4M   3% /mnt/mtdblock6
    /dev/mtdblock7          512.0K    196.0K    316.0K  38% /mnt/mtdblock7
    
    


Looks like your connection to Community was lost, please wait while we try to reconnect.