systemd cat and GNU cat hugging a Linux cat.

Systemd cat and GNU cat hugging a Linux cat.
you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago (4 children)

It's either Slackware (Linux, no systemd), OpenBSD or NetBSD.

True story: I install a Red Hat server with a disk shelf with about 12 SAS disk in it. Red Hat has systemd. Everything works fine for a month.

One (1) disk out of the 12 fails. No biggie. Shutdown the server cleanly. Replace disk. Flip power back on. Rebuild disk config. Simple, right?

Wrong. You see, systemd is unhappy. It detects a new disk. It has lost a previous disk. And so, it refuses to boot. Period.

Yes, there are ways out of this. But that was the day I decided systemd was the down of the devil.

  • source
  • hideshow 4 child comments
  • [–] 9 points 1 year ago (2 children)

    This has never happened to me on a systemd server before. Methinks you left out some details

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago (1 child)

    Probably systemd panicked because disk id has changed. Not a reason to stop booting but that is why people hate it. Tries to handle everything, badly.

  • source
  • parent
  • hideshow 1 child comment