The reason that your other 3TB HDD remains unaffected by the bug is that BIOS will only touch the drive that is highest in the boot order. This confirms that BIOS (or some other application) has truncated the drive.
The reason that DLG can only see 2TB is because the drive is reporting a capacity of 2TB via the ATA Identify Device command. If that doesn’t work then I think the drive itself may be a bit of a dud, in which case I’ll have to RMA or return it. If neither of these works, the last thing I’m going to try is a PCI-e SATA controller card. I’ve downloaded DLG as well as HDT (I think that’s what it was called), and I’m trying the write zeroes method now. It also doesn’t seem to explain the fact that the other 3TB drive is working fine. I have seen a BIOS update on their site which addresses a hard drive size problem, though from the description it sounded like it affects 1TB drives rather than affecting the size by 1TB. To answer a previous question, I do happen to have a Gigabyte motherboard, the P35-DS3L (though I’m not sure which Rev at the moment). I’ve also tried de-initializing it with diskpart and then re-initializing as GPT. One thing I noticed doing that is that Windows reported the space a little differently, with GPT being about 1 MB less than MBR. I’ve tried going back and forth between MBR and GPT. Since one of the drives works fine, I also tried disconnecting that one and leaving the other hooked up. So far, I’ve tried switching the SATA channel it was on (from 4-5 to 0-1). Here’s an update of where things are at present: Any ideas as to what the cause of this might be and what I could do to fix it? I remember having the problem with the first one where, once Windows was installed on it, it showed a 745GB unallocated chunk which I couldn’t use, but for this 2nd drive it’s only showing the 1 single block. I tried making a partition, thinking it might then see the rest after doing that, but it didn’t change anything. Tonight I installed the 2nd 3TB drive only to discover that, even after initializing it as GPT in Disk Management, it appears to recognize it only as a 2TB (1862.91GB). After I did that, I was able to convert the 3TB from MBR to GPT and I was able to make 2 partitions to use up all the drive. Of course, at the time I didn’t know that I couldn’t boot off of this drive and use the full 3TB with my BIOS so I had to move the boot volume to a 500GB drive I still had installed. I ended up doing a fresh install of WIndows 7, so I decided to work with just 1 of the drives at first. I’ve installed one of them but I’m having an issue with the second. I recently purchased 2 WD30EZRX 3TB drives.
0 kommentar(er)
