Draic

Members
  • Posts

    22
  • Joined

  • Last visited

Everything posted by Draic

  1. this modification also messes up using non root users in general as discussed here:
  2. is there a chance to get btrbk added to Nerd Pack? I would like to have the unraid server trigger my backup scripts
  3. so I had it running with increased poll timer for 24h and nothing changed. There is still no spin down happening
  4. I have increased the poll timer and will report back, but these settings weren't an issue on stable release
  5. sure, here they are prospero-diagnostics-20201224-1440.zip
  6. with my drives connected to the SATA ports on my motherboard (a ASRockRack C236 WSI) they still do not spin down in RC2
  7. atleast I now know that I am not the only person that takes issue with this change
  8. ah you expanded your answers. Thanks for the help. I do not think it is something inside the sshd_config that is causing the screw up. For all users their home directories are ignored and instead are redirected to /root/ which results in permission errors. THIS is what I want to disable again and I really wonder the reason why someone thought it good to implement that way
  9. thanks but it just states what they achieved, not how it was done. I am asking for the actual commit to check the actual changes to the configs
  10. This is not a webUI user and I never claimed it to be. I have created non-root ssh users and I know this isn't intended by unraid (which is stupid imo). Before it wasn't supported but it still worked just fine. Now there are these errors and user home folders do not work, redirects and permission errors are happening. I just want to know where/how this was configured so I can disable the "security improvements". I do not indent to follow unraids root-only paradigm. Before the 6.9 beta that wasn't a problem, but the new ssh changes are annoying. I just need to be pointed to a commit or something about what was changed/added to the config files, so I can rip it out again. Thanks the blog mentions it as "ssh improvements" https://unraid.net/blog/unraid-6-9-rc1
  11. I want to revert the SSH "Improvements". If you change something like this, atleast document what exactly has changed. I have modified my ssh configurations in the past and now everything is broken from the update. How can I revert ssh back to the way it was before? I also now have a problem with docker now when using a command that runs inside docker: WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied no idea how to fix this. there is no such config file but I guess there should be, but it wasn't created before because of all the permission changes? I noticed access to /root is messed up now. Even non root users are redirected to create configs inside /root instead of own /home directories? How can I revert this? There is NO benefit for security. Forcing everything to run as root is the opposite of security. Why force that? Inside passwd the home directory is set up correctly, but logging in as that user, all configs are pulled from /root instead which results in permission error... Some examples: logging in as non-root user -bash: cd: /root: Permission denied -bash: /root/.bash_profile: Permission denied trying to run mc as non-root: draic@Prospero:/home/draic$ mc Failed to run: Cannot create /root/.config/mc directory Rant: Personally this feels like a shoehorned attempt at security improvements for an outdated way to handle users. Instead of furthing sticking with using a root user (and root user only), there should be a rework of user management on unraid. I do not use ssh to run stuff on unraid, but to run stuff in docker containers that are hosted on unraid. This always felt way to hacky to achieve on unraid, but now I feel like being forced to switch OS because I can't utilize docker the way I want and need to.
  12. I want to revert the SSH "Improvements". If you change something like this, atleast document what exactly has changed. I have modified my ssh configurations in the past and now everything is broken from the update. How can I revert ssh back to the way it was before? I also now have a problem with docker: WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied no idea how to fix this. there is no such config file but I guess there should be, but it wasn't created before because of all the permission changes
  13. Can't say that I see less writes on my Samsung SSDs recreated with 1MiB-aligned... But one question: How can I check if my docker.img still has the no-cow attribute? chattr does not seem to work ("Inappropriate ioctl for device While reading flags on docker.img"). And is there a way to correct this without recreating the docker.img?
  14. why is every connection to the server now a forced redirect to the login page? I want to access a local service that has nothing to do with unraid, but cannot access it as the link gets redirected to the new login. how can I disable this?
  15. the latest docker updates python to 3.8 breaking compatibility with deluge plugins. Please stick to python 3.7.
  16. and here. I rolled back a version. Just change the repository entry to "linuxserver/letsencrypt:0.34.1-ls25" until an update with a fix is here.
  17. yep, but that is lycheesyncs pitch: Having both the lychee db (with its speed advantages) and the filesystem untouched. I am also testing the alternatives. Fileshow and others that pride themselfes with a no db pitch are just to always to slow for my usecase. The closest so far to what I have in mind is filerun as it leaves the structures untouched, but has been quite fast. It just is not really designed to be used primarily with photos in mind, so it does not offer all the features I would like. Still not a bad solution for now. Check it out. Piwigo shot itself in the foot instantly when the import feature crapped itself with utf8 problems, so that one was out quick Photoprism looked promising but was nowhere near where it needs to be, but worth revisiting in the future. Other options I have tried were not even worth mentioning. Never imagined photo/gallery server to be such a empty landscape
  18. That is one reason why I wanted to get some plugins added to the docker. The base install of lychee has no good ways for automation and large jobs like you mentioned. Might be lychee is just not a solution for use cases like this
  19. lychees github lists some extensions: https://github.com/electerious/Lychee Personally I need the functionality of lycheesync: https://github.com/GustavePate/lycheesync and I am also interested in lycheeupload for direct ssh uploads: https://github.com/r0x0r/lycheeupload
  20. I am just starting out with migrating to lychee, but I need to add some extensions (most importantly lycheesync). These are not included with the docker image afaik, but I do not see a way to change this. Any pointers, or could it be added to the image?
  21. just wanted to add to this aswell. Updated from 6.6.1 to 6.6.3 and now no drive other than the parity will ever go to sleep. Something is borked with the update
  22. So I am trying to get using the IGD for LibreElec to work. I am using a E3-1245 v6, so my CPU should be compatible. What I did so far: 1) I have disabled the IGD for the unraid OS as described by salora and after the bzroot the screen will freeze like it should. 2) When using Seabios and i440fx for the LibreElec VM, it will start, the screen will turn black and then stop getting output. Meanwhile the VM will occupy a single thread to 100% and nothing will happen anymore (the VM boots fine with VNC instead of IGD). 3) After switching to Q35 for the VM I got a error in the log, which I think indicates where my problem is: "2018-08-28T11:22:05.839331Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,id=hostdev0,bus=pcie.0,addr=0x2: IGD device 0000:00:02.0 cannot support legacy mode due to existing devices at address 1f.0" so there is something running on 1f.0 that is still in the way. Using lspci -nn shows the following for the device: 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a149] (rev 31) So I guess I need to disable the LPC controller to get this working, but here is where I can't make progress. I tried disabling as much as possible in the BIOS but the LPC Controller is still in the way. I thought it might be related to the serial port on my motherboard, but I am not sure what the LPC controller on my mobo even does. My mobo is a ASRockRack - C236 WSI. I hope someone has a good idea what I could try to get this working. EDIT: After reading further on here: https://vfio.blogspot.com/2016/07/intel-graphics-assignment.html I found out that my problem with Q35 is expected behaviour and the general reason, why Q35 won't work. So my mistake there But when sticking to i440fx I still can't get this to run and I have no idea what I need to change, as I have followed the mentioned instructions. So now I have no idea where my problem is. Any help?