Derek_

I had a squiz at this plugin, and decided to remove it. When i did so, it advised: Do i just delete the disklocation directory manually to fully remove it?

Yeah, they were still working. I already did the delete trick. Everything has been dandy since. One thing i remember is that my .img was less than 50% full. So that wasn't an issue.

My Dockers weren't updating, the last thing on my list was deleting the .img and starting fresh. As i was going to do that anyway, i thought i might do the folder thing. A friend of mine said he'd had much better reliability with the folder than the file when he switched.

I'm thinking of doing this. Why does the system suggest path: `/mnt/user/system/docker/docker/` ? When the first `docker` is empty (except for the to-be defunct .img file). Why not just go with `/mnt/user/system/docker/` ?

I would like to make Jellyfin available to be used over the internet, not just my local LAN. I will want to open up other things too when i feel more confident, photos and music. I also want to host an SSH backup server. I haven't decided on apps for these yet. Security is important. I only want authorised users to be able to access these services, or if possible to even be able to know they're there. I have no idea where to start with this, i've never 'exposed' anything before. Can someone recommend a good guide? The best guide? Thanks for any help you can offer.

I'm not sure when this issue popped up for me. It's been quite a while. At least 6 months, i'm confident somewhat longer. I was running Arch, and the install was 5 years old - and it was my first long-term Linux distro. I put it down to "i've been mucking around for so long, that maybe i need a clean install". I decided to give Nobara a go, and i changed from AutoFS to systemd for my mounting. At first it seemed ok, but then it started to happen again. It seems to happen when i make numerous changes rapidly, or i copy large files (the file still copied, but i can't navigate to it). Anyway, i've been looking around and it seems this issue happens on lots of different Linux system. But i've never seen a Windows client have this problem - has anyone else? I also had unRAID for a few years before i encountered this. I wonder what's done it. @NiLon As i'm hoping you'll appreciate, i avoid running commands (or changing settings) i don't understand without a little looking around. I can't find much on this `noserverino` option. It looks like you've been using it for about 2 years (3-ish now), so i'll give it a go and will report back. I'm writing here so i don't forget Thank you VERY much for your original post, and your follow-up some 2 years later. Truly appreciated. Wish me luck @ghostserverd I gave up on autofs. I had it set up on Arch and i found it very complicated compared to systemd, and even before i had these issues, i found it a little flaky. Here's some good reading that convinced me to try systemd: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/managing_file_systems/index#proc_using-systemd-automount-to-mount-a-file-system-on-demand-with-etc-fstab_mounting-file-systems-on-demand https://blog.tomecek.net/post/automount-with-systemd/ https://www.techtarget.com/searchdatacenter/tip/Mount-file-system-Linux-systemds-way The TL;DR is to add `x-systemd.automount` to your fstab entry!

Oh man. I was fixated on the 'warnings' re /mnt/disks - Your solution simply didn't occur to me. Sorry about that 🙃 I've just bought you a coffee

I have an issue with the backup of Duplicacy. I think it's because i use an Unassigned Device, that is only connected when i want to run the backup to it. I've shared the debug log with you (nice feature btw): 47d57179-09a3-460f-a435-2146ad89d7ba Thank you for this tool, it's much better than the previous one (except for this little issue )

Hiya. I procrastinate bad. So i haven't tried. A friend of mine suggested installing the new one and copying the database across. I don't know how to do that in a Docker and he didn't know if it'd work, so i had a quick look and i found this - but as i say, i haven't tried anything yet. https://jellyfin.org/docs/general/administration/migrate/

You're right, i noticed later that it only applies to the Ultra socket: https://www.asrock.com/mb/Intel/Z690 Pro RS/index.asp#Specification Though I don't know the difference between SATA and non-SATA device. How to tell? As an aside, i HATE the way these names keep coming about. Like USB's "full speed" and "high speed". That is literally impossible to know which is faster without reference. Likewise "hyper" and "ultra" for nvme. It's so stupid! I had to go hunting. To my surprise "hyper" appears capable of faster speeds than "ultra" :eyeroll:

