I got Armbian 21.08.1 Buster ttyS0 any Login incorrect

[RaymondDay]

I have a old Armbian 21.08.1 Buster on a NanoPi NEO and I like to get it fixed.

 

I can only see what is going on though the Serial port on it.

 

It boots up with a lot of things missing. May guess is the swap on the SD card went bad years ago. I like to get this working again it was working real good back then till it did not boot any more.

 

At the end of the boot on the Serial port it looks like this:

 

[FAILED] Failed to start The Apache HTTP Server.
See 'systemctl status apache2.service' for details.
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[FAILED] Failed to start Webmin server daemon.
See 'systemctl status webmin.service' for details.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Stopped OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Serial Getty on ttyGS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: Brings up/down network automatically.
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Stopped OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Stopped OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[FAILED] Failed to start MariaDB 10.3.39 database server.
See 'systemctl status mariadb.service' for details.
[  OK  ] Started Samba NMB Daemon.
         Starting Samba SMB Daemon...
[  OK  ] Stopped OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Stopped OpenBSD Secure Shell server.
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Started The PHP 8.2 FastCGI Process Manager.
[  OK  ] Started The PHP 7.4 FastCGI Process Manager.
[  OK  ] Started The PHP 8.3 FastCGI Process Manager.
[  OK  ] Stopped Webmin server daemon.
         Starting Webmin server daemon...
[  OK  ] Started Samba SMB Daemon.
[FAILED] Failed to start Webmin server daemon.
See 'systemctl status webmin.service' for details.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Armbian 21.08.1 Buster ttyS0

nano-doc2 login: root

Login incorrect
nano-doc2 login:
Login timed out
Armbian 21.08.1 Buster ttyS0

nano-doc2 login:

 

The is a lo of red color [FAILED] on it.

 

I guess because Failed to start OpenBSD Secure Shell server that is why I can't log in even on the serial port.

 

I have mounted it as chroom on another system and I guess just don't have it mounted right to run a:

 

apt --fix-broken install -y

 

Guess that would fix it if I could run it some how.

 

I did add it to a start up script but it did not work I guess that did not start up.

 

Hope some one can help. It be grate to have this working again.

[RaymondDay]

When I put this SD card in another system and mount it I can see it's files.

 

In it's bash history the last typed before it did not boot was this if this helps to know what is wrong to fix it.

 

pt upgrade
apt --fix-broken install
dpkg -i mysql-apt-config_0.8.29-1_all.deb
apt install perl
apt --fix-broken install
cd /usr/bin/perl
apt install perl
apt --fix-broken install perl
dpkg -i --force-overwrite mysql-apt-config_0.8.29-1_all.deb
uname -a
install mysql-server-5.5
atp install mysql-server-5.5
lsb_release -a
reboot

 

Hope some one can help.

Edited Monday at 10:14 AM by RaymondDay

[RaymondDay]

If I do chroom on it and try and fix it get errors:

 

root@rday1:~# mount /dev/sdf1 /mnt/temp
root@rday1:~# chroot /mnt/temp
root@rday1:/# ls
bin  boot  dev  etc  home  lib  lost+found  media  mnt  opt  proc  root  run  sbin  selinux  srv  sys  tmp  usr  var  webmin-setup.out
root@rday1:/# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libc-bin libc-l10n libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libjansson4 libnsl-dev libnsl2 libpam0g libsframe1 libtirpc-common libtirpc-dev libtirpc3 libzstd1
  rpcsvc-proto
Suggested packages:
  libpam-doc
Recommended packages:
  manpages
The following NEW packages will be installed:
  libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libnsl-dev libnsl2 libsframe1 libtirpc-dev rpcsvc-proto
The following packages will be upgraded:
  libc-bin libc-l10n libjansson4 libpam0g libtirpc-common libtirpc3 libzstd1
7 upgraded, 9 newly installed, 0 to remove and 649 not upgraded.
8 not fully installed or removed.
Need to get 0 B/2,453 kB of archives.
After this operation, 840 kB of additional disk space will be used.
Do you want to continue? [Y/n]
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or directory)
Setting up libc6:armhf (2.37-13) ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
dpkg: error processing package libc6:armhf (--configure):
 installed libc6:armhf package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 libc6:armhf
/usr/lib/armbian/armbian-apt-updates: line 24: /dev/null: cannot overwrite existing file
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@rday1:/#

 

This is on my rday1 server I put the SD card on it.

 

Hope this helps.