Well, I went to update my windoze last night and went to bed. Well, this morning, I come to my computer to a grub rescue cause of an unknown file system. What I did is went to our favorite friend google, began googling on how to fix it. Kept hitting road blocks and dead ends from what others have tried. (Been at it for bout 2 hrs). Then I began to realize that grub can't seem to figure out my filesystems. So I googled that into it and stumbled onto this:
https://askubuntu.com/questions/142300/ ... rub-rescue And with in it, it had some instructions on how to get into the OS (didn't think nothing of it till after the last command)
Code: Select all
set root=(hd0,6)
set prefix=(hd0,6)/boot/grub
insmod normal
normal
Now once I was in Debian, I logged in and ran to a terminal and ran the update-grub comnand and it went like normal. I had to reboot to see if it worked, which it didn't. so I reran the commands from above and got back in. I then googled up update grub debian (yes, I know the command, but it failed). And saw a couple wiki's on grub 1 n 2. As I was reading on 2 at the bottom had some info about configuring an encrypted grub and on the last step it had install grub n update grub as a finisher. I for shits n giggles went to terminal and just punched in the command grub-install and it did its thing and then the update grub. Rebooted the system and whammo, its live and going again.
Now out of all this, I had to share that if anyone is using windows 10 as a side os of Debian, the latest os version update may screw with the grub so if you loose grub with unknown filesystem, run the above and then you should be golden again. And hopefully this will be use to someone who stumbles on the issue
