Jump to content

olehj

Members
  • Content Count

    197
  • Joined

  • Last visited

Community Reputation

16 Good

About olehj

  • Rank
    Advanced Member
  • Birthday June 3

Converted

  • Gender
    Male
  • URL
    https://ubrukelig.net
  • Location
    Norway

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Under "Set warranty date entry", be sure that "Unraid" is selected. And then store the dates via Unraid page. You might have to force scan all disks, so try that as well.
  2. Are you sure you have selected the correct config for this? It has to use the "Unraid date" and not "self specified ISO"
  3. It's not a bug, it's a feature In all seriousness, the allocation configuration is NOT tray number, it is just a tray ID. So assign them after the ID. It is also written if you click the "Help" button in Unraid.
  4. First of all, get Unraid 6.7.2 or above and update the plugin to the newest version. Then you add three groups, 5+4+5 slots, first and last vertical, the middle horizontal with standard count 1->5 on all. Then you can adjust pixel sizes to make a difference for 3,5 and 2,5 manually. Something like this:
  5. First of all I see that two has the same path (20:0:0:0), this might cause some issues. So I suggest you run a "Force Scan All" under Configuration->Tray Allocation, this will rescan all drives and also wake them up from standby to get all SMART data. It will also purge invalid configs which might happen when replacing drives or controllers, or maybe other configurations. Else it might be that these drives simply don't trigger the HDD light when SMART data is requested, like most/all of the SSD's out there. No fix for that in this case.
  6. Update 2019.08.23 Commit #102 - IMPROVEMENT: Hints provided by @Squid to improve the dashboard integration. Further changes made to customize it and position it to your own liking. Check the configuration page to adjust the widget. It can be positioned under "Hardware Information" tab, or the "Disk array" tab, or simply turned off. When the tab has been selected, you can move the widget up and down to your liking.
  7. Notice: use the help button, it might show info about how, what and why
  8. It is intended for easy setup, you add the drives after the numbers shown in allocation and not the end result/chosen layout.
  9. If you see the disk then there's no real problem else - the plugin will mainly work for its main purpose: showing the disk locations. SMART is mainly for information only, so in worst case you will not see "power on hours", smart failures etc.
  10. I'm not sure what you mean when the drive is in read/write, but no, I have no issues with this. I use LSI HBA (IBM 1015 in IT mode without BIOS), onboard SATA and SCU and Adaptec 6805 raid controller. None of them behaves like that.
  11. Hi, thanks! What happens during a cronjob is that it looks for SMART activity. The way it works is that it request which state the drive is in before it pulls out the rest of the SMART data. If the drive(s) reports a typical spinning state (ACTIVE/IDLE), then it will request all SMART data from that drive. If this for some reason fails, or the HBA expander always says the drive is ACTIVE/IDLE regardless the real state of the HD, it looks like it will then wake up the drive to get the SMART data. But I'm not sure about this and I'm not sure how to really test this further. Maybe there's some special SMART override configurations for the HBA controller if it has a BIOS to prevent it from waking up when SMART is requested? Or maybe SMART is getting disabled, overridden or ignored? You can check if you trigger the messages from dmesg via these commands: Check SMART activity, will (should) only post results if the drive is either ACTIVE or IDLE: smartctl -n standby /dev/<device> Output should be something like "Device is in IDLE_B mode". If this line is missing, it is detected as standby or sleep (non-spinning). If the drive is detected as ACTIVE or IDLE, then the cronjob will go on and get the rest of the SMART data with this command (except it will get them via --json in the script): smartctl -n standby -x /dev/<device> One or both of these command is probably what causes your messages to happen, and be sure to check if the SMART data seems to be correct and not something the controller "makes"
  12. Yes, this happens now because LUN is ignored when scanning through drives. Earlier it was used to detect if the drive was an actual drive, but some drives doesn't even have LUN's so it had to be removed. At least you can choose to show it or not 😛
  13. Update 2019.07.12 Commit #100 - MINOR ISSUE: Fixed a non-numeric value warning message. Fixed padding for empty trays.
  14. Yes, it is per group basis.
  15. Delete it under "System Files"