TurboStreetCar

Pertaining to the migration from Unifi-Controller to Unifi-Network-Application, it seems Linuxserver.io doesnt offer a MongoDB container. Is there a plan for Linuxserver to offer one? Or are we using someone elses container?

Same problem here trying to reset root password, any help?

@DANgerous25 @lostinspace Glad to hear im not alone. I feel like this isnt normal, but i dont see it mentioned by many people.

Bump, Still looking for a way to set all albums to NONE for metadata in the mass editor. There's WAY too many albums to do it individually.

Been receiving these " Plugin run failed" entries in my system log. Everything seems to be working, but seems to be related to auto update? It shows for every plugin, every time it runs. Not sure what to do?

Glad it worked! Yep i got the option, but there's no "none" profile. You can only change it to standard. Also it doesn't look like my recycle bin is emptying, and i don't see the task "clean up recycle bin" in my tasks menu.

I was having same issue. For anyone having this issue, i found what i believe to possibly be the cause, at least it was in my case. I imported a large number of files that weren't formatted/tagged quite correctly. After importing them, i used Lidarr to rename all the files one artist at a time, this way it shows the preview of what its going to do, and allows you to proceed or cancel. I did this because sometimes it wrongly identifies the track, or uses a strange release, so i was able to verify it was all correct. If you enter the container console and run "htop", it shows the processes and one of them was what i believe to be the audio fingerprint process. It was stuck running on the same 3 files indefinitely. I believe at some point of moving/renaming files, the files it was currently working on broke the process and it was stuck, because the path of the file it was processing didnt exist any more. Restarting the container fixed it permanently. I do have a question, im looking to use the mass editor to set all of the artists metadata to "none" but its not an option. Is there a way to set all of the hundreds of artists to none without having to do it individually?

@JorgeB Interesting, Appreciate the help, its been up and running for a while now with no further issues. Thanks!

@JorgeB OK Replaced the SATA cable, and the duplicate drive moved to historical devices after the shutdown/power up. It appears to be working currently. Interesting if the cable failed. Is that something common?

@JorgeB So it seems that drive is unwritable currently. After i replace the cables, how do i remove the duplicate drive, and make the drive writable?

