📜 ⬆️ ⬇️

Home router, media server and lab in one HP Microserver (part 1)

They gave me the HP N36L Microserver at work for my birthday for incomprehensible merit, which puzzled me greatly with the question of its best use. So I have long dreamed of replacing the old HP DC4200 with something more compact and, most importantly, with a lot of space for hard drives. But I was looking more at the tower corps, in which one could shove a couple of baskets onto five 3.5 ”HDDs. And then there is such a chance.

Prosherstil internets, honored smart and not very people, and, as usual among real Komsomol members, decided to go their own way.


It was decided to bring the server to mind by installing additional hardware and putting XenSever on it. And already in Xen to wrap everything your heart desires.
')
The relative puniness of the processor in the microserver did not scare me - I do not need to compile on it. I'm not even a Komsomol member to master Ghent. But to put on it a router, a VPN server, an emergency Windows with terminal access, a web server, a torrent daemon and a couple of other virtual loops in the lab - it will be just right. Let's start.

Item 1. Iron


Network

Since the default server is equipped with only one network interface, I went to the store and foolishly bought the simplest LAN card for the PCI-E bus from an unknown TP-Link brand for 500 rubles. The only thing that I made sure before buying is that the card is sold for at least six months, the chip on it is Realtek, which means the latest version of Xen should recognize it. Because Since the card will look on the Internet, I didn’t care about its gigabit at all, as well as the fact that it loads the CPU to transmit traffic. Hope was not in vain, Xen picked up the card without question.

RAID

I honestly missed almost a day - trying to collect a raid in this box. He carried the brain to the Hindus, ours and the Americans. The Americans also tried to throw me off on the Indians, but they already know me and brought me back. The collegial decision was - with the mother something is not right and you need to take the server to the service. However, while RAID was not installed, I read a lot and found out that neither XenServer nor VMWare can see this fake raid without serious intervention in the system, so it’s best not to bother. Therefore, I threw this stupid lesson and just collected an LVM array of five screws. The fact that I for some reason cannot get into the raid configuration on the boot does not prevent other systems from working well.

A couple of days later, it turned out that with the “launch raid config” button, this same network card from TP-Link, which I tore at trial after a night dawned, fought. At the same time, it turned out that it was precisely because of her that Xen caught a wedge randomly a couple of times a day. And before that, I wrote off the exclusion of xenon on crooked crutches with which I tried to supply it for my needs. So keep in mind - this cheap writer can ruff your nerves.

Final config for screws:
1. USB 2.5 ”Toshiba 80Gb - attached to the internal port and lying inside the case. Xen lives on it. Very useful 10cm USB => Mini-USB cord with dealextreme.
2. Hitachi 1Tb - it will be a service-critical virtuals and dump torrents
3. 4 * 500Gb Hitachi - this is under guest OSes, again, torrents and stuff.
4. External 500Gb Seagate on USB-port - there will be a backup from desktops and laptops that is extremely expensive to me like memory, as well as service-critical virtual machines.

Let me explain why I chose LVM, and not the trendy ZFS, RAID-Z or something like that. Everything is simple, in fact - I do not like to spend time waiting. On Xen, I launched smartctl and configured ssmtp. If suddenly a screw gets to degraded status, I will get a letter, go to the store on my way home, buy a new screw, come home, attach a new screw with one team, copy the data from the dying screw to the third one, and unhook it it from the array, and then I will make a parrot a mirror, and I will get magnets for myself.
Rebuilding the same raid with a processor, hardly more powerful than my phone, can take too much time.

In addition, XenServer, which I love with all my heart for unpretentiousness, does not support these fashionable whistles, and I am afraid to prop it with crutches. Still, it will hold the heart of the entire home network.

Memory

By default, the server is equipped with a gig of RAM. It was decided to increase his memory. However, the price tag on the 4Gb-bar almost bit off my arm to the elbow. Therefore, it was decided to stick 2 * 2Gb. Laba, of course, turns out to be much more modest, but I am not going to sell a kidney for it yet.

Cooling

Because the majority of those living within the borders of the Russian Federation still have a fresh hellish summer of 2010 in the memory, it was decided to insure in advance with the cooling of this very tightly packed box.

From the old vaults, a 14cm cooler was extracted from some fashionable radiator and a small modding of the front door of the server was produced. According to the modding results, the cooler was powered via a “tee” from the connector on the board, in parallel with the rear cable, but without the control wire, so that the system would not go crazy, but through the manual speed controller. On the front side of the cooler there are two grids, between which a piece of fine-meshed window grid, folded in three, is clamped. Like a dust filter. When I find the material better - I will replace it in two minutes.

At maximum speed the net starts to “whistle”, but the noise becomes only slightly larger. But now everything is blown perfectly.

On this questions on the iron part ended.

Description of a set of virtualok with explanations and even pictures will be in the second part .

Source: https://habr.com/ru/post/119256/


All Articles