gilarelli

Hey @CarlosGomes , great blog! I found some times ago your post on your 3D printed nanopi case and it's really good and interesting! I didn't look further to try to solve my apt-get problem inside the chroot, as being able to download the packages was good enough for me - and my priority was to be able to boot as quickly as possible as all my documents are on this machine. Be careful with those 2.5 disks as I had the same RAID configuration and 3 out of 4 disks (WD black too) died at the same time... Luckily, I could get nearly 90% of my data back. My advice would be to use NAS designed disks (such as WD RED Pro) and not desktop ones as they are NOT designed to handle the kind of stress. And be careful with some WD disks: https://raid.wiki.kernel.org/index.php/Linux_Raid#Introduction Anyway, I'm honored to have been able to help you! Cheers! @StormMaster: the only advice I would give you then, is to check regularly dmesg for any SATA related errors just in case. You can find some tools that would help you with this monitoring as well as sending you an email if there are any errors. Cheers! Found the culprit thanks to this post: Missing dtb file for our board in the updated package:

You should try the mmc app to check your eMMC disk if you haven't already: https://packages.debian.org/stretch/mmc-utils https://mirror.sjtu.edu.cn/armbian/pool/bullseye-utils/m/mmc-utils/ # mmc extcsd read /dev/mmcblk1 |grep EXT_CSD eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01 eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x01 eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01 More info here on the values returned: https://developer.toradex.com/knowledge-base/emmc-linux#Health_Status_as_Defined_in_the_eMMC_50_Standard_Onwards

Sorry for you... You reinstalled on the same eMMC?

Hey, just solved the same issue yesterday evening (bricked nanopi v1 after kernel update last sunday). Here is what I did to solve it: create a SDCard boot disk plug the SDCard and boot with it (it will bypass the eMMC card) set the root password and you should be able to ssh into it mount the eMMC filesystem rw chroot in the mount (lol) - with the right folder binded before (proc & sys) wget some files - for me it was those 3: linux-dtb-legacy-rk3399_21.08.2_arm64.deb linux-headers-legacy-rk3399_21.08.2_arm64.deb linux-image-legacy-rk3399_21.08.2_arm64.deb from here: http://mirrors.netix.net/armbian/apt/pool/main/l/linux-4.4.213-rk3399/ (the new ones were still in /var/cache/apt/archives so I knew which ones were upgraded - and for some reason, I was unable to use apt-get in the chroot, that's why I had to download them directly - and I choose those versions because I thought that going back to the previous versions was enough) dpkg -i those files halt the nanopi and remove the SDCard restart and voilà I installed manually the linux-libc-dev package once booted with as I couldn't find it for downloading: # sudo apt-get install linux-libc-dev=21.08.2 -V To be sure that those packages will not be upgraded with future upgrades, I put a hold on them with "apt-mark hold": # apt-mark hold linux-libc-dev linux-dtb-legacy-rk3399 linux-headers-legacy-rk3399 linux-image-legacy-rk3399 # dpkg -l | grep "^hi" hi linux-dtb-legacy-rk3399 21.08.2 arm64 Linux DTB, version 4.4.213-rk3399 hi linux-headers-legacy-rk3399 21.08.2 arm64 Linux kernel headers for 4.4.213-rk3399 on arm64 hi linux-image-legacy-rk3399 21.08.2 arm64 Linux kernel, version 4.4.213-rk3399 hi linux-libc-dev:arm64 21.08.2 arm64 Armbian Linux support headers for userspace development Feel free to ask if you want any more information!