Ramshackles

First, thank you for your work with these community apps, I use quite a few off them I recently installed RapidPhotoDownloader, and regarding the install.py from 0.9.34 seems to be the last release supporting this install method. the later releases .35 and .36 doesn't have this file. Is it possible to update to newer versions using the same approach somehow? Thanks

All the options comes up, but when it starts formatting, it returns back to unmountable and asks to format again. Even after initially erasing the pool, it still shows nvme5 in that labeled pool with btrfs fi show. I also cant clear the disk before adding it to a pool; Mar 24 07:32:04 Slattenpatten unassigned.devices: Removing all partitions from disk '/dev/nvme5n1'. Mar 24 07:32:11 Slattenpatten unassigned.devices: Failed to reload partition table on device '/dev/nvme5n1' after multiple attempts. Also this is in the log when it tries to format, mount and it comes up as unmountable; Mar 24 07:35:21 Slattenpatten kernel: mdcmd (40): nocheck pause Mar 24 07:35:23 Slattenpatten emhttpd: creating volume: cache_ssd (btrfs) Mar 24 07:35:23 Slattenpatten emhttpd: shcmd (113346): /sbin/wipefs -af --lock /dev/nvme4n1p1 Mar 24 07:35:23 Slattenpatten root: wipefs: error: /dev/nvme4n1p1: probing initialization failed: No such file or directory Mar 24 07:35:23 Slattenpatten emhttpd: shcmd (113346): exit status: 1 Mar 24 07:35:23 Slattenpatten emhttpd: writing MBR on disk (nvme4n1) with partition 1 offset 2048, erased: 0 Mar 24 07:35:23 Slattenpatten kernel: nvme4n1: p1 Mar 24 07:35:24 Slattenpatten emhttpd: re-reading (nvme4n1) partition table Mar 24 07:35:24 Slattenpatten emhttpd: shcmd (113347): udevadm settle Mar 24 07:35:24 Slattenpatten kernel: nvme4n1: p1 Mar 24 07:35:24 Slattenpatten kernel: nvme4n1: p1 Mar 24 07:35:24 Slattenpatten emhttpd: shcmd (113348): /sbin/blkdiscard /dev/nvme4n1p1 Mar 24 07:35:26 Slattenpatten emhttpd: shcmd (113349): /sbin/wipefs -af --lock /dev/nvme5n1p1 Mar 24 07:35:26 Slattenpatten emhttpd: writing MBR on disk (nvme5n1) with partition 1 offset 2048, erased: 0 Mar 24 07:35:27 Slattenpatten emhttpd: re-reading (nvme5n1) partition table Mar 24 07:35:27 Slattenpatten emhttpd: error: mkmbr, 2329: Device or resource busy (16): ioctl BLKRRPART: /dev/nvme5n1 Mar 24 07:35:27 Slattenpatten emhttpd: shcmd (113350): udevadm settle Mar 24 07:35:27 Slattenpatten emhttpd: shcmd (113351): /sbin/blkdiscard /dev/nvme5n1p1 Mar 24 07:35:27 Slattenpatten root: blkdiscard: cannot open /dev/nvme5n1p1: Device or resource busy Mar 24 07:35:27 Slattenpatten emhttpd: shcmd (113351): exit status: 1 Mar 24 07:35:27 Slattenpatten emhttpd: continuing... Mar 24 07:35:27 Slattenpatten emhttpd: /sbin/mkfs.btrfs -f -d raid1 -m raid1 /dev/nvme4n1p1 /dev/nvme5n1p1 Mar 24 07:35:27 Slattenpatten emhttpd: btrfs-progs v6.12 Mar 24 07:35:27 Slattenpatten emhttpd: See https://btrfs.readthedocs.io for more information. Mar 24 07:35:27 Slattenpatten emhttpd: mounting /mnt/cache_ssd Mar 24 07:35:27 Slattenpatten emhttpd: shcmd (113352): mkdir -m 0666 -p /mnt/cache_ssd Mar 24 07:35:27 Slattenpatten emhttpd: shcmd (113353): rmdir /mnt/cache_ssd Mar 24 07:35:27 Slattenpatten emhttpd: cache_ssd: mount error: wrong or no file system Mar 24 07:35:27 Slattenpatten kernel: mdcmd (41): check resume

