mr2web

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by mr2web

  1. Suggestions for improving the template. Thanks for creating this template. Then I believe that "EMAIL_" ENVIRONMENT VARIABLES, found under "Configure passbolt" @ https://hub.docker.com/r/passbolt/passbolt/, also would be a good addition to the template. These are as well found under "Step 3" @ https://help.passbolt.com/hosting/install/ce/docker.html. Unfortunately I too am stuck at the issue with the browser extension not being recognised, but that is another story that I hope will have a good end eventually. Also a good remark that could be added to the template instructions as requirement is that the persistent storage for "Container Path: /etc/passbolt/gpg" as well as "Container Path: /etc/passbolt/jwt" need quite loose permissions as the container seems to use quite a few UID interacting with the persistent storage. I believe this is a big issue, BUT it is not the template to ask for mitigation rather the creators of the image. But until they releases a mitigation for this some not in the template instructions will most likely be useful. Keep up the good work. ๐Ÿ™‚
  2. Hi Siwat2545, I can not see the database directory path section anymore in the template. I have uninstalled my pervious version of OnlyOfficeDocumentServer and removed its image as well removed its persistent storage. Installing it again I'm faced with this template: No database directory path as far as I can see. ๐Ÿ˜ž Adding the data directory path manually as in @Wong recent post seems to fix it: Thanks for keeping your template up to date and alive. Much appreciated for sure mate. ๐Ÿ˜„
  3. Everything worked just fine after the reboot. ๐Ÿ™‚ Thanks for your great job ich777! ๐Ÿ™‚
  4. I got an issue downloading th edriver whilst upgrading Unraid 6.11.1 to 6.11.2. The error msg asked to make this post sho here it is. Please let me know if anyone need any more information. ๐Ÿ™‚
  5. Hi, I just updatet to the latest t-rex image, 4.4, and t-rex no longer recognised the nvidia driver, NVIDIA Driver v515.76 running on Unraid Version 6.11.1 2022-10-06. Rebooting the system did not make any difference at all. After rolling back to t-rex image 4.3 all is back up and running... Just thought I let u all know.
  6. @dlandon Hi mate, I'm sorry to bother u again, but my issue is back with that warning message on the main page. I have uninstalled UD and UD+, then reinstalled them and still have the warning message. serverbrain3-diagnostics-20211230-2109.zip
  7. @dlandon WELL DONE!!! ๐Ÿ˜„ Ok, on to the next one then... I did do some rearranging in my array and as I replaced old disks with new ones then zeroed the old ones to then be re-added to the array. Yes, that might seem a bit odd but lets not go into "why". When I added the old disks as unassigned devices to delete the partition on each disk to then pre clear them, prior to re-attaching them to the array, I got an "failure" message in a popup on the main page stating that deleting the partition had failed. But id didn't irl. This behaviour was consistent for each of the two disks when I deleted the old xfs partitions. Unfortunately I have no screen dump from these two messages nor any other documentation on the issue. As I have now reached the maximum of 12 attached storage devices for my PRO license I'm going to have a hard time to test anything at this point. But I thought I let u know at least.
  8. @dlandon Ok, here are a new diagnostics as well as a new "unassigned.devices.ini". Let me know if this can be considered as closed as I have another possible issue for u if u like. unassigned.devices.ini serverbrain3-diagnostics-20211208-1634.zip
  9. @dlandon Ok, finally the warning is gone from the main page. It disappeared as I refreshed the udev in step two in your instructions above. Running the mount cmd as you asked its still fine. Now all three partitions are also visual. Only 1 and 3 was visual earlier. Well done! :-D
  10. @dlandon Ok, I have updated UD to 2021.12.07. Warning still pressant. I have uninstalled the Pre Clear Disks plugin, rebooted the server. Warning still pressant. Attached is the "unassigned.devices.ini" you requested along with a new diagnostics taken post the actions taken described above as well as a scr dump showing the warning. ๐Ÿ™‚ unassigned.devices.ini serverbrain3-diagnostics-20211208-1049.zip
  11. @dlandon I'm pre-clearing two disks at the moment. I like to let that process finish before going a head with removing the pre-clear plugin. Sry 4 that. Will let u know a.s.a.p. when I have tried your suggested action, but it will be in one or two days.
  12. @dlandon Ok, but its visual on the main page. The system has been booted post the latest update of the UD plugin and pre the diagnostics and the screen dump attached here.
  13. @dlandon I have installed the update and are now running UD 2021.12.06. Still having that warning message though. Diagnostics is attached. serverbrain3-diagnostics-20211207-0756_UD_2021.12.06.zip
  14. @dlandon I'm sure I did as I downloaded it into a blank folder and unziped it there before removing the old file then copied the newly unzipped file to the specified location. I did not reboot though as I though the plugin refreshed itself loading the main page. was that a wrong assumption? I did reload the main page as well navigated away from it then back to it again. All before taking the diagnostics. I need to hit the sack as I need to get up and go to work in the morning (in 5 hours)... talk to u tomorrow...
  15. @dlandon Sure. Have a look around 6min into the clip. U'll see the behaviour I have talked about starting at 8 minutes into the clip. This has been working really nice for me for several years. I use this VM to edit 4k video. There of I need maximum performance out of my setup. (I hope I haven't cursed in the church by mentioning this tutorial, but I'm very pleased with Spaceinvador One's tutorials. He have helped me a lot over the years. ๐Ÿ˜„ )
  16. Attached are new diagnostics. Unfortunately I still get the warning. ๐Ÿ˜ž serverbrain3-diagnostics-20211206-0017.zip
  17. Just some more info regarding the disk u see in my diagnostics. The KINGSTON_SA2000M8500G..." disk I pass through to a WIN10 VM as its primary disk. I also pass through the SD-card reader to that VM. As the VM is running these two items are not available to unraid. But when the VM is not running these items are available to unraid. This is very convenient as I do not need e.g. two SD-card readers; one for the WIN10 VM and one for unraid. They can chare the same reader just not at the samt time though. the Same goes for the disk. Attached is a screendump from the WIN10 VM disk management view. The partition 2 is a EFI (Extensible Firmware Interface) system partition and the partition 1 is the main operation system partition for the win10 machine. The partition 3 is just empty as u describe. Dono if this helps at all.
  18. @dlandon Ok, I have had it set up like this for quite a few years without any issues. I did follow a tutorial made by Spaceinvader One at the time of setting up that VM. I have tested with UD 2021.12.03 and it has the same lovely behaviour as it always have had; whilst the VM is up and running the disk is not visual under Unassigned Devices on the main page. as soon as the VM is no longer running then the disk is available under Unassigned Devices on the main page and one can operate on the disk using UD plugin as any other disk that is unassigned. Prior to 2021.12.03 all was working very smooth and I did not experience any warning message like I do now. I know and I understand that a rollback is not an option. Would diffing the two versions give any guidance where the current 2021.12.03 do things differently than its presessor narrowing it down to find the problematic part of the code responsible for the warning message?
  19. @dlandon I haven't tested with UD 2021.12.03, but with previous versions the disk is no longer visual under Unassigned Devices on the main page as soon as I start my VM. So not very easy to double mount the disk. This behaviour has been great so far! ๐Ÿ™‚
  20. @dlandon No, that is what I do not like to do as I plan to use the partition 3 for storage outside the array and this should not be auto-mounted, I'll mount it when I need access to the storage. The VM is mostly not running. I need UD to mount the partition whenever I need to. This is one of the main features that I appreciate a lot from UD to be able to mount partitions when needed even though I pass them through to VMs at times. ๐Ÿ™‚
  21. Attached is the diagnostics file after mounting the nvme disk then unmounting it. This is a disk I HW passthrough to a WIN10 VM that utilises the partition 1. Naturally I should sort the partitions on this disk but it has been working just fine for a long time as it is. I'll be AFK for a few hours so, sry 4 not being able to respond quickly during those hours. serverbrain3-diagnostics-20211205-1507_debug_MONUNT_then_UNMOUNT_nvme_disk_UA_2021.12.03.zip
  22. @dlandon Hi, so I have now done three diagnostics dumps for u. one with the SD-card reader in the USB slot, one with the SD-card reader unplugged but no reboot and finally one with the SD-card reader unplugged and after a reboot. The thing is that that SD-card reader has been plugged into that USB-port for a long time without any problems prior to UA 2021.12.02. The issues and the warning was introduced in the UA 2021.12.02 version for sure. The issues u have already solved with the unassigned disks not showing up under "unassigned disks" on the main page. Thanks again foe that. still have the warning to solve though. Let me know if u need anything else or if u like me to test anything. serverbrain3-diagnostics-20211205-1412_with_SD-card_reader.zip serverbrain3-diagnostics-20211205-1416_without_SD-card_reader_NO_REBOOT.zip serverbrain3-diagnostics-20211205-1420_without_SD-card_reader_AFTER_REBOOT.zip
  23. I just upgraded unraid from 6.8.3 to 6.9.2 and I have this issue as well and only with the conbee2 usb dongle. I experienced no issues what so ever like this on unraid 6.8.3. I used conbee2 stick in a homeassistant docker container and the whole homeautomation platform goes down as soon as the conbee2 usb stick gets its device id changed. This is a showstopper for me. I might have to downgrade unraid back to 6.8.3 as I need to be able to rely on my homeautomation platform to be up and running 24/7 every day around the year. Unraid 6.9.2 will not provide the platform for that unfortunately. ๐Ÿ˜”
  24. @dlandon Morning. I did the new update u pushed after our troubleshooting session yesterday. This morning I see that I have that warning message still, see attached image. I also see that I had it last night as well after updating the lib.php manually. I was quite tired last night so I must have missed it. Now running UD 2021.12.03. I do see my unassigned devices though.
  25. Ok, that kind of fixed it. but it took a few seconds after loaded the main page for the disk to show up under UD but they do show up eventually so u r on the right track. When refreshing the page its just like it was before the issue started. Great work!! I need to hit the sack as its quite late over here. I really appreciating the work u do! Keep up the good work and if u like me to test some more please do not hesitate to let me know. :-)