DE

↑ ↓ select, Enter open, Esc close

Show server manufacturer, model and serial number

harmless rootSystem and hardwaredebian, ubuntu
root@server
dmidecode -s system-manufacturer && dmidecode -s system-product-name && dmidecode -s system-serial-number

Prints manufacturer, model and serial number in three lines, as stored in the BIOS or UEFI. On self-built and rented servers this often shows only the mainboard or a placeholder like To Be Filled By O.E.M.; in that case dmidecode -s baseboard-product-name helps.

Note: On virtual servers, the hypervisor’s designation appears, for example KVM or Standard PC (Q35 + ICH9, 2009). If the command is missing: apt install dmidecode.

Also searched as

  • what server model is this
  • get server serial number linux
  • show mainboard model

Related one-liners

All in System and hardware

Show installed RAM modules and free slots

#dmidecode -t memory | grep -E '^\s+(Size|Type|Speed|Locator|Manufacturer|Part Number):'
harmlessSystem and hardware

Show BIOS or UEFI version and date

#dmidecode -s bios-vendor && dmidecode -s bios-version && dmidecode -s bios-release-date
harmlessSystem and hardware

Show CPU and hardware temperatures

$sensors
harmlessSystem and hardware

Show CPU model, cores and threads

$LC_ALL=C lscpu | grep -E '^\s*(Model name|CPU\(s\)|Thread\(s\) per core|Core\(s\) per socket|Socket\(s\)|Virtualization|Hypervisor vendor|L3)'
harmlessSystem and hardware

Show hardware errors and warnings in the kernel log

#dmesg -T --level=err,warn
harmlessSystem and hardware

Show network, RAID and storage controllers with driver

$lspci -k | grep -A3 -iE 'ethernet|raid|sata|sas|nvme|non-volatile'
harmlessSystem and hardware

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.