Der gordische Knoten ist durchschlagen

Auf einmal ging alles ganz schnell. ist live! Irgendjemand hat wohl den ganzen Prozess knallhart abgekürzt. Ich sage bei Hotlines gerne: “Geben Sie mir mal einen Kotzbrocken!” Warum? Weil der unmöglich im Umgang ist, aber immer noch beschäftigt ist. Weil er richtig Ahnung hat. 🙂


Anruf einer Dame von IONOS. Sie habe sich das jetzt mal angeschaut, auch wenn sie gerade in einem Termin sei. Ich habe zu viele Mailweiterleitungen und deshalb ginge das nicht. (Mein Fehler also). Sie habe das jetzt noch mal angestoßen und wir sollen bis morgen warten, ob ich nicht vielleicht doch eine Mail bekomme. “Wie schnell wird denn so eine Mail zugestellt?” In ein oder zwei Minuten. Fein, die zwei Minuten sind doch dann schon rum. Sie wirft dazwischen, dass sie sich darum nicht kümmern kann, aber vielleicht die Frau Schmidt, weil sie ja jetzt wegmüsse.

Ich warte dann weiter auf Godot. Alle haben schrecklich viel Zeit. Ich habe mittlerweile für diesen Zweck genau ein neues Postfach angelegt, ohne alle Weiterleitungen. Das zählt dann als Ausflucht nicht mehr.


This is taking longer than expected

I fired off the domain transfer about 26 hours ago and it was approved half an hour later. I expected to wake up today with the move completed, but nothing happened. I do not have an ETA for this move to complete.

Moving to WordPress

Since I needed to move off of my old server, I took this opportunity to start all over with WordPress, replacing my almost 20 years old MovableType site. This change was long overdue.

I am not migrating MT posts into WP. But nothing will be lost. All existing content is made available directly from storage. Cool URLs don’t change.

Just one caveat: The search field on the front page will only reveal new content. For old content, you have to enter the archive and search there. Or you Google with “-site”

The domain is already being migrated to the new host. is being rebuilt

Harddisc Seagate Barracuda 1500GB

While is offline, a bit about what is going on. The site used to run in shared hosting at 1&1. When that broke, Stefan let me host on his server. The site got faster, much faster actually, and he added SSL via LetsEnrcypt.

Once in a while the site crashes. When that happens, Stefan has to restart it. If it happens at night or while he is working, it may take a few hours, but then it’s coming back. I like to phrase it as “ is taking a bath and will come back squeaky clean”.

Well, not this time.

The server hardware is failing. More precisely, the storage is failing. It’s a simple RAID 1 setup. Two drives, one holds a copy of the other. When a drive fails, which does happen more often than you think, you just replace it, the data gets synced back and everything is back in good shape.

Well, not this time.

While the RAID was rebuilding, the other drive failed as well. Again, this is more common than you might think, especially if you have Seagate Barracuda drives. (Hint: not recommended). Rebuilding puts a lot of stress on the old drive, and this time around it failed. If you followed along, that means catastrophic failure. Everything is lost.

Not, if you are Stefan.

Stefan has been doing server farms for more than a decade, on a very large scale. When a RAID drive fails, you don’t replace it. You take it offline so that nothing writes to it. Then you make a fresh backup. Only then do you start replacing the failed drive and rebuilding the RAID.

That’s where we are. Both redundant drives failed. Both have been replaced. The RAID is being synced. Next steps: reinstall and restore. That sounds easier than it is, if you are already living a 25 hour day.