Taking account of the various posts (including mine), this is what i did: Old Server Hardware: Run Parity check Turn off Array auto-start Stop the VMs and Dockers, and turn off auto-start. If any hardware pass-through on the VMs, change: a. Graphics to VNC b. untick any `USB Devices` and `Other PCIe Devices` c. Tools > System Devices > Untick any devices ticked for pass-through. (On new PC, reverse the disabling changes done in 2a,b,c.) Take screenshots/note of: Disk order (including cache disks) - note SATA ports with single parity drive doesn't matter, but the order shown in MAIN does matter (apparently the order of SATA ports used does matter if you have 2 or more parity drives - i don't have this). Network settings - also set static ip address if not already, and if multiple NICs note the correct one is selected on the new system. Backup Data and USB stick Shutdown Rename `-EFI` directory on USB stick to `EFI` on PC. New Server Hardware: Memtest (this can also be done with the unRAID usb stick, but i did it before i transferred the HDDs). Review BIOS/UEFI settings: a. Virtualisation is on, if there's IOMMU configurations, take note and adjust as appropriate (i don't have these in my new server). b. HDD set to AHCI (before installing HDDs) c. HDDs are detected (after installing HDDs), double-check AHCI setting. d. Boot from USB as first/only boot device. e. Check XHCI is enabled, per this post. f. Left TPM as enabled. g. Cleared SecureBoot keys, turned off SecureBoot. Boot unRAID. Check network settings (especially if connected to a monitor/keyboard) Check disks are all detected and in the correct order (including cache). Start array. Start Docker service - test each docker and turn on auto-start as desired. Start VM service. Check pass-through settings - test each VM and turn on auto-start as desired. Check access to shares/files via usual access means. Set array to auto-start if desired. Reboot to make sure everything comes back as expected. Parity check. Backup USB stick I think that's all i did. I did write notes, but as is often the case, they're a bit of a mess

Thank you for updating Borg to 1.2.4 Most appreciated

Worse than Micro-USB? 🤦‍♂️ 😄

Well i'm happy to report that the transition seems to have gone well. Touch wood. With all the research and notes, i was very careful and tested it on the workbench (in the garage, i don't like working on carpet). Moved it into the study and somehow during the process, one of the cache SSD SATA cables detached. Luckily i was double-checked 'Main' before starting her up, so noticed and fixed it. Put things back the way they were (Dockers, VMs - no passthrough) and it looks ok. Thanks to everyone who offered advice. I'll jot down my step-by-step in the next few days for reference.

Hmm.. when you changed to the official Docker, did you have to re-do all of your metadata stuff? I spent a while changing show ratings to suit my kids more appropriately.

Oh i spent quite a while searching for the meaning of XHCI hand-off. I found many explanations, many contradictory. What i THINK it means is that it probably doesn't matter much except for old OSes (pre-Win7 - i wouldn't know which Linux kernel) which do not have driver support for USB3. For such systems, it should be disabled so the ports will operate as USB2 ports. For current OSes, I *think* having it enabled (i.e. handing off to the OS once the driver loads) is probably preferable to using the BIOS controller driver, as the software drivers are constantly being updated whereas bios firmware rarely, for things like usb3 controller. Thanks for the post about XHCI for unRAID - it relates to booting the OS via USB3 port which i won't do anyway. I was curious as to whether the USB3 thing was still an issue, that post/thread is from 2018. I think i've done enough research. I'm doing backups, parity check and whatnot (per initial post) and hopefully tomorrow i'll do the transition. Thanks everyone (happy to hear any additional words of advice).

Yep, the old hardware still works. It's merely an upgrade I only have 3 drives in the array, all onboard SATA, plus 2 cache drives also on the motherboard's SATA. Plus one permanent Unassigned Device, also on the mobo SATA port. The new motherboard has 8 SATA ports (or 7 if i use all the m.2 sockets). Although it seems likely to be unnecessary, i'll put them in the same port number in the new build to further reduce the likelihood of issues. I hope someone knows answers to my no.2 and no.6 questions. I'd rather have the right BIOS/UEFI settings before i even first boot on the new hardware.

How does one do that? Was the messaging you showed during the boot? You had a monitor attached and watched it boot (or fail to)?

