October 05, 2009
Looks like the server comes up with a default IP of 169.254.244.117. That's part of one of the IANA "black hole" groups, similar to 10.*.*.* and 192.168.*.*. I use that latter on my LAN, and between that and the subnet mask, looks like I can't reach the server.
Man, it takes a long time after you boot in this mode before the server firmware finally gets around to turning on the ethernet interface!
It was nice of Acer to announce the IP it was trying (and failing) to reach in its error popup before the recovery program gives up and ends. That's how I know that the server has decided to be 169.254.244.117.
The quick answer is for me to temporarily switch the IP on the computer (it's the one I usually use for torrents) to a number in that same group, and that's what I'm about to try.
UPDATE: OK, once I did that they were able to contact each other just fine. Once it's all set up, assuming nothing bad happens, I'll have to use Arcturus (the torrent computer) to change the IP of the server (it's gonna be called Deneb) to 192.168.1.10 so that I can access it. And then Arcturus can be returned to its normal 192.168.1.160.
It's not impossible that there was nothing wrong with it except that its IP was out of the subnet I'm using (192.168.1.*) but it's too late to do anything about that now. The process has already begun and I saw a fast message that said it had redone the partition tables.
I've got both drives in, and it'll be interesting to see what it does with them. E.g. will it even touch the second one? Will it set it up as a separate nominal space? Will it automatically set up RAID 1?
I'm a little surprised that this is using TCP/IP. Given that it's a Windows client and a Windows server, I really did expect that Microsoft would use its own protocol over the network.
The recovery program is showing an advancing progress bar, and the ethernet lights are flickering occasionally. No sign of an HD activity light on the server though; maybe the boot firmware isn't set up to do that in this mode. (I hope. Because otherwise it means it still can't get to the HD's, and I'm screwed.)
UPDATE: Aha! I've seen the HD light blink a few times!
UPDATE: Just for future reference, this process started at 1630. It's now 1700 and the progress bar looks like it's about 15%.
UPDATE: 1720 and it's about a third done.
UPDATE: 1725 and now it's finished loading. The server is rebooting and I'll try the control software on Arcturus when it's through. I have no idea how long it'll take for the server to stop chuckling to itself.
UPDATE: 1730 and the reboot is complete. The "i" light is back to being purple and all four drive bays show purple again. I'm beginning to think that what this means is "the server isn't set up yet".
UPDATE: And it was just the same as before. So just for the hell of it, I tried setting the IP subnet mask on Arcturus to 255.255.0.0. And now it's managed to make contact with ASPIREHOME, and setup is beginning.
Progress being made here.
I have a feeling it is picking a random IP in the 169.254.*.* range, and after it rebooted the new one wasn't in the 169.254.244.* range, which is what Arcturus currently is in. Making the subnet 255.255.0.0 made it so Arcturus could see it anywhere in the 16-bit section.
UPDATE: Awesome! The drive lights are right now! The bottom two bays are blue, and the top two are black. The "i" indicator is red, which means I'm setting up.
UPDATE: Yup! Now it's 169.254.250.101. Gotta change that!
UPDATE: More progress: the server is now named DENEB (rather than the default ASPIREHOME) and it's using IP 192.168.1.10 like I need it to.
The workgroup name is the default WORKGROUP rather than SCDBPRIVATE, which is what I've always used, so I gotta fix that.
Both drives are formatted and available. I have to figure out how to make them RAID 1.
CURSE CURSE CURSE. The Console program installs a version of McAfee Antivirus on the PC, and there's also a version of it on the server. The version on the PC is already nagging me every few minutes to register and update.
UPDATE: I can't figure out how to change the workgroup on the server, so I may need to change it on my computers instead. Pain in the ass, that is.
I'm running Windows Update on the server now. It's got 61 patches to load -- but this is a good thing. It means it's able to operate through Regulus (the Linux Server) and reach the internet.
I think I'm not going to put the console software on my main computer because I don't want McAfee bitching at me all the time.
UPDATE: Oh, even more wonderful: as long as I refuse to register McAfee AntiVirus, the "i" LED on the console is going to glow red. DIE, MCAFEE! DIE DIE DIE!
UPDATE: I changed the workgroup on Procyon to "WORKGROUP", and...

...now I can access the new server from it. I'll do the same for Arcturus in a while, after the server finishes doing its updates.
UPDATE: Why is the keyboard-less screen-less server trying to install IE8? (I know the answer: because it's generic Windows Server 2003 and you can run that with a keyboard and monitor if the hardware support them.)
Posted by: Steven Den Beste in Computers at
03:37 PM
| No Comments
| Add Comment
Post contains 940 words, total size 5 kb.
Enclose all spoilers in spoiler tags:
[spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)
At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.
How to put links in your comment
Comments are disabled. Post is locked.18 queries taking 0.0118 seconds, 16 records returned.
Powered by Minx 1.1.6c-pink.