Flubster

Members
  • Posts

    30
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Flubster

  1. I ordered one of these which arrived yesterday, which should allow both TPU to be seen via a single PCIe lane. When I can find time to remove the server from the rack and test I'll reply back Dave
  2. Hi, (Unraid 6.9.2) I'm looking at the Wiki (link) for shrinking the array, and this doesn't mention anything about dual parity and if this actually matters. I have spent the last few months clearing down and moving data between disks to prepare to remove some drives with questionable SMART stats. I now have the overheads to remove these drives. I intend to use the rebuild parity method as I don't want to zero the 6 drives i'm removing. I assume I am ok to just follow the instructions, and it'll rebuild parity OK with dual parity assigned? Dave
  3. I'm using unifi on my Frigate instance. What resolution have you set the rtsp to? I have detect pointing at one, and record set at a higher res cameras: front: ffmpeg: inputs: - path: rtsp://link (medium) roles: - detect - path: rtsp://link (High) roles: - record detect: width: 1024 height: 576 fps: 5
  4. I have also seen this, I assumed it was me "faffing" with TS change ffmpeg options, then the reversion back. Luckily I've got frigate cache set to /dev/shm therefore it can never kill anything in the UnRAID GUI etc. Flubster
  5. Also ich777's plugin has a page in settings that shows the detected TPU's IIRC (I can't check right now as I'm back to using USB until my Dual Edge TPU -> PCIe adaptor appears) Flubster
  6. I've also noticed that the default recording format has changed so if you have explicit output_args defined you may want to review them (changed from mp4 to ts) Audio is now recording by default - the entire reason I had a output_args ffmpeg override anyway. RRB
  7. try removing the password from the redis container. you've got it set to allow a blank password (ie no password) but then have a password set. Either set ALLOW_EMPTY_PASSWORD to no and specify the redis password in the paperless-ng config or blank the password in the REDIS container config Dave
  8. I maybe being dense here, but the UnRAID GUI should not be accessible from the internet anyway so what benefit would this have? Services should be behind reverse proxies - and using SWAG / NPM (I personally use SWAG but assume its in NPM) fail2ban is implemented, as well as geoip database lookups to block country subnets etc.
  9. Select advanced in the docker config and check you don't have -rm in any of the parameter settings Dave
  10. Fyi I've got a usb coral plugged into the back of my HP server which I'm reasonably sure is USB2.0 and I do indeed get a LED lit with a frigate docker. My inference speed is around 37 in debug which i have no idea is good or not! Dave
  11. Not sure if the UDMP is different from my USG but i didn't need additional WANIN rules other than the default port forward rules, (the 3000 rules) Try disabling them for a start. See if that gets you anywhere. I did have some very bizzare issues with VLANS and the USG so it can be very frustrating, it forced me to setup a syslog server just to get the firewall detailed logs to fix the issues. Flub
  12. So, Over the last few months i've been gradually retiring some old 2gb SAS drives (with escalating "Elements in grown defect list" errors) and replacing with some SATA 4Gb's. As I run dual parity I could now retire my second shelf if I moved the drives into the spare bays in the server / shelf 1. (I've been using the zero method after clearing the data from the erroring drives - then removing when cleared) From what I understand UnRAID doesn't care where the drives are physically - they are tracked by serial - so can someone confirm if I fill the redundant bays with the drives from/ shelf 2, and with screenshots ensure they are allocated the same position within UnRAID (this should be automatic) dual Parity will be maintained - the sda/sdb linux moniker is not relevent? It may annoy my OCD that drive25 maybe in bay 3 in my server and not bay 1 shelf 2, but I use "Disk Location" plugin so can track where drives are. Is my thinking correct - I could do with removing shelf 2, if only to give my UPS a bit more headroom, and reduce some heat before we hit the 2 weeks of summer the UK has! Flubster
  13. I've got a 2 drive Cache pool in btfs RAID1 HP Ilo is now reporting predictive failure (Its Power On Hours are @ 44035 (5 years eek! - SSD has done well!) which I suspect has annoyed ilo! - Have purchased a replacement drive - same size. I have read the FAQ and want to check the process is still valid - Mount new HDD into Server (I do have enough spare ports to have them both connected at same time) Stop Array Swap failing cache drive with new drive in array config Start Array Wait for btfs balance - when complete "stop array" will become live. Stop Array - Halt Server - Physically Remove failing disk Move New Drive into correct bay Up Server. Start Array. Sound right? Do I need to do any formatting of the new drive in any way? Do I need to force a balance? Also as its a new drive (SSD) not sure if I need to worry about the SSD 6.9 reformatting MBR? as the other RAID1 drive will not have the MBR in the newer location. (Also a SSD) Dave (Most likely overthinking!)
  14. yup all good, now using CUDA 11.10 when pulling the cuda11 tag Dave
  15. If you used the linuxserver nvidia plugin (before it was pulled) then yes, you are on 440.59. If you use the prebuilt kernel files from here: you can update the 6.8.3 nvidia drivers to CUDA 11. (I'm on 6.8.3 and on driver 450.55 - CUDA 11.0) - I see its now on 455.45.01 Usual disclaimers apply on if you think its worth playing about - i did as I needed it further up to date for plex transcoding. Dave
  16. The example config.json that was pulled before the latest update has syntax errors (no space before the colons) and therefore are ignored. Either add a space on the api-bind-http variable or pull config.json from the GitHub as it doesn't update once pulled. Dave
  17. Yeah when I next take down the array I'll attempt to run the diagnostics for you. I'm not surprised i'm a tad of a fringe case, running a h221 with a msa60 hp enclosure (12 disks), with 12 spare disks unconfigured on the second channel..... therefore if this would even be a supported configuration it could be msa60's backplane firmware etc. God bless HP and it's oddities Dave
  18. Install the plugin today: Feb 13 18:35:55 demiplane kernel: mdcmd (144): spindown 14 Feb 13 18:35:55 demiplane SAS Assist v0.85: spinning down slot 14, device /dev/sdr (/dev/sg19) Feb 13 18:36:07 demiplane kernel: mdcmd (145): spindown 2 Feb 13 18:36:07 demiplane SAS Assist v0.85: spinning down slot 2, device /dev/sdc (/dev/sg3) Feb 13 18:36:08 demiplane kernel: mdcmd (146): spindown 9 Feb 13 18:36:08 demiplane SAS Assist v0.85: spinning down slot 9, device /dev/sdj (/dev/sg10) Feb 13 18:36:27 demiplane kernel: mdcmd (147): spindown 6 Feb 13 18:36:27 demiplane SAS Assist v0.85: spinning down slot 6, device /dev/sdg (/dev/sg7) Feb 13 18:36:38 demiplane kernel: mdcmd (148): spindown 10 Feb 13 18:36:38 demiplane kernel: mdcmd (149): spindown 13 Feb 13 18:36:39 demiplane SAS Assist v0.85: spinning down slot 10, device /dev/sdn (/dev/sg14) Feb 13 18:36:39 demiplane SAS Assist v0.85: spinning down slot 13, device /dev/sdq (/dev/sg18) Feb 13 18:37:17 demiplane kernel: sd 2:0:0:0: attempting task abort! scmd(0000000055d8e9bd) Feb 13 18:37:17 demiplane kernel: sd 2:0:0:0: [sdn] tag#6800 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00 Feb 13 18:37:17 demiplane kernel: scsi target2:0:0: handle(0x000b), sas_address(0x5000c50059359149), phy(0) Feb 13 18:37:17 demiplane kernel: scsi target2:0:0: enclosure logical id(0x500143800950db00), slot(1) Feb 13 18:37:17 demiplane kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0000000055d8e9bd) Feb 13 18:37:24 demiplane kernel: sd 2:0:0:0: attempting task abort! scmd(0000000055d8e9bd) Feb 13 18:37:24 demiplane kernel: sd 2:0:0:0: [sdn] tag#6800 CDB: opcode=0x1a 1a 00 1c 00 ff 00 Feb 13 18:37:24 demiplane kernel: scsi target2:0:0: handle(0x000b), sas_address(0x5000c50059359149), phy(0) Feb 13 18:37:24 demiplane kernel: scsi target2:0:0: enclosure logical id(0x500143800950db00), slot(1) Feb 13 18:37:24 demiplane kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0000000055d8e9bd) Feb 13 18:37:31 demiplane kernel: sd 2:0:4:0: attempting task abort! scmd(00000000bb542357) Feb 13 18:37:31 demiplane kernel: sd 2:0:4:0: [sdq] tag#6754 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00 Feb 13 18:37:31 demiplane kernel: scsi target2:0:4: handle(0x000e), sas_address(0x5000c50063298861), phy(3) Feb 13 18:37:31 demiplane kernel: scsi target2:0:4: enclosure logical id(0x500143800950db00), slot(4) Feb 13 18:37:31 demiplane kernel: sd 2:0:4:0: task abort: SUCCESS scmd(00000000bb542357) Feb 13 18:38:13 demiplane kernel: mdcmd (150): spindown 8 Feb 13 18:38:13 demiplane SAS Assist v0.85: spinning down slot 8, device /dev/sdi (/dev/sg9) Feb 13 18:38:14 demiplane kernel: mdcmd (151): spindown 11 Feb 13 18:38:14 demiplane SAS Assist v0.85: spinning down slot 11, device /dev/sdo (/dev/sg16) Feb 13 18:38:37 demiplane kernel: sd 2:0:2:0: attempting task abort! scmd(000000003e983a28) Feb 13 18:38:37 demiplane kernel: sd 2:0:2:0: [sdo] tag#7608 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00 Feb 13 18:38:37 demiplane kernel: scsi target2:0:2: handle(0x000c), sas_address(0x5000c5006386444d), phy(1) Feb 13 18:38:37 demiplane kernel: scsi target2:0:2: enclosure logical id(0x500143800950db00), slot(2) Feb 13 18:38:37 demiplane kernel: sd 2:0:2:0: task abort: SUCCESS scmd(000000003e983a28) Then I wimped out and removed it. (lol) Will now pm sas-util-out Dave
  19. Not that you want to hear this - but my recipes and meal plans migrated to version 3 with no issues at all. Dave
  20. Nope, i forked the repository and updated the version. (To use my version) edit your docker and change your repository to flubster/gsdock and it'll pull my updated version You'll need to add the mapping i stated above as i haven't created any UnRAID template, just pushed another docker image. YMMV. Be careful as I started from scratch (after pulling the initial image from the template) so haven't tried any upgrades etc Rubberbandboy
  21. The author changed the github, but didn't push to dockerhub to rebuild the image. After manually updating the container I noticed on 11.3.3.2 (possibly 11+) that for it to register - I needed to create a folder mapping to container path /etc/goodsync/ as it appears the license is mapped here not where it was before. Rubberbandboy
  22. I had the same issue last week 😞 I managed to correct the filesystem with testdisk on a Windows machine using a usb caddy. YMMV. I got the data off then started again. Be warned testdisk can make any recovery impossible if you select the wrong options! Testdisk can be difficult in usage and operation! So good luck, some better GUI based tools may exist, I've always used testdisk personally as in I have had a Linux LVM raid array die before and was the only thing that could read it let alone restore the filesystem. Dave
  23. I'm using a Cron job using rclones WebDAV remote to copy objects to my nextcloud instance locally. And as it's using a WebDAV connection I don't need to worry about the occ commands or permissions as nextcloud deals with the files directly as if you uploaded them via GUI or web. All my local file changes are synced to UnRAID file shared on my local laptop shutdown, which in turn every hour syncs to nextcloud via a custom Cron container so it'll be available remotely. (They are not edited remotely just viewed) but I can't see any reason why you couldn't sync both ways if needed. Dave
  24. package clamav-libunrar and unrar is missing from the dockerfile, also clamav is out of date as the dockerfile has a specific version installing rather than the latest in the alpine packages. You can fix (until the maintainer sorts) by: opening a console apk update apk del clamav apk add clamav apk add clamav-libunrar apk add unrar then restart the container. Dave
  25. If you look here you will see it's a direct pull from another image, all spaceinvaderone has done is provide the XML for the unraid definitions. Maybe research the base image to see if any missing variables you can manually add. I personally migrated to the migoller/shinobidocker:microservice-ffmpeg image so I can point at my own mariadb docker. Dave