Angstrom systemd-fsck fail

Hi!

I've compiled the latest Angstrom linux using setup-scripts, rootfs is
console-version.

I use a SD card for test purposes and have to reboot often. Suddenly
this message appears:

systemd-fsck[76]: Angstrom has been mounted 26 times without being
checked, check forced.
systemd-fsck[76]: Angstrom: Inodes that were part of a corrupted
orphan linked list found.
systemd-fsck[76]: Angstrom: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck[76]: (i.e., without -a or -p options)
Dependency failed. Aborted start of Getty on tty1 [ ABORT]

and the board hangs. The only I can do is hardware reset but after
that the system comes to the same state and there is only one way to
heal it: rewrite roofs on a SD card. Is there a bug or something?

Hi!

I've compiled the latest Angstrom linux using setup-scripts, rootfs is
console-version.

I use a SD card for test purposes and have to reboot often. Suddenly
this message appears:

systemd-fsck[76]: Angstrom has been mounted 26 times without being
checked, check forced.
systemd-fsck[76]: Angstrom: Inodes that were part of a corrupted
orphan linked list found.
systemd-fsck[76]: Angstrom: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck[76]: (i.e., without -a or -p options)
Dependency failed. Aborted start of Getty on tty1 [ ABORT]

and the board hangs. The only I can do is hardware reset but after
that the system comes to the same state and there is only one way to
heal it: rewrite roofs on a SD card.

Or run fsck manually on a different computer or use a card reader and use the current board

Is there a bug or something?

It's working as expected: letting you know the filesystem has become corrupted. If we had a proper initramfs we could try to recover from this, but the cons outweigh the pros on that front currently.

regards,

Koen

Koen, thanks for help. Anyway it is not clear for me those corruptions
occur. I always do reboot by "reboot" and power off by "poweroff".
What is wrong?

Koen, thanks for help. Anyway it is not clear for me those corruptions
occur. I always do reboot by "reboot" and power off by "poweroff".
What is wrong?

Well, the SD card. Some SD cards can't handle extN and silently corrupt data. I'm too scared to ask Arnd Bergmann for more info on all that...

well it is first time in my experience with Angstrom when data is
silently corrupted. All previous builds (marked as 2010.xx) worked
fine.