Summary: | sys-apps/smartmontools-7.3 fails to read nvme error log: Read 16 entries from Error Information Log failed: NVMe Status 0x13 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Miroslav Šulc <fordfrog> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | kernel |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/smartmontools/smartmontools/issues/193 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Miroslav Šulc
2023-05-15 05:37:45 UTC
i just tried to reboot to 6.1.28 and the issue persists. i also tried to reboot back to 6.1.19 and the issue is still there so it might not be kernel related. i also tried smartmontools-9999 but the issue is the same. i even created an ebuild for smartmontools-7.2, but even there the issue persists. it still seems weird to me that all three disks would fail to provide the data at the exactly same time. also, reading the error log using `nvme error-log /dev/nvme0n1` works just fine. smartctl links against glibc and gcc. gcc was last updated in january before this issue occurred, so it is probably unrelated, glibc was last updated on may 12. the issue appeared on may 14 after the reboot. Would you mind reporting this upstream? I don't have any guesses yet :( tbh idk what is the source of the issue. it started just after reboot, it did not appear before, but rebooting back to the original kernel did not evade the issue. upgrading/downgrading smartmontools had no effect either. (imo) the only thing i didn't try yet is downgrading glibc back to 2.36-r7. i just wonder why zabbix did not start to report this issue after glibc upgrade, but only after reboot. i'll try the glibc downgrade now. i just downgraded glibc to 2.36-r7, rebooted the server, and the issue persists... reported to smartmontools |