08-18-2012 12:45 AM
Ok, so I've tried pretty much everything.
Originally I was having a problem formatting drive in Windows. I went with MBR for simplicity and split the drive into 2 partitions. Problem is that when windows went to format drive in disk management, it would always come back with "Unable to complete" and then afterward the drive would disappear out of windows, and getting it back required shutting down (not restarting, shutting down and then pressing power button to start up again).
In Linux I was able to format the drive to full size (using GPT instead of MBR), so I thought maybe I was good and rebooted to windows, but the problem at that point was that when I was copying files to the partition, the transfer stopped a couple of minutes in and the drive disappeared just like before.
Then I tried updating BIOS since I read that BIOS may not support 3TB, and sure enough, looking at Gigabyte website 3TB support was added in the FG version, so I downloaded the FH update to get all the way up to date. (This is a X58A-UD3R)
I still had the same problem formatting in Windows as before.
Then I read that maybe turning on AHCI would work, so I enabled it for the part of the mainboard controller I'm currently using (SATA channel 7).
I guess I can try one more time to see if I can get SATA channel 0-3 as I think that's on an entirely different chipset but I'm doubtful this will make it successful.
I tried formatting using diskpart and received the error "The parameter is incorrect." whatever the heck that means.
The event log says things like
"The driver detected a controller error on \Device\Ide\IdePort9"
"The device, \Device\Harddisk2\DR2, is not ready for access yet." which I believe corresponds with the timing of the error.
Since this might be a controller error, I'm going to attempt to use the other ports so I'm on a different controller as a last ditch effort. I'll report back on success.
08-18-2012 01:40 AM
Ok, switching didn't work. Confirmed the drive works just fine in Linux even formatted to full size NTFS. Of course, this isn't entirely helpful because I want to use this drive for windows games/etc.
08-18-2012 09:22 AM
I just copied a ton of files in Linux to both an NTFS and ext4 partition on the drive, so obviously Linux doesn't mind the drive in the way Win7 does.
Why is windows so much more picky.. ugh..
08-18-2012 10:08 AM
Well.. now I'm finally having some linux problems with the drive..
An ext4 filesystem is now in read-only mode after doing some file transfers and dmesg has this over and over again.
[27664.070873] Buffer I/O error on device sda2, logical block 0
[27664.070875] lost page write due to I/O error on sda2
[27664.070883] EXT4-fs error (device sda2): ext4_find_entry:935: inode #11: comm dolphin: reading directory lblock 3
[27465.991587] sd 1:0:0:0: [sda] Unhandled error code
[27465.991590] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27465.991593] sd 1:0:0:0: [sda] CDB: Write(16): 8a 00 00 00 00 01 43 01 01 08 00 00 00 08 00 00
[27465.991604] end_request: I/O error, dev sda, sector 5419106568
Looks like this is a legitimate overheating/bad sector issue from looking around online so I will probably have to send this drive in for replacement.
08-19-2012 11:43 AM - edited 08-19-2012 11:44 AM
does your rig have a UEFI BIOS?
you need that to boot > 2TB