Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Do 25.07.2024 00:00:10 61.957 +1 3.577.506 57,7 Fosstodon 4.2.10 500 Mi 24.07.2024 00:01:07 61.956 0 3.574.077 57,7 Fosstodon 4.2.10 500 Di 23.07.2024 00:00:03 61.956 -3 3.570.705 57,6 Fosstodon 4.2.10 500 Mo 22.07.2024 00:01:10 61.959 +1 3.567.825 57,6 Fosstodon 4.2.10 500 So 21.07.2024 00:01:07 61.958 +1 3.564.861 57,5 Fosstodon 4.2.10 500 Sa 20.07.2024 00:01:10 61.957 +1 3.561.604 57,5 Fosstodon 4.2.10 500 Fr 19.07.2024 13:57:34 61.956 -1 3.558.474 57,4 Fosstodon 4.2.10 500 Do 18.07.2024 00:00:27 61.957 +1 3.553.476 57,4 Fosstodon 4.2.10 500 Mi 17.07.2024 00:01:10 61.956 -1 3.550.157 57,3 Fosstodon 4.2.10 500 Di 16.07.2024 00:00:36 61.957 0 3.547.999 57,3 Fosstodon 4.2.10 500
(@j_angliss) · 10/2022 · Tröts: 933 · Folger: 99
Do 25.07.2024 20:08
I've been getting some weird issues on one of my lab machines at home. Docker would literally take 15 minutes to start. Turns out containerd would keep being nuked with a SIGBUS, and core-dumped.
Every time it'd try to restart containerd, there'd be disk IO errors for a very specific sector on the disk, and had auto reallocate failures as well.
smartctl says disk is fine, no read/write errors, no reallocations, nada.
A completely different disk in same box _is_ throwing smartctl errors.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0