Well, I thought I would try using Windows/Intel software RAID and was surprised to see that Windows now sees the disk as one volume. This is weird but it works. The speed is 1683Mb/s.
I guess I should restart to be sure that it is still there.
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change. For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails. You have 2 options: A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name. B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change. For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails. You have 2 options: A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name. B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) if I do this the OS does not boot. That's the "feature" of Intel drivers in windows which is there for 15 years without change. For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails. You have 2 options: A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name. B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change. For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails. You have 2 options: A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name. B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
//WTHell, this forum just removes every post as a spam. Even when I am a registered and confirmed customer of Dell.
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change. For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails. You have 2 options: A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name. B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
//WTHell, this forum just removes every post as a spam. Even when I am a registered and confirmed customer of Dell.
That is crazy. Now, all the posts that I tried to copy-paste with small differences in order to pass the bot, are all rolled out. And I can not delete the duplicates. Dell needs to work seriously with this forum.
Maria Krastroup
1 Rookie
•
4 Posts
0
January 24th, 2021 20:00
Well, I thought I would try using Windows/Intel software RAID and was surprised to see that Windows now sees the disk as one volume. This is weird but it works. The speed is 1683Mb/s.
I guess I should restart to be sure that it is still there.
Andy812
2 Intern
•
202 Posts
0
January 24th, 2021 21:00
Re: Adding RAID to Windows 10
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change.
For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails.
You have 2 options:
A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name.
B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
Andy812
2 Intern
•
202 Posts
0
January 24th, 2021 21:00
Re: Adding RAID to Windows 10
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change.
For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails.
You have 2 options:
A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name.
B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
Andy812
2 Intern
•
202 Posts
0
January 24th, 2021 21:00
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) if I do this the OS does not boot. That's the "feature" of Intel drivers in windows which is there for 15 years without change.
For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails.
You have 2 options:
A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name.
B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
Andy812
2 Intern
•
202 Posts
0
January 24th, 2021 22:00
Re: Adding RAID to Windows 10
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change.
For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails.
You have 2 options:
A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name.
B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
//WTHell, this forum just removes every post as a spam. Even when I am a registered and confirmed customer of Dell.
Andy812
2 Intern
•
202 Posts
0
January 24th, 2021 22:00
Replying you is impossible because the moderator bot removes every explanation. So please wait for some human moderator brings the posts back... maybe
Andy812
2 Intern
•
202 Posts
0
January 24th, 2021 22:00
Re: Adding RAID to Windows 10
1)Raid 0 is very unreliable and usually not intended for more than 2 physical drives. Particularly soft-raid from intel. Particularly when speaking of SSD's which are not so manageable as HDDs. For mitigating highly possible 100% loss of data, RAID5 was offered, which distributes XOR data around the drives for keeping the volume available and reparable when any of the drives had failed. Particularly recommended for use with spare drives attached.
RAID0 is not that good idea in the era of nvme ssd's, which almost removed the disk transfer bottleneck. At least in Windows, which has many other obstacles for booting the software and data i/o. Figuratively speaking, Windows OS was developed with slow disk subsystem in mind and its design just do not use benefits of fast disk subsystem well. That's my opinion based on running windows/win-software from RAM-drives on big workstations.
Please read carefully intel's Microsoft's, and SSD manufacturer's recommendations on RIAD strip size, because incorrect strip length can either kill your SSD, or seriously impact the volume performance (even below non-RAID numbers)
2) "if I do this the OS does not boot." That's the "feature" of Intel drivers in windows which is there for 15 years without change.
For booting Windows you need ONE, and only ONE river for the system drive preloaded. But when changing from AHCI to RAID, you switch the controller firmware, device id and the command set. So the AHCI driver fails.
You have 2 options:
A)Reinstall windows while providing so called "F6 floppy" driver, which is the same driver, but packed for windows install environment. In older windows series you had to press F6 when installing and insert the floppy disk, that's where it got its name.
B)Try injecting the driver configuration data into the registry after copying the driver to Windows/system32 folder. It is not an easy process and requires both, the configuration donor system and full understanding of device configuration model in the registry. Sometimes, you an find a walkthrough in Google, but you still have to figure out necessary device-ids, and windows GUIDs of whet you want to inject/substitute. That is done one time before reboot, and the next reboot the new RAID driver will boot the system. But you still have to reinstall it clean.
3)Non-raid drives are visible on Intel raid controller in bypass mode, except some features filtered out (in some versions TRIM was stopping working).
//WTHell, this forum just removes every post as a spam. Even when I am a registered and confirmed customer of Dell.
Clintlgm
3 Apprentice
•
1.5K Posts
0
January 25th, 2021 13:00
Andy, they are all back now. not sure what the OP has decided
Hale_JP
1 Rookie
•
14 Posts
0
January 25th, 2021 18:00
That is crazy. Now, all the posts that I tried to copy-paste with small differences in order to pass the bot, are all rolled out. And I can not delete the duplicates. Dell needs to work seriously with this forum.
Clintlgm
3 Apprentice
•
1.5K Posts
0
January 26th, 2021 08:00
Agreed there are issues with the forum at times weekend seem to be the worst