JonathanM

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?tab=comments#comment-480421 That's an option as well. If you are never going to use a multiple drive pool, I'd recommend changing the format to XFS.

Default cache profile is RAID1 for redundancy, which means only 120GB is usable in a pool with a 120 and a 500.

A dodgy SATA cable would be more likely.

Restart in safe mode and see if that makes any difference.

Probably not going to happen, as unraid runs totally in RAM, and is unpacked fresh from the USB license stick on bootup. There are plenty of people running a VM with hardware passthrough on unraid as their main desktop already, and that accomplishes pretty much the same thing as a full DE built into the OS.

If you know the format you used, you may be able to run the appropriate file system tools and get the data readable. If the drive was healthy with a file system unraid understands, it would be that simple. Apparently your file system was damaged, based on the statement that it needed a rebuild.

Allowing access to array members (cache included) while the array is stopped is probably not going to happen, for various reasons Tom has stated before. However... I see no real reason that we couldn't allow VM's that aren't on the array to operate. It's not like you couldn't set up a VM configuration where all the required elements were on a non array device, but it wouldn't be able to easily share those elements with the VM's currently configured. You would need a separate XML storage location, and an iso location for install media. Maybe a GUI section for array limited VM's, and another for VM's on unassigned devices? As soon as limetech actually takes control of UD instead of relying on dlandon to maintain it, I see no reason why we can't have 2 VM types. However, as long as limetech doesn't actively manage unassigned devices, it's probably not going to happen unless someone writes a plugin.

The UD plugin by itself doesn't copy the data, it just allows you to access it at whatever linux path you tell it. It's up to you to copy the data, there are MANY ways to get that done. You can tell UD to share the drive over the network, and copy the data using windows explorer. You can use any of a few file manager dockers, Krusader and Dolphin are the top contenders. You can use Midnight Commander (mc), rsync or cp at the command line. Pick a method and google around, if you have questions about something feel free to ask, after you research the options. No. A properly working unraid system keeps parity in sync through all file operations. Besides, parity doesn't have any files anyway, all it knows how to do is recreate a whole drive intact, file system format and all.

Just wanted to pull out the bottom line takeaway here. Unraid can emulate and rebuild data on a failed drive, 2 if you have 2 parity drives. It can NOT protect against user error, file system corruption, or any of the myriad of other threats to your data. You MUST have a backup strategy in place if you want to protect your data.

If you wish to transfer the license to a new USB stick, you will need to go through the web wizard to complete the process. Be sure to copy the pro.key file to the config folder of the new stick before you boot the server.

If the OS USB stick hardware is ok but the files are corrupted, it would be easier to do a fresh install on the same key so your license is still valid. You will need to find a copy of your license key file, hopefully you have a backup, or still have the email with the attachment. Either way you will need to figure out which drive is which so you can assign them properly. Do you have... Recent diagnostics zip file? Recent status email from the server?

Or, mount the drive using the unassigned devices plugin, and manually copy the data to the new drive or whatever destination you want. Or, you can connect the drive to almost any computer running linux, and read the files that way. Many different methods, as long as the old drive is intact.

It doesn't. Unraid uses the drives as presented. Write cache is inherently risky, you need a UPS in place to mitigate the risk, so some enterprise drives ship with the setting off the lower the risk, it's up to you to enable write caching and ensure your infrastructure won't lose those writes.

Also, the attached devices is only checked at start of array. You are free to connect other devices after the array is started, and as long as they are disconnected when you need to start the array, you will be fine. So, just make sure any extra devices are powered down on array start, and you can hot plug extra drives into your hot swap bays any time you want. Or, upgrade your license if you wish to keep the devices connected at array start.

One page back. https://forums.unraid.net/topic/41044-recycle-bin-vfs-recycle-for-64-and-later-versions/?do=findComment&comment=732080 Or, on the VERY FIRST POST in the thread, 4th paragraph down.

Why did you post this in 2 different threads? Crossposting like that is incredibly unproductive, on 2 points. 1. The two threads you posted in are for 2 DIFFERENT implementations. They are supported by different people. You need to only post in the actual area that applies. 2. Responses to you in the different areas aren't guaranteed to be read by others trying to help. It's incredibly frustrating to spend a significant period of time analyzing and composing a response, only to realize that someone else went through the exact same procedure in the other thread. Please remove whichever post is in the thread that is wrong.

You misunderstand. The libvirt.img file is created when you fill in the path with the image file name included, and specify the size you want, default is 1GB (I think) In advanced view, make sure that your path has the file name at the end, like this /mnt/user/system/libvirt/libvirt.img

Exactly. Something like this https://www.amazon.com/gp/offer-listing/B002QJZLCA/ref=dp_olp_all_mbc?ie=UTF8&condition=all You can run 8 drives directly off that controller, and many more if you add an enclosure with an SAS expander.

Depends on the tablet. The UI is simply a web page, so if you can configure your tablet to use a barcode enabled keyboard app, then it works fine. A barcode scanning app isn't enough, it must be able to send input to the web page.

It will probably show up and be assignable, but I doubt it will make the situation better, probably worse. USB is not as robust as SATA, you will likely run into even worse performance and reliability issues, possibly even data loss. Do you have a PCIe slot available? If so, you could add a card with eSATA or even better external SAS connections to a disk cage.

You never lose any more disks than have failed. All good disks can still be used, so you never "lose the Array". Each parity drive, 1 or 2, allows for that many failed drives to be emulated. If you have 2 parity drives, you can have 2 data drive failures that are seamlessly emulated. 1 parity drive, 1 data drive emulated. Parity size is irrelevant, only the capacity of the largest data disk is used on the parity disk. Having an 8TB parity disk and 4TB data disks is wasteful until you upgrade one or more of your data drives to 8TB.

Depends on the motherboard BIOS. Some older boards had problems booting from anything besides the on board controller, but most modern boards should be ok.

After you set a new config, there is no valid parity, so nothing to check. Parity must be built from scratch.

Or, since parity must be rebuilt anyway, set a new config and assign ALL drives where you want them, and let the new parity be built with the old parity included as a data drive. The old parity drive should be the only drive that shows as unmountable, if other drives show as unmountable, don't format until those other drives are showing up properly.

The trial has no drive limits, only time limit enforced by authentication with limetech servers. If your hard drives aren't showing on the trial install, they won't show with a full version either. Post diagnostics if you want help figuring out why they aren't showing up. I suspect there may be issues with your controller, are you trying to use a RAID controller by any chance? Unraid needs a plain HBA with no hardware RAID to get in the way of drive management.