Access point stuck in continuous loop on terminal device
Access point stuck in continuous loop on terminal device
Set up the main drive on your laptop. Open /home/pi/.ssh and verify the authorized_keys file. Remove it if missing or incorrect, or swap in your valid public key. Review /etc/ssh/sshd_config to confirm password login remains enabled when needed. Search for specific settings like PermitRootLogin no PasswordAuthentication yes. Temporarily allow password access so you can log in, then secure it again. If you changed PAM rules or altered /etc/passwd, you can switch into the Pi’s root environment from your laptop and reset the user password using: sudo chroot /mnt/pi-root passwd pi. Once everything is fixed, reinstall the SD card on the Pi and it should accept login attempts. After that, you can properly restore your SSH credentials.
I understand the issue with the sshd_config, my challenge is logging into the Raspberry Pi directly. I can only type a username on the terminal and press enter, then see flashing text that’s hard to read before returning to the login screen. After mounting the root partition to /mnt, I attempted to chroot using `sudo chroot /mnt/pi-root passwd pi` but got 'no such file or directory'. Then I tried just `sudo chroot /mnt`, which failed with a bash execution error.
The Exec format issue arises when attempting to jump into an ARM device from an x86 machine. The software doesn’t match because of architecture differences. You should mount the SD card and run qemu-user-static with binfmt to simulate ARM, or directly alter /etc/shadow on the mounted root file system to reset the Pi’s password manually. This approach avoids chroot and lets you log back in normally.
You're dealing with a tricky setup issue. It sounds like you've successfully chrooted into your Pi and managed passwords, but when logging in, you're encountering an unexpected error. The message about "inconsistency detected" suggests a mismatch between expected and actual behavior. It might be worth checking if the SD card is functioning properly—corrupted files or a failing drive could explain the problems with commands like `ls` and `get-dynamic-info`. Also, ensure your SSH configuration (`ssh_config`) is correct and that you're not running into permission issues. If the issue persists after confirming hardware health, consider reinstalling or repairing the system from a known good image.