You are not logged in.
Pages: 1
So after using several different Linux distros on virtual machines over time I decided to give Arch Linux a try on a new partition alongside Windows 7. During the installation process I was having trouble with getting my network setup so I exited the installation and tried to escape to Windows to read up more in the Wiki. Apparently I made a mistake because I can no longer boot up windows.
Steps I took:
1. Download Archboot .iso
2. Create a bootable USB
3. Shrink my single 1 Tb HDD by 65 Gb to make room for the Linux partitions
4. Boot my PC from the USB
5. Went through the motions of Archboot to define my new partitions
/ 15Gb
/Home 50Gb
swap 2Gb
2007Kb for Bios
After the failed attempt I reverted to a Linux Mint Live CD to try and work this out. Im currently cloning my HDD with Clonezilla to make sure I don't screw things up further. At this point what I want to do is take a couple of steps back and see if I can read up a bit more and see what I did wrong setting up the dual-boot partitions and formatting. Can anyone lend some advice on how I can get Win7 back up and running? Once I have 7 running I will give Arch another shot.
I am pretty certain that I will somehow return my Windows bootloader to MBR and just delete the new partiotions, but I am not exactly sure the best way to proceed. Any help would be greatly appreciated.
Last edited by maat7043 (2015-01-27 04:21:38)
Offline
See: http://www.howtogeek.com/howto/32523/ho … -problems/
"/fixmbr" and "/fixboot" should be all you need to do. Finish your clone of your drive first though, just in case it makes things worse.
Offline
Do you think it's necessary to use a tool like GParted to remove the new partitions I created first?
Offline
It shouldn't be. They'll just show up as either non-DOS or unallocated space in the Disk Management snap-in in Windows if you look. They should be ignored by Windows.
Offline
If the fine advice given by @headkase doesn't work, post the output of:
# parted -l
That "2007Kb for BIOS" partition is only needed for GPT disk booting in non-EFI mode -- Windows will not boot in non-EFI mode from a GPT disk.
I'm thinking that you may have changed your partition table type during the aborted installation attempt...
Offline
Pages: 1