TwinTurboJosh
Weaksauce
- Joined
- Mar 15, 2005
- Messages
- 69
So I just built a new Core i7 rig, and last night I put in one of my Seagate HDDs that I had been using for pure storage in another PC. As I was installing the HDD I noticed that I still had the jumper in that limits the transfer speed to 1.5Gb/s, and not 3.0Gb/s. So for the heck of it I removed the jumper since surely all of the SATA ports on my Gigabyte X58 mobo support SATA II.
But now, I am sometimes I am unable to write data to the HDD. And by 'sometimes' I mean that if I find myself unable to write to the drive, if I reboot the PC I will most likely be able to write data to it again until the next reboot. If the jumper was the culprit, I would assume that the drive would be protected at all times.
The only other things that have stood out about getting this HDD up and running are that when I was in Disk Management trying to change the drive letter for this drive, that option was grayed out. I had to close Disk Management, and then go back in and only then was the option available to me. Also, I just checked Device Manager and this drive is showing as a 'SCSI Disk Device' even though it is SATA.
Any thoughts on things to check? I didn't see anything in the BIOS. Thanks.
But now, I am sometimes I am unable to write data to the HDD. And by 'sometimes' I mean that if I find myself unable to write to the drive, if I reboot the PC I will most likely be able to write data to it again until the next reboot. If the jumper was the culprit, I would assume that the drive would be protected at all times.
The only other things that have stood out about getting this HDD up and running are that when I was in Disk Management trying to change the drive letter for this drive, that option was grayed out. I had to close Disk Management, and then go back in and only then was the option available to me. Also, I just checked Device Manager and this drive is showing as a 'SCSI Disk Device' even though it is SATA.
Any thoughts on things to check? I didn't see anything in the BIOS. Thanks.