Jump to content

FlamongOle

Community Developer
  • Posts

    554
  • Joined

  • Last visited

Everything posted by FlamongOle

  1. It should force use the date set by Unraid variables if I remember correctly. If it doesn't, it's a bug - maybe the unraid devs suddenly changed something behind the scene. Maybe I look into it one day.
  2. Is the: Set warranty date entry: Set to "Unraid" and not "Manual ISO"?
  3. It mainly should do exactly that if you have entered the data already in UNRAID. However, try "force update all" and see if it updates it. If not.. maybe the UNRAID dev's changed something in the system. The documentation against plugin creators are appalling, I considered multiple times to just shut down the project entirely. Not the answer you want maybe, but the versioning and documentation updates are really crap with UNRAID.. and this is a paid licensed product..
  4. REQUEST FROM THE USERS Hey all! I consider modifying the core of the plugin for disk assignments and how they are bound, but I need some help/input from you guys. NB! I need info only from originally configured servers (not including non storage related devices)! Do not post from DIY servers! 1) I need the screenshot of the actual layout of the disks in a server. 2) Brand of the server and model. 3) The output of these two commands: lsscsi -g lshw -class disk -class storage -quiet -short 4) If possible, please attach the point 1-3 with a different disk configuration (like one less disk in the system, or positioned in a different slot), then post and describe the difference. Alternatively... If you can document the behavior of the kernel and storage devices path to be static, unique and reliable with the same assignment during reboots and that disks can be moved from one slot to another getting the correct assigned slot for it. Then that can be enough for my planning as well. So far I haven't found any proper information about it on google.. maybe I look for the wrong question? Any help appreciated! Thanks!
  5. I have no idea if I will.. there's a lot of requests about it, but still not really the intention with the plugin
  6. Yeah, can collapse a bit, but not entirely. Anyway, no big problem.
  7. Any possibilities to configure the Dashboard page? All my fans are controlled by IPMI, and under "Airflow" 1 fan get listed running 0 RPM 😛 Minor thing, but would be nice to remove sections not used/giving proper info
  8. Got affected by this when I swapped ISP, have been scratching my head some days because of this. Thanks. I believe next Unraid version will fix this whenever it launches.
  9. Thanks! You'll get that when you click to view the disk array in the big view. Else I don't think unraid's numbering make a lot of sense, hence why I made this plugin to begin with. Maybe in the future if I have time and motivation, but won't promise anything
  10. Update 2021.09.17 Commit #172 - BUG: Javascript MIME type fixed (probably) for the locate script, some might have experienced the problem with Firefox. Commit #171 - SECURITY: Boring security update, fixed some SQL and javascript injection security issues.
  11. You can already change the order, however, not after it is created by a simple click. But it should be fairly simple to just move over devices after adjusting the layouts. I might make it simpler in the future, but nothing I prioritize. If you want to move ex. layout 3 to 1, then copy the layout of the largest one, move the disks, then reduce the other one (if the sizes are different). If they're all the same, it's just a matter of reassigning the devices. Font colors should follow the unraid theme, not messing around with that (at least for now). Choose a better background color
  12. This was the main intention from the start, but I can't find a proper good solution to this yet. "by-path" is fine for most cases (as far as I can see), but it seem to have problems addressing SSD's. I have one SATA SSD and two nVME SSD's it does not add into the path section, and I don't want to mix two different systems for organizing drives in Disk Location. Not sure if this is a kernel issue, never meant to be, or if there's another solution for this altogether. Command below will show devices with paths defined. Even if you would see your SSD's there, it will break many systems and can't be implemented now. ls -l /dev/disk/by-path/ | egrep -v "part|usb"
  13. Update 2021.08.17 FEATURE: Added custom start number offset for trays other than 0 and 1. Also cleaned up the disk information tables a bit.
  14. Update 2021.08.16 BUG: Removed "prettyname" variable as it wasn't allowed with special characters. Might fix issues where some people didn't see "Disk Location" in the menus. I have been busy for quite a while, but this update, thanks to @Squid pointing out the flaw, is probably fixed. Please go ahead and try it out. Thanks!
  15. I haven't tried and likely won't. I'll leave the docker and the page up, but I will end the "support" now due to decreasing popularity in mining and the dockerhub won't build for free automatic anymore.
  16. It sort of says it.. either lower mem clock, or increase power and/or fan speeds and see if that helps.. GPU's are individual, try different values..
  17. Check first page, first post 😛
  18. Don't use that version on the host (if you want to OC), haven't tried 470. The container handles the rest and are setup with default nvidia driver which will likely be replaced regardless - hence the missmatch. Nothing to worry about what's happening inside the container.
  19. Front page updated with Nvidia driver version and the clock table with additional information below it.
  20. If it requires additional start up flag, then probably not. If it just requires open ports/port mapping, you can set that up manually yourself in the template setup and check if you can connect to it. I won't be using more time with this docker container unless it stops working.
  21. Ye, had the same experience here. Not so much I can do about it. Maybe there's some conflict with the 465 drivers between docker and unraid even if it's built from the same source, or just a bug. Won't use time to investigate this as it's probably at the near end of the ethereum mining era. Stable 460 drivers work, so I'll write a note about it at the front page. Thanks for the info trhough.
  22. It should auto detect and install correct drivers. Maybe the location it download drivers from are down for maintenance or something. I can't check it now, but it worked for me yesterday.
×
×
  • Create New...