Hello, i received a notification that one of my cache drives cant be written to, so i checked the system log and see alot of BTRFS errors. I also have a duplicate drive in unassigned devices. I have a 60GB drive just for plex metadata. Currently, that drive is active, and accessible, all seems fine, But i have the same drive with serial number and all, listed in unassigned devices. System diagnostics attached. All the drives in this system were being used with an older MB/CPU, recently upgraded the MB/CPU to a Asrock Pro RS/i3 12100. Also upgraded power supply from old OEM from a used computer to a EVGA 650W. Seems like it all started with this: Oct 10 06:02:33 Backup kernel: ata5.00: exception Emask 0x10 SAct 0x20000000 SErr 0x400100 action 0x6 frozen Oct 10 06:02:33 Backup kernel: ata5.00: irq_stat 0x08000000, interface fatal error Oct 10 06:02:33 Backup kernel: ata5: SError: { UnrecovData Handshk } Oct 10 06:02:33 Backup kernel: ata5.00: failed command: WRITE FPDMA QUEUED Oct 10 06:02:33 Backup kernel: ata5.00: cmd 61/20:e8:60:6b:72/05:00:00:00:00/40 tag 29 ncq dma 671744 out Oct 10 06:02:33 Backup kernel: res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Oct 10 06:02:33 Backup kernel: ata5.00: status: { DRDY } Oct 10 06:02:33 Backup kernel: ata5: hard resetting link Oct 10 06:02:33 Backup kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 10 06:02:33 Backup kernel: ata5.00: configured for UDMA/133 Oct 10 06:02:33 Backup kernel: ata5: EH complete And then turned into this, with the last BRTFS Error just continuing to count up in the "rd" field: Oct 10 06:02:56 Backup kernel: ata5: SATA link down (SStatus 0 SControl 310) Oct 10 06:02:56 Backup kernel: ata5.00: disable device Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=23s Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 Sense Key : 0x2 [current] Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 ASC=0x4 ASCQ=0x21 Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] tag#13 CDB: opcode=0x2a 2a 00 00 72 6b 60 00 05 20 00 Oct 10 06:02:56 Backup kernel: I/O error, dev sdb, sector 7498592 op 0x1:(WRITE) flags 0x1800 phys_seg 164 prio class 0 Oct 10 06:02:56 Backup kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Oct 10 06:02:56 Backup kernel: BTRFS: error (device sdb1) in btrfs_commit_transaction:2418: errno=-5 IO failure (Error while writing out transaction) Oct 10 06:02:56 Backup kernel: ata5: EH complete Oct 10 06:02:56 Backup kernel: BTRFS info (device sdb1: state E): forced readonly Oct 10 06:02:56 Backup kernel: BTRFS warning (device sdb1: state E): Skipping commit of aborted transaction. Oct 10 06:02:56 Backup kernel: BTRFS: error (device sdb1: state EA) in cleanup_transaction:1982: errno=-5 IO failure Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: rejecting I/O to offline device Oct 10 06:02:56 Backup kernel: ata5.00: detaching (SCSI 5:0:0:0) Oct 10 06:02:56 Backup kernel: sd 5:0:0:0: [sdb] Synchronizing SCSI cache Oct 10 06:02:57 Backup kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 10 06:02:57 Backup kernel: ata5.00: ATA-9: SanDisk SDSSDP064G, 2.0.0, max UDMA/133 Oct 10 06:02:57 Backup kernel: ata5.00: 125045424 sectors, multi 1: LBA48 NCQ (depth 32) Oct 10 06:02:57 Backup kernel: ata5.00: configured for UDMA/133 Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sdb] Stopping disk Oct 10 06:02:57 Backup kernel: scsi 5:0:0:0: Direct-Access ATA SanDisk SDSSDP06 0 PQ: 0 ANSI: 5 Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: Attached scsi generic sg1 type 0 Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB) Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Write Protect is off Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00 Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Preferred minimum I/O size 512 bytes Oct 10 06:02:57 Backup kernel: sde: sde1 Oct 10 06:02:57 Backup kernel: sd 5:0:0:0: [sde] Attached SCSI disk Oct 10 06:02:59 Backup kernel: BTRFS warning: duplicate device /dev/sde1 devid 1 generation 1932543 scanned by udevd (17894) Oct 10 06:02:59 Backup unassigned.devices: Disk with ID 'SanDisk_SDSSDP064G_133116400085 (sde)' is not set to auto mount. Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 3, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 4, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 5, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 6, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 7, flush 0, corrupt 0, gen 0 Oct 10 06:08:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 8, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 9, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 10, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 11, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 12, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 13, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 14, flush 0, corrupt 0, gen 0 Oct 10 06:13:04 Backup kernel: BTRFS error (device sdb1: state EA): bdev /dev/sdb1 errs: wr 1, rd 15, flush 0, corrupt 0, gen 0 backup-diagnostics-20221016-0822.zip

Is there a way to reset the data statistics plugin? Like to clear it out and start over?

To update my query, Im using this plugin, and ive attached pictures of my setup. plugin: Tdarr_Plugin_bsh1_Boosh_FFMPEG_QSV_HEVC

Did a ton of reading on this, but it seems hard to keep up with the evolving hardware and software quite recently. Is there is known working method to use Tdarr with 12th gen intel iGPU Quick Sync? There's no plugins available under the "QSV H265" selection in the plugin page that are referenced in many "how to's". I got it to work with one plugin, but the videos were transcoded improperly and corrupted. Other plugins seem to fail transcode with a "GPU needed" or some other obscure error that isn't apparent what happened.

Well, i would say computers are different that containers, as containers only use specific ports and have specific purposes. Additionally, when on host network, they all are using the same IP. I'm aware internally there is separate networks broken up within Unraid, or dockers network system, but externally, all three containers (Zabbix Agent, Server, and Web Interface) are all on the same host IP. Would be nice to break that out to a separate network. I will try passing /proc/net/dev to the container at the /host/ path, but im not sure how to "reroute" the net key to that new location. i assume it would be somewhere in the conf file? Only issue with that is updates would break that modification. Appreciate the input.