JonathanM

Do you have an EFI folder (no dash) on the flash drive?

But keep in mind slackware, and by extension Unraid, doesn't do automatic package version management, so it's up to you to keep on top of versioning and conflicts. You can easily cripple your server if you aren't careful. If you have issues with your server and want help troubleshooting, you will need to remove or rename all the modifications you have done before we can help.

Sure, you just need the appropriate server software and licenses from Microsoft.

What is the IP of the machine you are trying to view the GUI from?

Probably not unrelated. SATA power connectors are extremely flimsy compared to the 4 pin style, so you should really only have 1 drive worth of power through each SATA connector. Stock cables should have the proper number of connectors, so as long as you don't use splitters, the answer is "as many SATA connectors as came from the factory should be fine on one continuous run from the PSU" If you must use splitters, the PSU end should be the 4 pin style, and the SATA ends should be crimped or IDC not molded.

VM's are functionally the same as standalone computers from the user standpoint. What you are asking is a function of joining the machine to a windows server domain controller, so that is how you would need to do it with VM's as well.

Looks like you are moving from one disk number to another disk number instead of renaming on the same disk.

No. Are you sure you have /mnt/disk1/ on the left and /mnt/disk1/data on the right pane?

Tools, diagnostics, attach the zip to your next post in this thread.

Which means the replacement will be unmountable as well. Parity, if valid, will rebuild the drive as it is, with whatever corruption is present. Parity doesn't hold files, it works with the entire partition, file system included, so if the file system is corrupt that's what parity will rebuild. When did that disk become unmountable?

Shares are simply the root folders on each drive, so you are really just renaming the paths into a new root folder, no need to move the bits to a new physical location. in mc, navigate to /mnt/disk1 in the left and right pane, in the right pane Mkdir data, then navigate into the data folder. In the left pane select shares you want to move into "data", then RenMov them. Should happen very quickly. Repeat for /mnt/disk2 in the left and right pane, then /mnt/disk3, etc, etc. If the shares in question use pools, do the same thing using /mnt/poolname. STAY OUT OF /mnt/user while playing around with mc if you are working with /mnt/diskX or /mnt/poolname. If you want to work in /mnt/user, make sure BOTH PANES are in /mnt/user, never mix the two. You will need to change the host paths on each and every effected container, adding "data" into their paths, i.e. if the original host path was /mnt/user/movies, the new path would be /mnt/user/data/movies

Change /data/usenet in the container template to the array share location you want to download to, like /mnt/user/downloads or similar, then change the NZBGet MainDir to /data

Which portions are needed to update a running install? Or are you saying we need to blow away what is there already and start fresh?

Not enough people tried the RC's, so the problem didn't surface. When you have thousands of different hardware combo's available, it's hard to find issues that only effect a specific subset.

No. They belong to Microsoft Corporation. https://www.lifewire.com/what-is-a-private-ip-address-2625970 NetRange: 20.0.0.0 - 20.31.255.255 CIDR: 20.0.0.0/11 NetName: MSFT NetHandle: NET-20-0-0-0-1 Parent: NET20 (NET-20-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Microsoft Corporation (MSFT) RegDate: 2017-10-18 Updated: 2021-12-14 Ref: https://rdap.arin.net/registry/ip/20.0.0.0 OrgName: Microsoft Corporation OrgId: MSFT Address: One Microsoft Way City: Redmond StateProv: WA PostalCode: 98052 Country: US RegDate: 1998-07-10 Updated: 2022-03-28

See Q4. https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Did you read my reply in to your other post about the same thing?

This is often caused by a BIOS setting, where not all devices are fully cycled and initialized to save time. Look for "Fast Boot" or something similar, may possibly be effected by other boot settings like USB controller device detection, legacy or not, etc.

It was assumed the factory would put a single partition on the USB stick. This was valid for a large percentage of sticks, but some manufacturers tried to be cute and add partitions with various functions, like U3

I can't remember where I saw it, but at some point in the past I seem to remember that it wasn't always required to partition a flash drive, formatting the entire device without a partition defined is somewhat supported. How supported, depends on the implementation of the OS. Perhaps looking for a valid FAT system on the /dev/sd? device itself as well as parsing the partitions?

In my opinion, the KVM hosted VNC should not be used for anything but operations that require local console on the VM. RDP, nomachine, pretty much any remote access hosted in the VM itself is going to give you a much better experience.

Rebuilding the data disk will result in the lost+found folder being permanently committed, and you will have to deal with that. Rebuilding parity based on the data disks will put disk2 back like it shows in UD. Which do you want?

Yep. If it asks for the command line switch to clear the logs, that too. It should tell you what it wants.

Parity is kept realtime, so what is showing on the disk is in parity, if parity is valid. File system errors are faithfully followed in parity, just like any other write. You need to follow through with the filesystem check on disk2.