Just in case timp11 doesn't come back, and to be honest...I wouldn't blame him.
His laptop Seagate drive is the one that's throwing that error. It's also the one that has his OS installed on it. He says the cables are all brand new.
So I asked him how much data he had to lose, if he lost just that drive out of his system, and wiped it clean with one of his other drives. Apparently he doesn't have a problem with that.....
So he's removing the laptop drive, and he's going to run the two healthy Samsung drives (just checked) in RAID0 for a nice speed boost.
His laptop Seagate drive is the one that's throwing that error. It's also the one that has his OS installed on it. He says the cables are all brand new.
So I asked him how much data he had to lose, if he lost just that drive out of his system, and wiped it clean with one of his other drives. Apparently he doesn't have a problem with that.....
So he's removing the laptop drive, and he's going to run the two healthy Samsung drives (just checked) in RAID0 for a nice speed boost.












