frank_sp61

Hello - yes, it's the latter. We have a ton of photos on Amazon Photos and I've been setting up my IMMICH server here on UNRAID server. I don't want to have Amazon just decide to change the plan and I've been making an effort to get off all the cloud services. I think IMMICH can do some of this but I rather have a docker container grabbing everything and not tying up one of my computers. Of course there are VM options I'm sure, but then I'd just install the VM and then delete it. I have about 30GB (72K files) that I think would tie up a machine for a while, maybe even overnight.

I see there are several apps to backup iCloud Photos and I wa t to do the same with Amazon photos. I’ve looked and can’t find anything. Suggestions?

Very much a noob question. I installed Python 3 (Python 3 for UNRAID) thinking it was a docker container. Just needed to run a tinytuya script and I don't have another system to run it on. Question is, I don't need this since it's not a container. I "uninstalled" it but it said it didn't find 'xxxx' so I'm not sure It was uninstalled properly. Can you please let me know how to ensure it is no longer installed? Thanks!

I think I found it. Additional host and container path set to /dev/dri. Thanks. Things are running better. 😁

Okay, did that. Where is the iGPU setting? For video transcoding or images?

Pretty sure it’s the Immich docker. When I turned that off, the cpu and memory usages dropped to reasonable. So can I just “pin” 1 or 2 cpus so it reserves 2 for other things? Pretty sure with the number of phots I’m trying to import, it’s very taxing on resources. Once completed I think it’ll be fine. So is this what pinning is used for?

Hello all, Just had my first issue with my server. It went down for no apparent reason (that I know of) and I had to power cycle the unit. It seemed to be stuck in a recycle loop? Not sure. Just a newbie here. I've attached the logs for smart people to review. Hopefully this is a one off. I was running an 'immich' scan of my external library which might have been the culprit. It has 200k+ pics and videos. Maybe this? Maybe because the processors were 100% for a long time? See attached after reboot. Is this what CPU pinning is for? Would immich be the culprit or more likely Post-egres? Appreciate the assist. linc-diagnostics-20260211-0858.zip

Just fyi, I confirmed that the SMB does work! Thank you. Also LINCPLUS confirmed that they are using the smartctl in the go file to update the LCD display and is optional.

Excellent! I will try that! Thank you again. You've been a big help.

So now, back to my original issue. My Homeassistant server writes a backup file to my UNRAID server once per evening. Homeassistant is on a separate machine and is not on a docker container in my UNRAID server. The share is setup for primary storage as cache and then moved to the array. After the backup, I get an error from my Homeassistant that the NFS share is unavailable and I have to reboot my Homeassistant to clear the error. This does not occur when the share is setup for primary storage as the array. Looking to understand why this is happening. Attached are the logs. You will notice that my Frigate server (also separate, 3rd server) writes just fine without reporting any errors. I've included the diagnostics as well as screen prints from my Homeassistant and the UNRAID share in case anyone can spot a setup error. linc-diagnostics-20260127-1027.zip

That's my next step!

I 'disabled' the Monitor Service and smartctl messages seemed to have stopped. Attached are the logs. #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp # Enable probe modprobe i2c-dev # Install PKG installpkg /boot/config/pkg/i2c-tools-4.1-x86_64-1_slonly.txz # Start the Monitor Service # cp -r /boot/config/monitor/ /usr/local/sbin/monitor/ # chmod 777 /usr/local/sbin/monitor/monitor # nohup /usr/local/sbin/monitor/monitor >/dev/null 2>&1 & # Start the Screen Serial Service cp -r /boot/config/serial/ /usr/local/sbin/serial/ chmod 777 /usr/local/sbin/serial/serialtest chmod 777 /usr/local/sbin/serial/test.sh nohup /usr/local/sbin/serial/test.sh >/dev/null 2>&1 & # Start the RESET Service cp -r /boot/config/reset/ /usr/local/sbin/reset/ chmod 777 /usr/local/sbin/reset/reset nohup /usr/local/sbin/reset/reset >/dev/null 2>&1 & linc-diagnostics-20260126-1626.zip

Thanks. I can eliminate that at least!

I’ll give that a try and let you know.

Is it not an issue that smartctl -scan thinks these are SCSI drives but smartctl -I /dev/sdb shows ATA and SATA? root@Linc:~# smartctl --scan /dev/sdb -d scsi # /dev/sdb, SCSI device === START OF INFORMATION SECTION === Model Family: Western Digital Red Plus Device Model: WDC WD60EFZX-68B3FN0 Serial Number: WD-C80KK9GG LU WWN Device Id: 5 0014ee 269138f9e Firmware Version: 81.00A81 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5640 rpm Form Factor: 3.5 inches Device is: In smartctl database 7.5/6045 ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Jan 26 12:47:52 2026 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled