![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Horribly bizarre problem.
I'm running a bit older machine (Q6600 on a GIGABYTE GA-P35-DS3R) with a number of hard drives ranging from 640gb to 2tb. The two newest ones are 2tb and 1.5tb WD greens with the new block sizes. It seems that whenever my machine completely loses power both my BIOS and Windows7 lose the ability to read the last terrabyte of each drive. So they are recognized as 1tb and 0.5tb respectively.
It gets bizarre however. I have a rarely used ubuntu dual boot. Upon booting into linux the drives will be recognized as they're correct size and are full accessible (read/write) without any issues, NTFS partitions intact. Then if I reboot (without powering off) both the bios and windows7 will see the full size and behave normally. Any ideas where this problem might be stemming from? I'm thinking that I would like to repurpose this machine soon to be more of a server but I can't if I cannot track down this issue.
Thanks for the help.
I'm running a bit older machine (Q6600 on a GIGABYTE GA-P35-DS3R) with a number of hard drives ranging from 640gb to 2tb. The two newest ones are 2tb and 1.5tb WD greens with the new block sizes. It seems that whenever my machine completely loses power both my BIOS and Windows7 lose the ability to read the last terrabyte of each drive. So they are recognized as 1tb and 0.5tb respectively.
It gets bizarre however. I have a rarely used ubuntu dual boot. Upon booting into linux the drives will be recognized as they're correct size and are full accessible (read/write) without any issues, NTFS partitions intact. Then if I reboot (without powering off) both the bios and windows7 will see the full size and behave normally. Any ideas where this problem might be stemming from? I'm thinking that I would like to repurpose this machine soon to be more of a server but I can't if I cannot track down this issue.
Thanks for the help.