More computer hardware fun. Tried to build up a server to host a bunch of lossless video i wanted to not get rid of.
Started off trying to build the server using Ubuntu. After i spent several hours formatting drives, they all came up weird... Brushing that off, I made up some samba shares and rebooted to see if my win7 network could make heads or tails of them. The system failed to boot. Something killed the boot manager. I shut the system down, disgusted after playing around with it for a few more hours and getting nowhere.
Next attempt was to just load up Fedora 16 on the system because I was more comfortable with it than Ubuntu. I decided to use an old disk from my main system to be the main OS drive on the thing. Pulled it from my main case and started installing. Turned back on my main system and found (after several hours of debugging) that this old HDD was the only drive that had the boot table on it, and that my SSD that was running windows was actually slaving off of this thing for the past year. One repair CD and several reboots later, the main system was all set and I had wasted another 5 hours going absolutely nowhere.
I finally get Fedora going on my main system to find out (again after several hours of debugging issues) that several SATA ports on my motherboard are part of a different controller that the BIOS doesn't control and that there's no Linux driver support for in any release I could find. To add insult to injury, the video card I had on the system caused it to tweek out and crash X every time i logged in. Another 5 hours down the drain.
Screw it, I said last night. I'm just going to pop a drive from the file server and put it into my main system where that old drive i took out to install fedora on was plugged in. 2TB of space is more than enough. But wait... what's this? Windows thinks it's only 1TB. I proceeded to spend all night trying to figure out what was wrong and learning about a bug with certain versions of Gigabyte motherboards that stemmed from a BIOS back-up feature wherein the board tries to write a Host protected area to hard drives attached to it so that it can recover BIOS info in case of emergency. The bug was in calculating the space left on the drive that's hard-written to the header. From the OS level, the HDD is whatever size this value says. The tools used to fix this issue in a windows environment are all 32 bit XP based (and since they deal with hardware access and drivers and shit, they don't even work in compatibility mode). I'm pretty sure I now have 5x 2TB drives that think they're 1TB drives.
Still haven't been able to move my files off my editing drive to make room for more source or start work yet.