Interesting, i don't remember seeing it. I have an AMD Ryzen 2700X PC and a new (just about to build) Intel 12th gen for unRAID. Maybe this is new? Or maybe i've just not noticed it. Thanks for the info

Hiya, I'm about to update my hardware, from an AsRock Extreme/Intel i7-3770 16gb RAM, to an AsRock Z690 Pro RS/Intel i5-12500, 32gb RAM. I'm running unRAID 6.11.5 The old mobo had flaky UEFI, so i stuck with BIOS at the time. The new mobo almost forces UEFI - i need to install a GFX card to enable CSM, and i've read that doing so disables the iGPU! I don't presently want a dedicated video card, but i may one day. So i guess i'll go with UEFI - it's probably time anyway. I understand i need to change a directory name on the USB from `EFI-` to `EFI`. My unRAID has a couple of VMs (Linux, Windows), but none have hardware pass-through. My research indicates i don't need to change anything. It seems much has changed in the years since i last built a PC, and i have some questions: Any negatives to using UEFI in 2023? My research indicates that hardware pass-through in years past was easier/more reliable in BIOS. Has the situation improved for UEFI? TPM in the new motherboard UEFI settings. What do i do with that? My old motherboard doesn't even have TPM. Moving the array. Any gotchas i haven't covered below? (XFS, encrypted) Moving the cache drives. Any gotchas i haven't covered below? (mine are two SATA SSDs encrypted BTRFS mirrored) Is "don't use USB3 for the OS stick" still a thing? "XHCI Handoff" on the motherboard BIOS/UEFI settings - enable or disable? I don't understand the blurb on the screen: This is a workaround for OSes without XHCI hand-off support. The XHCI ownership change should be claimed by XHCI driver. It doesn't say whether it's enabled or disabled that applies the workaround, nor do i know if unRAID has the hand-off support. 🤯 Anything else i should be mindful of? I've also found these tips while researching: https://www.reddit.com/r/unRAID/comments/sak4pb/moving_unraid_to_new_hardware/ Summarised: Take a screenshot of your drives and hardware config like networking. Take note of drives. Hard drives and SATA port order doesn't matter so the Main page is more of a just in case drives don't show up correctly or the new board doesn't detect a drive (I forgot to plug a power cable into one). Disable auto-start Array. Do a parity check before and after to make sure the data integrity was good through this process. If 2 network cards (e.g. 1 motherboard, 1 PCIe), make sure they're mapped to the correct interface e.g eth0, eth1. Set static IP address for server: Settings -> Network Settings. Set the correct UEFI or BIOS Settings which you used before or plan to use. As in Virtualisation or IOMMU Groups. More tips thanks to the amazing SpaceInvaderOne: The main takeaways i got from his video was: Stop the VMs and Dockers, and turn off auto-start. If any hardware pass-through on the VMs, change: a. Graphics to VNC b. untick any `USB Devices` and `Other PCIe Devices` c. Tools > System Devices > Untick any devices ticked for pass-through. On new PC, reverse the disabling changes done in 2a,b,c. This shouldn't apply to me as i don't presently have any pass-through set up (i guess?) I also found this scary issue - serial numbers on HDDs changing after hardware change - it's from 2013 so hopefully it's not something that happens anymore: https://forums.unraid.net/topic/23982-solved-moved-drives-to-a-new-chassis-and-hd-serial-numbers-changed/ And, after typing all of the above, i found this post which has more tips https://forums.unraid.net/topic/120929-solved-hardware-migration/?do=findComment&comment=1105283 Have i missed anything?

Thanks, where does one check for that setting?

How do you see if a core is defective? I'm about to change hardware, so i'm researching possible gotchas.

Hiya, i'm doing research as i'm about to change my hardware, so i'm trying to see what gotcha's there might be. What's "Resizable Bar"?

Can we please have Borg updated to the current version of 1.2.3? If not, can someone please point me to a guide to show me how i can install this manually?

I wonder if updating the Borg package to the current stable 1.2.2 would help with the libffi.so.7 issue. Thanks to the earlier posts to workaround this for everyone.