itimpi

I don't think this could be run natively on Unraid as Unraid does not include a desktop. It might be possible to run it in a docker container or a VM - not sure if anyone has done this. Be interested to hear if anyone has managed this in any way.

You can either do this manually or use the technique described here in the online documentation that can be accessed via the Manual link at the bottom of the Unraid GUI.

This Unfortunately not

Are you trying to install the Desktop or Server editions of Ubuntu? If the Desktop version then 2 GB is the minimum RAM requirement. When you add in in overhead for running VMs in the first place this leaves little RAM for Unraid as the host to use. You might be able to get away with only giving 1GB RAM to the VM if you install Ubuntu Server. The alternative is to simply add more RAM to the Unraid server.

The speed + time quoted for the parity build will be optimistic as Unraid will give the wrong answer when you are manually pausing and resuming the parity build. It will assume you did the whole drive during the last increment when calculating the speed and time. You may want to consider installing the Parity Check Tuning plugin so that parity checks only run outside prime time. As a side effect it will give the correct duration + speed of the check as it takes into account pauses and resumes.

The parity swap process is documented in the online documentation that can be accessed via the Manual link at the bottom of the Unraid GUI.

You should be able to since you have single parity which can handled one drive missing/failed. Unraid will tell you if this is not possible.

Not quite - it is saying that it found a fatal error somewhere between 10% and 20% into the test and abandoned the test.

We can not tell much from the diagnostics with the array stopped, so redoing them after starting the array is better. They are also just after a reboot so no indication what lead up to your problem - in the future if a similar problem happens then take diagnostics before shutting down your system. I suspect that the original problem was that the disk in question dropped offline for some reason. If so then when you restart the array you may find that the system is successfully emulating the missing drive and showing all the data it should contain.

Parity in Unraid is real time so once you have a parity drive present it will start using it. You do not gain anything much by pausing a build of parity while copying. You should either let the parity build complete before doing any further copying (so your array is protected), or remove the parity drive from the array until copying is complete and add it afterwards (if you want to maximise copy speed).

It appears that disk1 has dropped offline as there is no SMART information for it in the Diagnostics. This will be what is causing the parity errors. It will also explain why you cannot see all your data. you will probably need to power cycle the server to see if you can get disk1 back online. After doing so post new pDiagnostics.

You could do that, although not sure it would help. Unraid would then automatically create a User Share for each top level folder on any drive, and this share would have default Settings (so you would need to check they were what you want).

You only have 4GB of memory in total, so it is quite likely that memory is an issue. How much RAM have you tried to assign to the Ubuntu VM?

You select the option to add a pool, and give the pool any name you like. You then configure at the individual share level whether they should use the pool for caching purposes. you were probably looking at something that predates Unraid 6.9 releases as in those days there was only a single pool allowed and the name was fixed as ‘cache’.

You seem to have another USB flash drive as parity - this seems a waste if it disk1 is just a dummy. You might be able to clear any issues relating to the dummy drive by reformatting it as described here in the online documentation that can be accessed via the Manual link at the bottom of the Unraid GUI. In fact thinking about it I am not sure a dummy drive even needs to be formatted to allow the array to start other than to eliminate Unraid offering that option on the Main tab.

Looks like that problem is related to trying to do things on the small flash drive that is the only drive in the array. I assume that this is just a dummy drive to enable the array to be started?

Unmountable does not mean unreadable (so the disk can still be part of parity) - it normally means a corrupt file system. Handling of unmountable dirks is covered here in the online documentation that can be accessed via the Manual link at the bottom of the Unraid GUI. No - if a disk shows as unmountable before a rebuild it will still be unmountable after the rebuild as all the rebuild process does is make the physical drive match the emulated one. If you try to format this will create an empty file system on the drive and update parity to reflect this (thus wiping its contents). This is only required for disks that are not currently part of the array (or have been removed from the array). If part of the array then you can use the GUI. The link above gives the way to do it by either the GUI or the console.

You certainly do not want a parity build running concurrently with a large copy as that will cause drive contention and is likely to take longer that running them one after the other. Many people leave the parity disk unassigned during the initial data load as the copying is much faster without a parity disk assigned. However your array it not protected against a drive failure until parity is built to it a risk trade-off that only you can make as to what best suits you.

You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post.

You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post.

All pool devices are automatically part of User Shares if the top level folder relating to that share exists on a pool so no idea why they should not show up for you. You can only limit array devices as to whether they can be part of the User Share sub-system. It might be worth toggling the setting for User Shares off, apply it and then change it back to Yes. It should make no difference but can do no harm to try.

The relevant UD device is not online, has not been mounted or has failed as /mnt/disks is where local UD devices get mounted. I assume that the vdisk image on disk1 is just your backup?

In what way? As long as the disk had been previously formatted then a file system check/repair would be expected to recover any content.

You probably want to start with this section of the online documentation accesible via the 'Manual' link at the bottom of the Unraid GUI.

A good reason to be using the Parity Check Tuning plugin so the check runs in increments outside prime time. The length of checks with modern large drives was one of the main reasons the plugin was developed in the first place.