OPI PC+ not booting

[andrejmoltok]

wanted to make a system install to USB pendrive, but aborted it.

Now it wont boot at all , but i managed to check out what may be the problem with the help of uart and the following came out:

 

Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=e59363f1-765c-4660-9275-4563bb872371 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument
[   69.860443] Restarting system.
[   69.863951] Restarting Linux version 3.4.113-sun8i (root@devel) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #18 SMP PREEMPT Thu Jun 15 02:16:06 CEST 2017
[   69.863963]

U-Boot SPL 2017.05-armbian (Jun 15 2017 - 03:36:18)
DRAM: 1024 MiB
Trying to boot from MMC2

U-Boot 2017.05-armbian (Jun 15 2017 - 03:36:18 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC Plus
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 1, SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0
38518 bytes read in 188 ms (199.2 KiB/s)
Unknown command 'bmp' - try 'help'
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3565 bytes read in 205 ms (16.6 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
136 bytes read in 153 ms (0 Bytes/s)
5914640 bytes read in 538 ms (10.5 MiB/s)
4750952 bytes read in 400 ms (11.3 MiB/s)
Found legacy kernel configuration
36392 bytes read in 450 ms (78.1 KiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5914576 Bytes = 5.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   1024MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_select: ion chipid  [0x2c00081!
ion_reserve_common: ion reserve: [0x50000000, 0x60000000]!
Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.

 

And this goes over and over, like the system would be corrupted or something. What should i try next?

[tkaiser]

15 minutes ago, andrejmoltok said:

What should i try next?

 

You need another Linux system and a card reader. Attach the card reader with SD card inserted, check output of

lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,UUID

Then you need to mount the 1st partition of the SD card and edit /mnt/boot/ArmbianEnv.txt and adjust there the line reading

rootdev=UUID=e59363f1-765c-4660-9275-4563bb872371

and replace the part after 'UUID=' with what lsblk showed for partition of your SD card.

 

The above example assumed that you mounted the partition to /mnt, if that differs you need to edit still the respective file (/boot/ArmbianEnv.txt on the SD card's 1st partition)

[tkaiser]

BTW: Opi PC Plus has 8GB eMMC. Why not choosing this as target? Or was your system running from eMMC already and then you wanted to transfer the rootfs to an external USB storage device?

[andrejmoltok]

I was runnimg it from the internal 8GB mmc. It seams that i messed it up really bad.

[tkaiser]

1 hour ago, andrejmoltok said:

I was runnimg it from the internal 8GB mmc. It seams that i messed it up really bad.

 

IMO no. The recovery procedure is basically the same and now it's even more easy since you simply download an Armbian image, boot from SD card and modifiy the first partition of your eMMC as described above. Then shutdown, remove SD card, boot from eMMC, done.

[andrejmoltok]

Its booting something, but it doesnt react to the sd card inserted. I keeps repeating the sequence i posted in the beginning. Dont know why it wont boot from sdcard. I checked it is bootable. And the screen remain black. No text, no nothing, only modifies the screen frequency and resolution, thats all. The ethernet ports leds are on. This is whats going on, nothing else. I see forward getting a new one.

[martinayotte]

The SDCard should boot in priority over the eMMC.

You're better getting also a USB-TTL serial dongle to diagnose the boot process.

[andrejmoltok]

On 11/25/2017 at 3:32 PM, martinayotte said:

The SDCard should boot in priority over the eMMC.

You're better getting also a USB-TTL serial dongle to diagnose the boot process.

I have the diagnostic in the first post, if you could take a look at it. I have also attached the .tty file into this post for you. Yes, I have tried usb-ttl debug, but i can't figure out what should I do to recover the system.

orangepipc.tty

[martinayotte]

Did you have done what tkaiser suggested with "lsblk" ?

Did you verified that both /boot/armbienEnv.txt and /etc/fstab contain the right UUID ?

 

[andrejmoltok]

Not yet. But is it possible to do it with the internal eMMC also, to connect orangePI directly to another PC, to do the thing tkaiser mentioned?

[tkaiser]

3 hours ago, andrejmoltok said:

But is it possible to do it with the internal eMMC also, to connect orangePI directly to another PC, to do the thing tkaiser mentioned?

 

Not in your situation on your board since this would require FEL mode, there's no FEL button on this board and to enter FEL mode you would need to boot a special mini SD card image. And since SD card is not working for you (check card detect pin)...

[andrejmoltok]

I have checked, the detect pin is working fine. Now i only need to test, whether will it boot or not. Last thing i was doing on the system, was installing wifi access point and a usb install on a usb attached. I wonder, whether these actions are responsible for not booting in any way.