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.

  • pinball_wizard@lemmy.zip
    2·
    2 days ago

    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.