Could this help?


sudo systemctl reboot

sudo apt --purge autoremove

Help what? What you expect it to do that might help?

I want we or You find the bad files
so DEBIAN can boot.
Thank You for help.

Won't know until you give autoremove a try, what is the worse that can happen at this point?

It's not too late to unforget. Just be sure the number you use refers to an attempt to boot the default Grub selection, so if that was 3 boots before current, use -3 instead of -1.

2 questions:

journalctl -b -1 | grep aile | pastebinit
Do I have to do it during DEBIAN is running?

2
I tried in the past
very often to use autoremove and autoclean.
But
autoremove
file not founf

apt-get install autoremove
Cannot find autoremove or autoclean.


What do I do wrong?

Are there other cleaning tools?
Shall I use bleachbit?

Regards and Thank You

Technically no, but you'll have to read the journalctl man page to determine how, or get someone else to respond how.

is how autoremove is done. It's not a separate program.
For what kind of cleaning?
For your current problem, I doubt it would do anything helpful, and possibly it would be harmful.

I'ts very common for all of the current versions of the grub boot-loader can easily get thrown out of kilter if you make an error when you select the hard drive onto which you want the grub-install script to install grub to. It's a common error made by new comers to Linux can really fowl up their configuration if they accidentally yell the grub-install scripts to install to the USB or other boot device from which they installed their OS from and install grub to the boot sector of the installation which means that if you don't have the USB stick that they installed from.

This can also become extremely painful if either by accident or intentionally wipe out that USB thumb drive your basically up the river without a paddle, which essentially means you need to reinstall from scratch. So I'd strongly recommend that the OP make a complete backup of their critical files before he/she even considers generating the installation media.

I did

$ journalctl -b -1 | grep aile | pastebinit
bash: pastebinit: Kommando nicht gefunden.
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
$

Thank You.

What do you mean by rescue mode? What version of debian is this?

This is in the grub entry that boots correctly?

should fix that.
Precede journalctl with sudo to avoid the hint, and see all messages.

$ journalctl -b -1 | grep aile | pastebinit
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
https://paste.debian.net/1304387/
~$

I repeated it in root terminal
then:
https://paste.debian.net/1304388



How can I read:

linux /boot/vmlinuz-5.10.0-15-686-pae


Rescue mode helps when booting made panic.


Thank You.

The pasted material suggests you may have a RAID device that is not accessible. We need more information about this, the whole journal, and fstab. Do this as root:Provide here URLs from those commands.

That's a large binary file (a PAE kernel). Nobody can "read" it.

I don't understand what you mean.

Thank You for Your friendly help.


journalctl -b -1 | grep aile | pastebinit
https://paste.debian.net/1304530/

cat /etc/fstab /proc/mdstat | pastebinit
https://paste.debian.net/1304532/

lsblk -f | pastebinit
https://paste.debian.net/1304533/


Is this ok?


Rescue mode helps when booting made panic.
This was the answer for colorpurple21858 in post 100.


Regards

Is
ls *.* > result.txt
the same
like
pastebinit

but
its given to the www.
Is this public and free
and everybody can use it?