You seem to be very new to these stress tools in UBCD. Well, I cannot give you advice on how to test your particular hardware (NAS is new to me), but, because I maintain the CPUstress test image, I can explain you how to use it.
First, know two things:
(1) There are several tools in CPUstress image, each with different purposes. Some tools put stress on CPU, some do on memory, and some do both. But none of them stresses hard drives or network, which are more important than CPU and memory for your NAS.
(2) The image assumes that you have basic knowledge on operating a Unix/Linux terminal. If you don't, reading the instruction on the screen when you boot up the image should help you get started quickly.
First, know two things:
(1) There are several tools in CPUstress image, each with different purposes. Some tools put stress on CPU, some do on memory, and some do both. But none of them stresses hard drives or network, which are more important than CPU and memory for your NAS.
(2) The image assumes that you have basic knowledge on operating a Unix/Linux terminal. If you don't, reading the instruction on the screen when you boot up the image should help you get started quickly.
- There are 6 virtual terminals available. You can switch between them by pressing Ctrl+Alt+{F1-F6}.
- You can monitor your CPU and memory load with the 'top' command. You probably want to run this on the 2nd terminal (Ctrl+Alt+F2).
- The 'sensors' command can show the temperature (and perhaps voltage) of your monitoring sensors. You may run the command repeatedly on the 3rd terminal (Ctrl+Alt+F3).
- The first terminal will be for your stress tool (either CPU Burn-in or mprime). These tools should halt if a hardware error occurs during the stress test. I cannot say they won't damage your hardware, but USE AT YOUR OWN RISK.
- Press 'q' or 'Ctrl+C' to terminate programs in CPUstress image.