I have tried with both root and the account I created at install. Both give the same reject response. Using both SSH and Console.
Ill give Tuned a shot... If I can ever get logged back in.
I didn't do anything special, but I might have seen service starting messages for them at boot (I am using the image for Helios64).
I made a copy of /etc/shadow before I edited it, but the result is the same. Still says I have 5 bad password attempts, even after days of not trying to log in.
I failed my password attempts (5 times) a few days ago. The account is still not allowing for a login.
I have attempted to remove the password from /ect/shadow but I am still getting prompted for a password, so either I didnt do it right or it didnt save.
Here is a pastebin of me just pressing the reset button. Full unedited output.
https://pastebin.com/jB1xJjLE
It booted normally but I did notice that there was a FSCK that happened.
The corruption seems to happen over time, if I leave it run for a few days it will end up rebooting itself and Ill have to FSCK again before it will boot normally.
I just did a FSCK, so I can try to reboot manually but I dont think that will show me any corruption. If I leave it to do its thing with the console up and monitoring I can hopefully capture the output and Ill update.
So, I came down tonight to the system in the same state, halted on the FSCK.
Seems to have booted fine after I manually ran it, but if it reboots every few days and I have to go do the FSCK every time, I might actually cry.
I was able to get it booting. The following is the error that was causing it to hang.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1 contains a file system with errors, check forced.
/dev/mmcblk0p1: Inode 753 seems to contain garbage.
/dev/mmcblk0p1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/mmcblk0p1 requires a manual fsck
I then just ran
fsck.ext4 /dev/mmcblk0p1
After that it ran and booted to OMV on its own.
I have run into this issue multiple times and the process flow is this:
Flash image "Armbian_20.11.6_Helios64_buster_current_5.9.14.img" to a micro SD card.
Run through the config (installing OMV with SAMBA)
Kick over to the OMV to configure the share / media so its available on my network
Runs for some time (this last install was running for maybe a few weeks before it triggered a Kernel panic)
Power off.
Power on.
Board boots, hangs on "Starting Kernel..."
Is there some trick I am missing to get this thing to actually boot / reboot correctly?
Troubleshooting info:
No jumpers are shorted.
I had a similar issue with a previous img as well.