Page 1 of 1

how can I fix boot list windows entry?

PostPosted: Aug 13th, '12, 11:23
by arminius
I've used clonezilla to move my dual mageia/windows hard drive to a larger drive.
Then I used parted magic boot cd to expand both partitons into the new drive.
Mageia boots up fine, but windows just hangs at the "starting up...." prompt.

Code: Select all
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=f02f245b-14f1-48aa-bf79-036507d2ccc6  splash quiet resume=UUID=68c9b0f6-df01-47e0-8383-8d55a0f20b9c vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=f02f245b-14f1-48aa-bf79-036507d2ccc6  resume=UUID=68c9b0f6-df01-47e0-8383-8d55a0f20b9c
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=f02f245b-14f1-48aa-bf79-036507d2ccc6  failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1


this is the first time I've looked at grub.conf so I don't know if the windows entry is right or wrong.

Re: how can I fix boot list windows entry?

PostPosted: Aug 15th, '12, 07:51
by arminius
Bump

Re: how can I fix boot list windows entry?

PostPosted: Aug 15th, '12, 08:13
by Ken-Bergen
Mageia boots up fine, but windows just hands at the "starting up...." prompt.
It looks like grub has done its job so it appears your Windows partition was corrupted by the re-sizing and moving.

Re: how can I fix boot list windows entry?

PostPosted: Aug 15th, '12, 08:26
by arminius
Hangs I ment to say, but windows hasn't even begun to start up.

Re: how can I fix boot list windows entry?

PostPosted: Aug 15th, '12, 08:35
by Ken-Bergen
arminius wrote:Hangs I ment to say, but windows hasn't even begun to start up.
Yes I know you meant hangs.
If your grub entry was wrong it would show an error.
Could you post a picture of this prompt it stops at?

Re: how can I fix boot list windows entry?

PostPosted: Aug 15th, '12, 15:03
by arminius
ok, first pic is what grub turned into after the transfer to the new hard drive.
second pic is what happens after you enter into windows, just hangs on that forever.

Also I tried using windows XP install cd to use the rescue part, but it claimed it couldn't detect any windows partitions on the drive.

But in the 3rd pic you can see there is a windows partition.

how do I make them thumbnails?

Re: how can I fix boot list windows entry?

PostPosted: Aug 15th, '12, 20:56
by doktor5000
Either use testdisk on the windows partition to see if it can still see some files in there, or use the recovery console from the windows install disk to run chkdsk /f/r on your windows partition. For testdisk, this is explained here: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

Re: how can I fix boot list windows entry?

PostPosted: Aug 16th, '12, 12:15
by arminius
how do we install test disk on mageia?
extremely frustrating, I downloaded the files for linux.
uncompressed it to a folder, but whenever I put in
Code: Select all
./configure

I got back
Code: Select all
bash: ./configure: No such file or directory

all the readme files in the folder were no help.

Re: how can I fix boot list windows entry?

PostPosted: Aug 16th, '12, 12:42
by arminius
damn, tried rocovery console, and everything I tried with chkdsk always came back with "the volume appears to contain one or more unrecoverable problems"
I'm hoping it was seeing ext4 and didn't know what to make of it.

Re: how can I fix boot list windows entry?

PostPosted: Aug 16th, '12, 19:31
by doktor5000
testdisk is in the standard repos, f.ex:

Code: Select all
[doktor5000@Mageia2 ~]$ urpmf -f --name -m testdisk
testdisk-6.13-3.mga2.x86_64:Core Release
[doktor5000@Mageia2 ~]$ urpmq --sources testdisk
ftp://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/2/x86_64/media/core/release/testdisk-6.13-3.mga2.x86_64.rpm



As you didn't post what exactly you did with chkdsk, i can't help you any further with that, put aside your mentioning of ext4, which sounds totally confusing.
You want to check an NTFS partition, but hope that chkdsk will see an ext4 filesystem? How do you come that that assumption?