Sounds good, you're welcome. May need to download, extract and load a controller driver in order to access the other storage.
--please don't forget to close up the thread here by marking answer if the reply is helpful--
installed 2x 1tb m2 drives in RAID 0 from old motherboard onto new, odd behavior now...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 93%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENT%3C/text%3E%3C/svg%3E)
Nicolas Triana-Baltzer
25
Reputation points
I had (2x) M2 drives from a z390 chipset motherboard in RAID 0 configuration booting windows 10, using regularly and behaving fine. RAID was set up in windows disk management. It wouldn't work from the bios and I don't honestly remember how I managed to set it up I think cloning was involved at the time. Moving to a z790 chipset and...
Attempted to clone to a single drive before installation in case I needed it would not work because of the RAID being set up with software not bios. ok...
So, reinstalled windows from scratch onto one of the 2 drives. No more RAID but this is fine, operating off a single drive is fine with me.
But...now...within windows disk management it still shows the combined volume of RAID from the previous build!
It is also showing the healthy single drive that windows is installed and running from now, as a separate entity.
Attempting to access the combined volume fails. Attempting to format the volume from disk management fails. Disk management shows it as a still combined ~2tb volume (the drive is only 1tb). When I attempt to format the errant drive from file explorer window it returns an error.
Attempting to convert the combined volume in disk management to a dynamic volume returns an error.
Physical removal of the errant drive results in boot errors (!) and cannot boot windows from the single drive without the 2nd drive physically on the board, even though it is not part of the OS volume and is not accessible (in terms of formatting to use for storage or anything else).
What is going on and how do I fix this?? I want the system running off the single drive without the physical need for the 2nd un-used drive to be on the motherboard..I also want to be able to use the 2nd un-used drive as a storage drive. Right now it's a very strange place this system is in..
Screens attached
Windows for business | Windows Client for IT Pros | User experience | Other
Answer accepted by question author
7 additional answers
Sort by: Most helpful
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-18T17:33:40.79+00:00 Asus support has been very responsive but has not been able to resolve the issue. It is being elevated to a higher level I am being asked to fill out forms etc. Will follow up here with final results/answer
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-18T17:48:38.7666667+00:00 -
Nicolas Triana-Baltzer 25 Reputation points
2023-12-18T23:34:16.9+00:00 Update: CMOS reset and all motherboard chipset drivers reinstalled, still no change to the issue.
In device manager windows is able to see both drives but views 1 of the (2) 1tb drives as a nearly 2 tb volume. Cannot access it. Cannot format it. Cannot populate volume properties, drive is completely useless in windows yet system cannot boot without it being physically on the motherboard. Within BIOS both drives show independent with correct sizes and tests return healthy drive results. WINDOWS cannot figure it out. Still need help!
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2023-12-19T00:03:10.43+00:00 I'll assume from the screenshots the two 1tb disks are disks 3 and 4 and since you want windows installed to one of the 1 tb disks I'd remove all the others disk 0, 1 ,2 included. Then boot the install media and at this screen delete any partitions found
then create a new one and continue the windows install.
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-19T00:12:38.2733333+00:00 negative, disk C:\ is one of the 1 tb drives that the OS is running from, top of list in my screens there.
disk 4 partitions 1 3 and 4 there are all windows 10 thinking there are 2 in raid instead of just a 2nd 1tb drive. Trying to manipulate that in any way results in a hard stop.
When windows setup starts from a USB boot drive all it sees is this disk 4... it doesn't see the C:\ drive. When I try to delete it, error code. When I try to install to it, error code. When I refresh it nothing changes. When I try to install windows from boot with only 1 drive installed, it still sees it as a 2 tb drive that cannot be formatted, deleted or installed to. It's like I am really, really stuck here
-
Anonymous
2023-12-19T00:17:28.95+00:00 Try both disks one at a time as above.
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-19T03:07:21.1766667+00:00 results are the same regardless of which drive is connected while the other is disconnected. Setup sees a 2 tb volume that doesn't exist and does not see the 1 tb drive installed.
refreshing does nothing, deleting returns an error, installation attempt returns an error.
resetting the cmos on the motherboard did nothing. I am at a loss for thoughts except to attempt an installation with a different new single drive which hasn't arrived in the mail yet. But to expect different results seems a foolish thought because both of these drives are healthy. My problem persists despite all these efforts and I still need help
-
Anonymous
2023-12-19T03:13:08.02+00:00 Ok, well that's sort of good news in that it proves the disks don't have anything to do with it. There appears to be another boot device and or configuration within the pc. The pc or mobo manufacturer will be your best resource to troubleshoot problems with the hardware.
--please don't forget to close up the thread here by marking answer if the reply is helpful--
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-19T03:16:12.4866667+00:00 ok will continue dialogue with the motherboard manufacturer thank you for your time
Sign in to comment -
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-20T01:10:12.1766667+00:00 Solved!
Enabled Intel Rapid Storage in BIOS
Then was able to enable VMD Controller in BIOS
Within the VMD Controller, was able to manipulate all drives to create or delete RAID volumes.
Deleted the ghost RAID 0 volume. Ensure only 1 drive installed on board before
reinstalling windows.
Had to download and install Intel RST driver from motherboard manufacturer website, add that to windows boot drive.
On windows setup it sees no drives. Load driver, browse, locate RST driver on usb, install driver.
Now windows sees all drives. install. replace 2nd drive for on board storage. ghost raid volume gone, drive accessible, done.
-
Anonymous
2023-12-20T01:40:47.2933333+00:00 Glad to hear.
-
Nicolas Triana-Baltzer 25 Reputation points
2023-12-20T02:35:27.75+00:00 honestly the reason for my confusion is the lack of lammen's terms for what to do with the BIOS. Intel Rapid Storage Technology, and then Rapid Storage Technology...to deal with M2 drives and raid arrays...what the heck is going on, to a simple man...is simply lacking. Add to this windows setup not navigating this stuff for you, and windows virtual disk manager just complicating things...crazy
Sign in to comment -