Custom Query (1556 matches)
Results (346 - 348 of 1556)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1628 | invalid | Add to drivedb: MSI SPATIUM M470 | ||
| Description |
This is a NVMe (PCIe) SSD. I'm aware that NVMe drives are not in the database right now, but I wanted to open this ticket submit the smartctl output so you have it when NVMe drives are added to the drivedb. Link to drive page smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-121-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: MSI M470 1TB Firmware Version: EGFM13.2 PCI Vendor/Subsystem ID: 0x1987 IEEE OUI Identifier: 0x6479a7 Total NVM Capacity: 1,000,204,886,016 [1.00 TB] Unallocated NVM Capacity: 0 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 6479a7 5ba0c002d8 Local Time is: Thu Jun 30 13:44:37 2022 PDT Firmware Updates (0x12): 1 Slot, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005d): Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 90 Celsius Critical Comp. Temp. Threshold: 95 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 9.78W - - 0 0 0 0 0 0 1 + 6.75W - - 1 1 1 1 0 0 2 + 5.23W - - 2 2 2 2 0 0 3 - 0.0490W - - 3 3 3 3 2000 2000 4 - 0.0018W - - 4 4 4 4 25000 25000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 - 4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 31 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 0% Data Units Read: 155,662 [79.6 GB] Data Units Written: 353,361 [180 GB] Host Read Commands: 1,295,874 Host Write Commands: 661,272 Controller Busy Time: 3 Power Cycles: 1 Power On Hours: 63 Unsafe Shutdowns: 1 Media and Data Integrity Errors: 0 Error Information Log Entries: 2 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Error Information (NVMe Log 0x01, max 63 entries) No Errors Logged |
|||
| #47 | fixed | strange disk count when dealing with external cciss arrays | ||
| Description |
I have 2 MSA arrays off of my system, each with 28 disks. I also have the internal smart array on my system, with a variable number of disks. When I run my smartctl, I do have to enter -d cciss,{disk_number} /dev/cciss/cXd0. This is expected and makes sense to me, somewhat. Running smartctl -d cciss,7 gets me the 8th disk in the array from controller 0, as I understand it (cciss,0-7 all return good values). This makes sense to me, too. The next controller starts the weirdness. Running smartctl -d cciss,28 /dev/cciss/c1d0 gets me the 28th disk of the first external array (I think). I get values for cciss,0-28, which means I get 29 values from 28 disks. Then, running smartctl -d cciss,29 /dev/cciss/c2d0 gets me the 28th disk of the second external array (again, I think). I get values for cciss,0-29, meaning I get 30 values for 28 disks. My assumption is that some of these are actually reporting on, say, the bus of the array, not just the disks. So, how can I know what is disk response, and what isn't? |
|||
| #850 | invalid | how to setup disk failure alerts notification to email in centos 7.3 | ||
| Description |
how to setup disk failure alerts notification to email in centos 7.3 The requirement is i should i get email notification if some disk's failed on the server. Now its very difficult to get to know some disk's are failed in the server. Could you please help on this, I am new to smartctl |
|||
