OS stuck at boot 看全部

Hi,
I have some orangepi zero boards running armbian and I was having issues with SD card corruption. Doing some research led me to the conclusion that I should make the OS read only. So i created 2 partitions on the SD card with armbian on the first partition and made it readonly and other partition I mounted as read/write since I needed to have a persistent storage also. But after doing that I still have random devices getting stuck at boot after running fine for sometime. I got one of them and attached the serial converter and got some logs but searching about them online is leading to various conclusions like power supply or end of life SD card. I am not very experienced with low level kernel stuff, so if anyone can help me point in some direction how to narrow down this issue, it would be a grea help.

Logs from the serial port: https://pastebin.com/embed_js/XKaY1vyY
  • 推荐 Jagger
  • 2022-10-1 05:12:39
I recommended that my colleague go to this website called https://howtowiki.net/how-to-write-a-good-dissertation/. And the outcome pleased him much. There are no disadvantages.
Well its  some time since you posted this, but the answer is indeed in your logs:

  1. [ 18.893668] EXT4-fs error (device mmcblk0p1): __ext4_get_inode_loc:4699: inode #973: block 136: comm armbian-hardwar: unable to read itable block
  2. [ 18.907601] EXT4-fs (mmcblk0p1): I/O error while writing superblock
  3. [ 18.920729] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected
  4. [ 18.933947] EXT4-fs (mmcblk0p1): I/O error while writing superblock
  5. [DEPEND] Dependency failed for Network Manager Wait Online.
  6. [ 18.956421] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1531: inode #11733: comm armbian-hardwar: reading directory lblock 0
  7. [FAILED[ 18.969158] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1531: inode #11727: comm armbian-hardwar: reading directory lblock 0
  8. ] Failed to start Dispatcher daemon for systemd-networkd.
  9. [ 18.982688] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1531: inode #4367: comm armbian-hardwar: reading directory lblock 0
  10. [ 18.999378] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1531: inode #29827: comm armbian-hardwar: reading directory lblock 0
  11. [ 19.011391] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1531: inode #12: comm armbian-hardwar: reading directory lblock 0


So what its showing is corruption on the cards file system.
The linux filesystem is much more  resilient than FAT32 and NTFS and the individual
sectors are called inodes.
Has this card been used in anything else, camera, laptop ?

It is possible to repair the errors if you can get the sd card into a laptop running linux.
The command would be:
sudo fsck.ext4  /dev/sdx

Device sdx would be the designation of the card, as its sometime since you posted
you may have solved this error.

The buster version of Armbian now  has a major advantage in that the partition is expanded
to use the full sd card making corruption less likely. When I used Raspberry Pi it had two partitions a FAT partition which would always corrupt. The Orange Pi is more powerful and uses less power and with Armbian ideal for IoT
Hope that helps.
This article is an excellent example of how journalism ovo game can make a real difference in people's lives.
1234.. 7NextPage