Ducky Posted September 15, 2018 Share Posted September 15, 2018 Evening, Following on from another post, I switched out the 410 raid controller on my HP DL380G8 to an LSI 9207-8i, in the hope I would have more control of the drives, and no longer need to do the 'Raid0' thing for each drive. Long story short, I eventually rebuilt the system in the end as the drives were coming up as unknown (no big issue to restore everything). However, whilst hoping I would then have access to the SMART data, I find that Unraid is unable to read the capabilities of the SAS drives, but the SATA drives are fine. Each time I try running the SMART tests I get an error, or the system says the drive needs to be spun up (I think they are all spinning anyway, as I thought it wasn't possible for unraid to spin down a SAS drive? Was it a wasted upgrade? thx Quote Link to comment
JorgeB Posted September 15, 2018 Share Posted September 15, 2018 Does the SMART data show up? If yes and for SMART tests you can always run them manually and make a feature request for the GUI to be corrected for SAS drives. Quote Link to comment
bonienl Posted September 16, 2018 Share Posted September 16, 2018 There is already support for SAS devices built-in. As @johnnie.black says, check manually (CLI) if smart attributes can be read and post the result here. Quote Link to comment
Ducky Posted September 19, 2018 Author Share Posted September 19, 2018 This is what I get using the 'smartctl -a' against one of the hard drives: It does look like SMART data is available, but whenever you run the test in the gui, it flags up errors (is it referring to the ones in the 'counter log' bit maybe)? thx ---------------------- smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.49-unRAID] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HP Product: EG0900FBVFQ Revision: HPDE User Capacity: 900,185,481,216 bytes [900 GB] Logical block size: 512 bytes Rotation Rate: 10020 rpm Form Factor: 2.5 inches Logical Unit id: 0x5000cca02211f1e0 Serial number: KPV9VY4F Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Wed Sep 19 09:21:49 2018 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 27 C Drive Trip Temperature: 60 C Manufactured in week 01 of year 2013 Specified cycle count over device lifetime: 50000 Accumulated start-stop cycles: 84 Specified load-unload count over device lifetime: 600000 Accumulated load-unload cycles: 1092 Elements in grown defect list: 0 Vendor (Seagate) cache information Blocks sent to initiator = 11520304325066752 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 0 2532168 0 0 0 128424.213 0 write: 0 5717982 0 5717982 0 43665.787 0 Non-medium error count: 1127 SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 24740 - [- - -] # 2 Background short Completed - 24655 - [- - -] Long (extended) Self Test duration: 7308 seconds [121.8 minutes] Quote Link to comment
JorgeB Posted September 19, 2018 Share Posted September 19, 2018 19 minutes ago, Ducky said: Description number (hours) # 1 Background short Completed - 24740 - [- - -] # 2 Background short Completed - 24655 - [- - -] There are 2 short tests logged, if you're not sure these were done by Unraid do another one and check if it's listed. Quote Link to comment
Ducky Posted September 19, 2018 Author Share Posted September 19, 2018 (edited) Yup, it does. If I run it in the GUI it starts the test and then throws back the 'error' message, but if I check the progress in the CLI it shows it still running: ----------------- Self-test execution status: 52% of test remaining SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Self test in progress ... 6 NOW - [- - -] # 2 Background short Completed - 24740 - [- - -] # 3 Background short Completed - 24655 - [- - -] ------------------ and then eventually completed: ------------------ Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 24748 - [- - -] # 2 Background short Completed - 24740 - [- - -] # 3 Background short Completed - 24655 - [- - -] ------------------- There is a bit that says 'non-medium error count' and this goes up by one each time what ever that means! Edited September 19, 2018 by Ducky wrong data Quote Link to comment
JorgeB Posted September 19, 2018 Share Posted September 19, 2018 14 minutes ago, Ducky said: what ever that means! SAS SMART is very different than ATA, and a lot less info, don't quite understand it all myself since I never had SAS disks. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.