I've encountered this after upgrading some Debian/Ubuntu/Mint based systems for no explicable reason, although there are some bug trackers on Ubuntu that document this: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509 The short end of the solution is that you need to properly reinstall grub. 1.) Boot from a LiveCD 2.) Mount your root / filesystem and don't forget to mo........

Before you try to install and dual boot it is very important to understand the concept of "what boot mode your BIOS is in" and "what mode you booted the installer to". Then follow the example of Linux Mint (but most Linux installers are very similar)to carefully understand WHERE you are installing your Boot Loader to whether that be MBR or EFI. How Am IBooted? First it's important to check your BIOS to see........

I find that the default settings for the radeon driver that is applied to most AMD cards is horrible. For example by default TearFree is not enabled and it causes videos to have some kind of square artifacts. Here are the settings I have found most suitable for AMD cards: You need to create file in the following path and restart Xorg or your computer to apply it: *Beware that making a mistake here will possibly make your computer........

There are many ways but a favorite way is to boot any Linux LiveCD and to use the syslinux package like so: Just change the "sdx" to your sd for example /dev/sda or whatever the drive is that is supposed to boot Windows. sudo dd if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdx 0+1 records in 0+1 records out 440 bytes copied, 0.0197808 s, 22.2 kB/s........

Iwas surprised to see that Linux Mint at the latest 17.2 version still has NO mdadm installer option, and worse the installer will not be able to create a proper booting environment even when you do install it. How to setup mdadm in Linux mint LiveCD sudo su apt-get install mdadm # partition as you need and then create your mdadm devices # create your SWAP md0 mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /d........

I had a system running a 128MB live CD image with 2.8 gigs of available RAM and the OOM kernel killer went crazy when using dd for more than 8 minutes and kept killing everything. I've read that this is due to a low-memory issue and paging in the kernel and 32-bit systems with lots of RAM. I even enabled swapspace on my LiveCD and the issue happened 25 minutes into dd rather than 8 minutes, so what gives? Also no swap space was ever used! cat /proc/s........

I wanted to Import/Use a .vmdk hard disk image file from VMWare. Generally you can just "point" VirtualBox to it and use it and it will work but I found an exception. One of my Centos 4.4 x64 images wouldn't boot. I had two copies, an older one and the newer one. The older one booted as normal (once I changed the VirtualBox driver to IDE from SATA). The newer one stopped at the "GRUB loading" message no matter what I tried. As far as........

From a LiveCD or if you're doing something like converting your non-RAID install to mdadm here's how you would chroot properly (you have to mount your proc, sys and dev on the running system/LiveCD to your chroot environment if you want things to work right, especially if you need to run update-initramfs due to a driver change etc..) *replace "path" with your mount/chroot path mount -o bind /proc /mnt/path/proc mount -o bind /dev/ mnt/pa........

I have an md0 arary that my Centos install refers to. I feel this is half the reason why it won't boot anymore. I saw the initrd for Centos was assembling it as md127 even though it was known as md0. The reason for this is because I used mdadm --assemble --scan to detect the array on a LiveCD. I had no idea this name would stick (but now I realize the name is permanently stored in the metadata once you mount md127 or whatever random name assemble gives it). W........

I successfully created a single RAID 1 partition which includes /boot inside it and my root directory through the Debian installer. It said GRUB installed successfully but when I try booting the OS it seems GRUB can't read anything. When trying to boot from GRUB GRUB Loading stage 1.5. GRUB loading, please wait... Error 2 I get "Error 2" when trying to boot Debian. I also notice from a LiveCD that........

It's not just as simple as running the chroot command, you need to ensure the /proc and /dev entries are passed through and populated to the chroot environment. Step 1 - Mount Your Off-lineOS mount /dev/sda1 /mnt Step 2 - Mount Proc mount -t proc none /mnt/proc Step 3 - Mount Dev Most guides will tell you to use this: mount -o bind /dev /mnt//dev but that doesn't work for some reason in many cases: mount: wron........