Derek_

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.

Thank you for this plugin, it's most appreciated. Any chance you could update Borg? Current stable version is 1.2.2. https://www.borgbackup.org/releases/ (installed in the pack is v1.1.15). Thank you again.

Did you change the settings from 'simple' to 'advanced'? (near the save button).

I had the freezing/lost frames in my recordings on my camera with a microphone. I set the audio codec to `aac` and it fixed it For memory, `no audio` also fixed it. It took me a while to figure it out because i kept trying different audio settings in the "Stream" section. I forgot entirely about the "Recorder" section of the settings

@damnshaneisthatu I don't think it shows until/unless you select "Watch Only" in the Identity section.

Bump Hiya. Dredging up old posts - not my favourite thing to do - but this thread seems spot on. RE ProFTP - is that the same as ProFTPd? I'm looking for the same reason as the OP, and ProFTPd is the only one that isn't a Docker from my search.

I'd probably be capable of making a custom power cable, but I'd never know what it meant to the PSU. Man, PC building is so much more complicated than it used to be (when you want it the way you want it). I have built pretty much every PC i've owned, but i'm going to have to ask for some help from a friend who is much more into PC building than i am. I build it, then forget about it for 4-5 years until i upgrade. Then i have to learn pretty much from scratch. I might just ask my friend to choose my components, then explain why and perhaps offer some degree of option in there, like a bit more for this, a bit less for that etc. Thanks heaps

@AgentXXL Thanks for the info, it will be very useful when i upgrade my system. I really appreciate it

Is there anyone who can help me with the settings for my HikVision camera detection > FTP triggering? I've been trying off and on for a couple of weeks now. Shinobi detection is working fine, but i would prefer to offload the processing to the cameras for accuracy and better resource preservation of the server. The best i can get is 'username or password is wrong'. I'm using the credentials i use to login to Shinobi: `[email protected]` I've gone with the default paths illustrated here: https://hub.shinobi.video/articles/view/LyCI3yQsUTouSAJ HikVision doesn't allow paths with `/` per the instructions. I've tried various permutations of root/parent/child settings in the cameras GUI to no avail. Using the Monitor ID, or that with the Group Key (what collates the monitors) and even root (which gives no options). The directory structure is there, i can see it in the docker console. The camera just won't communicate with it. I'm using the cameras and on a VLAN (like SpaceInvader did) and Shinobi is in the same VLAN.

Fantastic SpaceInvader has updated his image. Good to see, because the videos he made about it are exceptionally good.

I'd love to see it! But i understand if that's a bit of a bother. My NAS experience was Synology, and i got unRAID about 2 years ago i think? 3? Anyway, i thought "i'll only need the basic license"... i just bought the mid-tier license a couple of days ago. I did contemplate going back to Synology for size, efficiency but i just like the way the unRAID works. Like i can take a drive out, connect it to my PC and run regular Linux commands and read it. Anyway, so i am totally unprepared for discussions around this "LSI" thing and "miniSAS" which, if i'm reading you right, would make the cabling much easier/neater. Any pointers to articles or videos or your own words would be very much appreciated. But again, no worries if it's a bit of an ask. Cheers. And i can't believe you might need a case with even more storage!

Thanks for the post, i was just looking at the same case. How many drives do you have and how do you find cable management? Jeez it would be nice if they optionally supplied a SATA plug plate to slap in the back of all those HDD bays. I can't imagine the mess of running 18 SATA cables

Oooooohh.. It took me a while, but i get it now Local UDs: /mnt/disks/ Remote UDs: /mnt/remote The help text wording was confusing to me, it doesn't make a distinction between local UDs and remote UDs. It implies that all UD mappings should be set to /mnt/remotes:

I'm trying it out right now. I was able to add a user dandy. The trick is to use an email address. Even if it's just "[email protected]".

Interesting. My camera in testing does the same - seems to be when light changes (dusk/dawn). Anyway, perhaps Reddit is the better place to ask about that. The developers frequent it. Also, they have a Discord.

Ah righto. Done, tks (i had also previously pressed a button, which put a pretty little green tick which seems to make the editing of the title redundant now).

Hiya, Is it possible to run MariaDB Docker across more than one VLAN? Or can i have two MariaDB instances, one for each VLAN? I read that in theory i could have two MariaDBs as long as they had different: - Socket - Port - Data location. I'm quite new to Dockers, VLANs and Databases! Use-case: I am looking at using MariaDB for both Shinobi CCTV (in a VLAN) and NextCloud in main LAN. I'd prefer one docker across both, but can i do that? Cheers.

I couldn't figure out how old Shinobi is, but MariaDB is quite old vs current: 10.4.13 (2020-05-12) vs 10.6.5. Furthermore, his Source Repository doesn't even exist anymore: https://hub.docker.com/r/spaceinvaderone/shinobi_pro_unraid Points to Repo: https://github.com/SpaceinvaderOne/shinobi_pro 404 Error He doesn't have any iteration of Shinobi in his current GitHub repositories: https://github.com/SpaceinvaderOne?tab=repositories So it appears this Docker hasn't been updated since before August 2020 (when the next Maria version became available). Considering his excellent videos show how to expose this to the internet is it wise to use such old software? Is there a way to politely ask whether any dated image (not just this, generally) should be maintained or removed? Even an update on the App info for it would be good, as in this case there are 4 other versions available.

I've heard "Motion" is simpler, could maybe give that a try.

Soooo... I figured out why DHCP wasn't working on the VLAN on the NAS only (was working elsewhere). At some point, i tagged the port `LAN`. Not `ALL`. I probably did this not long after getting the router, because i couldn't figure out how to secure my VLANs while letting some traffic i wanted through, through. I got that sorted quite a while later - but i didn't remember to flip the port back to `ALL`, i forgot all about it. It just popped into my head a short while ago. Tested it - all good. Spent SO long on this. LOL. CRY. Not sure how to mark as "solved".