Jump to content

Recommended Posts

Posted

Hello,

i try to move it from SD to eMMC on a Orange Pi Zero +2 H5, but without success.
Shouldn't be two partion created on eMMC by the nand-sata-install script ? 

 

root@orangepizeroplus2:~# fdisk -l /dev/mmcblk2
Disk /dev/mmcblk2: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe8c6ce8d

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk2p1       8192 15117183 15108992  7.2G 83 Linux




Old UUID:  /dev/mmcblk0p1
SD UUID:   UUID=85ffa85e-4784-4cfd-93bb-db6f93f8ef0b
UUID=dcb9caff-046e-4a9f-8d17-580c67514cf6
SATA UUID: UUID=dcb9caff-046e-4a9f-8d17-580c67514cf6
eMMC UUID: UUID=dcb9caff-046e-4a9f-8d17-580c67514cf6 ext4
Boot: $1 /dev/mmcblk2p1 ext4
Root: $2 /dev/mmcblk2p1
Usage: 1137
Dest: 6781

 

 

regards

MoHorst

Posted
  On 10/31/2018 at 9:59 AM, mohorst said:

Shouldn't be two partion created on eMMC by the nand-sata-install script ?

Expand  

No ! partitioning of the eMMC should be identical to the one on SD.

Can you provide boot log details from serial debug port ?

Posted (edited)

Thanks, for the quick response.
 

  Reveal hidden contents

 

 

 

 

 

 

 

Edited by Tido
added Spoiler
Posted
  On 10/31/2018 at 1:25 PM, mohorst said:

ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!

Expand  

This means that maybe either /boot/armbianEnv.txt or /etc/fstab present on eMMC, or both, have the wrong UUID.

Boot again with SDCard, mount the eMMC manually, and check/edit those to have proper UUID.

Then halt the OS, eject the SDCard, and recycle power to boot from eMMC.

 

Posted

The fstab is fine 

 

blkid
/dev/mmcblk0p1: UUID="85ffa85e-4784-4cfd-93bb-db6f93f8ef0b" TYPE="ext4" PARTUUID="cac5f6cc-01"
/dev/mmcblk2p1: UUID="f817ad43-5219-4498-a6ac-f14e5ac76fd3" TYPE="ext4" PARTUUID="8bc978ec-01"
/dev/mmcblk0: PTUUID="cac5f6cc" PTTYPE="dos"
/dev/mmcblk2: PTUUID="8bc978ec" PTTYPE="dos"

 

 

root@orangepizeroplus2:/mnt/tt/etc# cat fstab
# <file system>                                 <mount point>   <type>  <options>                                                    <dump>   <pass>
tmpfs                                           /tmp            tmpfs   defaults,nosuid                                              00
UUID=f817ad43-5219-4498-a6ac-f14e5ac76fd3       /               ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide  0       1

 

I assume, i have to add to armbianEnv.txt

rootdev=UUID=f817ad43-5219-4498-a6ac-f14e5ac76fd3 

rootfstype=ext4

 

root@orangepizeroplus2:/mnt/tt/boot# cat armbianEnv.txt
#       $OpenBSD: sshd_config,v 1.100 2016/08/15 12:32:04 naddy Exp $
# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.
# This sshd was compiled
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Posted

I think, here is the issue, if the rootdev is not in the original file, it wouldn't be changed or added.

 

------nand-sata-install line 224-----
# new boot scripts
                if [[ -f ${TempDir}/bootfs/boot/armbianEnv.txt ]]; then
                        sed -e 's,rootdev=.*,rootdev='"$targetuuid"',g' -i ${TempDir}/bootfs/boot/armbianEnv.txt
                else

 

------nand-sata-install-----

Posted
  On 10/31/2018 at 1:59 PM, mohorst said:

root@orangepizeroplus2:/mnt/tt/boot# cat armbianEnv.txt # $OpenBSD: sshd_config,v 1.100 2016/08/15 12:32:04 naddy Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Expand  

This seems to be a file corrupted, because it kind of copy of /etc/ssh/sshd_config, hoping that there is no other files corrupted ...

 

Take a copy of SDCard /boot/armbianEnv.txt and place it into the eMMC after changing the UUID.

Posted

Could it be that the image on the SD card you first used was corrupted? Did you use Etcher to create the SD card?  Just curious... :-)

Posted
  On 11/1/2018 at 1:56 PM, pzw said:

Could it be that the image on the SD card you first used was corrupted? Did you use Etcher to create the SD card?  Just curious... :-)

Expand  

I couldn't reproduce the problem, it was a fresh installation with only a few changes. I used ImageWriter.

  • Tido changed the title to Orange Pi Zero +2 H5 - SD to eMMC
Posted
  On 11/3/2018 at 9:32 AM, mohorst said:

I used ImageWriter.

Expand  

There is a reason why Etcher is recommended by the creators of Armbian... It is for sure one of the (few) image writing utilities which actually verify after the writing... And yes, that is important, because corrupted SD cards can generate strange issues.....

Good to hear it is working, but I would strongly recommend using Etcher to create the flash cards in the future, to ensure you are not dealing with a corrupted image on the card...

Posted

Hi 

Does anyone know how to do the opposite.

Meaning copy from the emmc back to the sd card?

I ran out of space on my 8GB

 

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines