Kilrah

Click the blue wrench and reset layout.

The flash backup is stored in the backup folder with the rest so as folders get purged it goes with them. Problem is you filled the optional "also copy it to another location" field, and that is not managed.

It's fine as long as you move disk to disk. Unbalanced does that of course.

Do the manual install process. Unraid keeps the previous version on the stick so you can downgrade, 2G is too tight. Got about 2.3GB used on mine.

The dark themes that have been built in for ages work.

As mentioned it's a limit, and transcoding should not use more than a couple of GBs anyway so sure you can increase it but it probably won't change anything since even that much isn't needed anyway.

No VLANs? Maybe check you didn't have MAC address filtering enabled on your router with the old machine's IP...

So is 192.168.1.1 correct as gateway?

Do you have a delay set after gluetun start on the Docker page? If not set a minute or so. Gluetun's probably not ready and connected instantly.

Look at the display output to see what the system is stuck on. Also you often have to manually reload the page but if your fans are spinning fast it's likely unrelated and the system is stuck on POST before even starting to boot the OS.

It is mounted readonly due to filesystem corruption. Oct 24 21:36:35 Tower kernel: XFS (md3p1): Metadata corruption detected at xfs_buf_ioend+0xa5/0x380, xfs_inode block 0x6952c000 xfs_inode_buf_verify Oct 24 21:36:35 Tower kernel: XFS (md3p1): Unmount and run xfs_repair Oct 24 21:36:35 Tower kernel: XFS (md3p1): First 128 bytes of corrupted metadata buffer: Oct 24 21:36:35 Tower kernel: 00000000: f1 78 ad b8 74 46 2a 61 4a 29 a6 40 8b 52 2f f5 .x..tF*aJ)[email protected]/. Oct 24 21:36:35 Tower kernel: 00000010: 42 e8 61 d5 69 1a 12 cf 19 ab cf cb a6 ee f7 45 B.a.i..........E Oct 24 21:36:35 Tower kernel: 00000020: 6b 47 af 8f ee 18 42 fa c9 61 5c 26 ea 7c c2 26 kG....B..a\&.|.& Oct 24 21:36:35 Tower kernel: 00000030: 84 1a 1a 65 20 de 47 dd 5f 20 5f c0 22 c5 5c 83 ...e .G._ _.".\. Oct 24 21:36:35 Tower kernel: 00000040: ed b6 aa 09 70 df 1e 82 04 27 bd b6 61 b5 df a8 ....p....'..a... Oct 24 21:36:35 Tower kernel: 00000050: e0 26 b8 ee 8b a9 dc 7f f4 b3 e3 a7 d6 bd d5 ab .&.............. Oct 24 21:36:35 Tower kernel: 00000060: 02 40 94 90 21 d7 5e 1c 08 3a ac bf 5a d5 df 56 .@..!.^..:..Z..V Oct 24 21:36:35 Tower kernel: 00000070: d9 c5 48 f1 1a 83 c9 28 95 95 80 70 b7 99 6c d0 ..H....(...p..l. Oct 24 21:36:35 Tower kernel: XFS (md3p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x6952c000 len 32 error 117 Oct 24 21:36:35 Tower kernel: XFS (md3p1): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x19c/0x270 (fs/xfs/xfs_trans_buf.c:296). Shutting down filesystem. Oct 24 21:36:35 Tower kernel: XFS (md3p1): Please unmount the filesystem and rectify the problem(s) Check filesystem and repair.

Nope, CODE app has been available for a few years at this point

They're rated for 8h/day use and 120TB/year with a 2 year warranty, unlike Ironwolfs/Exos that are 24/365 rated with 5 year warranty. What that means in practical durability if you use them in a NAS is... too early to tell basically since they've only been out there for a few months. https://www.seagate.com/content/dam/seagate/en/content-fragments/products/datasheets/barracuda-3-5-hdd/barracuda-3-5-hdd-DS17-1-2501US-en_US.pdf

No, unless your flash drive is really slow

These typically have Barracudas inside that have pretty low usage/endurance ratings

I tried a couple of times but never managed to get cuda integrated and working. If someone knows/has ideas to help...

You're supposed to put all the containers that depend on it in the same group, so they all get stopped with gluetun last, then processed, then gluetun started first and the others next, then it moves on to the next group. Having gluetun alone in a group achieves nothing.

Do you want to keep it removable? If so no. If you want it permanently attached then either created a new pool for it or add it to the array. Unassigned devices can be shared but only individually, not merged with an unraid share.

No, you now selected the 2.6 tag which currently points to the same image as 2.6.3, so it'll only show an update if that 2.6 tag was ever updated e.g. if a 2.6.4 was released, probably won't happen. I.e. you'll have to manually change it again if you want to change version. Should probably read the changelogs and docs of the app, maybe config changes are required going from 2.6 to 2.7. That means it's the "latest" tag. You'd know by date basically, if you keep your containers up to date with daily/weekly updates it should be pretty quick to find from the list.

Select the tag for a previous version you were running, or run them backwards if you don't know... https://hub.docker.com/r/gotify/server/tags

[Template only, I am not the container author/maintainer] GitHubGitHub - librespeed/speedtest: Self-hosted Speed Test for...Self-hosted Speed Test for HTML5 and more. Easy setup, examples, configurable, mobile friendly. Supports PHP, Node, Multiple servers, and more - librespeed/speedtest Not much to say other than you don't want to reverse proxy it since that'd affect results.

Disable filename validation, or remove those special chars in the filenames, it's just asking for things to break.

As the previous quote shows there is nothing on the "downloads" drive for the "downloads" share at the time of those diags. So look at other shares to see where data is present and check the settings for those. Apparently there's a "t..p" (temp?) share that does have data on that drive and is set to only live there so won't be moved.

That's C code, not a script... would need to be compiled