You probably didn't do an "update-grub" and grub no longer has any proper menu entries, but before you can fix it let's try to get grub booting anyway. If you get this lovely black grub screen here's how you can get things booting. In my case I have a gpt partition with partition 1 and 2. Partion 1 is just my EFI / ESPand partion 2 /dev/sda2 is my root which includes /boot. You will have to adjust this if you had a separate /boot partition.........

Just a quick note and warning is that if you are testing to see if EFIPXE booting works on a VM, MAKE SURE it actually works. For example Iinitially tested using my Distro's QEMU 2.5+dfsg-5ubuntu10.46 and ovmf BIOS firmware (OVMF supports EFI). However, I found on old versions of QEMU (like 2.5), EFIbooting with GRUB NEVER works so it may appear that you have made a mistake when everything is fine when you boot a physi........

The problem seems to be that whatever kernel and initrd you have is tied to an old version of CentOS 7 that is no longer in the current repos of most mirrors. If you were previously able to PXEboot and install CentOS and you are sure your network and tftp are good the problem is that you have an outdated kernel and initramfs that point to a defunct version.........

I don't consider a lot of these "extra" kernel modules "nice to have" as they often contain drivers for essential items like your soundcard, your NIC and many other devices that may not work. Sometimes you may find that "sound" or "ethernet" worked before a kernel/OS upgrade and now in the new version they don't. Often it will be because you need to install the "extra" kernel modules. One other weird thing is that sometimes........

This is not the normal "black screen"issue and I was shocked to eventually find out why. The normal advice of reconfiguring Xorg didn't work. Even booting into "Recovery Mode" did not help. Here is the short end of the stick that fixed it: sudo apt-get install mdm mate-desktop-environment Yes you got it right, mdm and the mate-desktop-environment / gnome were somehow uninstalled. This must be whe........

This guide will work for most modern Linux versions like Centos RHEL 7, Debian, Mint, Ubuntu etc... In Centos 7 the days of editing the "kernel"line and adding "single"are gone. On top of that sometimes after a new install passwords do not work, maybe you forgot your password or for some other reason you need to break in or fix your system? It could also be because you can't mount your root / or some other /etc/fstab error and many other err........

*Update so this doesn't work it must be something to do with the path of nfs or something else but the installer fails with "Installer crashed" at the end whereas with the CD/USB it works. This assumes you've already installed and configured a separate PXE/DHCP server somewhere else and your /tftpboot directory is setup. This is for Linux Mint 18.1 but generally applies to most versions although you may have tro change things like "casper"........

Here is the scenario you or a client have a remote machine that was installed as a standard/default minimal Centos 6.x machine on a single disk with LVM for whatever reason. Often many people do not know how to install it to a RAID array so it is common to have this problem and why reinstall if you don't need to? In some cases on a remote system you can't easily reinstall without physical or KVM access. So in this case you add a second physical or disk or already ha........

Thsi is very handy when doing your own kernel development. -m specifies how much ram (in the example it is 768MB) -kernel specifies the path to the kernel file -net tap,ifname=tap1,script=no (the ifname=tap1 is what you need to change and setup manually). *Run "tunctl -b" to create a tap device and use the one it gives you for ifname= Enable networking to the outside like this: *Note we assume that your bridge is br0 i........

./configure ./configure: line 91: cd: /lib/modules/2.6.32-042stab084.25/build: No such file or directory Error: kernel version not found. Please make sure your kernel is configured. dr-xr-xr-x. 4 root root 4096 Feb 21 06:13 .. lrwxrwxrwx 1 root root 45 Feb 21 06:13 build -> ../../../usr/src/kernels/2.6.32-042stab084.25 drwxr-xr-x 2 root root 4096 Feb 12 20........

mount -o bind /proc /sda2/proc mount -o bind /dev/ /sda2/dev mount -o bind /sys /sda2/sys chroot /sda2 mint / # mount -o bind /proc /sda2/proc mint / # mount -o bind /dev/ /sda2/dev mint / # mount -o bind /sys /sda2/sys mint / # chroot /sda2 mint / # cd ~ mint ~ # ls Desktop mint ~ # cd / mint / # ls bin Desktop dev-temp home&nb........

This booting error is because the Xen PV guest image uses the Xen kernel, this is not compatible with anything but a host running a Xen kernel. I did a kpartx -av virtual.img and then it created some partitions that showed up in fdisk. I mounted it and did a chroot into it and removed the xen kernel and installed a normal kernel but Xen still shows the same kernel in Grub (only the Xen one). This is strange but it seems like this Xen PV guest has some sort of hidden or........

This is something I often setup for clients because it's very helpful for people in datacenters, this allows custom OS installs on demand, you can customize it more by using kickstart etc.. but here's a base I use before customizing more: This little script below will install everything you need to get booting by PXE Linux. It also assumes you set a local IP (be sure not to overwrite your existing IP) on eth0:0 (note the :0) as 192.168.1.10 and it........