Quanta Posted January 5, 2019 Share Posted January 5, 2019 (edited) Preamble: I have done numerous hours of reading and searching (due diligence). See end. I have a FA NanoPi NEO Core-2 LTS with shield and 64G M.2 (This shield uses JMS567-LGBB1A chip USB to sata for M.2 access). I have successfully installed Armbian from SD to and booted from the eMMC. Armbian Stretch mainline kernel 4.14.y - This image https://dl.armbian.com/nanopineocore2/Debian_stretch_next.7z armbianmonitor -u results http://ix.io/1xAA Logs indicate formatting did occur correctly as far as I can tell. The volumes are formatted as I selected - along with an 'extra' ext4 volume that looks like it is just for boot. NOTE: Since I could not boot, I re-tried using default ext4 for both which works. System now boots Armbian without TF. ATM OS resides on sda1. Console output: INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON U-Boot SPL 2018.05-armbian (Oct 27 2018 - 08:32:18 +0200) DRAM: 1024 MiB Trying to boot from MMC2 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):c9f55c0 NOTICE: BL3-1: Built : 08:32:12, Oct 27 2018 NOTICE: DT: sun50i-h5-nanopi-neo-core2 NOTICE: SCPI: dummy stub handler, implementation level: 000000 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2018.05-armbian (Oct 27 2018 - 08:32:18 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO Core 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... MMC: no card present ** Bad device mmc 0 ** Failed (-5) In: serial Out: serial Err: serial Net: No ethernet found. MMC: no card present ** Bad device mmc 0 ** MMC: no card present ** Bad device mmc 0 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3090 bytes read in 4 ms (753.9 KiB/s) ## Executing script at 4fc00000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 208 bytes read in 2 ms (101.6 KiB/s) MMC: no card present ** Bad device mmc 0 ** 30102 bytes read in 11 ms (2.6 MiB/s) 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo 504 bytes read in 14 ms (35.2 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo 4179 bytes read in 13 ms (313.5 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 4923549 bytes read in 247 ms (19 MiB/s) 13148168 bytes read in 649 ms (19.3 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4923485 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49b4d000, end 49fff05d ... OK reserving fdt memory region: addr=4fa00000 size=6d000 Loading Device Tree to 0000000049add000, end 0000000049b4cfff ... OK Starting kernel ... Loading, please wait... starting version 232 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. Begin: Will now check root file system ... fsck from util-linux 2.29.2 done. mount: Invalid argument done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: No such file or directory mount: invalid option -- done. mount: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 No init found. Try passing init= bootarg. Rebooting automatically due to panic= boot argument To elaborate on the process, after writing TF card and booting, I ran armbian-config selecting option "eMMC boot | USB/SATA/NVMe root install" and selected format of btrfs for sda1. Also, "Select filesystem type for eMMC /dev/mmcblk2" ... "Formating /dev/mmcblk2 to f2fs ... please wait". The utility responded with the appropriate warnings (about erasing/formatting) and appeared to execute correctly, returning no errors and prompting for reboot at end of process. I shutdown, removed card, powered up and system did not come up properly. I saw no special advisories about additional manual steps etc. Question: Did I miss a step when using the alternative disk format options on this platform? Are they a WIP? Should I file a bug report? 'Bibliography:' https://docs.armbian.com/User-Guide_Getting-Started/ https://docs.armbian.com/User-Guide_Armbian-Config/ Nearly all NanoPi NEO2 forum posts here Many others... Edited January 6, 2019 by Quanta correct board reference in title and elsewhere Link to comment Share on other sites More sharing options...
Recommended Posts