1343
Your logging is probably down (media.piefed.social)
submitted 7 months ago by to c/selfhosted@lemmy.world
173 comments fedilink hide all child comments
๐Ÿ˜† 4
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] 1 point 7 months ago (3 children)

are you sure it really bricked it? when turning it on, on next boot it needs to go over all the files and retag them or something like that, and it can take a significant amount of time

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [โ€“] 1 point 7 months ago (2 children)

    Honestly, I don't know what happened, but it was unreachable via SSH and the web console. There shouldn't have been a ton of files to tag since it was an Almalinux system that started with SELinux enabled, and all we added was a container app or two.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 2 points 7 months ago (1 child)

    that started with SELinux enabled

    that does not matter, it needs to go over all of them. I don't know how long it takes with SSD, but with HDD it can take a half an hour or more, with a mostly base system. and the kernel starts doing this very early, when not even systemd or other processes are running, so no ssh, but web console should have been working to see what its doing

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •