Forusim

Any news on this one?

@primeval_god Thanks for clarification. Non-intuitive is an understatement to say at least. Maybe there is a good reason, why it is working the way it is, but I find my use case reasonable. I have now solved it, like you suggested in the entrypoint.sh.

From the linked reference I understood, that you can "put" files into the volume during the build time via Dockerfile. Somehow this only works only during the runtime, but then I do not see a point in volume declaration in Dockerfile and can directly map it on docker run. However I want to have all required files routed to one location and map in the Unraid gui only this one /config location.

Hello, I appologies, if my question is too nooby, but I was not able to figure out, what I am doing wrong. I am running Unraid 6.9.2 and was mostly a docker user, but not a developer. I want to create a custom docker, which pulls some python apps from git (not my repo) and run it there. This python app has some hardcoded config / logs paths, which I would like to route via a volume to a persistent store on /mnt/cache/appdata/my-docker. I tried it via Dockerfile, like it is described here, but the created files are not initialy in the volume, when I start the docker contrainer. I made a sample project to show my issue. Dockerfile: FROM alpine RUN apk add --no-cache bash RUN mkdir /config RUN echo "test" > /config/config.yaml VOLUME /config COPY entrypoint.sh /entrypoint.sh ENTRYPOINT ["bash", "/entrypoint.sh"] entrypoint.sh #!/bin/bash echo "Run in loop" while true; do sleep 30; done; Docker config in Unraid From above I would expect on first start of the container the "config.yaml" file to be inside /mnt/cache/appdata/test. However the file is not created in the contrainers /config and therefore is not inside /mnt/cache/appdata/test. When I execute the command 'echo "test" > /config/config.yaml' in the running container the file shows up in /mnt/cache/appdata/test. Do I missunderstand, how the volume is supposed to work?

+ for writing Chia plots to a second array without paritiy. Initially I had the idea to make a "no cache" share on multiple disks with "most free" allocation. But wrting the 101 GB plot to parity protected array is slowed down by 50-70%, which takes too much time in parallel plotting. So the only reasonable way of plotting is against unassigned devices and rotate the destination disks in the plotting script.

Easy and effective. Thanks a lot!

Somehow I messed up the device names in UD with my formatting attempts. The disk, which was initially Dev 1 - ST8000AS0002-1NA17Z_Z840E2KD (sdh) is now only sdj. This would not bother me, but now I cannot spin down the disk anymore (the green dot is not clickable for this disk). And when I click on the sdj link to attributes and SMART info, it only display "Can not read attributes" sections. How can I fix this to initial behaviour?

As of Unraid 6.7 or 6.8 XFS is formatted with reflink=1, which uses a lot of space (e.g. 69GB on 10 TB disk). I found this feature is not worth the space and keep formatting my new disks with custom approach as described in the linked thread. Since I run out of SATA ports, I would like to add additional disk via USB & UD. I was hoping to format them with same command as I did for the array. mkfs.xfs -m crc=1,finobt=1,reflink=0 -l su=4096 -s size=4096 -f /dev/mdX However UD refuses to mount from such disk and only offers me to format it. Is there a way to trick UD to accept my disk (with reflink=0), like it does work in Unraid 6.8 and newer? Edit: Solved it myself. I formatted the disk with XFS in UD and then run the command on the first partition: mkfs.xfs -m crc=1,finobt=1,reflink=0 -l su=4096 -s size=4096 -f /dev/sdX1 It took the dashboard some mounts and unmounts to recognise the reduced used space.

I would like to thank everybody, who helped me in this thread. Cooler Master accepted my RMA and sent me a new PSU, unfortunately a lower tier MWE 550 Gold V2. From my research this one has quiet bad reviews, so I decided not to risk my other components. I purchased a new PSU - Seasonic Focus PX 550W, which now is quietly powering my NAS.

My PSU has single 12V rail and is semi-modular with 3x3 SATA connectors. I used 2x3 for my 6 disks for about a year now without issues. Tested also with 3x2 (3 cables), but the results are same, if I read test with dd on more than 4 disks, the system crash + reboot. It seems like that PSU dies exactly before 5 years warranty (purchased 02/10/2016). Hope that Cooler Master will accept the RMA.

I did some stress tests on my systems: Mprime ran without issues for half an hour in hard test mode - no issues. Diskspeed.sh ran without issues for all disks - each disk sequentially. Then I tried to simulate parity check load with parallel call of dd: (dd if=/dev/sdd of=/dev/null bs=1G count=1 iflag=nocache) & (dd if=/dev/sde of=/dev/null bs=1G count=1 iflag=nocache) & (dd if=/dev/sdf of=/dev/null bs=1G count=1 iflag=nocache) & (dd if=/dev/sdg of=/dev/null bs=1G count=1 iflag=nocache) 4 out of 6 disks can run in parallel, when I add more -> crash + reboot. I will check all the cabling of all my disks now. Any recommendations how to test, whether a PSU is failing?

Crashes occur even in safe mode without docker or VM running. The trigger is highly likely the parity check - usually it crash directly on start, but sometimes few minutes after start.

Unfortunately I do not have a spare PSU to test. Can I simulate a high load on PSU without running parity check? I already removed the UPS and plugged the server directly into the socket - still crashing. Temps are at 40 °C as per Temp plugin and fan are running as usual. My current state is, that I can mount the array with old flash drive (UNRAID not forcing a parity check here). The last time I started the parity check it ran for 15 minutes and checked 154 GB (1.5 %) with 179.0 MB/sec - out of a sudden crashed + reboot.

Hello ChatNoir, thanks for your reply. Yes I started with UNRAID on 02/2016 at low scale with ASRock N3150-ITX, 8 GB RAM, 1 Samsung EVO 850, 1 WD Red 8 TB and SanDisk Ultra Fit flash drive. Upgraded Mainboard and CPU on 09/2018 and upgrade cache SSD´s on 06/2019. Had no major issues in all these years and overall very happy with UNRAID Pro purchase. About 2 weeks ago I started with passing though the IGD of my i3-8100 to a Windows 10 VM, which is more potent than my notebooks i3-3110M. If all works out, I would completely switch my daily desktop to the Windows 10 VM, since all my data is already on Unraid. It all looked very promising until I started a parity check, which is usually scheduled every month. However the last one was missed, because to server was sleeping in last day of January. So I started the parity check from the Main menu and the server just crashed + rebooted. So here I am with my issue, stated in the initial post.

Ok, now it looks like a hardware issue to me, which is triggered by parity check... Booted from old flash drive, started array, started parity check and let it run for several minutes without further actions. Suddenly the system crash + reboot. Some information about my hardware: UPS: Cyberpower EX Series 850 VA / 490 Watt (Purchased 02/2016) Case: Fractal Design Arc Mini R2 (Purchased 02/2016) PSU: Cooler Master VS Series Modular 80+ Gold 450 Watt (Purchased 02/2016) MoBo: Gigabyte H370M D3H GSM - BIOS F12 (Purchased 09/2018) CPU: Intel i3-8100 (Purchased 09/2018) RAM: Kingston KVR21E15D8K2/32 - 32GB (16GB 2Rx8 2G x 72-Bit x 2pcs.) PC4-2133 (Purchased 07/2017) HDD: 6x Western Digital Whitelabel(Red) 8TB / 10TB as array (Purchased over last 4 years) SSD: 2x Samsung EVO 970 Plus as cache (Purchased 06/2019) Where should I start to look at?