Hello good folks. I started another thread, which was kinda solved, for detecting and testing, but I think the title and description I went with was somewhat erroneous. Basically what I was originally thinking wasn't expressed properly, so I'm trying again.
Here's my problem. I have 3 internal HDDs, technically 4.
C: drive is 2 HDDs that are 1 TB Seagate SATA III 6GB/s 7200 RPM in RAID0
E: drive is a 1 TB Seagate SATA III 6GB/s 7200 RPM HDD
F: drive is a 1 TB Seagate SATA III 6GB/s 7200 RPM HDD
All are plugged into Sata III ports on a GIGABYTE GA-870A-USB3 AM3+ 870 DDR3 US rev 3.1 mobo, my CPU is an AMD PHENOM II X6 1100T Black Edition running Win 7 Pro with 16 GB Kingston 1600 RAM and C: drive has some AMD strip thing for RAIDing (sorry, I'm not at all comp savvy. To put that into perspective, even though I've had comps since the Commodore 64 and 128 days, about 5-6 or so years ago I still tried to fix a comp tower with a five pound hammer. Sure it didn't fix anything, but I did feel a lot better afterward 😀 )
Now back to the problem, both C: and E: are recognized as SCSI Disc drives and have the name Seagate & model number up, while drive F: is referred to as simply an ATA device with no name just a model number.
E: and F: are identical drives, from the same factory, same production batch, same everything, and plugged into Sata III ports. I was informed that certain detection/scanning software won't work on RAIDed drives, even Seagate Tools can test C:, but won't give info like hours on and such for it, because it's RAIDed. That's fine, but everything detects and IDs E: drive while many things don't detect F: drive, such as CrystalDiscInfo, which only detects E: and my externals (C: is RAIDed so not registering that is understandable).
Moving along, both E: and F: tested healthy and fine, BUT from what I know, SCSI is run by the comp's controller while ATA uses the HDD's internal controller, plus SCSI has speeds up to 160, while ATA only goes up to 100. I know SCSI is faster, because transferring same files to E: goes faster than to F:.
How can I make my computer recognize drive F: as SCSI as opposed to ATA?
Here's my problem. I have 3 internal HDDs, technically 4.
C: drive is 2 HDDs that are 1 TB Seagate SATA III 6GB/s 7200 RPM in RAID0
E: drive is a 1 TB Seagate SATA III 6GB/s 7200 RPM HDD
F: drive is a 1 TB Seagate SATA III 6GB/s 7200 RPM HDD
All are plugged into Sata III ports on a GIGABYTE GA-870A-USB3 AM3+ 870 DDR3 US rev 3.1 mobo, my CPU is an AMD PHENOM II X6 1100T Black Edition running Win 7 Pro with 16 GB Kingston 1600 RAM and C: drive has some AMD strip thing for RAIDing (sorry, I'm not at all comp savvy. To put that into perspective, even though I've had comps since the Commodore 64 and 128 days, about 5-6 or so years ago I still tried to fix a comp tower with a five pound hammer. Sure it didn't fix anything, but I did feel a lot better afterward 😀 )
Now back to the problem, both C: and E: are recognized as SCSI Disc drives and have the name Seagate & model number up, while drive F: is referred to as simply an ATA device with no name just a model number.
E: and F: are identical drives, from the same factory, same production batch, same everything, and plugged into Sata III ports. I was informed that certain detection/scanning software won't work on RAIDed drives, even Seagate Tools can test C:, but won't give info like hours on and such for it, because it's RAIDed. That's fine, but everything detects and IDs E: drive while many things don't detect F: drive, such as CrystalDiscInfo, which only detects E: and my externals (C: is RAIDed so not registering that is understandable).
Moving along, both E: and F: tested healthy and fine, BUT from what I know, SCSI is run by the comp's controller while ATA uses the HDD's internal controller, plus SCSI has speeds up to 160, while ATA only goes up to 100. I know SCSI is faster, because transferring same files to E: goes faster than to F:.
How can I make my computer recognize drive F: as SCSI as opposed to ATA?
