From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v3 manager 1/2] report: overhaul `dmidecode` related output
Date: Fri, 19 Apr 2024 18:26:41 +0200 [thread overview]
Message-ID: <20240419162642.260130-1-a.zeidler@proxmox.com> (raw)
While using keywords (-t bios,...) would be possible, depending on the
server it also bloats the report with uninteresting information,
hiding the relevant. Therefore the non-grouped, specific number types
are used.
Where we only need specific information, not serial numbers
etc., we print the information from /sys/... which is the same source
that dmidecode uses per default.
New output includes:
# cat /sys/devices/virtual/dmi/id/sys_vendor
HP
# cat /sys/devices/virtual/dmi/id/product_name
ProLiant·DL380p·Gen8
# cat /sys/devices/virtual/dmi/id/product_version
Not·specified
# cat /sys/devices/virtual/dmi/id/board_vendor
ASUSTeK·COMPUTER·INC.
# cat /sys/devices/virtual/dmi/id/board_name
Z13PP-D32·Series
# cat /sys/devices/virtual/dmi/id/board_version
60SB09M0-SB0G11
`-t 0`:
(like the previous "BIOS" output, but without "BIOS Language" block)
`-t 3`:
Chassis Information
Manufacturer: HP
Type: Rack Mount Chassis
Boot-up State: Critical
Power Supply State: Critical
Thermal State: Safe
Number Of Power Cords: 2
(...)
and
`-t 32`:
System Boot Information
Status: Firmware-detected hardware failure
which can hint to Proxmox-independant issues, debug-able via IPMI.
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
v3:
* as discussed also off-list, switch to `cat` for board and product
output to avoid complexity
v2: https://lists.proxmox.com/pipermail/pve-devel/2024-April/063284.html
* reformat and extend board output
* add product output
* adapt dmidecode output
v1: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062350.html
PVE/Report.pm | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/PVE/Report.pm b/PVE/Report.pm
index 1ed91c8e..73f14744 100644
--- a/PVE/Report.pm
+++ b/PVE/Report.pm
@@ -110,7 +110,13 @@ my $init_report_cmds = sub {
hardware => {
order => 70,
cmds => [
- 'dmidecode -t bios',
+ 'cat /sys/devices/virtual/dmi/id/sys_vendor',
+ 'cat /sys/devices/virtual/dmi/id/product_name',
+ 'cat /sys/devices/virtual/dmi/id/product_version',
+ 'cat /sys/devices/virtual/dmi/id/board_vendor',
+ 'cat /sys/devices/virtual/dmi/id/board_name',
+ 'cat /sys/devices/virtual/dmi/id/board_version',
+ 'dmidecode -t 0,3,32',
'lspci -nnk',
],
},
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-04-19 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 16:26 Alexander Zeidler [this message]
2024-04-19 16:26 ` [pve-devel] [PATCH v3 manager 2/2] report: add recent boot timestamps which may show fencing/crash events Alexander Zeidler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240419162642.260130-1-a.zeidler@proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal