Thursday, October 7th, 2010 09:53 pm
I would like everyone to meet Watson
The server is built. It's name, by the way, is Watson.
Powered up to check connections and everything worked beautifully--and I say this knowing tomorrow when I get home it will all go to hell and blow up or something--but it powered up and asked for an OS and I almost cried, but
dreamatdrew says there is no crying in servers, and I believe this. I've been building this since five o'clock, I'm bleeding from several metal cuts I don't remember getting, but holy shit I just built my first computer. And apparently, I christened it in my own blood, which when you think about it is probably something I would have done deliberately anyway.
My OS is also loaded and installed on a jump drive and ready to go (Ubuntu Server, yeah, I know, why make this easy when I can do this learning a whole new operating system?), it has 2T of 3.5 drives and about 600 G of 2.5 drives, since I got a hot swap for the 5.3 by that holds four laptop drives. It has bluray, six SATA connections, and by the way, nothing came with goddamn screws so thank God I went through and did a huge screw organization drive earlier this year and had some (read: many). Then I had to go find more for the fan, which IDEK what is up with that. The board came with VGA and DVI, so I hooked it up to my TV to watch it open up for me, gorgeous, a huge black screen with blocky white writing that spelled out You totally fucking didn't blow anything up if you read between the lines. Which I did.
Did I mention nothing came with screws? Because it didn't. Okay, the power source did, but everything else, not so much. So many lies.
Anyway, I can't find a spare keyboard--Child is going to be in pain tomorrow, let me tell you--so installation of drivers and OS commence when I get home. I'll also write up the breakdown of the build for my own reference, because there's a few thing I want to remember.
Hardest parts:
1.) the goddamn fan installation.
2.) The realization that yes, they expect me to divine how to install the CPU in the board with pictures alone.
3.) restraining myself from reorganizing all the cables in the case. It looks terrible, but I don't think I can help the situation trying to make it neater, since I don't think that's possible.
4.) not setting things on fire.
Things to Do Tomorrow:
1.) Verify all connections are secure and working.
2.) Install OS and drivers (remember to change boot to USB)
3.) Not set things on fire.
4.) Learn Ubuntu Server. Oh God, I'm an idiot.
5.) Watch it, enchanted, as it boots up.
Things to Do This Weekend:
1.) Set up ethernet access.
2.) Configure for FTP.
3.) Configure network access to Adam the laptop for interface purposes, since it will more or less run headless.
4.) Watch it, enchanted, as it boots up.
5.) Start moving files.
6.) Pray.
Things to Add Someday Later:
1.) PCI RAID controller with SATA ports.
2.) Still not setting anything on fire.
3.) Another T of hard drive.
4.) Watch it, enchanted, as it boots up.
Things to Do This Year:
1.) Configure a RAID array.
2.) Keep learning Ubuntu Server.
3.) Don't set anything on fire.
4.) Everything else I don't know that I need to learn how to do.
5.) Watch it, enchanted, as it boots up.
Ladies and gentleman, Watson has entered the building.
ETA: Fixed spelling of
dreamatdrew as he will cut me off chat and that's terrifying.
Powered up to check connections and everything worked beautifully--and I say this knowing tomorrow when I get home it will all go to hell and blow up or something--but it powered up and asked for an OS and I almost cried, but
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
My OS is also loaded and installed on a jump drive and ready to go (Ubuntu Server, yeah, I know, why make this easy when I can do this learning a whole new operating system?), it has 2T of 3.5 drives and about 600 G of 2.5 drives, since I got a hot swap for the 5.3 by that holds four laptop drives. It has bluray, six SATA connections, and by the way, nothing came with goddamn screws so thank God I went through and did a huge screw organization drive earlier this year and had some (read: many). Then I had to go find more for the fan, which IDEK what is up with that. The board came with VGA and DVI, so I hooked it up to my TV to watch it open up for me, gorgeous, a huge black screen with blocky white writing that spelled out You totally fucking didn't blow anything up if you read between the lines. Which I did.
Did I mention nothing came with screws? Because it didn't. Okay, the power source did, but everything else, not so much. So many lies.
Anyway, I can't find a spare keyboard--Child is going to be in pain tomorrow, let me tell you--so installation of drivers and OS commence when I get home. I'll also write up the breakdown of the build for my own reference, because there's a few thing I want to remember.
Hardest parts:
1.) the goddamn fan installation.
2.) The realization that yes, they expect me to divine how to install the CPU in the board with pictures alone.
3.) restraining myself from reorganizing all the cables in the case. It looks terrible, but I don't think I can help the situation trying to make it neater, since I don't think that's possible.
4.) not setting things on fire.
Things to Do Tomorrow:
1.) Verify all connections are secure and working.
2.) Install OS and drivers (remember to change boot to USB)
3.) Not set things on fire.
4.) Learn Ubuntu Server. Oh God, I'm an idiot.
5.) Watch it, enchanted, as it boots up.
Things to Do This Weekend:
1.) Set up ethernet access.
2.) Configure for FTP.
3.) Configure network access to Adam the laptop for interface purposes, since it will more or less run headless.
4.) Watch it, enchanted, as it boots up.
5.) Start moving files.
6.) Pray.
Things to Add Someday Later:
1.) PCI RAID controller with SATA ports.
2.) Still not setting anything on fire.
3.) Another T of hard drive.
4.) Watch it, enchanted, as it boots up.
Things to Do This Year:
1.) Configure a RAID array.
2.) Keep learning Ubuntu Server.
3.) Don't set anything on fire.
4.) Everything else I don't know that I need to learn how to do.
5.) Watch it, enchanted, as it boots up.
Ladies and gentleman, Watson has entered the building.
ETA: Fixed spelling of
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
no subject
From:I am so fucking impressed especially because computer innards intimidate the shit outta me after I had to crack my box open and replace pretty much evertyhing. (nothing has caught on fire...yet, though sometimes I swear I can smell something burning. Friend says it's all in my head.)
(- reply to this
- link
)
no subject
From:*is impressed by uber awesome impressiveness*
(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:*Disowns you*
(- reply to this
- thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)
no subject
From:I've heard this is traditional.
(- reply to this
- thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)
no subject
From:(Hi, I've been lurking and uh, this is apparently what it finally takes to make me poke my head out.)
(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:If you didn't actually have this declaration in your post, I'd have no idea what you were talking about, only because my knowledge of computers is laughable, at best. My reaction to my computer not turning on is to glare balefully at it like it murdered my dog before making a sandwich or something.
However, there is nothing about this that doesn't sound hot. Go you!!!
::cheers::
(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:::shudder::
God, why do they DO that? Were the pictures at least decent?
(- reply to this
- thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)
no subject
From:Then again if you plan to run it mostly headless, getting over the hump of dealing with command line is probably good.
(- reply to this
- thread
- link
)
no subject
From:Yes. I read the documentation on-site first. If it's too difficult I can switch to something else later, but since I'm starting with clean drives and a new setup, it seemed like a good time to try.
I mean you could install X and the rest if you wanted, but that'd be kinda silly.
Not sure I follow. What would be silly?
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:Going through the trouble of installing X and something like GNOME, there are quite a few packages, and some tweaking (if I remember right, it's been a while since I tried to do that) to get GUI working on top of the Server install. It certainly can be done, but it would be much more straightforward to just install the desktop version if the CLI wasn't something you were interested in. It's a bit of a non-point since you're well aware of what you're getting into :)
Anyway, kudos and good luck!
(- reply to this
- parent
- top thread
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:(- reply to this
- link
)
no subject
From:http://en.wikipedia.org/wiki/Ubuntu_%28philosophy%29
I think I saw a translation of it as "I am who I am because of you."
School teaches you such crazy things.
(- reply to this
- link
)
no subject
From:My own relationship with computers could probably be best described as 'alt, ctrl delete' as the one true solution to all ills. Though I did spend the better part of one night with my previous laptop jury-rigging the power supply with electrical tape, a pen barrel and pure will. Good times. Good times.
(- reply to this
- link
)
no subject
From:And OMG it sounds like you have been busy. :D
-Bree
(- reply to this
- link
)
no subject
From:\o/
(- reply to this
- link
)
no subject
From:My ex-boyfriend tried to build a completely silent PC because the noise was keeping him awake at night. He bought a fancy cooling system to try, but first he decided to experiment... and removed the fan.
My tech-illiterate self thought: umm, I don't think that's going to work. But he had a degree in computer science so I just gave him the side-eye and kept my mouth shut (or he would've screamed at me, because he was just that charming)
Cue my utter lack of surprise when the new components he'd installed got utterly fried. But the thing that puzzled me most was that he was SHOCKED and ANGRY and blamed the manufacturer. Y'know, for the fact that since his PC had NO COOLING SYSTEM it got overheated.
/rambling
I love telling that story to people who build their own systems. The bug-eyes are epic.
(- reply to this
- link
)
no subject
From: (Anonymous) Date: 2010-10-09 05:06 am (UTC)--Jessica
(- reply to this
- link
)