Debian Installation :: Dual Boot Problem Windows 7 And EeePC?
Feb 1, 2011
I have used dual boot systems using various versions of windows and Debian for many years and have encountered no problems. However, I have a problem with installing Debian on a EeePC (ASUS PC1201) which uses Winows 7. I can not even get started because I can not understand the information that I have on my hard drive partitions. Windows 7 says that I have the following :
Local Disk(C:) 78.1 GB free of 99.9GB
Local Disk(D:) 49.8 GB free of 83.8.GB
NewVolume(G:) 948 KB of 0.99 GB
Local Disk(F:) 37.9 GB free of 38..0 GB
(Originally the ASUS only had two partitions C: and D: I used Gparted to genetate F: and G:)
gparted-live-0.7.1.5 says that I have the following :-
/dev/sda1 ntfs 992.5 KB
/devf/sda2 ntfs 100.00 GB with 66.09GB unused
/dev/sda3 ntfs 132.88GB with 129.88 GB unused
unallocated 1.00 GB
Debian Squeeze (the net install version) will not install. G was the result of trying to provide some swap space. How do I prepare the hard drive so that Squeeze it will install on F: ?
I'll start off with stating my problem and summarize how I got to it.
I installed Windows 10 on an SSD. I installed Debian 8.2 after it. The SSD was/is a GPT disk. I installed both installations from a UEFI booted device (DVD for Windows, and USB drive with Live CD for Debian).
I tested it after each installation making sure I could boot via UEFI into Windows, then Debian, then Windows, to make sure nothing broke.
I rebooted the machine. Suddenly, no more UEFI. Nothing. I didn't change any BIOS/UEFI setup menu settings. Not even my USB drive with Live CD will boot through UEFI anymore. Even when nothing else is plugged into the system.
My situation is actually a bit more complicated than that, but I think that will suffice for now. I can still boot into the Live CD on the USB drive, just in Legacy mode only. I mounted the EFI partition on /mnt/boot after I mounted the file system for Debian on /mnt. It is identical, as far as I can tell, to as it was before when it was working.
My motherboard has CSM and Secure Boot, both have been set up how they need to be to boot UEFI into Debian. Tinkering with them further after things broke did not fix it. I tried all variations of options/settings.
The GRUB Reinstall guide says to be in EFI mode before starting it, so I can't do that.
My motherboard is an ASUS X99 Deluxe, and I've heard ASUS has special "features" (read: bugs) that come with their boards. Searching hasn't brought up any other people with this issue. I believe the firmware is updated to it's most current one.
I've tried dd-ing my backup of my old system, from before trying to migrate to a Dual Boot system, to the SSD (after backing up the dual boot setup with dd -> <name>.img via the Live CD USB). However, that won't boot either as it is a UEFI install as well.
The layout of my EFI partition is as such: /boot/EFI/Boot/bootx64.efi /boot/EFI/Microsoft/<Microsoft-naming>.efi /boot/EFI/debian/grubx64.efi
I've heard that the standards on how that's supposed to be set up isn't a standard. However, since it worked booting into the OS' the first time, I don't see how that could be the issue (a bad hierarchy layout leading to the UEFI not being able to see the OS installs).
I've seen that I can boot to an EFI shell (called Shell.efi, apparently) via an option in my UEFI BIOS setup menu on my motherboard. Is that an option here to somehow bypass this strange issue?
All I can think to try is burn it all and start over. But not knowing what caused it means I could just make it happen again. Plus, I can't boot into UEFI install media, so I can't install UEFI boot OS'. :/
I've recently bought a new computer and installed Windows 7 on it, but left 100GB of space on a separate partition so I could put Debian next to it in dual boot. I have the new Intel i7 950 processor and I run Windows 7 Proffesional 64 bit, so I assumed I had to pick the ia64 debian image. However the CD I burned from the ia64 image didn't boot. (a black screen started and an underscore kept flashing, but nothing else happened)[URL]
I've managed to install i386 Debian on a older intel pentium 4 computer before and that worked fine. I believe I used another application to burn the CD then. This time I've burned the CD with the default Windows CD burn application. I can try burn more CD's but I don't have much left so I want to make sure this is the problem before attempting again. (the burned files on the ia64 CD look exactly the same as the files on the i386 CD, when browsing through the cd files in windows) "If your PC has a 64-bit AMD or Intel processor, you will most likely need the "amd64" images (though "i386" is also fine), the "ia64" images will not work."This seems a bit strange, they recommend me to use the amd64 image if you have a "64-bit AMD or intel processor". I dunno if this is a typo, but it seems weird to me that the AMD-64 Debian version would also work on my Intel machine
I recently installed Debian 7 on a dual boot with Windows Vista. Thus, when I boot the computer, I am prompted by a GRUB screen to select Windows Vista loader, Debian, and Debian (recovery mode). I would like to upgrade Windows Vista to Windows 7. Will this cause an issue with GRUB? Will a Windows 7 loader be added to the list or will a Windows 7 loader replace the Windows Vista loader? Will there have to be a setting change within Debian? Within Windows?
I have a Dell laptop (inspiron 1150) which was dual booting Windows XP and Ubuntu 9.04. I have successfully installed Debian Jessie Standard over the Ubuntu. I pre-partitioned using gparted-live to make a separate single partition for the Debian install. Guided partitioning was then carried out by the installer producing separate /, /home, and swap partitions. After installation, the grub menu shows an entry for Debian and Windows XP. I can boot Debian, but not Windows XP. The symptoms are the same as reported in other forums: A terminal is displayed, vanishes and the system reboots defaulting to the Debian boot.
The grub.cfg file for the Jessie system has an other-os entry:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" { set root=(hostdisk//dev/sda, msdos2) search --no-floppy --fs-uuid --set=root cc0ce0ab0ce091ae drivemap -s (hd0) ${root} chainloader +1 }
The original Windows entry for the Ubuntu install was:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" { insmod ntfs set root=(hd0,2) search --no-floppy --fs-uuid --set cc0ce0ab0ce091ae drivemap -s (hd0) ${root} chainloader +1 }
The partitions produced by partman look OK (during the pre-partitioning I did not touch sda1, sda2, or sda3):
Code: Select all~ # os-prober /dev/sda2:Microsoft Windows XP Home Edition:Windows:chain
So it seems that everything is in place, but there are perhaps important differences in the grub.cfg files. Are the two "set root" commands equivalent for example?
I have Windows 10 and Deb 8 dual boot, and I need to re-install Windows but want to avoid (or at least plan for) losing Grub/Linux boot.
Last time I re-installed Windows after Linux I ended up having to re-install Linux again afterwards as well, because I couldn't recover it (seemingly due to complications from encryption). So this time I'm wanting to plan and avoid that.
CURRENT DISK PARTITIONS:
Code: Select allsda1 | 550M | EFI System sda2 | 128M | Microsoft reserved sda3 | 175.8G | Microsoft basic data sda4 | 286M | Linux filesystem (Boot) sda5 | 28.2G | Linux filesystem (Root) sda6 | 91.3G | Linux filesystem (Home) sda7 | 1.9G | Linux swap
[Code] ....
As there is a "Microsoft Reserved" partition and a separate Microsoft directory within the EFI partition, if I just go ahead and reinstall Windows will it install it's boot loader/image to one of it's own partitions? And NOT affect anything else like Grub and other Linux things?
Logic tells me yes, but there seems to be many issues on the internet about installing Windows after Linux.
My primary concern is whatever happens with Windows or anything to do with dual loading etc, is that Linux will still just boot, or I can get it working again without much hassle.
Why is there a reserved Microsoft partition AND a Microsoft directory in the EFI partition? Which one boots Windows?
Why is there a separate Linux Boot partition AND a Linux directory in the EFI partition? Which one boots Linux? Where is Grub invoked from, is one redundant, etc?
How these work. It is possible I've set them up wrong, or with redundant partitions, but both systems have been booting ok for months.
I've been using Debian for a few years but always on dedicated boxes and/or VMs.
Finally decided to dual boot Debian and Windows on my main Desktop PC.
Installed as I normally would using, however this time using a seperate drive (one for the existing Windows 10 install and the other for Debian), Debian install detects that windows has an EFI partition and sticks an entry in there, which is fair enough, and everything working fine. Then I spent some time configuring all my software and set it all up just the way I like it. I've rebooted Debian a few times to check it's working correctly and it is.
The issue arrives when I reboot and load into Windows 10. It boots fine.
However after a further reboot GRUB no longer loads... and the machine just boots directly into Windows 10.
After doing some further digging into my EFI partition (and reinstalling various times) it would appear that after a reboot Windows 10 deletes the entry GRUB creates in my EFI partition after EVERY reboot.
Done some googling and most people advise turning off 'fast boot' in Windows as it locks certain partitions to facilitate the machine going into hibernation, only to find that it's always been turned off on my machine (I recall due to a driver issue with my graphics card this had to be turned off when I installed Windows 10).
I've found this article on the Ubuntu forums : [URL] .... however I've tried their steps and windows is still doing a hostile takeover of my EFI partion after a reboot!
Any way to stop Windows 10 from interfering with my EFI files after a reboot? (without doing the obvious thing and kill Windows off).
how to install Debian after Windows is already installed. Could someone give me a brief guide to begin the process of installing Windows? When I installed Debian I already made a partition for windows (in the same hard disk), I hope I did it right.
I had a dual boot machine with fedora 12 and windows vista and I could use grub boot-loader to switch between two. Few days ago windows got corrupt and I have to reinstall it. I put windows 7 now and as usual it erased grub. So to reinstall I put the fedora 12 installation CD on and followed some usual setup steps. When I got the command line I issued the command "grub-install /dev/sda" (sda not hda because It showed bunch of sda, sda1..) but surprisingly it said grub command not found. I remember doing it before while it worked fine.
I had 9.10 installed and I did an upgrade to 10.04. However I cannot see anymore my Windows Vista partition with grub.. I have a Toshiba laptop Satellite p305.This is my boot script output:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in [code].......
I just did an upgrade from 9.10 to 10.04 and now I can't boot into Windows 7 on this dual boot desktop. I usually do a clean install but with a laptop and desktop a copy of Windows 7 and Ubuntu on each machine it's getting very tiring with 4 os's so opted for the upgrade this time.
During the installation there was a window that game up about upgrading grub and what devices to install it on. The help box was not very complete and seemed to say to click all the check boxes which included the main drive and it's partitions including windows. During the install somewhere it said something like grub could not be installed on one of the devices which I think was sda6 which is probably the Windows 7 partition.
So how would I get the option of booting into Windows 7 on startup as now I only get a blank black screen when I click on the Windows 7 option upon bootup? I hope I don't have to reinstall one or both os's again from scratch as this is becoming to much work to do on two systems every 6 months, especially with the amount of programs I have installed.
I have a netbook running Windows XP as standard. There is also a recovery partition which came from the factory.
In the past I installed Ubuntu (I think 9.something) from USB key and all worked fine. However my XP became corrupted and I needed to do a repair on it. After this, Ubuntu became removed from the boot select menu.
Since then, Ubuntu has become updated to 10.04, which I now cannot install.
The Live CD tells me there is a "file IO error" and simply stops installation at around 70%.
I did manage to get into Ubuntu from a Live USB using Wubi. However when I chose to install Ubuntu to a Harddrive, the option to "install side by side" was missing.
After reading on the forums, I did a chkdsk /f on Windows and tried again. Now my liveUSB does not show a boot menu!
When I select to boot from USB stick, the screen goes blank with a flashing cursor. Ctrl+alt+dlt reboots.
I'm really lost here! It seems when I fix one problem, another problem arises!
Also when trying to instal Ubuntu within Windows, the process goes through to 100% and asks me to reboot. When I do so, the option for Ubuntu does show in the boot menu. However when I select it, I get an error "Windows boot failed: file wubildr.mbr and status: 0xc00000f - something is corrupt".
I have Ubuntu 10.04 LTS and Windows XP installed on my laptop. Usually when booting, I get the GRUB 2 menu and I can boot into either Ubuntu or XP.I was playing around with EasyBCD, then after trying to remove it I was unable to boot into Windows, I used a Windows 2000 CD recovery console to fix the MBR (using: fixboot and fixmbr).Now Windows starts up when I power on, but I don't get the grub menu anymore with an Ubuntu option. If I boot from the Ubuntu Live CD and try to mount my Ubuntu partition (/dev/sda5) I get this error:
mount: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error In some cases useful info is found in syslog - try
I have just installed Ubuntu 10.4 x64 onto a machine with Vista Ultimate x64. When I boot the machine, the Windows option comes up in the GRUB menu. However, when I attempt to boot Windows, I receive the following error: No such device: de80ab9f80ab7d21. error: No such partition. Press any key to continue...
I looked around and found a similar issue at [URL] However, before trying to fix the issue by guesswork or via solutions that worked for a similar, though not necessarily identical problem. I've run the boot info script (see output below) mentioned several places on this site as a valuable input for boot problem tracking. how to get Windows to boot on my computer?
I just set up a dual boot on a system with fedora 12 and XP. XP in on one hard drive (sda) and Fedora on a second hard drive (sdb).
I installed grub on the Fedora disk so as to not touch the windows disk at all.
Prior to installation, in the bios, I set the Fedora disk (sdb) first in the boot sequence, and then XP (sda) so that the grub loader would boot up by default. (If I set the windows drive first then the system bypasses grub and loads straight into windows.)
My system can now boot up into Fedora fine, but if I select windows from the grub loader menu I just get a blinking cursor - windows will not boot.What do I have to do so that grub can boot into XP?
I am trying to install Ubuntu on a machine that already has Windows 7 on one partition. Obviously I intend to install it on the other free partition. So I downloaded the iso burnt it onto the disk and pop in the disk and the boot the machine. The installation screen comes up I selected the first option (Try Ubuntu without installation), I just see a prompt after a few seconds and then the screen goes blank and nothing happens. Unable to detect a signal, The monitor goes into standby. The same thing happens if I use "install Ubuntu" option as well. I downloaded minimal install version Ubuntu and tried to install with that. since its old school installation, the installation completed without any errors, but when I restart the grub come up and when I select to boot into Ubuntu, I see the same behavior i.e. the screen goes blank and never boots to anything. This is a machine on which I was using 10.4 until yesterday.
I have set up authentication when I am logging from my laptop using windows 7 (putty) into Debian server (see this post [URL].....) but since my laptop is dual boot (Windows 7 and Ubuntu) how would I set up authentication when i am using Ubuntu since from Ubuntu I will be logging into Debian SSH as same user that I am when logging from windows?
I just got a Toshiba Mini NB305-310 and tried to install Ubuntu 10.04 on it using the .iso file on a flash drive. When I try to boot into Windows XP, the loading screen comes up for a second, flashes blue, then restarts the computer. I'm able to boot up in Ubuntu, but it takes a LONG time with the screen black before it goes to the Ubuntu loading screen. I saw in an earlier post that it's helpful to post the output of the Boot Info Script, so I've posted it below. I'm new to the forums, so if I'm doing anything wrong, please let me know:
Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ============================== => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #5 for /boot/grub.
I am trying to run a dual boot system with Windows 7 and an Ubuntu 9.10 installation from a live CD. I am running this on a Dell Inspiron M5030. Both operating systems have installed fine however whenever I run Windows the computer subsequently fails to run Grub upon rebooting and gives the following error message:
Grub loading the symbol 'ob_bioslgrub?+E?U? Not found Aborted press any key to exit
The unrecognised symbols are different each time. I have also had (' ') and ('ee*??S ') and ('un'). I cured this initially by reinstalling Ubuntu but after looking at the support documentation have now found that I can cure it temporarily by simply reinstalling Grub using the command:
I had to boot into my Windows 7 install on my laptop for the first time in a few months and I noticed that the Windows clock was 4 hours ahead. Windows sync'd its time with the internet, then I booted back into Debian (Lenny) and my clock was now 4 hours behind. Both OS's are set to the same time zone (EDT). The minutes were correct in both systems. Could the fact that EDT is UTC-0400 be relevant?
I've a Lenovo G50-80T with W8.1. I want to install Debian 8.1 in dualbooting mode. I've done this other times without problems. But this time I want encrypt the Linux partition (not the Windows partition). I'll use dm-crypt to do that. I want to know if this way is secure for protect the data on Linux partition or if I need encrypt the entire drive.
I'm currently dual-booting Squeeze & Windows XP on a machine i use frequently.
In my experience on the desktop, i now see no reason to have Windows XP as a boot option, & wanted to try & avoid a full re-installation of Debian in order to remove XP (merging it's partition with / ).
I have a checklist that i put together, but wanted to be sure this was all correct before going forward.
1. Perform full back-up of all data.
2. Boot into Debian, through GUI -
System Tools > Disk Utility
- Select HDD (80GB Hard Disk) - Select windows partition ( /dev/sda1 ) - Format /dev/sda1 to Ext4 Filsystem
3. Boot Live CD
- Use gParted to extend /dev/sda2 (was 38GB, will extend to 78GB)
4. Remove XP from the boot menu.
( Note: My ~ folder is on the same physical drive as / (same volume), but i actually store all Media on a separate physical drive which is formatted in NTFS. I plan on reinstalling XP using a virtual hard disk, & sharing that with the virtual machine.Here is a screenshot of my Disk Utility - [URL]
This problem goes back to when I first purchased my laptop 4 years ago: Dell Precision M90. It came with Vista, but I wanted Ubuntu on instead. In order to get bluetooth to work, I had to downgrade the firmware. This is all fine and means bluetooth works in XP too. However, now, I have a dual boot with Windows 7 and Squeeze, I use Vista drivers (as Dell don't provide 7 drivers) and this has upgraded the firmware, and broken bluetooth in Squeeze. How can I get bluetooth working in both Squeeze and Windows 7? Could changing the hardware help? If so, what to?
I've successfully used Fedora 11 from a USB stick as a live cd iso. Everything seems to work on my netbook so i want to try installing it but I need it to be a dual boot with windows. How can i do this? And will it definitely work or are there issues (I've read that F11 has problems installing if not taking over the entire HD)?
I just installed Fedora and I love it but I can no longer boot Windows 7. I have two hard drives, sda and sdb.sda1 is my windows partition. sda2 is my /boot for Fedora. sdb1 is an ntfs partition for storage. sdb2 is swap. sdb3 is my 40 gig /root partition. Why can't I boot windows?
A while ago I used a friends computer with F11 installed on it. I definitely want to install F13 on my computer now. Please, can someone either tell me complete information from the beggining to the end, or simply direct me to a guide somewhere else on the internet. I have a F13 live cd and want Windows 7 to be in control of the boot (by I suppose LiveBCD).
