I have a recently purchased Lemur Pro (Winter of 2024/2025) and I am attempting to install Debian. However, the touchpad is completely unresponsive on Debian. Is this a common issue with the machine? Are there any known fixes? Thank you all so much for any help/advice.

The Debian GUI Installer provides multiple automated partitioning options. I've had no issues with "use entire disk and set up encrypted LVM" so far. But toady I had to install Debian on a disk that is preoccupied by multiple operating systems. In the beginning of the disk there is a Windows installation, and in the end of the disk there is an Ubuntu installation. There is one continuous space in the middle of the disk. When I chose the "use the largest continuous free space" option it correctly selected the entire space but there was no automated process to encrypt the volume. So I have an unencrypted Debian installation in the middle of my disk. Is it possible to encrypt only the entire Debian portion of the disk after an unencrypted installation in the same way as the guided "use entire disk and set up encrypted LVM"? I chose to put "All files in one partition". If there are no native methods, can third party software such as Veracrypt help? If there is no solution but to reinstall, how should I partition next time to achieve what I want?

We're building a Debian based product. To simplify building these in the factory, I'm trying to build a live disk that will install the main OS. We have an older product that uses this processbut was based on Debian 7. I'm using Debian 11. I've based my Debian 11 recovery process and image on the Debian 7 one. Both use live-build. The Debian 11 system pulls the OS from mainline bullseye repos plus my repo for the one package that carries our bits. It's a multistep process where we run live-build to build the operational system's OS, squash it into a squashfs, then build a live OS around it with a script that does things like partition the driven, unsquash the squashfs file to the appropriate partition, and, most critically not working, apply GRUB. Part of the build does:

install -d /boot/seed
grub-mkimage -Ox86_64-efi -o /boot/seed/BOOTX64.EFI -p '(hd0,1)/EFI/BOOT/grub' \
	part_gpt part_msdos fat
grub-mkimage -Oi386-pc -o /boot/seed/mbr-core.img -p '(hd0,msdos1)/biosgrub' \
	part_msdos fat biosdisk
grub-mkimage -Oi386-pc -o /boot/seed/gpt-core.img -p '(hd0,gpt1)/biosgrub' \
	part_gpt fat biosdisk
cp -a /usr/lib/grub/i386-pc/boot.img /boot/seed/boot.img
cp -a /usr/lib/grub/i386-pc/modinfo.sh /boot/seed/modinfo.sh
grub-editenv /boot/seed/grubenv create

These files end up in the live OS and get copied to the ESP partition prior to attempting to install GRUB. Those files and all the various GRUB modules are copied midway through the install script. Later on in the script, we call grub-install.

grub-install \
    --directory /mnt/biosgrub \
    --boot-image boot.img \
    --core-image core_img \
    /dev/sda

The problem here is that the newer versions of grub-install no longer support core-image and boot-image switches like the version from Debian 7 did so that fails immediately. I took out the boot-image and core-image switches and now it fails with:

