BRiT

Upgrade unRaid to latest RC 5. Early RC Kernels have large issues that can cause system stability issues. Try that first.

Again, sorry to see such bugs affect anyone. The good parts of the discussion starts on page 5 of this thread, with some trying normal file and directory permissions before trying the immutable attribute (chattr +i). I have all my movies/shows/videos set as +i but leave the metadata info and pictures from scrapers left as modifiable since they can easily be recreated.

You could take precautions as listed in the malware prevention topics, especially the "chattr +i" command.

The search for babybuddy should have at least 1 hit, https://hub.docker.com/r/bergerx/babybuddy Though this one has a multistep build process if you do this manually, so I'm not sure exactly what the committed image in the docker registry contains. There a lot of instructions at the above link if you were to do this manuallycaveat: i dont know if unraid has docker-compose or if its available in an addon like nerdpack or devpack.

You could install the image directly with Community Apps advanced mode to search docker regsitry for it. CA will do its best to come up with what needs to be filled out. Thats what I would try first, it also requires the least amiunt of work. No forking needed.

Enter numbers and not names in the User_ID and Group_ID fields. Their example run cmd doesnt even have those vatiables, but i suspect their own documentation is out of date: docker run -d --name=bliss \ -v /share/Container/bliss:/config \ -e PGID=0 -e PUID=0 \ -e TZ=Europe/Madrid \ -p 3220:3220 \ -p 3221:3221 \ romancin/bliss:latest

Pedantic nitpic on the help text, the default setting is "No" and not "OFF" looking at the UI.

/boot/config/plugins/dockerMan/templates-user

There is. Its in my-templates on the boot usb drive.

Is your hardware even 64bit capable?

And that is why some folks no longer bother to reply to threads with varioous items to try.

Fully specify the config location.

Not sure if anyone has tried the 9305-16i or 9400-16i, if they need or want Pcie 3.0 or nvme.

Post in the emby forums. They likely have better support for that specific situation.

This certainly would be nice.

Of course not. I'm a Lazy Dev. I forget that not many folks around this forum is aware of that knee-jerk reaction joke. It shows up all the time on the graphical/game related forums. Frankly, developers' time is better spent developing than it is documenting, unless it's a fundamental breaking change that requires manual steps to adjust.

Lazy Devs.

They were still out there a year ago when I was shopping around, but they seem to be harder to find at more typical retail and even some online shops.

No. I did not forget that RC does not mean Release Candidate here. Other's have. That's why I asked why they don't ask for features.

Why? It's not like RC(s) here mean feature freeze that goes along with Release Candidate.

https://www.linuxatemyram.com/

And bad news for all existing mb owners ... I'm fine (accepting there's nothing I can do now) just ignoring the temps for monitoring and just spot checking since I know its setup fine.

I don't see anything that's not expected from the process/syslogs. At the time of the diagnostics capture it shows you have 2 "rsync" processing running that's causing the load from the "unbalance" plugin. nobody 15606 0.4 0.1 110180 14136 ? Sl 11:04 0:18 /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 nobody 27569 21.4 0.0 20164 3308 ? D 12:03 0:39 \_ /usr/bin/rsync -avPR -X Video/Action Cam /mnt/disk2/ nobody 27570 0.0 0.0 19556 2556 ? S 12:03 0:00 \_ /usr/bin/rsync -avPR -X Video/Action Cam /mnt/disk2/ nobody 27571 15.3 0.0 19996 2384 ? S 12:03 0:28 \_ /usr/bin/rsync -avPR -X Video/Action Cam /mnt/disk2/ From your SMARTS on your cache drive(s), I'm not sure if the RAW value has any meaning for SSDs, but for most spinners, it does for field 187. Do you have a lot of power outages? If not, perhaps your power plane for the cache drives needs to be corrected. The larger ones report a number of "unexpected power loss" as well. Model Family: SandForce Driven SSDs Device Model: SanDisk SDSSDA240G Serial Number: 154836404031 LU WWN Device Id: 5 001b44 f188d033f Firmware Version: Z22000RL User Capacity: 240,057,409,536 bytes [240 GB] 174 Unexpect_Power_Loss_Ct -O--CK 100 100 000 - 24 187 Reported_Uncorrect -O--CK 100 100 000 - 5872 0x04 0x008 4 5872 --- Number of Reported Uncorrectable Errors --- Model Family: SandForce Driven SSDs Device Model: SanDisk SDSSDA240G Serial Number: 161337404732 LU WWN Device Id: 5 001b44 4a4758b33 Firmware Version: Z22000RL User Capacity: 240,057,409,536 bytes [240 GB] 174 Unexpect_Power_Loss_Ct -O--CK 100 100 000 - 16 187 Reported_Uncorrect -O--CK 100 100 000 - 2 0x000a 2 4 Device-to-host register FISes sent due to a COMRESET SMART Extended Comprehensive Error Log Version: 1 (1 sectors) Device Error Count: 1 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 [0] log entry is empty SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] --- Model Family: SandForce Driven SSDs Device Model: TS64GSSD320 Serial Number: A2910611949538650037 LU WWN Device Id: 0 0232d0 000000000 Firmware Version: 5.0.2 User Capacity: 64,023,257,088 bytes [64.0 GB] 174 Unexpect_Power_Loss_Ct ----CK 000 000 000 - 122 0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET

Try using a usb2 port instead.