Hummmm Curiouser and curiouser. This is starting to sound like a boot problem. For this next part you are going to need a Utility Disk such as KNOPPIX that will allow you to mount the /boot and /root (under which you should find /etc) partitions. There are 3 files that you need to LOOK at: /boot/grub2/grub.cfg; /etc/default/grub; and /etc/grub.d A quick place to start is to view /etc/grub.d You *should* see something that looks like this:paco wrote:Hi desertcat,
861MB of free space.
These are the files that you *should* have correctly id'ed:
*00_header
*00_tuned
*01_users
*10_linux
*20_linux_xen
*20_ppc_terminfo
*30_os-prober
*40_custom
*41_custom
Sometimes these file numbers get out of whack. Here is where you will find things moved, renumbered, duplicated, or omitted. These files should have a chmod of 755 ( -rwxr-xr-x), and be owned by root:root. I just had this this problem trying to dual boot one machine into the other and then vice versa. If you see this list out of order or renumbered, then the chances are good your boot config file has been toasted.
See if you have a file in /boot, /etc/default, or /etc/grub.d called /backup.
Apparently this is and old problem in as much you are told to in /etc/default/backup under RESTORE_INSTRUCTIONS:
How to restore this backup
--------------------------
* make sure you have root permissions (`gksu nautilus` or `sudo -s` on command line) otherwise you won't be able to copy the files
* to fix an unbootable configuration, just copy:
* '/etc/grub.d/backup/boot_grub' to'/boot/grub2'
* to reset the whole configuration (if it cannot be fixed by using grub customizer), also copy these files:
* '/etc/grub.d/backup/etc_grub_d' to /etc/grub.d'
* '/etc/grub.d/backup/default_grub' to '/etc/default/grub'
Most of these files are throwbacks to a virgin system and lack any customizations you may have made between install and the point where you become toasted. The files that are most likely to become mangled are found in /etc/grub.d which interact with the files in /boot/grub2/grub.cfg referenced above.
Referencing the above list which show the config files names and the correct order in which they should appear, see if yours matches this list. IF you see say *10_linux sporting a new name or is numbered like *31_linux, or worse still duplicated, the procedure is to eliminate one of the two IF THEY ARE THE EXACT DUPLICATE OF EACH OTHER and then simply rename the the misidentified back to *10_linux you would then do the same for each config file until you have replicated the list. WARNING: If you have NOT messed with these config files and/or know what the contents should look like DO NOT ATTEMPT!!!! Once you have the list back in order you then run grub2-mkconfig -o /boot/grub2/grub.cfg After that reboot the machine and cross your fingers.
If however your list matches the supplied list you have eliminated one suspect.
Two final questions:
1) Can you still boot into the previous kernel or is that too whacked?
2) Did you change anything?!? Pulled cards, inserted cards, etc., etc., etc. If so just for fun run grub2-mkconfig -o /boot/grub2/grub.cfg It should tell you if the machine is fine or it sees ERRORS. If it sees ERRORS that may -- or may NOT (mine were very cryptic and did not make a lot of sense) -- point you in a direction.