Nico21311

Hello I would like to know if it is possible to have 2 partions on the emmc. Indeed My emmc have 256go for only the os armbian with OMV (2.5go only used). I would like to have for example a boot partition with size of 50go and an other partition for my data (200go). However when I use armbian-config the full emmc is formated. If a solution exist could you please share with me the solution. Thanks in advance for your support.

Hello everyone I would like to provide you with my experience to maintain an OMV server with docker. the information below are strategi and not a tutorial step by step. After several installation I found for me the best install easy to maintain. My server is a nanopc T6 with EMMC memory and NVME disk. could work also with all other similar pc cards The solution works aloso with SDcard. the installation of armbian and OMV will installed on the SDcard or EMMC memory. Please note that in case you want to use EMMC memory please transfer os to EMMC before install OMV After that I recommend to spleet the NVME in two partitions one for docker data and other one for general data. The partition dedicated for docker I recommend 60 go (depend your size of your container) The data partition take the rest After that connect you in OMV, install service compose and declare all hard drive you have. In the partition for docker, create folder as following: - for docker named docker - one compose named compose - one data named data after that go to service compose parameter in OMV and declare all dossier above in the appropriate location example data for data etc. For the folder docker copy the exact folder link from share folder area in OMV. after that you can install portainer with compose file added in compose --> file. when you have installed portainer you can continue all docker installation through portainer. Now the most interesting, if you want to change your armbian os with a clean installation or pass to the new version of OMV. you can format the SDcard or EMC memory without a risk to loose your docker installation. indeed you reinstall the os and OMV on EMMC or SDcard after that you follow the instruction above to declare the different existing folder in OMV for docker configuration in compose, you save and all docker installation reappear as it its installed previously. hoping this information help you.

I have reinstall the device and the docker. However, I need to install the firmware 5.10.160. Indeed the nanopc-t6 don ot star with any image with firmware 6.1.43 or 6.8.9. I do not understand why ?. Apprently I understand that you are able to install the version 6.1.43 without issue. Could you please explain me the procedure you have used ? Thanks in advance for your support.

Hello Fever_wits Thanks you for your answer. I tried to reinstall an Armbian image with SD but the device never boot. when I use an official image all working well. Could you help me to recover the the possibility to install armbian image ? Thanks in advance for your support.

Hello all I have broken my installation when I tried to install the kernel 6.1 my current kernel 5.10.160-legacy-rk35xx. My nanopc t6 do not start. My installation is on EMMC and start on it. Could you please help me to recover it ? I have a backup file from OMV but I don't know how to push the backup to the EMMC? other possibility I guess copy the boot folder backup to EMMC boot folder but I do not know if it is enough. I really appreciate an help furthermore a clear turial could help evryone to recover an installation on EMMC memory. Thanks in advance for your support.

removed

Dear all I have a nanopc T6 with kernel 5.10.160 bullseye and omv 6 EMC 256gb avec NVME I would like to pass on omv 7 with bookworm. I found this command which change all automatically and keep the configuration. "omv-release-upgrade" Could you please confirm that this command could be used with armbian or an other metod exist ? Thanks in advance for your support.

Dear all My nanopi M4 V2 does not start My configuration is a sd card for booting + a NVME for the system. I have installed a lot of applications : OMV Docker with portainer history : I would change version from nightlight to stable with a bug during the pre-configuration of OMV. I need to perform a CTRL + C to stop this frozen action. After that I reboot my device with the same issue from post 1 Could you please help me to recover my device ? I would like tried to comeback to the previous version But I do not find the process. Thanks in advance for your support. example of message during the boot. failed to find ep-gpios property ethernet@fe300000 Waiting for PHY auto negotiation to complete.... done Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.8.60 (22 ms) *** Warning: no boot file name; using 'C0A8083C.img' Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'C0A8083C.img'. Load address: 0x800800 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-0e-26-67-a6-1d-cf Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/01-0e-26-67-a6-1d-cf'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8083C Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A8083C'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8083 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A8083'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A808 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A808'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A80'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A8'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399-evb_rk3399 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default-arm-rk3399-evb_rk3399'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default-arm-rk3399'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default-arm'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again Config file not found failed to find ep-gpios property Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.8.60 (53 ms) Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'boot.scr.uimg'. Load address: 0x500000 Loading: T T T T T T T T T T Retry count exceeded; starting again Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.8.60 (52 ms) Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'boot.scr.uimg'. Load address: 0x2080000 Loading: T T T T T T T T T T Retry count exceeded; starting again Invalid bus 0 (err=-19) Failed to initialize SPI flash at 0:0 (error -19) =>

Dear all I have the same issue with my nanopi M4 V2 My configuration is a sd card for booting + a NVME for the system. I have installled a lot of applications : OMV Docker with portainer history : I would change version from nightlight to stable with a bug during the pre-configuration of OMV. I need to perfrom a CTRL + C to stop this frozen action. After that I reboot my device with the same issue from post 1 Could you please help me to recover my device ? Thanks in advance for your support. example of message during the boot. failed to find ep-gpios property ethernet@fe300000 Waiting for PHY auto negotiation to complete.... done Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.8.60 (22 ms) *** Warning: no boot file name; using 'C0A8083C.img' Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'C0A8083C.img'. Load address: 0x800800 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-0e-26-67-a6-1d-cf Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/01-0e-26-67-a6-1d-cf'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8083C Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A8083C'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8083 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A8083'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A808 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A808'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A80'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A8'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0A'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C0'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/C Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/C'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399-evb_rk3399 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default-arm-rk3399-evb_rk3399'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399 Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default-arm-rk3399'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default-arm'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: bootfile Retrieving file: pxelinux.cfg/default Speed: 100, full duplex Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'pxelinux.cfg/default'. Load address: 0x600000 Loading: T T T T T T T T T T Retry count exceeded; starting again Config file not found failed to find ep-gpios property Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.8.60 (53 ms) Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'boot.scr.uimg'. Load address: 0x500000 Loading: T T T T T T T T T T Retry count exceeded; starting again Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.8.60 (52 ms) Using ethernet@fe300000 device TFTP from server 192.168.8.1; our IP address is 192.168.8.60 Filename 'boot.scr.uimg'. Load address: 0x2080000 Loading: T T T T T T T T T T Retry count exceeded; starting again Invalid bus 0 (err=-19) Failed to initialize SPI flash at 0:0 (error -19) =>