While trying to move my computer to Debian, after allowing the installer to do it’s task, my machine will not boot.
Instead, I get a long string of text, as follows:
Could not retrieve perf counters (-19)
ACPI Warning: SystemIO range 0x00000000000000B00-0x0000000000000B08 conflicts withOpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) /20250404/utaddress-204)
usb: port power management may beunreliable
sd 10:0:0:0: [sdc] No Caching mode page found
sd 10:0:0:0: [sdc] Assuming drive cache: write through
amdgpu 0000:08:00.0 amdgpu: [drm] Failed to setup vendor infoframe on connector HDMI-A-1: -22
And the system eventually collapses into a shell, that I do not know how to use. It returns:
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait lomg enough?)
- Missing modules (cat /proc/modules; ls /dev)
Alert! /dev/sdb2 does not exist. Dropping to a shell!
The system has two disks mounted:
– an SSD, with the EFI, root, var, tmp and swap partition, for speeding up the overall system – an hdd, for /home
I had the system running on Mint until recently, so I know the system is sound, unless the SSD stopped working but then it is reasonable to expect it would no accept partitioning. Under Debian, it booted once and then stopped booting all together.
The installation I made was from a daily image, as I am/was aiming to put my machine on the testing branch, in order to have some sort of a rolling distro.
If anyone can offer some advice, it would be very much appreciated.
I can, already done before coming here and I risk I’m going to do it again because people are telling me to do this and that and I’m feeling way over my head.
But not in the mood to quit. Yet.
I’m running a clean machine. No secondary OS. The only thing more “unusual” that I am doing is partitioning for different parts of the system to exist separately and putting /home on a disk all to itself.
Just in case you end up with reinstallation, I’d suggest using stable release for installation. Then, if you want, you can upgrade that to testing (and have all the fun that comes with it) pretty easily. But if you want something more like rolling release, Debian testing isn’t really it as it updates in cycles just like the stable releases, it just has a bit newer (and potentially broken) versions until the current testing is frozen and eventually released as new stable and the cycle starts again. Sid (unstable) version is more like a rolling release, but that comes even more fun quirks than testing.
I’ve used all (stable/testing/unstable) as a daily driver at some point but today I don’t care about rolling releases nor bleeding edge versions of packages, I don’t have time nor interest anymore to tinker with my computers just for the sake of it. Things just need to work and stay out of my way and thus I’m running either Debian stable or Mint Debian edition. My gaming rig has Bazzite on it and it’s been fine so far but it’s pretty fresh installation so I can’t really tell how it works in the long run.
I’m on track for that, I admit.
As I read this, I’m trying a freshly installed live image.
I have to try… I’m already too invested in this stupidity to just quit at this point.
Why am I interested in a somewhat rolling release of Debian? Because I’m a dreamer with not enough technical capabilities. I like the stability Debian offers and the years I’ve used it as my default distro is a fond memory.
The bare bones mentality, the basic, clean approach to the UI/desktop distro customization and the minimal starting software package was a big plus, especially when using very underpowered machines, like I had then.
What is not a fond memory is having an OS remain static for such a long time span to the extent it feels like jumping into a completely new OS when migrating to the next release and lacking on having newer versions of software. Yes, I do know Backports are a thing but nonetheless.
But the more user friendly distros overcompensate on this, by overloading the starting software package and bloating the distro. Polishing can be too much.
No, I am not about to go and try LFS, Gentoo, or whatever distro that puts me in charge of everything. I have a life. Kind of. But still.
Like you say, I want things to work, I don’t mind doing some work but I really don’t care about nor need the extra bells and whistles the (excessive) polishing carries.
End of rant.
I’m going to torture myself trying to figure whatever might have gone wrong for a bit more.
Ah, yes I saw all the comment suggestions and was hoping a fresh reinstall would work for you.
Did you format before reinstall? Definitely seems like fstab issue dropping you into initramfs that would need some manual intervention.
A format and fresh install should totally resolve this (assuming installation options and selections are sound).
What does ‘ls /dev/sd*’ ran from shell show you?
Once time I’ve had two bad installs in a row, it was due to my install media.
Many install media tools have an image checker (check-sum) step, which is meant to prevent this.
But corrupt downloads and corrupt writes to the USB key can happen.
In my case, I think it turned out that my USB key was slowly dying.
If I recall, I got very unlucky that it behaved during the checksums, but didn’t behave during the installs. (Or maybe I foolishly skipped a checksum step - I have been known to get impatient.)
I got a new USB key and then I was back on track.
I’m fairly confident at this point that the worst of my problems is to be found between the chair and the keyboard.
How is your /home disk plugged in?
Through a cable, to the onboard SATA ports…? But somehow I don’t think that was the answer you were expecting.
Yeah I was thinking you might be using a portable drive for home, which might not be detected early enough in the boot process to mount.
If you haven’t reinstalled yet, swapping the order of the SATA cables might change the order they are detected, so your home disk that was B to the installer will once again be B to the boot drive.