b00

Thanks for the detailed "how to", and all the posts below it, it was really helpful for a noob like me. After running I had this one warning in logs: 2022-05-25 16:10:28,913 WARNING Limited tf.compat.v2.summary API due to missing TensorBoard installation. 2022-05-25 16:10:28,930 WARNING Limited tf.summary API due to missing TensorBoard installation. Had exactly the same thing when the classifying of the photos started. At first run I also experienced an empty screen with no photos. Waiting a few minutes did not bring a change. But a reset and waiting did the job. At first this looked very optimistic, but still is very premature. After reading the blog of Photonix author I don't feel confident that this project will evolve quickly. I will have to get back to photoprism. Question to all: I have followed the steps from the first post to install Photonix. How to properly undo them? So that I leave no mess in my system? Unistaling a docker seems easy, but I gues this will leave some data/records/anything left behid?

Wow, @JorgeB it looks You were right! I would never thought that it was the RAM problem. Since most of my hardware is re-used (motherboard, CPU, PSU) i need to double check if the problem is the memory (which is new) or a CPU/mobo. Thanks for pointing me into that direction.

Hello guys, I have built together an unraid server- everything except the drives and RAM is new. It consists of three HDD's and one NVMe for cache. Today I started moving data (movies) from a PC to server. When I started moving the data from cache to HDD's I found out a bunch of these errors in the logs: Mar 4 12:26:00 Tower emhttpd: shcmd (561): /usr/local/sbin/mover &> /dev/null & Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4164747264 csum 0xa80daef8 expected csum 0x0c17a62f mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 Mar 4 12:28:04 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 Mar 4 12:28:04 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 Mar 4 12:28:04 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 I'm not sure what to do with it. Does it mean that my new NVMe is failing? Can I test it somehow? Should I delete all the data transferred from cache to hdd and transfer them again? I'm not using any docker or apps yet (I've only used the preclear plugin on the hdd's on different pc) tower-diagnostics-20220304-1244.zip tower-syslog-20220304-1144.zip

First of all, let me thank You for this great post!🙏 I was about to make a mistake of buying an old used PC with ITX ASRock J4105-ITX with embedded Intel Celeron J4105. But then, I stumbled up this thread and realized that this will be a bad road to choose for starting my journey in building my first NAS. Since You seem to have a lot of experience in this matter, let me ask You a few questions (hopefully You still check this forum from time to time). My objective is to build a compact size, fairly quiet, low power NAS with ~3 HDD + 1 SSD as cache. Ah and I want to buy all the parts cheap It looks that I have to stick with used parts, as the prices on new items are crazy. The ITX boards are rare and not as easy to find as the bigger formats. Question: 1. If You would have to choose Your components today, what would it be? (mobo + cpu) 2. Do You know any other small cases for mATX boards that don't cost as much as HDPlex? 3. You were using 2,5 HDD - were there really more quiet than 3,5? 4. You wrote I don't understand. If two lanes are used by SATAs, does it mean that for the total four disks, they have to share this two lanes? Where can I find this kind of information, when looking for a motherboard? The documentation of motherboard, the chipset, the cpu? Or what phrase to search for? 5. If I buy a SAS controller I dont need to use a SATA ports at all? Will there be a significant difference for a small NAS of 4 drives? (Also, can I attach a normal SATA drive to a SAS controller?) 6. Are You still using this set, or You have upgraded to something else? From Poland with love