root@Slattenpatten:~# btrfs fi show Label: '245123801609' uuid: a1be4576-2b0a-47fe-85f0-74f43ef6f61e Total devices 3 FS bytes used 574.02GiB devid 1 size 0 used 0 path MISSING devid 2 size 931.51GiB used 288.03GiB path /dev/sdd1 devid 3 size 1.82TiB used 576.03GiB path /dev/nvme5n1p1 Label: none uuid: 4fb91221-b1f3-4489-885f-b516bf11dff5 Total devices 2 FS bytes used 1.06TiB devid 1 size 3.64TiB used 1.07TiB path /dev/nvme1n1p1 devid 2 size 3.64TiB used 1.07TiB path /dev/nvme0n1p1 Label: none uuid: d46ceceb-3c18-4708-a8c8-dd52ba78c1bf Total devices 2 FS bytes used 2.75TiB devid 2 size 1.82TiB used 1.67TiB path /dev/nvme2n1p1 devid 3 size 1.82TiB used 1.66TiB path /dev/nvme3n1p1 Label: none uuid: cc1f197c-7714-4833-8143-3fe1ac96ff03 Total devices 1 FS bytes used 22.36GiB devid 1 size 465.76GiB used 24.05GiB path /dev/sdc1 I already got the data back from the cache_ssd. But running into trouble making a new pool with the these two drives, nvme5n1 and nvme4n1. I see one of the drives mentioned in the first output of the command, but that pool is not showing in the gui, can i remove that somehow and start over?

I think I managed to get access to some of the data, with the help of the FAQ and a post from you there. FAQ for unRAID v6 - Page 2 - General Support - Unraid I guess I can mark one of your posts as answer, you been a great help.

Alright I can boot with the old flash backup, excluding cache_ssd.cfg and cache_nvme.cfg. I know which disks were part of these pools, I'm not able to mount them directly sadly with the unassigned devices plugin. I also just can't recreate the aformentioned cache pools, the disks comes up as unmountable asking to be formatted before being able to start. Is there any way to get the contents of these cache pool disks without too much hassle? One of them (cache_ssd) has all the appdata which I would love to retrieve.

The culprit stems from the pools folder, 1 specific file, cache_ssd.cfg - that was actually the particular cache pool that was doing btrfs balancing switching from 3 to 2 drives when power when out. Still odd that it makes nginx not start and the webui be unavailable. Guess next step is to put all from last backup back on the drive, except that one file.

The -2309 was the latest. I just tried with a stock usb, web gui loads fine, but previous test only had key, super.dat, pools folder and the docker templates. which could possibly have that outcome?

Strange, fresh usb with latest unraid, only moved over; key, super.dat, pools folder and the docker templates. Same result. I might try a different usb, different port and differt unraid version, but this makes little sense to me. Diagnostics from the latest. syslog tower-diagnostics-20250320-2307.zip tower-diagnostics-20250320-2309.zip

Thanks for assisting JorgeB. I've made a fresh usb, and copied only the last complete /config folder over. Server boots but still not able to reach the web gui - I can login locally just fine though through ipmi. Any ideas? Attaching latest diagnostics. tower-diagnostics-20250320-0956.zip

Hi all, I guess multiple failures occured for me yesterday. I'll try to make this brief. I noticed my cache pool ssd's having errors, so figured i'd replace them and actually add a few more while i was at it. Bought nvme's and installed them, but I had unplugged the UPS and failed to connect that again. Booted the server, added the new nvme to the respective pools, waiting for btrfs balance to finish. It finished so stopped array and removed one of the pool drives with errors, started the array, then disaster struck, while balancing the power went out. Tried booting the server again, seemed ok, but couldnt get the web gui to connect. I figured i'd download the flash backup and try my luck, but the backup must've been taken sometime after the outage, since web gui doesnt work using that either and it has even more errors. I still have the original content of the original usb flash. But unsure what would be the best path to take forward, just start with a fresh clean usb drive - and setup again? or try to salvage from the old content of the usb? I have quite a lot of drives in the system, is the array configuration saved somewhere on the flash drive? I see the pools are and shares are atleast stored there, but cant located the others. Attached is the last diagnostics of the orignal usb and the first of the restored usb from unraid connect. Actually I see the last diagnostics of the orignal usb is named "tower" which is not what I called my server, so something must've happened there also. tower-diagnostics-20250319-2119.zip tower-diagnostics-20250319-2329.zip

Was this app removed ?

I've been having a slight nuisance with the Pterodactyl panel/daemon, every gameserver container it spins up doesn't show cpu/mem usage. The team behind Pterodactyl says it has something to do with using cgroup v1 and changing it to v2 should correct this issue. Is this possible and if so, are there any negative effects? Issue discussed on Pterodactyl github: https://github.com/pterodactyl/panel/issues/3999