There are three drives on my computer, the first two are in Raid 0 and have Windows 8.1 installed. In my third drive, I had openSUSE installed. Every time you started the computer it would have the Grubloader open up and you could choose an operating system, openSUSE or Windows.
I wanted to give Ubuntu a shot, since it’s been years since I last used it, and when I put the install disc in, it didn’t detect the Windows partitions or the two hard drives in raid 0. It only detected the openSUSE partition and the swap partitions. I thought okay, no problem, and partitioned the entire third hard drive to have Ubuntu installed.
Now this is the problem, Ubuntu installed fine, but I’m not able to boot into Windows. If I choose to boot through the Raid 0 drives, Ubuntu loads up instead. When I take out the third hard drive and restart the computer, it goes into Grub Rescue mode. I put the Windows installation CD back in, and it was able to detect the Windows partitions and it was able to detect that Windows 8 was still installed, but programs like gParted say “Unallocated” for one of the hard drives in raid 0, and “Unknown” for the other hard drive.
How to get Windows to load correctly again? Did the openSUSE grubloader somehow ‘encrypt’ the hard drives in a way so that only grubloader could see it?
Hi
Since it’s Ub* you probably need to ask in their forums, but no openSUSE wouldn’t have done anything… I suspect the boot order in the BIOS may have changed to the drive you installed Ub* (or active partition) depending on whether it’s efi or mbr booting, running fdisk -l or gdisk -l on all the drives should identify.
Yeah I mean I can change the boot order from the BIOS, even if I choose to boot the Raid 0 drives, it skips it and goes to Ub*. When I physically remove the third hard drive, it goes into grub rescue.
It’s just not detecting there’s even a Windows at all. But when I insert a Windows install CD though, it’s able to detect the Windows partition is there.
Also I posted in the Ub* forums as well, trying to find out what’s wrong :\
This is what I get with fdisk -l:
/dev/sdc1 * 2048 216602623 108300288 83 Linux
/dev/sdc2 216604670 250068991 16732161 5 Extended
/dev/sdc5 216604672 250068991 16732160 82 Linux swap / Solaris
not showing sda or sdb drives for some reason, but they are in there
Hi
So you need to set the active flag from sdc1 (the *) back to which ever
disk sda or sdb (need to see the fdisk output).
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.51-52.31-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
That’s correct. According to BIS you posted in above thread GRUB is installed on your RAID disk and this GRUB points to the third disk (i.e. one with Ubuntu).
When I take out the third hard drive and restart the computer, it goes into Grub Rescue mode.
Which is again correct because then GRUB does not find its files.
I put the Windows installation CD back in, and it was able to detect the Windows partitions and it was able to detect that Windows 8 was still installed, but programs like gParted
gParted? On Window installation CD?
How to get Windows to load correctly again?
Run bootloader recovery from Windows installation CD. But you may be better off asking on Windows forum for guidance.
You may be able to simply install generic bootloader on your RAID disk, but then you are better off asking on Ubuntu forums how to do it in correct way. And I do not see in BIS output you provided any hint that Ubuntu set up RAID0 from the two disks, and you should not mess with individual disks here.
SOLVED! Thank you sir. You had to put in the Windows installation disc, select repair windows, go to command prompt, then type in the following:
bootrec /fixmbr
bootrec /fixboot
bootsect /nt60 all
Headache cured! This entire time I was trying to solve it through linux, but you gave the suggestion of fixing the “Windows bootloader” I just searched how to fix windows bootloader, then followed some of their instructions. Thanks, I don’t think I would have been able to come up with that on my own.
blindly installed bootloader on the first disk it saw instead of at least asking you where to put it
It means next time you update Ubunu kernel or bootloader it likely happens again and you lose Windows.
I strongly advice you to ask on Ubuntu forums how to tell Ubuntu to install bootloader on specific disk. Otherwise it is just time bomb waiting to fire off.
There are so many things inherently wrong with Ubuntu after my first day of using it that I remember why I stopped using Linux a few years ago, and I’m considering going back to openSUSE again.
My only issue is that there are some packages in APT that aren’t in RPM, maybe I’ll switch back to openSUSE again and post threads asking for help on those packages.
Here’s a really stupid Ubuntu issue:
So in Firefox, if you click on the Downloads arrow, then “Show All Downloads” then right click on a download and click on “Open Containing Folder” it opens Gwenview instead of dolphin. I found a thread that links this issue back to 2012: askubuntu.com/questions/131695/firefoxs-open-folder-opens-gwenviewa
There are so many issues, listing them all out would be an article on its own.
zypper if python3-devel
Loading repository data...
Reading installed packages...
Information for package python3-devel:
--------------------------------------
Repository: Main Repository (OSS)
Name: python3-devel
Version: 3.4.1-6.2
Arch: x86_64
Vendor: openSUSE
Installed: No
Status: not installed
Installed Size: 494.7 KiB
Summary: Include Files and Libraries Mandatory for Building Python Modules
Description:
The Python programming language's interpreter can be extended with
dynamically loaded extensions and can be embedded in other programs.
This package contains header files, a static library, and development
tools for building Python modules, extending the Python interpreter or
embedding Python in applications.
This also includes the Python distutils, which were in the Python
package up to version 2.2.2.
