Ask Your Question

Windows boot partition /dev/sda1 lost in dual boot Fedora 21

asked 2016-04-12 10:45:14 -0600

pal1 gravatar image

updated 2016-04-13 00:21:54 -0600

Hi all

For some reason, I am not able to boot into my Windows (10) anymore. It has been a long time that I have been busy with Fedora and do not remember since when it has been lost. It might be because of a couple of errors I had, during loging into Fedora from "Journalctl" entering "emergency mode" that I fixed it by "Fdisk -l and Fsck". Now I have my Fedora and Windows options in boot menu but choosing Windows goes to error, saying;

Error; no such a device xxxxxx

Error; HD0,msdos1 not found

Error; HD0,msdos1 not found

Fdisk gives me these without /dev/sda1 which is now 106MB of free "unallocated space" but not shown here and no boot device marked but boots to Fedora just fine.

fdisk -l /dev/sda

Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x7dceab2d

Device     Boot     Start       End           Sectors       Size     Id    Type
/dev/sda2          206848    209020927  208814080   99.6G   7     HPFS/NTFS/exFAT
/dev/sda3       209020928  209942527    921600       450M  27    Hidden NTFS WinRE
/dev/sda4       209942528  468860927 258918400  123.5G   5     Extended
/dev/sda5       209944576  210968575   1024000      500M  83    Linux
/dev/sda6       210970624  344743935 133773312    63.8G  8e    Linux LVM
/dev/sda7       344745984  468860927 124114944    59.2G   7     HPFS/NTFS/exFAT

I wish to fix this problem without wiping off my Windows nor Fedora (because of all the installed software and saved projects and settings). Otherwise, would just use my Windows USB recovery media to rewrite the MBR Boot partition and reinstall Fedora 23.

Any help would be much appreciated.

ps; Looks like my grub and grub2 have issues also, when I run grub2-mkconfig, I get these errors;

grub2-mkconfig -o /boot/grub2/grub.cfg

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.1.13-100.fc21.x86_64
Found initrd image: /boot/initramfs-4.1.13-100.fc21.x86_64.img
Found linux image: /boot/vmlinuz-3.17.4-301.fc21.x86_64
Found initrd image: /boot/initramfs-3.17.4-301.fc21.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-5bc3b0146bfa44b1b157766d86d3d8f8
Found initrd image: /boot/initramfs-0-rescue-5bc3b0146bfa44b1b157766d86d3d8f8.img
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 147
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub2/ file attached.
edit retag flag offensive close merge delete



Please check if this Q/A is any helpful...

florian gravatar imageflorian ( 2016-04-12 14:39:06 -0600 )edit

Thanks, @florian, in that particular case in EFI, the Windows Boot partition is available, looks just in the wrong order, while in this case it is BIOS and for some strange reason the partition is wiped off and I do not know what sort of information were sitting there. One suggested scenario, to fix this would be, to create the partition (NTFS, BOOT?) in that /dev/sda1 unallocated space and then to reinstall the grub, but How to reinstall the Windows Boot part (by Windows recovery media or Fedora and GRUB) is a question and if Grub would recognise the Windows partition later to boot from?

pal1 gravatar imagepal1 ( 2016-04-12 20:54:39 -0600 )edit

Ah, I see. Sorry, I didn't read your question carefully enough in the first place. Your sda1 is "missing". Your grub (installed in MBR of /dev/sda) seems to work, otherwise you wouldn't be able to boot Fedora (which has its /boot on /dev/sda5).

In regards on how to restore/reinstall the content of the Windows system partition sda1, I can't help you because I have no clue about MS Win, especially not the new releases. Maybe this one is helpful but I am sure there will be other users to jump in here.

florian gravatar imageflorian ( 2016-04-12 21:22:09 -0600 )edit

@florian Thanks a lot for your help, I think Windows could recover itself with Windows recovery media but the problem is that Windows will take over the Boot loader and removes Fedora, do you think if I do that, Fedora could then be recovered too?

pal1 gravatar imagepal1 ( 2016-04-13 00:30:12 -0600 )edit

Sure, Fedora can be recovered. All Windows does is installing its bootloader into the MBR of /dev/sda. So, what you need to do is starting a Fedora Live System, chroot into your existing Fedora installation, and reinstall grub. Grub will automatically detect the existing Fedora and Windows OS'. This site has plenty of questions regarding chroot, Reinstallation of grub, and system rescue. Let us know if you can't find them.

florian gravatar imageflorian ( 2016-04-13 09:24:40 -0600 )edit

1 Answer

Sort by » oldest newest most voted

answered 2016-04-13 05:47:02 -0600

pal1 gravatar image

OK, I solved this issue by using my Windows recovery media, which repaired my /dev/sda1 and then restarted and booted to Windows successfully and everything was fine as it used to be. I also restarted again to check the damage affected Fedora but surprisingly it works just as smooth! Thanks to their smart design! So everything is back to normal, and I might repair my Grub when I get a chance. Thanks to @florian and all who checked this page, I will now mark this as answered for future references.

edit flag offensive delete link more


Feel free to mark your own answer as the correct one.

Just for my understanding, what is wrong with Grub? Or, how can you select and start an OS if Grub is not installed? Or how did you boot Fedora (in case Windows installed its own bootloader into your MBR)?

florian gravatar imageflorian ( 2016-04-13 09:28:06 -0600 )edit

And btw: Now it's time to upgrade your Fedora. Fedora 21 is End-Of-Life since December 2015 and not supported with important security updates. Please check out this page for upgrade instructions

florian gravatar imageflorian ( 2016-04-13 09:38:06 -0600 )edit

@florian Looks like there are some errors in grub and also grub2 could not be configured which I did not get to look at it but it should not be a problem as the system works. I first booted the system using a Windows 10 USB recovery media and repaired the first partition; /dev/sda1 which is now back and has the BOOT sign next to it. After Windows installed its Bootloader, for some reason it did not touch the system configuration which was not something I would expect from Windows but it was appreciated! Thanks for your help and advice, I sure will upgrade soon as I get a chance.

pal1 gravatar imagepal1 ( 2016-04-13 16:45:48 -0600 )edit

Question Tools

1 follower


Asked: 2016-04-12 10:24:21 -0600

Seen: 1,098 times

Last updated: Apr 13 '16