FreeMan

I'm not sure I follow why you had to release an update to production to support 6.12 while 6.11.x is still in production, but again, your plugin, do as you wish. Obviously, some folks are throwing their toys out of the pram over it, I'll just double check the weekly FCP warning that it's incompatible until 6.12 is released, then I'll update. I think I'll then get an FCP warning that my current version of DL isn't compatible, and I'll go manually update it. Life goes on.

Managed to get it set up & working. Now, if I could only figure out why my backup server keeps crashing...

olehj is the maintainer and it's his choice to do with the plugin what he sees fit. It is, however, unusual to release to production a version that requires a beta OS release, instead of releasing the plugin as a beta/test/dev release until the OS release that requires the breaking change is into production. Those who are on 6.12 beta would, I'm sure, be most happy to install the beta version of disklocation to test it out, while the rest of us who are happy to sit on an OS release until the next one is in production (no matter how stable the latest beta might be) are confused by a notification saying our plugin is only compatible with an OS release that doesn't (and won't) exist and come here asking 20 dozen questions about it.

Could you give some directions on how to do this, please? It's been ages since I've messed with a bare metal Unix system (HP-UX anybody? Like last century...). I've only installed plugins & dockers on my unraid box.

Excellent! I saw the urBackup server part, but must have missed the client part. Thank you, I'll take a look at it.

This was from 3 years ago, but I presume that it's still accurate, right? I'd like a server to server backup option that's more-or-less plug'n play. I've got some rsync scripts, but not sure I want to continue using them. I'd like something a little more robust.

It seems I didn't turn on notifications on this post, but thanks! Even though I could have gotten started yesterday...

That might just make sense. I just took a look at all my plugins and I'm running versions dated between 2017 and 2020. Told you this machine was just being recommissioned after a long period of inactivity. I'll update all plugins before asking any other questions...

Fix common problems has reported that "Invalid folder addons contained within /mnt". This is an old machine that was just restarted after being out of service for > 1 year. I'm pretty sure that it was on 6.x when last booted, but that's as detailed as I can get. In my backup server, I've got /mnt/addons, but do not have an "addons" directory on my main server that's been running and kept up to date quite regularly. Is this the invalid directory that it's reporting? backup-diagnostics-20230303-1925.zip

I appear to be an id10t today. TYVM...

I'm confused. I've built a new USB drive, booted the backup server off of it and transferred the license key to the new stick. When I look at my unassigned drives, this is what I get: None of them give me the same thing I saw when I plugged a couple into my main server. None have a "Mount" button (enabled, disabled, or otherwise). What am I missing here? Realistically, I could go ahead and rebuild this completely from scratch and I don't think I'd loose much, as far out of date as my last backup was, but I'd like to understand what's going on, first.

I read further down the "replace your USB key" page and yes, that is the safe assumption - it's spelled out there. Just gotta keep reading, kid, the answers are there.

I've had 10000 other things going on and I'm just getting back to this (under a new account because of the change to the unraid.net login). Would someone please confirm that this assumption is correct? I've got a new USB stick built, and I've pulled 2 drives from the old machine. When I mounted the first drive in a USB dock, it showed up in Unassigned Devices and offered me a chance to format the drive. I respectfully declined. The second drive gave me an active "Mount" button. I mounted it and was able to see some of the old disk shares there. In my mind, the first drive was the parity drive and the rest are, obviously, data drives. I just want to be sure I'm correct before booting the old machine on the new stick and rebuilding the array & parity.

After the update that required me to log in using an unraid.net account (which I fortunately had, though, having not been by in a while I was at a loss as to why I couldn't get logged in & post), I can no longer see any of my post activity under my old forum account name. I saw the stickied thread about requesting a forum name change, is this what I need to do to get my new & old accounts tied together, or is there some other process I need to go through?

In this section of the docs it reads Is 32GB really a max size limit? It's starting to get difficult to find drives with smaller capacity, particularly physically small drives that one might be willing to leave hanging out the back of a server that's not in a rack. Especially from anything resembling a recognized brand. Of course, my el cheapo 8GB drive from <random brand> has lasted many years in my backup server...

Seems my USB stick has died. Plugged it into my Win10 machine, it beeps, noting that a USB device has been plugged in, but Win doesn't seem to be able to access it. It's been at least a year since this machine has been powered on, I'm not sure I've got a backup of the config (my bad, I know...) I believe I should be able to identify the Parity from the Data drives by plugging them into a USB dock on my main machine - if I can read a file structure, it's a data drive, otherwise, it's parity, is that a reasonable assumption? Once I've identified parity, I can transfer the license to a new USB stick and rebuild the array by assigning the parity drive, then the data drives, then build parity and all will (should) be good, right? Of course, I could probably just clear the drives as a year-old backup isn't doing me any favors, either.

Thanks, @JorgeB. Been a bit busy, just now getting a chance to look at this again. I presume you mean that I should backup the flash drive to another machine then rebuild on the same physical drive, then copy the config back over, and not (yet, at least) replace the drive itself. Perusing this section of the manual for instructions.

I have a feeling that this is a sign that I need to retire my old backup server... I'm getting a kernel panic on boot on the machine: Yes, this is old hardware. No, the machine hasn't been on for a year or so, therefore the version of Unraid is old. No, I won't be unreasonably sorry if I have to upgrade my primary server to pass its MoBo on down to my backup server. However, if anyone has any idea about a possible recovery solution for this, I'm all ears. I don't have diagnostics, since the machine hasn't booted fully for me to get to the GUI to run them. If there are any logs being written to the USB boot drive, I'm happy to pull them and post it here. I'm attaching a photo of the last bit of what's on the display. Maybe there's an issue with the lines above and I may have a possibility of recovery?

Because I know just enough to be dangerous and don't recall who makes which GPUs. My bad. I used to obsess over this stuff, but I've got too many other priorities in life to worry about keeping up. Now I just dabble when I can. Tucks tail and scurries away

Will these drivers allow UNRAID to access the 8 GPU cores on an older A10 series CPU? hmmm... a test of the installation indicates that no, it won't find the "built in" GPU: Anyone have any tips on configuration items that might enable this? Had I been paying enough attention when I purchased the CPU, I wouldn't have purchased this one for a server. Sigh...

Very nice! Thanks for the quick update.

I'm just so happy to be able to use this again! It's been "broken" for quite a while, and I'm 99.9999999% sure it happened when I switched the server from HTTP to HTTPS without thinking through the consequences. At this point, I'm not super concerned about the configuration bit again, but getting that sorted will be helpful in the long run for everyone.

After a quick test, yes, this is the issue. By default, the link takes me to https://nas.local:2379 I edited that to https://nas.local:2378 and got: Secure Connection Failed An error occurred during a connection to nas.local:2378. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG I changed that to http://nas.local:2378 and got a Firefox warning about there not being an HTTPS site available. After telling it to continue to the "unsafe" HTTP site, I got a QR code that is so large, it barely fits on my 24" 1920x1080 monitor. Might be helpful to scale the QR code down a bit.

Same here. The settings defined port is 2378, but the green link takes me to 2379. Don't know if that's the issue...

No QR code: Oh. My. Gosh. For the longest time, I did not have SSL enabled. I enabled it a while back and had completely forgotten I'd done so. When I tried to connect manually, I was using HTTP and port 80. I just used HTTPS and port 443 and it connected. Wow...