bartdejonckheere

2 of which one is Unraid and one is Ubuntu server.

In the field in your screenshot you write the IP of your server in CIDR-notation, so if it's one single address, the address of your server, and hit Add. You can, on single lines, also add other addresses you want accessible over Tailscale. Don't forget to approve every route in your Tailscale admin-panel. https://login.tailscale.com, search your server, click the three dots, choose Route settings, tick the routes you want accessible, click apply. Let me know if you need more help!

What do you all use to unpack archives on your server? Zip Manager is very handy but developing has stopped, so I'm exploring new possibilities. Plugin, docker, everything goes.

Oooowh, thanks a lot! Yes, I put the USB-drive in the slot next to the flash, I might have bumped it... I'm going to put in a USB-hub, so I can connect to it from the front of my server and don't need to touch anything in the back. And I'm also going to move to internal boot anyway, sooner or later... 😅

Looks like that was indeed my drive, since sdf normally isn't used. But why does that bring my server down if it's just an unassigned device?

Something very weird just happened. I connected an empty USB-drive (at least, it's supposed to be empty, I erased it last month) and when I came back to my PC upstairs, nothing was responding. I could ping it, but no containers were reachable, the webUI was not reachable, SSH wasn't reachable,... I could only ping its IP, but no containers custom IPs. After searching for half an hour, I gave up and power cycled the server. After booting back up, everything seemed fine. The stored syslog shows a whole lot of read errors from the moment I connected the drive. The complete file is attached. 1 20:25:32 Willow kernel: usb 5-2: USB disconnect, device number 2 Jun 1 20:25:33 Willow kernel: sd 6:0:0:0: [sdf] Synchronizing SCSI cache Jun 1 20:25:33 Willow kernel: sd 6:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Jun 1 20:25:33 Willow kernel: I/O error, dev loop0, sector 1202912 op 0x0:(READ) flags 0x800 phys_seg 8 prio class 2 Jun 1 20:25:33 Willow kernel: SQUASHFS error: Failed to read block 0x24b5c56b: -5 Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read fragment cache entry [24b5c56b] Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read fragment cache entry [24b5c56b] Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read page, block 24b5c56b, size 7b49 Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read fragment cache entry [24b5c56b] Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read page, block 24b5c56b, size 7b49 Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30688) failed Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30689) failed Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30690) failed Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30691) failed Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30692) failed Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30693) failed What could this be? Is that drive at fault, or did I bump something while connecting it at the back of the server? Just trying to understand what happened to avoid it in the future. As said, the server is running fine now it's rebooted with the drive disconnected. crash.txt

Edit already! There's a reset-button right underneath the errors counter-screen... 😁 A few months ago one of my pool drives gave up, causing of course a lot of read errors. I since replaced the drive with a brand new one. But now, with updating to 7.3, my pool indicated errors. I checked and indeed, thousands of read errors. Could it be these remain from the failure? If yes, how can I reset it? Since replacing the drive, everything worked perfectly fine. So I'd be surprised if the errors are current events... Thanks a lot!

I've been using UrBackup for a while now, but only for file backups of two Windows stations, mainly as security for my wife's writing. I also experimented with image backups, but this is inherently flaky in docker, due to permissions, container isolation,... Also my Linux-systems are all in btrfs and UrBackup only spews errors on this. So I've been thinking of spinning up a VM and let that host my UrBackup server, writing to a btrfs-formatted drive. Anyone has experience with that? Any things I need to pay attention too? Does the drive it writes the btrfs-backups to actually have to be btrfs itself? Thanks a lot in advance!

Good to know it's not just me. Yeah, let's wait and see. 🙂

This is a great tool, thanks for the effort. While I don't really use the templates, as I do everything in compose with DockGE, it made me discover a great replacement for iVentoy. But is it just me, or are the docs down? Every page gives an error for me.

I had the same issue with icons not loading. But just now I tried downloading the icon, storing it in the appdata-folder of the app and pointing the label to there. It worked straight away. So looks like it's an issue with reaching out to the specified URL for the icon.

Would it perhaps be an option to include the extension .tgz? As far as I know, it's just a shorter version of .tar.gz, so I suppose it would work? My Google Takeouts are .tgz-files, so logically many users would have these files as well. Thanks for the great tool!

Is there an alternative for this app that is still being maintained?

32 GB because I had an opportunity to upgrade a year ago. I paid 45 euros for 2*16GB. The same package now would cost me 300 something Euros at my local hardware store...

I had the same issue earlier, but then it didn't stop loading. Now it does indeed fail with the same error and the same logging.