# Fedora partitions are not recognized after a Windows update

Hello,

Yesterday, I did a Windows update, and I don't know how, it ruined my fedora partitions.
I have a SSD, with some partitions for Windows, and two partitions for Fedora:
- /boot/EFI (500 Mo)
- / (88 Go) in ext4 format.

Now, when I look on Gparted for example, my two fedora partitions are marked as "unknown", with a /!\ before, as you can see in this picture.

Before the Windows update, it was working great. When I was switching the PC on, it was bringing me on the Grub.
Now it starts on Windows directly, and my fedora partitions seem to be corrupted...

edit retag close merge delete

Follow this how to restore grub instruction, if this doesn't fix it, try running testdisk or this ubuntu instructions just change the commands to fedora commands.

( 2017-12-10 16:54:30 -0600 )edit

How did you run gparted? Where you able to boot Fedora? Or is there a Windows version of gparted out there?

( 2017-12-11 00:20:59 -0600 )edit

Sort by » oldest newest most voted
 1.
Boot your system using a "live DVD" or (preferably) a “Live Demo” image on a USB drive

2.
Open a shell window and become root: sudo su

3.
Create a directory: mkdir /x

4.
You need to know which drive partition holds the target system, i.e. the Linux system you want to boot. For clarity, let’s discuss things using the shell variables $partition and$drive. An example might be: partition=/dev/sda6 ; drive=/dev/sda

If you happen to know, based on experience, where the target system lives, define $partition and$drive accordingly, and skip to step 8. If you need to figure it out, proceed as follows:

Get a list of disk drives: cd /dev/disk/by-label; ls -al

With any luck, you will see something like this:

drwxr-xr-x 2 root root 200 Mar 26 07:59 .
drwxr-xr-x 6 root root 120 Mar 26 08:00 ..
lrwxrwxrwx 1 root root  10 Mar 26 08:00 emu -> ../../sda9
lrwxrwxrwx 1 root root  10 Mar 26 08:00 linux-root -> ../../sda5
lrwxrwxrwx 1 root root  11 Mar 26 08:00 lnx -> ../../sda11
lrwxrwxrwx 1 root root  11 Mar 26 08:00 more -> ../../sda10
lrwxrwxrwx 1 root root  10 Mar 26 08:00 SERVICEV003 -> ../../sda1
lrwxrwxrwx 1 root root  10 Mar 26 08:00 SW_Preload -> ../../sda2
lrwxrwxrwx 1 root root  10 Mar 26 08:00 usrsrc -> ../../sda7

If necessary, you can get additional information from cfdisk /dev/sda. This has the advantage of showing the partition size, along with the partition-type for each partition.
Identify which partition(s) might plausibly hold the target system’s root directory. In the example above, linux-root is almost certainly the right answer, but lnx is a semi-plausible alternative.
To make sure, mount each plausible partition and take a look at it.

mount /dev/sda11 /x
ls -al /x/boot/vm*
ls: cannot access /x/boot/vm*: No such file or directory

That tells us that sda11 is definitely not the right answer. So let’s try again:

umount /x            # unmount previous hypothesis

mount /dev/sda5 /x
ls -al /x/boot/vm*
-rw-r--r-- 1 root root 4275712 May 30  2013 /boot/vmlinuz-2.6.39.4
-rw-r--r-- 1 root root 4678720 Aug 25  2013 /boot/vmlinuz-3.10.9
-rw-r--r-- 1 root root 4599824 Mar 23 18:45 /boot/vmlinuz-3.11.3+
-rw-r--r-- 1 root root 4599824 Mar 23 18:43 /boot/vmlinuz-3.11.3+.old

5.
When you find the desired partition, leave it mounted on the mountpoint /x.

6.
Define $partition and$drive accordingly. Example: partition=/dev/sda5 drive=/dev/sda.

7.
If not already mounted: mount $partition /x 8. Reinstall grub: grub-install --root-directory=/x$drive

Beware: You want to install grub on the drive (e.g. /dev/sda). If you install it on the partition (e.g. /dev/sda6), the grub-install program won’t complain, but the results won’t be what you wanted.

more