From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager 8/9] report: add info about (un)used memory slots
Date: Fri, 22 Mar 2024 19:05:09 +0100 [thread overview]
Message-ID: <315511a06b1178a20bfde4c4cbd34a1a111be679.camel@proxmox.com> (raw)
In-Reply-To: <20240322135933.164404-8-a.zeidler@proxmox.com>
On Fri, 2024-03-22 at 14:59 +0100, Alexander Zeidler wrote:
> * to see if a RAM upgrade is slot/capacity-wise possible
> * to spot added/replaced RAM that may now be causing issues
>
> # dmidecode -t memory ...
> Maximum Capacity: 2 TB
> Number Of Devices: 8
> Size: 16 GB Micron Technology 18ASF2G72PZ-2G6D1
> Size: 16 GB Micron Technology 18ASF2G72PZ-2G6D1
> Size: 16 GB Micron Technology 18ASF2G72PZ-2G6D1
> Size: 16 GB Micron Technology 18ASF2G72PZ-2G6D1
> Size: No Module Installed
> Size: No Module Installed
> Size: No Module Installed
> Size: No Module Installed
>
> + 'dmidecode -t memory | grep -E "Capacity|Devices|Size|Manu|Part" | sed -Ez "s/\n\t(M|P)[^:]*: (\S*)/\t\2/g" | sort',
Thank you Mira for pointed out, that the regex is not strict enough on your
system. Originally, I limited the strictness as a trade-off to the command
length. However, by slightly modifying the output, the command line can be
shortened and a higher level of strictness can be achieved:
dmidecode -t16,17 | grep -P "^\t(Max[^:]*city|Size|Part)" | sed -Ez "s/\n(\tP[^\n]*)/\1/g" | sort
Maximum Capacity: 2 TB
Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
Size: No Module Installed
Size: No Module Installed
Size: No Module Installed
Size: No Module Installed
next prev parent reply other threads:[~2024-03-22 18:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 13:59 [pve-devel] [PATCH manager 1/9] report: add kernel command line including boot time Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 2/9] report: add `jobs.cfg` to debug related network/load/backup/etc issues Alexander Zeidler
2024-03-25 8:08 ` Thomas Lamprecht
2024-04-11 17:07 ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 3/9] report: add list of upgradable packages Alexander Zeidler
2024-03-25 8:02 ` Thomas Lamprecht
2024-04-11 17:08 ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 4/9] report: add `apt-cache policy` to list recognized APT sources Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 5/9] report: move `lscpu` & cluster info to more appropriate sections Alexander Zeidler
2024-03-25 8:11 ` Thomas Lamprecht
2024-04-11 17:12 ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 6/9] report: switch `dmidecode` to quiet to omit almost never needed info Alexander Zeidler
2024-03-25 8:20 ` Thomas Lamprecht
2024-04-11 17:13 ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 7/9] report: add info of the mainboard in use Alexander Zeidler
2024-03-22 14:26 ` Aaron Lauterer
2024-04-11 17:14 ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 8/9] report: add info about (un)used memory slots Alexander Zeidler
2024-03-22 18:05 ` Alexander Zeidler [this message]
2024-03-22 13:59 ` [pve-devel] [PATCH manager 9/9] report: add microcode info to better assess possible system impacts Alexander Zeidler
2024-03-22 16:44 ` Stoiko Ivanov
2024-03-22 18:54 ` Alexander Zeidler
2024-03-25 9:00 ` Thomas Lamprecht
2024-04-11 17:15 ` Alexander Zeidler
2024-03-25 7:52 ` [pve-devel] [PATCH manager 1/9] report: add kernel command line including boot time Thomas Lamprecht
2024-04-11 17:07 ` Alexander Zeidler
2024-04-11 17:20 ` Thomas Lamprecht
2024-04-18 15:57 ` 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=315511a06b1178a20bfde4c4cbd34a1a111be679.camel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox