There are a number of reasons why Drauger OS may not boot. This is true of any operating system. Here, we try to provide some instructions on how to get Drauger OS to boot. However, we cannot cover every situation in which Drauger OS will not boot. So, if you do not see a solution that helps you on here, please reach out to us on our Telegram Support Group, on our Discord Server, Submit a Bug Report, or email us.
First off, please note that all of the instructions below are for computers with AMD64/x84_64 architecture. If your computer has a 32-bit (x86 architecture) processor, or if it has ARM, PowerPC, RISC-V, or any other CPU architecture, it will not boot because we do not make ISO images for these processor types.
Computer Turns on but the screen stays blank
If you have this issue, then most likely you have a BIOS or UEFI issue. To fix this follow the below instructions. NOTE: THIS IS NOT A GUARANTEED FIX. ONLY ONE POSSIBLE FIX.
- Open up your computer and find the CMOS battery. These are usually flat, shiny, and silver. If you are familiar with Lithium Cell Batteries, it is one of those.
- Once you find it, carefully remove it then disconnect your desktop from power (unplug it from the wall).
- Leave your computer alone for about 10 minutes
- Put the CMOS battery back and plug your computer in.
- Your computer should now boot. Your UEFI and BIOS setting have now most likely been reset.
- Look on the bottom of your computer for a very small hole. It may say “Reset” next to it. Your computer may not even have one of these. If it does not, refer to the instructions for desktops.
- If you find the hole, get a paperclip, a push-pin, a SIM Ejector tool, or something similarly long and thin, and push it down in the hole.
- If you feel something like a button click, hold it there for about 2-5 minutes, with your computer unplugged.
- Pull your prodding device out and attempt to power on your computer. If it works, your BIOS settings may have been reset.
For both the above instructions, do not be alarmed if it takes longer than normal to boot up. This is normal from a fix like this.
Computer boots then says it can’t find anything to boot from
This error essentially means that your computer cannot find the GRUB install.
If you installed Drauger OS using UEFI, make sure that the EFI partition is formatted in either VFAT or FAT32. Otherwise, your UEFI cannot read it. (Drauger OS currently has issues with UEFI. We suggest installing with Legacy BIOS instead if you can. We will make a wiki page about that later and link it here.)
If you installed Drauger OS using Legacy BIOS, then you likely installed GRUB to the wrong place.
The below instructions may help you fix this issue. However, proceed with caution because this could bork your drive, so make sure you back up your data. If you are at all unsure about this, just try reinstalling Drauger OS.
All of the following should be done from a Live USB.
This will list all drives and partitions, real and virtual, on your system. Look for the drive that matches the drive you installed to. Note it’s location (usually /dev/sda1 for normal SATA drives and /dev/nveme0n1p1 for NVMe drives).
- run the following, replacing /drive/location with the location lsblk told you your drive was at (the /dev/sda1 thing)
sudo mount /drive/location /mnt
Afterwards, if you go to /mnt on the Live USB you should be able to see the contents of your drive.
- Bind the directories GRUB needs to fix the GRUB install on your drive:
sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bing /proc /mnt/proc sudo mount --bind /sys /mnt/sys
- Now, we will chroot into your install:
sudo chroot /mnt
- For the rest of this, you only need to remember what drive your installation is on. So, if your install was at /dev/sda1, you only need /dev/sda, if at /dev/sdb2, you only need /dev/sdb, and so on.For NVMe drives, this slightly more complex: if you are installed to /dev/nvme0n1p1, then remove the “p1” to get the drive itself
- In your new shell prompt, run (replacing /drive/location with the location of your drive):
grub-install /drive/location grub-install --recheck /drive/location update-grub
- exit out of the chroot:
- un-mount everything:
sudo umount /mnt/sys sudo umount /mnt/proc sudo umount /mnt/dev/pts
- Shutdown the computer now, remove the Live USB, then boot back up. It should work now!
Computer boots to manufacturer logo then gives a Grub Command prompt
If this happens then /boot/grub/grub.cfg has an incorrect formatting. This requires a complex fix. If you do not wish to go through these steps, then just back up your data then re-install Drauger OS.
If you do wish to fix this and not to re-install Drauger OS, follow the following steps:
- Download and make a bootable USB of almost any Linux distribution
- On your computer, boot from this USB drive and go to where you can try out the OS.
- Connect the OS to the internet
- Mount the internal drive on your computer, taking note where the install for Drauger OS is mounted at.
- Open a terminal and type this, replacing /mount/point/for/Drauger-OS with the path to where the Drauger OS installation is mounted:
- Next, run:
apt update apt dist-upgrade apt autoremove dpkg --configure -a update-iniramfs -u grub-mkconfig --output=/boot/grub/grub.cfg
- This should fix anything wrong with your install, from GRUB, to the Initial Ram File System, to any issues with dpkg, to errors in apps. Your computer should now be able to boot Drauger OS. If it does not, consider re-installing Drauger OS after backing up your data.
Computer Boots to an initramfs command prompt
Issues such as this can be caused by many things one common error is file system issues if this is the case, run:
If you get dropped back at an initramfs command prompt, it may tell you what partition is messed up. If this is the case, run
Replacing /corrupted/partition/path with the partition that initramfs mentioned. If this does not fix it, consider re-installing Drauger OS after backing up your data.
Computer boots to log in screen but then loops back when log in is attempted
This is common issue. It can be caused by a number of issues. Try these steps to fix this:
1. Try login in again. Sometimes Xfce/LightDM will crash the first time but will work the second time. If this doesn’t work, continue to Step 2
2. Press Ctrl+Alt+F2 to get to a login shell. Login using your Username and Password (you will not see your password. It’s going in, just not showing it)
3. If you made any scripts the run at login and/or boot-up run this command to edit it, replacing /path/to/script with the path to the script you made:
Use Ctrl+O to save and Ctrl+X to exit. You are wanting to take out the command ‘exit’ anywhere you use it that is not in some sort of sub-shell.
If you DID NOT make some sort of login script, ensure the file “.dmrc” in your home folder exists. If it does not, run this command:
echo -e "[Desktop]\nSession=xfce\n" > $HOME/.dmrc
This will create the correct “.dmrc” file for the Xfce desktop. For other desktop environments, you will need to change the text after “Session=” to get it to work correctly.
4. Run exit to log out, then Ctrl+Alt+F7 to get back to the login screen.