Debian update failed

[wedolearnlinux]

Good afternoon
I did the update to Debian 11.
Then I had to boot and this failed.
Now I cannot boot again.
What can I do to repair the OS.
What detauils shall I write here.

 

[tinfoil-hat]

what's the output of:

sudo apt-get update && sudo apt-get -y dist-upgrade

?

 

[wedolearnlinux]

Sorry.
I did bad asking.
I did update to Debian 11.
The update was successfull.
Maybe.
Then after update system was asking:
Do boot.

I did
Then:

panic occured.

Now I can only boot the recovery modus.

Thank You.

 

[tinfoil-hat]

You could make a live ISO and Chroot into your faulty Debian installation. Then from there we can fix your installation

til/how-to-chroot-from-live-cd.md at master · hlfernandez/til

Today I Learned: a collection of useful, concise tips on small things that I learn day to day. - til/how-to-chroot-from-live-cd.md at master · hlfernandez/til

github.com

 

[osprey]

Sorry.
I did bad asking.
I did update to Debian 11.
The update was successfull.
Maybe.
Then after update system was asking:
Do boot.

I did
Then:

panic occured.

Now I can only boot the recovery modus.

Thank You.

There are several things that could cause a kernel panic. The first place to look is the logs.

If you can boot up with an older kernel that works, which you may be able to choose from the grub menu, if it appears, then you could look at the logs in /var/log, in particular the files syslog or syslog.1 and kern.log. To get the systemd log run something like:

journalctl -b1 | less

where -b1 means the boot before last, which I'm presuming is the kernel panic boot, and find the log entries at the time of the panic. The -b has to be adjusted to get the right boot ... see the man page.

Looking towards the end of the logs just before the panic is where some useful info is likely to be.

This command may give info on errors, but there may not be much about the kernel panic itself:

journalctl -b1 -x -p 3

Kernel panics may not leave lot of info in logs because once they panic they stop outputting, but just a few hints may be helpful.

 

[wendy-lebaron]

I did the update to Debian 11.

Which operating system were you using before this "update"?

Where are you booting Debian from now?

Spoiler: Keeps on babbling

If the OS was booted with BIOS before the "update" then it might cause a conflict. I'm not technically inclined. I have seen an update failing after 1500 files and four or five times "initramfs" was rebuilt. I didn't even try to reboot with it, just replaced it with something else. Might have to do a full reinstallation.

 

[wedolearnlinux]

You could make a live ISO and Chroot into your faulty Debian installation. Then from there we can fix your installation

til/how-to-chroot-from-live-cd.md at master · hlfernandez/til

Today I Learned: a collection of useful, concise tips on small things that I learn day to day. - til/how-to-chroot-from-live-cd.md at master · hlfernandez/til

github.com

Thank You.
I did put in DEBIAN LIVE CD and
the same crash.
Im sorry.

Panic occured.


Before there was
DEBIAN 10.

 

[wedolearnlinux]

Id dis this find in www
but I dont understand

kernel panic in Debian

I'm not good in English!! my friend has Windows 11 and Debian seed, dual boot on his laptop, today he decide to add an HDD to his laptop. when Windows is hibernated he opened the laptop and add the...

unix.stackexchange.com

or

What to do in case of a Linux kernel panic

Here's how to avoid panicking when you see a Linux kernel panic.

www.redhat.com

or

How to troubleshoot kernel panic error in Linux - Blog | Liainfraservices

How to solve kernel panic error in Linux. The blog explains with the commands and screenshots to solve kernel panic error in Linux

www.liainfraservices.com

Thank You

Who can help
step by step.

 

[osprey]

Id dis this find in www
but I dont understand

If you don't understand the info on the links, then another alternative is to reinstall, and presumably, since the machine did work before, that it continues to. Perhaps just stay on debian stable where the updating is mainly just security matters and bug fixes. Currently debian bookworm is about to become debian stable so you could install the current bookworm with some confidence, and it's a relatively up to date distribution with a reliable 6.1 kernel.

 

[wendy-lebaron]

I agree with osprey.

If you can you could reinstall Debian "Bullseye" v11.7, using an ISO which is only about a month old, found here:

Index of /debian-cd/current/amd64/iso-dvd

Be aware that in a 64-bit system, this OS will expect to install bootloader via UEFI. So if you were able to boot v10 "Buster" before with BIOS and you only did it that way then it could present a problem for you. If you can spare the entire internal HDD/SSD for it, you should pick "use entire disk" in partition settings of Debian Installer, to make sure an EFI System Partition and Linux "swap" partiton are created and set up properly.

If you install again and you still get a kernel panic then it must be a problem with your hardware. A device failure such as a bad chip (RAM), or something inside the computer not connected properly, or incompatible with the motherboard.

 

[wedolearnlinux]

"If you don't understand the info on the links, then another alternative is to reinstall,"

The problem with reinstall is:

I put CD in
Do booting.

Panic occured.

Can You help me?

 

[arochester]

debianforum.de - Startseite

 

[osprey]

"If you don't understand the info on the links, then another alternative is to reinstall,"

The problem with reinstall is:

I put CD in
Do booting.

Panic occured.

Can You help me?

Is there a problem with the media you are using? Did you verify it with the checksums before running it?

 

[wendy-lebaron]

One of two things.

Either wedolearnlinux has a computer which is not advanced enough to run Debian v11 "Bullseye" (or v12 "Bookworm"). But probably could run v10 "Buster".

Or the computer suffered an unfortunate malfunction in the process of their trying to install another operating system.

While trying to boot from an ISO which is on CD or an USB drive, if there is a kernel panic, the chance is great there is a hardware problem.