Nanopi M1 plus boot error

[franksmith]

Hello,
I’m new to the Nanopi M1 Plus development board. I followed the instructions on FriendlyARM's wiki page. I loaded the image from my Ubuntu OS and connected the device to my PC. The blue LED is blinking normally. I used PuTTY to view the logs, and during booting, it shows:


Members
Posted June 11, 2018
Hello I am new to Nanopi m1 plus development board. I followed the instruction as on friendlyarm's wiki page. I loaded the image from my Ubuntu OS and connected my device to the pc. The blue led was blinking normally. I used Putty to view the logs. While booting it is showing:



resize2fs 1.42.12 (29-Aug-2014)
resize2fs: Bad magic number in super-block while trying to open /dev/mmcblk0p2
Couldn't find valid filesystem superblock.
resize2fs exited with status code 1
done.
mount: mounting /dev/mmcblk0p2 on /root failed: Invalid argument done.
Target filesystem doesn't have requested /sbin/init.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ...
mount: mounting /dev on /root/dev failed: No such file or directory done.
No init found. Try passing init= bootarg.
Rebooting automatically due to panic= boot argument
[ 45.460839] reboot: Restarting system



I uploaded nanopi-m1-plus_friendlycore-xenial_3.4.y_YYYYMMDD.img.zip image.

What is the issue and how can it be resolved?

[wellshop]

Hi!
Based on the log you posted, the error Bad magic number in super-block usually means that the root filesystem on your SD card is corrupted or not properly written.
Here’s what I suggest:

Verify the image file: Make sure the .img.zip file downloaded correctly. Check its MD5 or SHA256 checksum if available.

Re-flash the SD card: Use a reliable tool like Etcher or dd to write the image to your SD card. Sometimes the write process fails silently.

Use a different SD card: Some cheaper or older SD cards can cause filesystem corruption. Try using a Class 10 or UHS-I card.

Check partitioning: Ensure the image was properly extracted and written to the SD card; the root filesystem (/dev/mmcblk0p2) should exist and be mountable.

After re-flashing, try booting again. If the problem persists, it might be a bad image build or incompatible SD card.