Linux監控查看系統cpu溫度,風扇轉數,電壓...等

安裝套件 指令 yum install lm_sensors 按enter Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package lm_sensors.i686 0:3.3.1-1.fc15 will be installed --> Finished Dependency Resolution Dependencies Resolved ============================= Package Arch Version Repository Size ============================= Installing: lm_sensors i686 3.3.1-1.fc15 updates 129 k Transaction Summary ============================= Install 1 Package(s) Total download size: 129 k Installed size: 387 k Is this ok [y/N]: y Downloading Packages: Setting up and reading Presto delta metadata Processing delta metadata Package(s) data still to download: 129 k lm_sensors-3.3.1-1.fc15.i686.rpm | 129 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : lm_sensors-3.3.1-1.fc15.i686 1/1 Installed: lm_sensors.i686 0:3.3.1-1.fc15 Complete! 進行第一次偵測設置 指令 sensors-detect 按enter 讓程式全部自動偵測,都回應YES # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200) # Board: Gigabyte Technology Co., Ltd. xxxxxxx-xx This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SISxxxx... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE xxxxxx Super IO Sensors' Success! (address 0x290, driver `it87') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8705F Super IO Sensors' Success! (address 0x290, driver `it87') Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): YES Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Using driver `i2c-viapro' for device 0000:00:11.0: VIA Technologies VT8237 South Bridge Module i2c-dev loaded successfully. Next adapter: SMBus Via Pro adapter at 5000 (i2c-0) Do you want to scan it? (yes/NO/selectively): YES Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `it87': * ISA bus, address 0x290 Chip `ITE IT8705F Super IO Sensors' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES ln -s '/lib/systemd/system/lm_sensors.service' '/etc/systemd/system/multi-user.target.wants/lm_sensors.service' Unloading i2c-dev... OK 完成偵測 往後就可以輸入指令sensors查詢 指令 sensors 按enter 執行結果如下 it87-isa-0290 Adapter: ISA adapter in0: +1.60 V (min = +0.00 V, max = +4.08 V) in1: +2.67 V (min = +0.00 V, max = +4.08 V) in2: +3.14 V (min = +0.00 V, max = +4.08 V) in3: +2.40 V (min = +0.00 V, max = +4.08 V) in4: +3.07 V (min = +0.00 V, max = +4.08 V) in5: +1.55 V (min = +0.00 V, max = +4.08 V) in6: +1.10 V (min = +0.00 V, max = +4.08 V) in7: +1.41 V (min = +0.00 V, max = +4.08 V) Vbat: +0.00 V fan1: 4560 RPM (min = 0 RPM, div = 8) fan2: 0 RPM (min = 0 RPM, div = 8) temp1: +30.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +23.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +46.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode

---

補充:LINUX 查詢 硬碟參數狀態序號,讀取速度和溫度(限HITACHI)

硬碟溫度 指令hdparm -H /dev/sda (限HITACHI)
執行結果
/dev/sda:
drive temperature (celsius) is: 29
drive temperature in range: yes

---

讀取速度 指令:hdparm -Tt /dev/sda
執行結果
/dev/sda:
Timing cached reads: 4932 MB in 2.00 seconds = 1966.06 MB/sec
Timing buffered disk reads: 488 MB in 3.01 seconds = 195.58 MB/sec

---

硬碟參數 指令:hdparm -I /dev/sda
執行結果
/dev/sda:

ATA device, with non-removable media
Model Number: HITACHI HTS725032A9X064
Serial Number: 101033CCKC04BPGZU91K
Firmware Revision: PC3ZC70F
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6; Revision: ATA8-AST T13 Project D1697 Revision 0b
Standards:
Used: unknown (minor revision code 0x0028)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 625142448
Logical Sector size: 512 bytes
Physical Sector size: 512 bytes
device size with M = 1024*1024: 305245 MBytes
device size with M = 1000*1000: 320072 MBytes (320 GB)
cache/buffer size = 15151 KBytes (type=DualPortCache)
Form Factor: 2.5 inch
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = ?
Advanced power management level: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* Idle-Unload when NCQ is active
* NCQ priority information
* DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
88min for SECURITY ERASE UNIT. 88min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000cca649ae0213
NAA : 5
IEEE OUI : 000cca
Unique ID : 645ca6213
Checksum: correct

Release