DavidSpek

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

4 Neutral

About DavidSpek

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Do I understand correctly that unRAID will support iSCSI with this release or the 6.9 stable release? If not I think this is definitely a welcome feature.
  2. Given the power management fixes in the new 450.36.06 driver (and assuming also newer ones once they are released), would it be possible to add this driver once it is available through SlackBuild? I know the usual procedure it to have one release for each unraid build unless there is a critical bug, but given the fact that many use their GPU's for Plex transcoding and power usage in P8 is ~30% of the power usage in P0 wit a P2000 I think it is debatable if this should be considered critical. Reading through the thread I linked earlier the issue with Plex and power management was actually somet
  3. Not sure if this has been requested already, but could the driver version be updated to 450.36.06? There is a bug with Plex where the GPU stays in power state P0 after transcoded streams are terminated and this is supposed to be fixed in the new Nvidia driver. https://forums.plex.tv/t/stuck-in-p-state-p0-after-transcode-finished-on-nvidia/387685/101
  4. As others have already said downgrading the firmware from P20 to P16 fixes TRIM on my 860 EVO. However, I recently upgraded my regular H310 to an H710 mini mono card in my R720xd and I'd like to share a few things. First off, a tool has been made which will effortlessly flash H310 mini mono, H710(p) mini mono and H710(p) full sized cards (https://fohdeesha.com/docs/perc/). I followed this procedure for my H710 rev. D1 and it worked flawlessly. The issue is that this tool uses P20 firmware and replacing the P20 firmware file with a P16 firmware one stops the tool from working as it can't boot t
  5. I created a docker version of a tool to create the labels on HDD caddies of HP and Dell Servers. If anybody has issues please let me know. https://github.com/BShurilla/homelablabelmaker https://hub.docker.com/repository/docker/davidspek/homelablabelmaker
  6. I'm having this same issue both when trying to send the ebook to a kindle or just opening a file. I've checked the paths and changed them to be consistent (even though as mentioned the importing of the downloaded books to the library location is working fine). I've also tried new permissions on the files but nothing has been able to fix it. Without being able to open/download the books from LL or send it to a kindle this whole program is fairly useless sadly.
  7. I honestly had no idea the backups were taking 3 hours. Could it be that I am manually starting the docker containers before the backup is complete, as I usually check around 7:30 am? Regarding the scheduling, should I turn off the auto-update schedule and let the backup app schedule the update, or schedule the auto-update at a different point in time? Also, is there a way to reduce the time it takes to make a backup? Sorry for the large amount of questions, but I am guessing this information is probably also applicable for others. Again, thank you for the help.
  8. For the past 2 weeks or so I have also been having the problem that the CA Backup/Restore is stopping my dockers but not restarting them. However, in the morning I am just able to properly start all my dockers manually without any problem. This has been happening almost every night, but not always strangely enough. The Backup is run at 5 am and the auto update runs at 6 am. This is an example of the system log for one of the containers but it is nearly the same for all of them (except the port X (vetheXXXXXX) entered disabled state. Oct 10 05:00:01 Tower CA Backup/Restore: Stopping
  9. I had quite a bit of trouble getting OnlyOfficeDocumentServer to work with nextcloud and letsencrypt. So I had letsencrypt install for plex etc and got it working with nextcloud. The confusing part of getting OnlyOfficeDocumentServer to work with letsencrypt is that you need to create self-signed ssl certificates for the docker container itself, and then have letsencrypt create certificates for your public address. So a short overview of the steps I took. I left the ports of the container default as I wanted to eliminate potential problems. 1. Install the OnlyOfficeDocumentServer