fishpen0

I went ahead and tossed a PR to update the instructions https://github.com/atribe/unRAID-docker/pull/11/files

The most up to date version from before telegraf was updated to package this file differently is still in the git history. This is from the exact commit that removed the file: https://github.com/influxdata/telegraf/blob/d8db3ca3a293bc24a9120b590984b09e2de1851a/etc/telegraf.conf Obviously if telegraf has some kind of major update this file will no longer work. Given this uses the official image, the project can't be updated with a startup shim that runs the telegraf config command before launching telegraf if it doesn't already exist. Meanwhile, you don't actually need to download the file. You can tweak the instructions like so and run this before you launch telegraf for the first time and prevent the chicken-egg problem you are hitting: docker run --rm telegraf telegraf config > /mnt/cache/appdata/telegraf/telegraf.conf

That seems to have done the trick. I'll know for sure in 3 days when the rebuild is done 😬 Thanks!

Had a disk (disk 6) go bad, ordered a replacement. Turned off the array. I unseated the wrong disk (disk 5) in the array while looking for the bad disk and reseated it. Found the bad disk, then popped in the replacement, then selected the new disk from the dropdown and then clicked start. Then something went horribly wrong and disk 5 failed to mount. Now I have a disk on rebuild and a disk on failed to mount. I reseated the now failed disk 5 and now I need to figure out how to get it back into the array so I can rebuild 6. I only have a single parity disk. I cancelled the rebuild and stopped the array because I'm not sure how to continue. Most of the advice here for keeping an existing disk relies on the rest of the disks still being workable to do an in-place rebuild of the one you are keeping, but I can't do that for this disk. box-diagnostics-20221003-0902.zip

It seems like native ARM support for the OS is just never going to come. I'm staring down the barrel of getting the Turing Pi 2 and moving my entire homelab to it when it ships sometime late this year and not being sure how unraid fits into that model

ARM support because the Turing pi 2 is the future of my homelab.

That worked. Thanks.

I upgraded to 6.1.9 and now my shares do not list on the shares page. The shares still work and they still show up on the dashboard. I can't reconfigure any of them from the shares page since they don't show up.

I recently upgraded to 6x and I think I didn't overwrite my old backup of unraid with the more recent one. Between my last backup of my config directory and this one, I had added a new disk. Now, my newest disk is no longer on the list of devices in my array. If I try to select it again, it shows up as a "new device, not in an array". If I start my array, any file from that disk is completely missing, even though it is presumably on the parity disk. If I manually mount the disk to /mnt/test/ all the files are still on the disk. Is it possible to manually re-add the disk to the array without having to wipe it and rebuild from parity?