grub-install: error: failed to get canonical path of `overlay'.

And yes, there really is an opening backtick with a closing single quote on overlay. I've tried removing the GRUB step, letting it unsquash everything, then booting to a graphical live disk running Manjaro (had it laying about) to try to get more info on the GRUB situation. Running grub-install there fails in the same way. From googling, I've learned that this is because grub-install thinks the target device is using an overlayfs and can't figure out which actual device to use but I'm not really sure where to go from here nor am I certain what questions to ask. I'm happy to provide more details although somethings will have to be redacted for proprietary software reasons. If it matters, manually mounting the created OS partition off-system shows everything to be in the right place, our code is in place and would probably run well if there were a bootloader. ETA: I've made some progress here, mounting the unsquashed OS into a directory in the live disk, mounting /proc, /sys, and /dev into that directory, mounting my EFI partition into it, and chrooting into it. Then running grub-install /dev/sda but grub is still missing on startup.

I have a USB Debian installer and I would like to add a new menu item to the grub menu (Automated install with some boot parameters). I did find grub.cfg and I added my custom menu item but it does not show up in the grub menu. Rechecked the grub.cfg file, my menu item is still there so it did not get overwritten but it does not work. Any idea what I am doing wrong?

I want to install Debian (actually Open Media Server, a derivative) by using a Mac laptop (EFI) on a disk (connected via USB), to then transfer it to an headless machine already installed and configured, but the target machine doesn't support EFI, so I want to stick to MBR. Is it possible to achieve this with the current Debian 11 installer? During the installation process, there was no prompt for it, and EFI was selected, even when I manually created an MBR partition on the disk. I saw [this old question](https://unix.stackexchange.com/questions/518377/where-does-the-debian-installer-choose-mbr-vs-gpt) , but it doesn't really answer

I'm attempting to preseed a [debian testing](https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/) installation that creates following partitions: - /boot/efi - /boot - encrypted VG with: - / Everything appears to work, only that the LVM definitions are not read/used. For instance, no matter what I do, the swap partition is _always_ created. Preseed:

d-i debian-installer/locale string en_US.UTF-8
d-i debian-installer/fallbacklocale select en_US.UTF-8
d-i debian-installer/language string en
d-i debian-installer/country string ES
d-i localechooser/languagelist                  select      en
d-i keyboard-configuration/xkb-keymap select us
d-i netcfg/use_autoconfig                       boolean     true
d-i netcfg/choose_interface select auto
d-i netcfg/use_dhcp string true
d-i netcfg/dhcp_failed note
d-i netcfg/get_domain string unassigned-domain
d-i netcfg/hostname string p14s
d-i netcfg/wireless_wep string
d-i hw-detect/load_firmware boolean true
d-i mirror/country string manual
d-i mirror/http/hostname string deb.debian.org
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string
d-i mirror/http/mirror                          string      deb.debian.org
d-i passwd/shadow                               boolean     true
# Root password, either in clear text
d-i passwd/root-password password insecure
d-i passwd/root-password-again password insecure

d-i passwd/username string user
d-i passwd/user-fullname string User Name
d-i passwd/user-password password insecure
d-i passwd/user-password-again password insecure

d-i clock-setup/utc boolean true
d-i time/zone string Europe/Madrid
d-i clock-setup/ntp boolean true

### Partitioning
# If the system has free space you can choose to only partition that space w/ value
# of 'biggest_free'. This is only honoured if partman-auto/method (below) is not set.
#
# TODO: is 'custom' value needed/working/valid? is this option needed at all?
#d-i partman-auto/init_automatically_partition select custom

d-i partman-auto/disk string /dev/nvme0n1 /dev/sda /dev/vda
d-i partman-auto/method string crypto
d-i partman-auto-lvm/guided_size                string      max
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true
d-i partman-auto-lvm/new_vg_name                string      crypt

# Allow to not set a swap partition
# note if this is false (default) & we don't define swap partition below, then
# one will be created regardless.
d-i partman-basicfilesystems/no_swap boolean false

d-i partman-auto/choose_recipe select custom-crypto


d-i partman-auto/expert_recipe string                        \
      custom-crypto ::                                       \
              538 588 538 free                               \
                     $iflabel{ gpt }                         \
                     $reusemethod{ }                         \
                     method{ efi }                           \
                     format{ }                               \
              .                                              \
              1024 1074 1024 ext4                             \
                      $primary{ } $bootable{ }                \
                      $defaultignore{ }                       \
                      method{ format } format{ }              \
                      use_filesystem{ } filesystem{ ext4 }    \
                      mountpoint{ /boot }                     \
              .                                               \
              # explicit LVM creation:                        \
              #100 2000000 -1 ext4                            \
              #        $defaultignore{ }                       \
              #        $primary{ }                             \
              #        method{ lvm }                           \
              #        format{ }                               \
              #        vg_name{ crypt }                        \
              #.                                               \
              #6000 6040 6000 linux-swap                       \
              #      $lvmok{ }                                 \
              #      in_vg { crypt }                           \
              #      lv_name{ swap }                           \
              #      method{ swap } format{ }                  \
              #.                                               \
              50000 50000 -1 ext4                             \
                    $lvmok{ }                                 \
                    in_vg { crypt }                           \
                    lv_name{ root }                           \
                    method{ format } format{ }                \
                    use_filesystem{ } filesystem{ ext4 }      \
                    mountpoint{ / }                           \
              .                                               \

d-i partman-partitioning/choose_label select gpt
d-i partman-partitioning/default_label string gpt
#
# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman-md/confirm boolean true
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true

### Base system installation
d-i base-installer/initramfs-tools/driver-policy select     most

### Apt setup
d-i apt-setup/disable-cdrom-entries boolean true

# Choose, if you want to scan additional installation media
d-i apt-setup/cdrom/set-first                    boolean     false
d-i apt-setup/cdrom/set-double                   boolean     false
d-i apt-setup/cdrom/set-next                     boolean     false
d-i apt-setup/cdrom/set-failed                   boolean     false


d-i grub-installer/only_debian boolean true
d-i grub-installer/with_other_os boolean true
d-i grub-installer/bootdev  string default
# Avoid that last message about the install being complete.
d-i finish-install/reboot_in_progress note

Resulting layout:

$ lsblk

NAME                    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
vda                     254:0    0     5G  0 disk  
├─vda1                  254:1    0   533M  0 part  /boot/efi
├─vda2                  254:2    0   763M  0 part  /boot
└─vda3                  254:3    0   3.7G  0 part  
  └─vda3_crypt          253:0    0   3.7G  0 crypt 
    ├─debian--vg-root   253:1    0   3.2G  0 lvm   /
    └─debian--vg-swap_1 253:2    0   564M  0 lvm   [SWAP]

1. how to achieve the goal? 1. what is partman-auto/init_automatically_partition option about and should it be defined?

I've been trying to install Debian and I've done the following in order to try to fix this: : 1. Changed USB drives. 2. Added the fb=false parameter to boot 3. Tried Testing build (stretch) and Stable build. 4. Added nomodeset to the boot parameters 5. Tried both normal and graphical install (screenshots attached) My computer is an HP Probook 440 G2 with a core i5 and Intel HD 4400 Graphics running in UEFI mode. I need it UEFI mode since Legacy BIOS (and MBR drive partitioning) is unacceptable Anything else I can try to get it working?

When I boot up my Debian 11.2 live USB stick it gives me these errors: ACPI BIOS Error(bug) : Failure creating named object[\ADBG], AE_ALREADY_EXISTS ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog and after these errors Debian doesn't run. I tested it with two different USB sticks made with Rufus.

I'm having an unusual struggle in installing Debian on my new N150 board ([hardware](https://www.aliexpress.com/item/1005008547529767.html?spm=a2g0o.order_list.order_list_main.17.67411802cCMki3#nav-description)) . The install process runs for about 2 seconds, before stopping at "SATA link down" in advanced mode. Here is the log before the install stops. In "normal" installation mode, there is only the underscore in the upper left corner of the screen. It blinks for a few seconds before remaining there. I'm not quite sure what the issue is. I have tried booting with the "nomodeset" parameter, as well as disabling the SATA controller, to no avail. The Graphical install leads to a black screen. Any suggestions as to how to debug this?

I am setting up debian on an old machine to use as a home fileserver and am having issues installing. I hooked up the network over Ethernet using my laptop's network share and I think the connection is working (is there a way to test this in the installer?) but the installer freezes on "Retrieving apt" and then fails about a minute later. Does anyone have any suggestions?

I was trying to install [Seedsync](https://github.com/ipsingh06/seedsync) . I followed the instructions on their github Download the deb package from the latest release Install the deb package: sudo dpkg -i When I try to install the deb package I get this error Selecting previously unselected package seedsync. (Reading database ... 276845 files and directories currently installed.) Preparing to unpack seedsync_0.6-0_amd64.deb ... Unpacking seedsync (0.6-0) ... dpkg: dependency problems prevent configuration of seedsync: seedsync depends on libreadline6 (>= 6.0); however: Package libreadline6 is not installed. dpkg: error processing package seedsync (--install): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.27-3ubuntu1) ... Errors were encountered while processing: seedsync Trying to install libreadline6 tell me that it's either moved somewhere else or obsolete. **Edit:** sudo apt-get install libreadline6 gives me Reading package lists... Done Building dependency tree Reading state information... Done Package libreadline6 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libreadline6' has no installation candidate **Edit2:** Tring to install libc-bin or libreadline7 shows that it's already the newest version, 0 upgraded,0 newly installed and 0 not upgraded. The seedsync package asks for libreadline6 (>=6.0) and I think I have libreadline7 apt-get install libreadline7 Reading package lists... Done Building dependency tree Reading state information... Done libreadline7 is already the newest version (7.0-3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I am using debian installer together with a preseed config-file to automate installation steps. Currently the network-card selection still shows up and I cannot find out why. I have the following networking-related lines d-i netcfg/choose_interface select auto d-i netcfg/choose_interface select enp0s8 d-i netcfg/link_wait_timeout string 20 The selected interface-card is available in the dialog that appears and also when installation finishes: $ sudo ifconfig enp0s8: flags=4163 mtu 1500 ... However the Debian installer still stops and forces me to choose the network-card to use. How do adjust the preseed file to also perform this selection automatically?

I've created a custom installer ISO to automate Debian bookworm installs, and most of it is working just fine. However, I tried to activate automatic upgrades by installing the unattended-upgrades package and setting enable_auto_upgrades for it, with the following lines in my preseed.cfg: d-i pkgsel/include string unattended-upgrades unattended-upgrades unattended-upgrades/enable_auto_updates boolean true When I booted into the new install, it always showed enable_auto_updates as false. I also tried setting the owner of that debconf setting to d-i instead, but that didn't help. I've worked around the issue by setting it with debconf at the end of the install, and reconfiguring the package: echo "unattended-upgrades unattended-upgrades/enable_auto_updates boolean true" |debconf-set-selections TERM=none dpkg-reconfigure -u unattended-upgrades That does work, but I don't like it. What is wrong with the preseed entry, and what can I do to get it to work? Thanks!

I'm trying to install Debian 11 on a computer without an internet connection. According to the Debian website : > To install Debian on a machine without an Internet connection, it's > possible to use CD images (700 MB each) or DVD images (4.7 GB each). So officially, it's possible. However, when I try, as you can see from the two attached screen photos, it asks to set up a network and doesn't give me an option to skip it. It seems that the installation won't progress unless I connect to a network. I notice that this is completely different from all of the online guides such as this one . In these guides the installer goes from "Configure the keyboard" to entering a hostname. For me, it goes from "Configure the keyboard" to "[!!] Configure the network". The Debian installation documentation doesn't consider the possibility that there is no network to connect to during installation. The problem occurs irrespective of whether I use the text or graphical installer. How do I proceed?

A class of Linux machines we maintain/build has up to 8 network interfaces, all but one aren't connected in the build phase. I'd like to speed up the build process by telling the initrd to ignore all but the connected one, but can't seem to find kernel parameters to add to the boot options to do so. The PXE part is not the problem, it's the intrd probing all interfaces so it can then pull down the base image via NFS and then proceed w/ the actual install on the target machine. We'll look into hiding the interfaces from BIOS (as Marcus suggested), even though then having to wait through 2 lengthy POSTs extra probably defeats the purpose (making the turn around time shorter). Can anyone think of a different approach to avoid the lengthy wait for each present nic to time-out on net boot?

I wanted to install Debian 10.4 (Gnome version) on external usb 3.1 pen-drive for usage on multiple computers.So i searched for tutorials online but most were for ubuntu or manjaro linux.Also i am relatively new to linux. So,first I created a bootable usb stick using rufus on windows 10. After booting into debian i started the installer after inserting the pen drive where i actually wanted to install the os. When I reached the partitions part,I chose the usb, chose the manual partitioning method and created 4 partitions(in the given order) 1. EFI 512MB Flags:"esp","boot" Mountpoint: "/boot/efi" Format:FAT32 2. Root 10GiB Flags:"root" Mountpoint: "/" Format:ext4 3. Swap 4GiB Flags:"swap" Mountpoint: none Format:linuxswap 4. Home 12GiB Flags:none Mountpoint:"/home" Format:ext4 After finishing the install,I tried switching off the computer and turning it in again without removing the pendrive.It worked perfectly. Then I removed the pendrive to see whether windows would boot normally.It did.But when i plugged the usb back in,I could not boot into the pendrive.I could see the pendrive name as debian in the uefi settings before removing it but afterwards, I could only see it as sandisk. So I was wondering whether the whole portable usb thing is possible? If possible, what did I do wrong and how to fix it. Can someone who have already went through the process give me a detailed guide(If it is possible that is)? I also tried live usb with persistence but didnt like the idea of it.

## Setup Assume we're installing a current Debian release (i.e. Bookworm as of 03/2025) on a modern and "standard" PC, i.e. some modern x86_64 architecture CPU where no special kernel modules or any special input from the user is required during installation (aside from the regular high-level config like keyboard layouts etc.). It's the most basic and simple installation on a SSD where it is the only installed OS, in a machine which has only this SSD as a hard drive. Now we take this SSD and move it to a different PC, same basic simplicity, but possible a different CPU (e.g., the one maybe had an AMD and the other an Intel, but both x86_64) and possibly different mainboard (again, for argument's sake, say we're switching between Intel and AMD). Maybe more or less RAM or a different video card (or onboard video). Likely a different network chip, audio chip, USB controller and whatever else comes with the mainboard. But all of it perfectly supported by Debian with the standard kernel modules. Both machines would work flawlessly if Debian was installed from scratch on either and would have comparable capabilities. Aside from the basic installation (with some X desktop, say Gnome or KDE, in basic default settings). ## Question Would one expect for this installation that we have moved from PC 1 to PC 2 by simply moving the SSD over to work perfectly from the first boot? Or are some things, during the Debian installation, installed or configured only as needed for the specific hardware, so there is a significant chance that something does not work out-of-the-box on the second PC? ## Addendum ... if the answer was "yes, something would very likely go wrong", is there something that can be done after the initial installation on PC 1 to make it more likely that such a move would work on a new PC (not knowing exactly which PC that would be)?

I used the Debian 12.5.0 ISO DVD image from the official website and wrote it to a USB flash drive via Rufus. During the "Load installer components from installation media" process got stuck, and by switching to the command line via CTRL+ALT+Fn, I could look at the Log and found that it triggered a Kernel Bug, is there any relevant clues? Edited: I've tried many times and the problem occurs at different steps of the installation, but the error remains the same and 95% of the time it occurs at the "Load installer components from installation media" step. There are two paragraphs in the Log, the first of which is:

[   20.009517] WARNING: CPU: 0 PID: 876 at mm/shmem.c:1193 shmem_evict_inode+0x26e/0x2b0
[   20.009521] Modules linked in: storage_ssd_mod intel_spi_cr_platform fat isofs hid_generic usbhid hid ...
[   20.009523] CPU: 0 PID: 876 Comm: kworker/u8:1 Not tainted 6.1.0-10-amd64 #1 Debian 6.1.76-1
[   20.009524] Hardware name: ASUSTeK COMPUTER INC. System Product Name/Pro WS W680-ACE IPMI, BIOS 3501 04/19/2024
[   20.009525] RIP: 0010:shmem_evict_inode+0x26e/0x2b0

The second is:

[ 20.009567] kernel BUG at fs/inode.c:613!
[ 20.009568] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
[ 20.009569] CPU: 0 PID: 876 Comm: debconf Tainted: G W 6.1.0-18-amd64 #1 Debian 6.1.76-1
[ 20.009571] Hardware name: ASUSTeK COMPUTER INC. System Product Name/Pro WS W680-ACE IPMI, BIOS 3501 04/12/2024
[ 20.009572] RIP: 0010:clear_inode+0x7z/0x80

See image for details:

this is about Debian 12 and partman. Swap is getting the incorrect size. All other partitions / lv's have the expected size. However, swap just doesn't seem to listen. I want 4GB, but I'm getting 9760145408 bytes. RAM is 4GB, sda is 60GB (plenty of space). I started with 4295 4295 4295, but that produced 9760145408 bytes. Now I'm trying 100%, which is not good because I do not want a relative size. Anyway, I still get the same silly size. # d-i partman-partitioning/choose_label select gpt # d-i partman-partitioning/default_label string gpt d-i partman-auto/method string lvm d-i partman/alignment string optimal d-i partman-auto-lvm/guided_size string max d-i partman-lvm/device_remove_lvm boolean true d-i partman-lvm/confirm boolean true d-i partman-lvm/confirm_nooverwrite boolean true d-i partman-auto/disk string /dev/sda d-i partman-auto-lvm/new_vg_name vgroot # if only we could specify units: mib vs mb # https://askubuntu.com/questions/1340402/ubuntu-preseed-expert-recipe-priority-max-size-dont-translate-into-correct-resu d-i partman-auto/expert_recipe string ems-debian :: \ \ 2048 6000 2048 ext4 $primary{ } $bootable{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } label { boot } mountpoint{ /boot } . \ \ 1 1 -1 lvm $primary{ } method{ lvm } device { /dev/sda2 } vg_name{ vgroot } . \ \ 2148 2148 2148 lvm $lvmok{ } in_vg{ vgroot } lv_name{ lvhome } method{ format } format{ } use_filesystem{ } filesystem{ xfs } label { vgroot } mountpoint{ /home } . \ 17180 17180 17180 lvm $lvmok{ } in_vg{ vgroot } lv_name{ lvopt } method{ format } format{ } use_filesystem{ } filesystem{ xfs } label { vgroot } mountpoint{ /opt } . \ 9664 9664 9664 lvm $lvmok{ } in_vg{ vgroot } lv_name{ lvroot } method{ format } format{ } use_filesystem{ } filesystem{ xfs } label { vgroot } mountpoint{ / } . \ 2148 2148 2148 lvm $lvmok{ } in_vg{ vgroot } lv_name{ lvtmp } method{ format } format{ } use_filesystem{ } filesystem{ xfs } label { vgroot } mountpoint{ /tmp } . \ 21475 21475 21475 lvm $lvmok{ } in_vg{ vgroot } lv_name{ lvvar } method{ format } format{ } use_filesystem{ } filesystem{ xfs } label { vgroot } mountpoint{ /var } . \ 2148 1000 100% linux-swap $lvmok{ } in_vg{ vgroot } lv_name{ swap } method{ swap } format{ } . \ \ d-i partman/confirm_nooverwrite boolean true d-i partman/confirm boolean tru d-i partman/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm_nooverwrite boolean true d-i partman/confirm boolean true

We are facing issues while installing Debian 11 on a Dell PowerEdge R720 server equipped with 11 x 1.2TB disks. We have tried multiple approaches, but we are encountering blocking errors. Server Configuration: Model: Dell PowerEdge R720 Storage: 11 x 1.2TB SAS disks Boot Mode: Tested both UEFI and Legacy BIOS USB Boot Creation Tools: Ventoy and Rufus Steps Taken & Issues Encountered: 1. First Attempt with Ventoy (Abandoned) We created a bootable USB using Ventoy and the Debian 11 ISO. The server detected the USB, and we accessed the Ventoy menu successfully. Issue: We were unsure which option to choose to start the installation, so we decided to try another tool. 2. Second Attempt with Rufus (Successful Installation, But Boot Failure) We recreated the USB with Rufus, using MBR (BIOS mode). This time, the installation completed successfully, and Debian was installed on disk h0. Issue: After rebooting, we got the following error: "No boot device available" 3. Troubleshooting & Diagnosis Attempts We suspected an issue with h0, so we removed it and tried to boot without it. Result: The same error ("No boot device available"). We then removed h1 along with h0 and tried again → same issue. 4. Reinstalling Debian on Another Disk (h1) We removed h0, assuming it was faulty. We restarted the Debian installation, this time selecting h1 as the system disk. New errors during installation: Failed to create the swap partition → Error message displayed (see image 1). I/O error on /dev/sda during partitioning → "Input/output error during read on /dev/sda" (see image 2). Questions & Investigation Paths: We are unsure whether the issue is caused by hardware failures (disks or RAID controller), BIOS misconfiguration, or Debian's disk detection process. BIOS or UEFI Mode? Should we enable a specific mode in the BIOS (UEFI vs Legacy) for Debian to properly detect the boot disk? Possible RAID Issue? Are our disks part of a RAID configuration (hardware or software)? Could the Dell PERC RAID controller be interfering with the installation? How can we verify and properly configure RAID for Debian? How to Check if Disks Are Faulty? Is there a command to check disk health before installation? Should we try another Linux distribution to see if the issue is Debian-specific? Any help or suggestions would be greatly appreciated as we are currently stuck with this installation. Thanks in advance!