On Sat, Oct 28, 2023 at 02:02:29PM +0000, Schwibinger Michael wrote: > SUMMARY
After a lot of questions backwards and forwards: Sophie has: A desktop machine with one user and regular backups. It was originally running Debian 9 and has been updated to Debian 11. It has booting problems: it doesn't boot from the latest kernel and hangs. It does run if started from "recovery" >From reading the replies: it sounds like a kernel panic with a screenful of text. We don't know exactly what. The machine is an older machine if it has been running since Debian 9. This could be from a number of causes: a misconfigured/failed update to Debian 11, Grub not being installed properly, maybe even a boot partition being full so that the kernel was not installed. Suggestions made here: * Boot from an external medium, run recovery from there and reinstall Grub. For Sophie: chroot is a way of moving to and working from the filesystem on disk once you have booted from an external medium like a USB stick. If you use something else to boot from - the installer, for example, then changes you run are in memory until you write them. The recovery mode of the installer runs entirely in memory. At one point you "change root" and pivot to the other filesystem. If the filesystem you want to use is mounted at /target cd /target chroot . Now you are running from /target filesystem * Run a complete install using the Debian 12 Bookworm installer This might be the easiest way forward but will need someone to work out * how to write the install medium - netinst.iso from the Debian website - * how to persuade the desktop machine to boot from something other than the hard disk > With every good wish, as ever, > > I did only understand > chroot. > > Is this another kind of booting? > > Does this repair > DEBIAN?. > > If yes > what do I have to do? > > > https://en.wikipedia.org/wiki/Chroot > I did find this. > > Good idea? > > > Regards Sophie > > > Andy [amaca...@debian.org] > > > ________________________________ > Von: Cindy Sue Causey <butterflyby...@gmail.com> > Gesendet: Donnerstag, 26. Oktober 2023 21:22 > An: Debian Users <debian-user@lists.debian.org> > Betreff: Re: Panic again > > On 10/26/23, Schwibinger Michael <h...@hotmail.com> wrote: > > > > Good afternoon > > Thank You for help. > > > > I ll answer into Your email > > with > > +++ > > > > > > Von: Andrew M.A. Cater <amaca...@einval.com> > > Gesendet: Mittwoch, 25. Oktober 2023 12:04 > > An: Schwibinger Michael <h...@hotmail.com> > > Betreff: Re: AW: AW: Panic again any idea IV > > > > On Wed, Oct 25, 2023 at 10:59:09AM +0000, Schwibinger Michael wrote: > >> Good morning > >> > >> Thank You. > >> > >> I do booting. > >> Crash. > >> Bug report I did send. > >> > > > > Hi Sophie, > > > > Thank you. You didn't really send a bug report > > > > > > +++ > > I know. > > But how can I produce a bug report > > when the PC is frozen? > > > An afterthought up top here: Is there a program that will snag and > retain boot messages specifically geared toward systems that never > fully boot? It seems like I've seen that topic come up and be answered > one single time in the last ~25 years. I actually tried to find some > form of that type of program the other day when I saw an earlier > portion of this thread then. I was thinking, hoping maybe such a > program could possibly be installed via chroot if it does exist. > > Now my original thought.......... > > Has chroot been suggested and/or attempted? I'm imagining that it was > possibly yes, suggested. > > If not, what about attempting a chroot to then next attempt apt or > apt-get update then upgrade? > > As a user who has occasionally battled issues, I know that, ideally, > it would be nice, i.e. satisfying, to find the cause of bigger issues > like this. At some point, I also know firsthand that outing the cause > becomes less important when weighed against moving on in Life. :) > > Apt/apt-get upgrade via chroot would potentially help preserve a > particular setup rather than going with a new install if that is why > this continues to be a topic. > > If anyone can think of a reason why running apt/apt-get in chroot > would only stand to cause data harm in this particular situation, that > would be great to know. > > My firsthand experience has been that tinkering via chroot has > eventually gotten me back up and running maybe 99% of the time, > including against multiple kernel panic-ish fails a few years ago. > > Biggest reason my chroot repair attempts ever failed was due to not > properly mounting maybe 4 or 5 basic necessities that apt/apt-get use > to properly install programs. /dev and /proc come first to mind as > examples there. That knowledge came from working through the manual > steps necessary during debootstrap installs, in case that ever helps > anyone else. > > Cindy :) > -- > Talking Rock, Pickens County, Georgia, USA > * runs with a retirement state of mind * >
