Hardware

The test of new hardware is generally not necessary, the failure rate of today’s components is pretty low.

A burn in is already done on the manufacturer side and usually is not necessary either.

Storage devices

When using larger hard disks, the following error may occur. In this case, the block size used must be raised accordingly (-b 4096).

# badblocks -wsv /dev/sdc
badblocks: Value too large for defined data type invalid end block (9766436864): must be 32-bit value
# badblocks -b 4096 -wsv /dev/sdc

stressapptest

# apt-get install stressapptest
# stressapptest -s 30
Log: Commandline - stressapptest -s 30
Stats: SAT revision 1.0.6_autoconf, 64 bit binary
Log: buildd @ lgw01-amd64-022 on Thu Apr  5 10:28:35 UTC 2018 from open source release
Log: 1 nodes, 48 cpus.
Log: Defaulting to 48 copy threads
Log: Total 257895 MB. Free 254409 MB. Hugepages 0 MB. Targeting 244809 MB (94%)
Log: Prefer plain malloc memory allocation.
Log: Using memaligned allocation at 0x7f389f6ff000.
Stats: Starting SAT, 244809M, 30 seconds
Log: Region mask: 0x1
Log: Seconds remaining: 20
Log: Seconds remaining: 10
Stats: Found 0 hardware incidents
Stats: Completed: 1135370.00M in 30.03s 37813.12MB/s, with 0 hardware incidents, 0 errors
Stats: Memory Copy: 1135370.00M at 37825.20MB/s
Stats: File Copy: 0.00M at 0.00MB/s
Stats: Net Copy: 0.00M at 0.00MB/s
Stats: Data Check: 0.00M at 0.00MB/s
Stats: Invert Data: 0.00M at 0.00MB/s
Stats: Disk: 0.00M at 0.00MB/s

Status: PASS - please verify no corrected errors

fio

# apt-get install fio
ssd.fio
[global]
bs=4k
ioengine=libaio
iodepth=16
size=10g
direct=1
runtime=60
filename=/dev/nvme2n1
numjobs=4

[seq-read]
rw=read
stonewall

[rand-read]
rw=randread
stonewall

[seq-write]
rw=write
stonewall

[rand-write]
rw=randwrite
stonewall
nvme-rnd.fio
[global]
bs=4k
ioengine=libaio
iodepth=32
size=10g
direct=1
runtime=60
filename=/dev/nvme3n1
numjobs=4
sync=1

[rand-read]
rw=randread
stonewall

[rand-write]
rw=randwrite
stonewall
nvme-seq.fio
[global]
bs=128k
ioengine=libaio
iodepth=4
size=10g
direct=1
runtime=60
filename=/dev/nvme2n1
numjobs=4

[seq-read]
rw=read
stonewall

[seq-write]
rw=write
stonewall
# fio nvme-seq.fio
[...]
Run status group 0 (all jobs):
   READ: bw=3022MiB/s (3169MB/s), 756MiB/s-756MiB/s (792MB/s-792MB/s), io=40.0GiB (42.9GB), run=13551-13552msec

Run status group 1 (all jobs):
  WRITE: bw=2264MiB/s (2374MB/s), 566MiB/s-567MiB/s (594MB/s-595MB/s), io=40.0GiB (42.9GB), run=18057-18091msec

Disk stats (read/write):
  nvme2n1: ios=327721/327676, merge=0/0, ticks=210520/282496, in_queue=468716, util=98.90%

Note

Consult the datasheet of the hardware for the block size, IO queue depth, .. to be used.

Memory

Note

Using memtest86+ (available as a package in Ubuntu) is not possible when using UEFI.