|
Hi beginstart
If I were you, I would use a live distro to backup all my documents. And then, install from scratch a beginner-friendly distro. This can be easier and faster than trying to fix the problem. There are a lot of distros to try, a good one is linux mint cinnamon edition. It also runs as a live distro before the install so you can do any backup and try it before install. |
Quote:
Im sorry. We do backup every day. So data files are no problem. So my first idea was download Debian 11 burn it boot with DVD and make a new Debian. This didnt work. Only recovery does his job. Im sorry. Thank You. https://paste.debian.net/ https://pastebin.com/ This is for long messages/files, isnt it. Thank You. |
I asked in post 9 if Debian ever booted successfully. What I meant was did the upgrade to Debian 11 ever boot successully. If you did the update/upgrade from within the older Debian using apt get, it should have installed new Grub files and updated Grub before the installation finished.
A possible reason for the kernel panic is the grub menuentry pointing to an old kernel which no longer exists. Look at the menuentry when booting as explained above, then boot a 'live' system and check the /boot directory on Debian to see what vmlinuz (kernel) files are there. No one here can be more specific as you are the only one with that information. |
Quote:
I have to study all. Short naswer. " asked in post 9 if Debian ever booted successfully. What I meant was did the upgrade to Debian 11 ever boot successully. If you did the update/upgrade from within the older Debian using apt get, it should have installed new Grub files and updated Grub before the installation finished." Old Debian. Boot ok. Also after some updates upgrades. Fresh update to 11. update upgrade on HD. Debian said: Update successful, please boot for complete. Panic. Again my stupid question. Is it easy for newbie: Boot in recovery. Debian is active. I do copy system files and post them here for find the bug. Thank You all. Regards. Short: Never DEBIAN 11 could boot "normal". |
There isn't enough information for us to know exactly what the problem is. Did you try what I suggested in the second paragraph of my earlier post, #19?
|
Don't panic, you need to analyze this problem. The best way to do that is with a "live CD" or "rescue cd", Slackware just happens to work excellently as a rescue "cd" as well as a distro. So I suggest that if you can, you download it and put it on a DVD or USB.
You need to boot into such a disk and analyze your situation, in particular your partition situation. Are they there? Can you mount them? Is the content there? If so, everything should be fine, so take care not to destroy things further. With Slackware, you can boot from the disk using the disc Kernel and setting your root partition to any available partition on your system. This is very handy in case there is something wrong with your Kernel and/or boot process. From such a disk, you can do a range of things, you can repair your system and/or your grub setup, or backup files and many other things. |
Quote:
Code:
apt upgrade |
Quote:
I ll try it. The other post I can only understand 90%. If the update fails I ll ask for details. Thank You. Only this 2 tasks I have to do. apt upgrade apt dist-upgrade |
You can try those two commands as root or sudo.
Another thing you can try: The current Debian is version 12 available from a mirror site near you if you want to do a fresh install of the latest. If you prefer to stay with Debian 11, you can get installation media from here. Choose the latest version which is 11.8.0 If you would like to try repairing the current upgraded installation you have, I suggest just downloading the CD image, which should be around 450/550 MB, (Netinstall image), burn it to a USB stick, boot the stick and select Advanced/Rescue/Repair Grub or repair boot loader. It will go through a few questions similar to installing Debian but will eventually ask which drive is the Debian root drive, you will enter the proper information and if you have a UEFI based system you will be asked if you want to also mount the EFI boot partition to which you select yes. If everything goes correctly, I believe it'll just fall back to the rescue menu when done where you select "Reboot". |
Thank You for Your patience.
I do check these strange tasks. I did find: vmlinuz https://debian-handbook.info/browse/...tallation.html boot with e https://www.redhat.com/sysadmin/inte...x-boot-process efibootmgr https://packages.debian.org/de/sid/efibootmgr paste.debian.net but pastebin.com sounds more easy. But I dont understand what do I have to do. Please an instruction I can follow. I did update upgrade dist problem us the same. I try to follow: If you would like to try repairing the current upgraded installation you have, I suggest just downloading the CD image, which should be around 450/550 MB, (Netinstall image), burn it to a USB stick, Isnt it more easy to burn on CD or DVD? boot the stick and select Advanced/Rescue/Repair OK Grub or repair boot loader. It will go through a few questions similar to installing Debian but will eventually ask which drive is the Debian root drive, What is the answer? you will enter the proper information and if you have a UEFI Do I? How can I check this? based system you will be asked if you want to also mount the EFI boot partition to which you select yes. Only a "yes. If everything goes correctly, I believe it'll just fall back to the rescue menu when done where you select "Reboot" OK. |
Code:
# efibootmgr |
If running a 32 bit system it seems almost certain that the PC would not boot into efi mode. After all those systems did not have support for efi as that was a bios update to support 64 bit systems.
In the first post the OP said he was using debian 11 and 32 bit. In later posts he said he had upgraded from [debian] 7 to 8 and so on. |
Im sorry.
Im confused. DEBIAN was installed long time ago. I dont know why I did install 32 bit. I did install LXDE because it looks most easy and I can do gedit gimp firefox and thunderburd. No speicual software is installed, only the "classics". Please tell me a task not dangerous I can check the system or the system files. And until the last but one update. I was looking for help for update but it worked. I think not important. Once a week I do the normal update. This is working. Thank You all and a relaxed Sunday. |
My understanding of your problem is that you updated/upgraded to Debian 11 and since that time have been unable to boot unless you select recovery mode. Is that correct? If so, boot in recovery mode and open a terminal. In the terminal run the following command and post the output here:
Code:
ls /boot Did the upgrade also update grub when you did it? I don't use Debian so...? I would expect that it would if there was a new kernel installed. |
All times are GMT -5. The time now is 10:53 PM. |