Ask Your Question
0

Windows dont start after Fedora 20 Beta update

asked 2014-04-20 09:35:41 -0500

VoidByte gravatar image

updated 2014-05-11 13:40:41 -0500

mether gravatar image

Hey guys,

so i have had this Fedora Beta 20 x86 for too long. Today i updated it with: yum check-update yum update

after a few hours of updating process, a grub update follows. After a reboot everything works fine, excapt by starting windows. heres what happen:

Starting Computer -> BIOS Screen shows up. -> GRUB launch and waits for my answer -> Windows -> Blackscreen with a flashing bold white cursor in the upper left. -> Nothing more until i restart and choose fedora.

so i decide that this must have to do something with GRUB and where trying to update it again with: grub2-mkconfig -o /boot/grub2/grub.cfg

The process´s runs done without problems. But windows wouldn´t start. Because im not good @ such boot things i was trying the "Grub Customizer" and installed GRUB on another partition. Same result. I have no clue what to do now.

This is the current grub.cfg:

 #
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="Windows 7 (loader) (on /dev/sdb1)"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

terminal_output console
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux_proxy ###

### END /etc/grub.d/10_linux_proxy ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-D2E4C8FFE4C8E6B7' {
    insmod part_msdos
    insmod ntfs
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  D2E4C8FFE4C8E6B7
    else
      search --no-floppy --fs-uuid --set=root D2E4C8FFE4C8E6B7
    fi
    chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/31_linux_proxy ###
menuentry "Fedora, with Linux 3.13.10-200.fc20.i686+PAE" --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.10-200.fc20.i686+PAE-advanced-1229ae78-eaec-4c86-9c60-092faddda296' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  52a5991b-8c2e-4628-85f7-5960a993ff11
    else
      search --no-floppy --fs-uuid --set=root 52a5991b-8c2e-4628-85f7-5960a993ff11
    fi
    linux   /vmlinuz-3.13.10-200.fc20.i686+PAE root=UUID=1229ae78-eaec-4c86-9c60-092faddda296 ro rootflags=subvol=root vconsole.font=latarcyrheb-sun16  rhgb quiet 
    initrd  /initramfs-3.13.10-200.fc20.i686+PAE.img
}
### END /etc/grub.d/31_linux_proxy ###

### BEGIN /etc/grub.d/33_linux_xen ###

### END /etc/grub.d/33_linux_xen ###

### BEGIN /etc/grub.d/34_ppc_terminfo ###
### END /etc/grub.d/34_ppc_terminfo ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply ...
(more)
edit retag flag offensive close merge delete

Comments

I've seen this a couple of times, can you do a Windows filesystem check from inside Linux? If your C: drive is /dev/sda1, do a fsck.ntfs /dev/sda1 as root.

fidelleon gravatar imagefidelleon ( 2014-04-20 10:14:18 -0500 )edit

Ok interesting result. I was make sure with Gparted that Windows lay on sdb2 and tried it:

[VoidByte@localhost ~]$ sudo fsck.ntfs /dev/sdb2
[sudo] password for VoidByte: 
Unsupported: replay_log()
Unsupported: check_volume()
Checking 955648 MFT records.
Unsupported cases found.
ntfsck was unable to run properly.

seems bad, but maby the right way. So how can i fix problems there?

VoidByte gravatar imageVoidByte ( 2014-04-20 11:31:26 -0500 )edit

I'd boot with a Windows CD and run CHKDSK from it. For Windows XP you'd need to boot from CD, press "R" at the initial screen, you may be asked for your "Administrator" password, and then run CHKDKS C: /P. Windows Vista and Windows 7 have a "Repair boot problems" (or something like that) which may autodetect your NTFS problems and fix them, but be advised you MAY lose GRUB - well, recovering Grub is way easier than recovering Windows boot ;)

fidelleon gravatar imagefidelleon ( 2014-04-20 11:48:59 -0500 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2014-04-20 11:50:00 -0500

VoidByte gravatar image

I solved it by myself. Here´s the solution:

The "Grub Customizer" shows me something like "Script: OS-PROBE" in the bootparameters. I changed that to Chainloader+1 and set it to SDB1 (what i get from Gparted named as: Windows Recovery)

after this step i saved all up, reboot, and everythings fine now!

Thanks fidelleon

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2014-04-20 09:35:41 -0500

Seen: 220 times

Last updated: Apr 20 '14