itimpi

Have you checked that they have the ‘execute’ bit set? One of the changes in the 6.8 series is to limit the attributes of files on the flash drive. This may mean you need to explicitly set the ‘x’ bit after copying the files off the flash drive.

It might be worth posting the output of the following command: as this will help us see if there is any folder somewhere on your system that might be causing a problem with creating the share.

Looks as though there may be some issue at the Amazon end? If you can get the zip file then you can manually upgrade by extracting all the bz* type files overwriting the versions the flash drive

That sounds too long. I would expect something in the range of 2-3 hours per TB. It might be worth posting your current diagnostics.

The license is tied to the GUID of the flash drive used to boot Unraid, not the hardware of the machine running Unraid.

It does not look like the 8368 is even showing up at the hardware level, and thus there is no attempt to even load a driver for it. the Realtek is definitely being shown as 8139 which is limited to 100Mbps.

You should post the system diagnostics zip file (obtained via Tools->Diagnostics) to get some informed feedback. That will help with seeing if Unraid has a driver for the card that you are trying to use.

During a rebuild ALL the ‘good’ data drives are read for each sector that is being rebuilt on the failed drive. The system uses the contents of the sectors on the ‘good’ drives in conjunction with the same sector on the parity drive to work out what must have been in the sector on the failed drive to give the right value for the parity drive.

Any data written while the drive is being emulated will be there. No. Unraid will know that it disabled that drive so will not automatically try to rebuild onto it without user intervention. Note that a failed drive is not "rebuilt from parity". It is rebuilt by reading all the 'good' drives in conjunction with the parity drive. This is why you never want untrustworthy drives in the array as a rebuild requires that all 'good' drives are. read without error. It is possible this is what you meant but it may also mean that you do not understand how parity works.

I do not believe that anything like this is even on the roadmap.

That is fair enough. there is also a benefit to having a drive pre-cleared if you know you are going to add it as new data drive in that when you add it to the array it immediately available for use without you having to wait for a clear to take place. You can schedule the pre-clear to happen in advance of the add step at a convenient time which may be more efficient use of your time.

The question you should be asking is what location on the cache drive contains the files you want moved to the array? You should make sure that the User Share corresponding to that location has a Use Cache setting of Yes if you want mover to move files from cache to array. If you want to do from Windows what is wrong with the standard Windows File Explorer?

It USED to save downtime when adding a new data drive to a parity protected array as Unraid would take the array offline if it had to Clear a drive to maintain parity. However in Unraid 6 when a clear is needed the array is available for use - it is just the new data drive is not available until a clear completes.

Unraid will mark a drive with a red ‘x’ if a write to it fails. Writes can fail for all sorts of reasons, and in fact real problems with a drive are only a small proportion. External factors such as SATA/Power cabling, RAM, or evening vibration can cause this and are far more likely.

Many people use their only graphics card for VMs so it is definitely possible. What specific requirements there are to achieve this I have no idea.

the pre-clear steps are unnecessary unless you do not trust the drives and want to do a stress test on the drive before committing it to the array.

If you add a new data drive to a parity protected array then Unraid will Clear (I.e. write zeroes) to the drive before adding it to ensure parity remains valid. This will wipe any existing content on the drive.

These are the important points! In addition you need to realize that parity works at the physical sector level and has no understanding of what the contents of that sector might mean - the sector contents are just treated as a bit pattern. If a drive is missing, then Unraid can read a particular sector number off all the data drives and the parity drive. It can then calculate what must have been in the corresponding sector on the missing drive to give the result for that sector that is currently stored on the parity drive.

Quite likely! Since you have to stop the array to add the new drive it would not be normal to even attempt this if currently building parity! I must admit I have never tried the scenario of adding some parity drives and then before parity is built trying to add an array disk. I might try this on mu test system to confirm the behaviour.

A parity rebuild is not required for this. The only time you need to do a parity rebuild is when setting up a new array, or when you use the New Config tool (which puts the array into the same state as on a new array).

This is a not uncommon misconception about the Use Cache setting. It only applies to New files, not to existing files. When you use the 'mv' command at the Linux level you are potentially by-passing the Unraid User Share system as Linux first tries to rename the file if it thinks it is on the same mount point, and only if that fails does it do a copy/delete operation. Since as far as Unraid is concerned a file that is renamed is not a new file so you can end up with 'orphan' files for a share left on the cache drive. The presentation for the Use Cache setting in the GUI has been altered for the 6.8.0 release to try and make this clearer. I think it might also be worth expanding the GUI help associated with this setting but that has not yet happened.

I am not seeing anything like that on my system! What theme are you using as that may be relevant?

I still think you have not clearly specified when you think the value should be reset to 0? for instance do you mean when: when you first started using Unraid on this flash drive when you installed the release that is currently running onto this flash drive something else without a clear understanding of what is being looked for it Is not possible to discuss the merits of a suggestion, let along try to implement something.

The appdata share is the amalgam of the appdata folder on ALL drives. If you backup at the share level then Unraid will handle this transparently for you. With Use Cache=Prefer then if their is space on the cache mover will transfer files from array to cache (assuming the files are not open).

The procedure is correct if you WANT to reorder disks, but it is not clear from anything else you have said that this is the case. Most people simply add a new data disk in the next available slot in the Unraid GUI so that no re-ordering is required. it might be worth pointing out that re-ordering disks in the GUI has nothing to do with how they are physically connected. Unraid recognises disks by their serial number, not by where they are connected.