Installation :: How To Install On RAID 0 Non UEFI System
Feb 10, 2016
I've rescued an old small server(working with Red Hat enterprise -- but I can't have the OS as it's licensed by the office) from our office --was being chucked out but looks quite good to me.
4 SATA bays populated with 4X 3TB HDD's (the HDD's were mine BTW !!!). I'm thinking of using this as a NAS server - 16 GB RAM and decent Intel CPU (i3 equivalent -- good enough for media server).
The only problem is that it's MBR BIOS and I have two RAID 0 arrays consisting of 2 X 2 3TB HDD's.
Installing Windows though -- No HDD's seen !!! yet there's 12 TB of them in the system.
The RAID is onboard --not a separate RAID controller.
Should I remove the HDD's and send the server on it's original journey to a one way trip to the City's TIP.
(On board VGA good enough also for running a GUI - if I can ever install an OS on it -- preferably W10).
I'm upgrading my mom's laptop from windows 7 to windows 10. Since my last upgrade I seem to have misplaced my USB Stick that has the UEFI Windows 10 install media on it. I do, however, have a few DVDs lying around that are large enough to make a Installation DVD. If I use the Microsoft Windows 10 Media Creation tool, will it create a UEFI Installation DVD?
So, I have Windows 10 already installed on my PC. I upgraded it last Summer from Windows 7 for free.
I've been trying to update it for the past 6 weeks but keep getting the error: "Windows 10 couldn't be installed. Windows can't be installed because this PC has an unsupported desk layout for UEFI firmware."
I have 3 hard drives and Win10 is running on my main SSD, disk 0. I remember having some funky upgrade issues and needed to unplug certain hard-drives due to strange ownership issues. Heres is a look from Disk Management. I've got an MSI m-board plus BIOS, all new.
As the title says how exactly do you achieve this?
I have an ISO Ran RUFUS 2.6 GPT Partition Scheme for UEFI Fat 32 8192 Default X Quick Format X Create a bootable disk using X Create Extended label and Icon Files
so the next part is the Kicker Dell did a number on their Bios and rather than using standard logic as we have done so many years just setting the boot order to "Boot USB" first, you "Only" have the option to create a "Boot Program"!!! so you select your USB Drive then which ever file you want it to boot I'm Assuming? So I tried selecting Setup, bootmgr.efi, and autorun with no results!
I get the secured boot error crap, turn that off and I get Legacy BIOS (that defeats the entire point) What the hell happened to Win95 Boot Discs and FDISK?
I am so frustrated with this garbage, I found out the hard way with Windows 10 and trying to nuke the SSD and put a clean install of 8.1 on it.
How do I set my BIOS to have the DVD boot and install Windows 10 in UEFI mode? I do see a setting on my Asus motherboard UEFI "CSM Compatability" and in there are three options:
UEFI and Legacy OPROM Legacy OPROM only UEFI only
Do I select UEFI only option here?
What is the benefit of installing in UEFI vs Legacy? All I understand is that the system sets up more partitions.
If I create a DVD with Windows 10 Home and try to perform a clean install on a computer that came with Windows 8/8.1 Home pre-installed. Will Windows 10 Home recognize and accept my genuine Windows 8/ 8.1 Home Key stored in UEFI or firmware etc?
By Clean install I mean not updating but directly trying to install on a computer, on which Windows 10 have never been installed before.
I have an ssd and I want to get another to configure it in raid zero for faster pc but I have already installed windows 10 on one, is there a way I can configure it in raid zero without having to reinstall windows?
Just converted my systems to Windows 10. Working well, so far. I would like to install 4TB disks on a couple of the systems and understand that I need to use UEFI. Looks like my ASUS P8Z68-U GEN 3 MB supports UEFI, but I don't understand how to enable it. The other system has ASUS B85M-E mother board. I've seen some one paragraph descriptions, but they don't really walk me through the process.
1 - Can I upgrade my existing system without a complete Windows 10 reinstall? I have lots of apps installed so I'd like to avoid complete system rebuilds.
2 - Due to legacy use of Mirrored drives, I'm using the Intel RAID stuff, although I no longer need it. Will that be a problem? SSD and other disks are JBOD. I'd like to get rid of that, but I think that does require a complete system reinstall since disabling the RAID wipes the disk.
Looking for step by step process to convert a system to UEFI to support 4TB disks?
I have a Toshiba that I wanted to run Windows 10 Pro, the OEM was Home; I have Windows 7 Pro and decided to install that and do the upgrade and then a clean install, I needed to run Legacy Mode to install Windows 7, after the install and upgrade I wanted to change it to UEFI but since that isn't possible to do without doing a clean install or a recovery media device, I can't and don't want to do that.
If I do a clean install of Windows 10 Pro, from a USB and delete all partitions, will Windows 10 activate?
I have done so on my desktop, it has worked, BUT when I did it on my Toshiba after it activated to Windows 10 Home, it failed to activate during the clean install. What are the chances it won't activate this time? The process from Windows 7 to 10 isn't fast and I don't want to have to do that again..
I am converting an existing Windows 10 Pro laptop to RAID 0 - and I keep getting to the final boot where it says INACCESSIBLE_BOOT_DEVICE. What am I doing wrong? The laptop has two 1 TB Samsung 850 SSDs that are identical. Laptop is a HP Zbook 17.
Here are my steps:
1. Made a good System Image of C: drive on separate external SSD drive connected by USB. D: drive didn't have anything on it to be saved. 2. Used Win 10 Pro DVD to delete all partitions/format drives. 3. Went into BIOS and changed from AHCI to RAID, and also to turn on ability to do Control-I to get to Intel RST ROM. 4. Rebooted, did Control-I, created a RAID 0 of the two disks. 5. Rebooted, installed Windows 10 fresh. Verified it would reboot on its own. 6. Rebooted, went into Repair on Windows 10 DVD. Selected external SSD image to do image restore from. 7. Rebooted - verified on Control-I that the RAID 0 array is listed as "bootable" 8. Rebooted - get INACCESSIBLE_BOOT_DEVICE.
The place it dies - I see the little Windows 10 blue window, and the spinning circle at the bottom - then I get the blue screen with the message.
last few hours I spent trying to manually deploy Windows 10 on clean GPT disk but after applying image and rebooting I always end in unbootable state.
I manually setup drive like this:
Code:
select disk 0cleanconvert gptcreate partition primary size 350 #RE tools won't fit 300MB anymore :-)format quick fs ntfs label "Windows RE tools"assign letter tset id de94bba4-06d1-4d40-a16a-bfd50179d6acgpt attributes 0x8000000000000001create partition efi size 100format quick fs fat32 label Systemassign letter screate partition msr size 128create partition primary format quick fs ntfs label Windowsassign letter wlist volumeexit#no recovery image partition as per documentation it is no longer needed and followed by pretty common deployment:
After reboot I always end unbootable (as we talk Apple computer it means 1) no partition on Option or 2) folder with ? or 3) just gray screen, make your pick). There's a chance that Windows rely on some UEFI 2.0 feature, which is not available as the old guy has 1.2 only. Or maybe I missed some step somewhere.
I have two systems.System 1 is a desktop running W7 Premium SP1. I did clean install of W10 from iso on separate partition. W10 will not activate using W7 numbers. I suspect that is because I moved W7 to an SSD 6 mos. ago and W10 expects the old HDD. BTW, installed W10 to partition on the SSD
System 2 is dual boot laptop (Dell Inspiron) with W7 SP1 and W8.1. I want to keep W7, and I could try W10 install either by upgrading 8.1 or clean install to the 8.1 partition. Reccomendations? I don't want to risk losing the W7. I do have disk image backups of both W7 and W8.1.
Microsoft released an update (specifically KB3064209) in June (2015) for Windows 7 that effectively caused a system with an Intel Pentium G3258 processor to not boot after the update was applied.
Interestingly, it DID boot successfully but the screen remained black. The screen works perfectly fine up until just an instant after the 'Starting Windows' logo displayed, then the black screen.
This was not motherboard manufacturer/video card/video driver/etc. specific. It happened on many different configurations with the only common factors being the G3258 CPU, Windows 7, and the KB3064209 Update.
Fast forward to the the wonderful, new, shiny Windows 10 officially released a couple of days ago.
Windows 10 Will Not Install On a System With a Pentium G3258 CPU! (In almost every case)
Neither trying the install through 'updates' nor trying the install with an ISO image will work.
The installation fails with this error: "We couldn't install Windows 10 0xC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during boot operations"
As I predicted in other forums, this issue has come back to haunt us with a vengeance after most of us agreed that simply not installing the Update 3064209 was a 'fix' to it causing the headache in Windows 7.
In Windows 10, this is not an 'update' that you can elect to not install, it is internal to the Windows 10 code.
Microsoft blames Intel, Intel blames Microsoft, and just a very, very few motherboard companies (1 that I know of; Asus) have issued a BIOS update which supposedly fixes this.
Some reports say that Intel has agreed to "look into the problem but it may take a few weeks."
A huge amount of discussion in other forums offers two possible workarounds:
1) Removing ALL overclocking of the CPU (a few people have said this allows a successful Windows 10 install) 2) (And this is just ridiculously unacceptable), going into the UEFI BIOS and disabling one of the cores of the CPU. However, the reports are that 100% of the time, this allows a successful installation of Windows 10.
99% of Pentium G3258 owners who want to install Windows 10 (and perhaps selfishly want to use both cores), we are out of luck for the foreseeable future.
A lot of reports are that a couple of the Windows 10 Preview versions did not have this problem, but the final 29 July 2015 release does.
There is a large number of motherboard owners who have somehow gotten the mistaken impression that you're golden if you have a Z series motherboard. Mine is a Z87 and the problem is present with it. So don't waste your money thinking you can just buy a new Z87/Z97/Z99 and the problem will magically go away, it won't.
Note: I will burn in Hades before I disable a CPU core to allow some BS 'fix' to a Microsoft/Intel complete and absolute debacle.
I'll guess I'll remain a faithful Win 7 x64 user for some time to come, it looks like.
Is it advisable to set the UEFI BIOS (Asus ROG Hero Maximus VI motherboard) to a factory default settings before installing Windows 10? Or should I at least set the memory "XMP" profile?
Get Important updates: cleared. Gets windows 10 ready but then it Checks requirements:
Windows does not prompt any choices,
We couldn't update the system partition Dialog crashes. Does not allow one to choose which partition
Gateway Nv59 64 bit Intel 430m Duo core Windows 7 Premium 500GB hdd 8GB Gskill ram 1333mhz
Take note here that I cannot merge any of the disks, they all result in error or System lock. I can't make the 35MB system disk larger, but Easeus, Windows disk formatter and some other major ones I've tried just say No. But the problem is windows 10 doesn't give me the choice to overwrite the C or H which is quite large enough.
Take note that i just used the SAME flash drive to boot/install windows 10 to a friends lower spec Intel i3 laptop with 1/2 as much ram from Win 7 BASIC. Don't tell me It's not powerful enough..
I currently plan on doing a clean install on a new ssd of Windows 10. My current mobo is a ASUS P8z68-V which has UEFI so I plan on doing a UEFI installation of Windows 10. However, I plan on getting a new processor and motherboard sometime in the future, so would I have to do a reinstall of Windows 10 when I get my new motherboard, or could I expect it to boot up normally as would a traditional BIOS system would work?
I just brought a 128GB sandisk ultra usb 3.0 because as a computer tec im tired of fumbling through my tons of usb drivers to do a job. , i want my windows installers & Linux, bookable tools and such all in one usb. so i looked into multibooting usbs and came across many tools, one being SARDU. But i need a hybird UEFI/MBR boot and my laptop doesn't support uefi & legacy simultaneously only one or the other.
So using SARDU i cant see or boot from the usb unless i switch bios to legacy mode, works well because i see and can boot from all of what i have windows installers and linux distros but i have to keep switching back and forth between legacy and uefi. i was wondering if i can make the usb primarily Uefi bootable BUT also bootable for a old MBR if needed.
i've installed windows 10 on linux before and i've never had any problems booting it (from what i remember, through UEFI boot sources). currently the windows 10 iso seems to be the only one that isn't appearing in UEFI; i installed peppermint from lubuntu using the same image disk writer on the same usb 30 minutes ago.am i supposed to have some specific settings enabled/disabled in my bios to boot the windows install? secure boot is disabled and legacy boot is enabled.
Assume a computer with the UEFI firmware interface.
Assume that during or after a user has upgraded a W8.1 machine to W10 things go horribly wrong - Black screen, Blue screen, No screen. The user now tries to Boot from a USB Emergency Boot Disk that they previously created using the W8.1 utility and then they try to restore W8.1 from a System Image Backup (the one in File History) that they previously created.
Will this be possible and will the Product Key in the UEFI firmware allow a reinstall of W8.1 after a W10 upgrade...?
After resetting UEFI to default values, I can't start WIndows because boot goes to UEFI.
I wanted to make a clean install of W10 and for that I had to make some changes in UEFI because it wouldn't allow me otherwise. But after the installation I see that I have some problems with the sleep and fast boot, not working well. So I went to UEFI and reset it to default, saved and exit. On boot, it goes to UEFI once and again. Windows doesn't load.
So I have to do the same changes that I had to do for installing W10. Disable fast boot, etc. And then yes, I get to Windows, but keep having the same sleep and boot problems. Both work really bad in different ways.
I also did other changes, by the way. I couldn't install W10 because it said that my disk was GPT partition style, so I had to follow some instructions to change that, which wiped my disk and partitions completely and maybe I missed some step...
Okay, so the other week i received a new Clevo P650SE laptop. The laptop only had a 500GB 7200RPM HDD with Windows 10 to begin with, so yesterday i added my Samsung 840 EVO SSD. As i wanted this to now be the primary drive, i made another new installation of Windows onto here. After doing this, the system now displayed a boot selection at startup with the choice between the new Windows 10 installation on my SSD or the old one on the HDD.
As i no longer wanted to use the HDD for running Windows, i decided it would be best to delete Windows from this drive. So i booted onto an Ubuntu USB and wiped the entire drive of it's data in GParted, which included three different partitions. This seemed perfectly fine to me at the time, because i had a the new installation from the SSD showing up in the boot manager.
However, when i rebooted the machine and attempted to boot into the new installation on the SSD, it gives me this message:
"The boot configuration data from your PC is missing or contains errors. File: /EFI/Microsoft/Boot/BC Error code: 0xc000000f"
I have tried everything to recover the system but nothing has worked. Startup repair from my Windows USB doesn't do anything, the system reset wouldn't operate because it stated that the partition was locked.
Nothing with the Command Prompt is working, I have done 'bootrec /fixmbr', 'bootrec /fixboot' and 'bootrec /rebuildbcd', but the last command returns the following error:
"The requested system drive cannot be found."
I also did 'bcdboot C:/Windows' but that also refused to work. I assumed the reason for this might be because the drive didn't have a letter, but when i attempted to add a letter is says:
"The specified drive letter is not free to be assigned."
Both drives in my laptop have now been completely wiped and converted to MBR, but even with the two drives empty the original message still appears when booting my Windows USB in UEFI.
I have only had this laptop a couple of weeks and it's already completely messed up. I can boot the Windows USB in Legacy and install Windows as normal, but of course i'm looking to have it back on UEFI as it was before.
My computer is trying to install Update to Windows 10 Home, version 1511, 10586, but can't. It claims there is no system reserved partition, but there is. This computer was upgraded from Windows 7 to 10, and immediately after doing that I installed a Samsung SSD and migrated the system to it using the software that came with the SSD. The migration went well and I've been using Windows 10 for months.
All of a sudden, when trying to do some updates it claims it cannot update the system reserved partition. The partition is there, it's 100MB in size. So I tried booting from the install CD, which I burned to do the upgrade (so I know it's a good disc). My computer recognizes there's a disc in the DVD drive, but no matter how I set the bios boot order it will not boot from the DVD, so I can't do a repair on the SSD.
Okay. I have been doing a lot of cloning and migrating an OS before but I haven't done cloning or migrating an OS from dual drives in RAID 0 mode.
It's not my PC. Is it a different approach or is it just like working on a single drive? Can Macrium handle this?
Btw, I know clean install is the best way to go, but I was told by the PC owner that she can't afford to install all her programs back due to time issues, etc.
I bought two new SSDs to be used in a RAID 0 configuration with a Dell 9020 under Windows 10.
Before the drives I arrived I configured two old HDDs in RAID 0 and installed Windows 10 as a clean install. This worked perfectly.
Once the new SSDs arrived I configured these in RAID 0 and started a clean install. Windows correctly identified the disk with the correct capacity and the install completed without issue.
When the computer restarts I got a "A disk read error occurred" error.
If I boot from the installation media to a command prompt I can see that the Windows files have been correctly installed to the C drive of the RAID 0 array.
I also tried loading the RAID drive during Windows install but this made no difference, and if it was the driver causing the issue it would not have worked with my old HDDs.
If I open diskpart I see that the drive is not marked as boot, which it is when I check these details on the old HDDs in RAID0.
