Since the forum only allows 4 Images in a thread I’ve posted this HERE. Anyone with a multidisk configuration might find this helpful. It took me some trail and error before getting all this right.
Since I took the time to figure out how to do this I figured I’d post a thread. I would suggest having your windows 7 Disk handy before loading SUSE. You can also create a repair CD in windows by searching repair. This will allow you to recover the windows MBR in the event you have issues. I usually load Grub to my windows C: drive MBR and let it be the boot manger. However, this time I wanted to used EasyBCD add SUSE to the Windows boot manager. This worked out great. I loaded SUSE to my Disk 2 which already had 2 partitions I created in windows (one fat and one NTFS). I didn’t want to involve my Windows SSD (Disk 3) to install the MBR/Grub.
Here’s a picture of my disk management in Windows prior to loading SUSE. This is taken from my thread here.
Disk 3 is where my Windows 7 load resides on a single partition on my 128GB Intel 510 SSD.
Disk 2 is where I put my Backups for my Windows 7 system among a few other things. This is a single 640GB Western Digital WD Black Drive
Disk 1 and Disk 0 Consist of TWO 1TB 7200 RPM Western Digital WD Black Drive Drives Running a Short Stroked Partition for my Games on Drive D using 460GB
Disk 0 Is part of the Two disk RAID 0 setup with 701GB used for my various applications with the additional 710GB unallocated.
Here’s my Windows Partition Setup:
So, what I’m did was used create partition tool in expert mode and installed it to my Disk 2 single 640GB Western Digital WD Black Drive. I was going to use the following space on the 454GB I have free on this drive to load SUSE.
/root - 20GB
/swap - 2GB
/home - 150GB
Upon loading SUSE off USB stick and clicking install it presented me with a default setup to load SUSE to my part of my spare/unused RAID Disk 1 location with 701GB free.
Also, When asked this question by setup I choose NO.
Following MD compatible RAID devices were detected:
If they are clean devices or contain partitions then you can choose to use
MD Partitionable RAID sysbsystem to handle them. In case of clean device you
will be able to install system on it and boot from such RAID.
Do you want MD Partitionable RAID subsystem to manage those partitions?
I didn’t want to load it where the SUSE default proposed so I clicked on create partition and selected my 640GB Western Digital WD Black Drive unused portion of the disk with the above allocations.
Here’s the Default of how it was prior to me modifying the setup. As I mentioned, it wanted to load to it to my part of my free RAID setup. I didn’t want to risk any issues with my RAID so that’s why I loaded it to my my 640WD I use as a backup drive. I also wanted my 2 partitions on the WD drive to remain intact. The default SUSE proposed might of worked but I had too many applications installed for windows on my RAID setup.
And here’s how I set my modified partitions to:
Next, I clicked on Accept and proceed to the next Screen where I modified the default GRUB installation disk and Boot order of the disk.
When you get to this Screen click on the Change Button at the Bottom and click on Booting.
This was the Default setup for Grub I had to modify for my setup.
PAST 4 IMAGE LIMIT. See link above for all images.