-
pjusticeHad a panic this morning.
-
pjustice2024-11-18T15:40:32.932053+00:00 copacabana savecore: [ID 570001 auth.error] reboot after panic: I/O to pool 'zones' appears to be hung.
-
pjustice2024-11-18T15:40:32+00:00 copacabana savecore: [ID 315959 auth.warning] incomplete dump on dump device
-
pjusticesavecore doesn't like the resulting dump file:
-
pjusticehmm, lost that bit, something about tag 1082 and invalid magic number
-
pjusticemdb doesn't like the extracted vmcore
-
pjusticeMETRICS says the dump was written ~crash time, 15:18 UTC today
-
pjusticecompressed file is ~10 GB.
-
pjusticecopacabana 9 $ mdb unix.0 vmcore.0
-
pjusticemdb: vmcore.0 is not a kernel core file (bad magic number 0)
-
pjusticemdb: failed to initialize target: No such file or directory
-
pjusticeplatform joyent_20241017T041739Z
-
pjusticesata ports from C620 chipset
-
bahamatpjustice: You should first look into hardware failure. The "pool appears to be hung" error is almost always hardware related.
-
bahamatIf savecore is still running it may still be extracting the dump, but with a hung pool I wouldn't expect there to be a full dump anyway.
-
pjusticeIt's interesting that it managed to write _some_ with a hung pool.
-
pjusticeOr else something else initiated the panic, and the hung pool during dump save concealed the tracks of that.
-
pjusticeSince the pool doesn't claim to have any problems and was recently scrubbed, I'm guessing a controller or sata backplane/expander issue.
-
pjusticeNothing useful in the SEL log.
-
bahamatWell the kernel message explicitly says that it detected the pool as hung.