Tag-Archief voor » laars «

Zondag, 4 augustus, 2013 | Auteur:

Ik had een stroomstoring invloed op mijn server het grote md RAID reeks. Eerder dan laat de server als geheel naar beneden tijdens het wachten voor het aan een te voltooien fsck, Ik had het op te starten zonder de grote serie, dus ik de fsck handmatig zou kunnen lopen.

Echter, als u handmatig het runnen van het besefte ik dat ik had geen manier om te weten hoe ver het was en hoe lang het zou duren. Dit is vooral problematisch met zo'n grote reeks. Met een beetje zoeken vond ik het puntje van het toevoegen van de C-parameter bij het aanroepen van fsck. Ik kan dit niet vinden in de documentatie echter: fsck –hulp toonden geen dergelijke optie.

De optie blijkt ext4-specifiek te zijn, en toont dus een perfect functioneel voortgangsbalk met een percentage indicator. Om de informatie te vinden, in plaats van “fsck –helpen” of “man fsck”, je moet invoeren “fsck.ext4 –helpen” of “man fsck.ext4”. 🙂

Dinsdag, February 17th, 2009 | Auteur:

Some of you may already know that I built a home server not too long ago. I documented some of the very important parts of how it was built though I was planning on releasing all the documentation all at once. I was using Arch Linux and I hadn’t nearly finished everything, especially the documentation. Bij voorbeeld, it was supposed to be a media server. After some disk shuffling, it was supposed to end up having a RAID1 for the boot and RAID 10 for the rest (the media part).

This didn’t work out at all.

I got as far as having an efficient (en goedfirewalled) routing gateway server. I was finally satisfied that the customised local routing* was working correctly and I was confident that my tests with DHCP meant I could disable the DHCP service on the flimsy ADSL router and have all my flatmates start using the server as the Internet poort. In plaats daarvan: I was logged in to the server from the office, I’d just installed Apache2**, and I was about to consult with a colleague regarding getting nice graphs put together so the flatmates could all see who was using up the bandwidth***when I noticed a little message indicating that the root filesystem had been remounted read-only due to some or other disk failure.

And then I lost my connection to the server.

And then I gained a foul mood.


When I arrived home, I found that, as I had guessed from the descriptive message given at the office, de (zeer) old 80GB IDE disk that I was using for the root filesystem had failed. Unfortunately, the server would never boot again and there was little chance of prying everything off onto another disk to continue where I’d left off.

I’m buying a replacement (SATA) HDD this next weekend just after pay dayand I’ve changed my mind about documenting my progressand backing up my configurations:

Release Early. Release Often.

* ISPs in South Africa charge less (easy price comparison) voor “local-only” (within South Africa) traffic on ADSL but only if you use an ADSL account that CANNOT access web services outside of South Africa. This means that if you want to take advantage of the reduced costs but still be able to access the Internet at large, you need to set up some sneaky routing.

** one-command-install: ~$ yaourt -S apache

*** Internet Access in SA is expensiveyou get charged about R70 ($7 / £4.9 / €5.46) per GB when using ADSL, or about R2 per MB if using GPRS / 3G.