olehj

Members
  • Posts

    369
  • Joined

  • Last visited

About olehj

  • 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.

olehj's Achievements

Contributor

Contributor (5/14)

37

Reputation

  1. 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.
  2. 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
  3. 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"
  4. 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.
  5. 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!
  6. 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.
  7. 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..
  8. Check first page, first post 😛
  9. 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.
  10. Front page updated with Nvidia driver version and the clock table with additional information below it.
  11. 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.
  12. 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.
  13. 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.