itimpi

You have mover logging enabled, and according to the syslog files are steadily being moved off the cache (note that file names when mover logging is active are NOT anonymised). Not knowing how big the files in question are it is difficult to comment on the speed as no disk related problems show in the syslog.

You are correct in that you need a licence upgrade to support the number of drives attached, but it is not clear why the GUI did not load and simply refuse to start the array without the upgrade.

Your data should be intact as long as you do not make the mistake of assigning a data drive to a parity slot. You may find this section of the online documentation to be of use.

Your symptoms suggest that that the flash drive was not correctly mounted at /boot during the later stages of the boot process so no settings were found and no network drivers were loaded. Without further investigation at your end it will be difficult to determine if this is really what happened, and if it is why it happened.

I need to try and work out why I did not see the same message on my 6.9.2 system when testing. I have just gone back to that system and this time that message IS being displayed which is weird. In theory the code line that precedes the session_start() should mean that function should only be called if needed but that is obviously not always working as expected. I Will work on correcting it on my system, but I will also add some diagnostic logging around that bit of code to help me get more information about why my check on whether the function is needed is not always working.

It could be caused by the cabling (or possibly even a port). 100Mb Ethernet needs less working connections in a cable than 1GB Ethernet.

Exactly how are you doing the move? Ideally it should be a copy/delete. The problem comes that if you are using a move at the Linux level you are potentially bypassing the User Share system as Linux is not aware of User Shares. Linux implements move by first trying a rename and only if that fails does a copy delete. This can result in the file ending up in a new folder on the same drive corresponding to the target User Share.

I can see where that message could originate from in the code - but I am not sure why. Where are you seeing this message (GUI, syslog etc) and if the GUI on what page. I did not see it when testing - but maybe I am not looking in the right place? I need to be able to replicate the issue to be able to work on it (and know if I have fixed it). Also if it is the GUI what browser are you using?

There were various recent reports of error messages appearing in the GUI and/or syslog generated by recent plugin updates (although the functionality appeared to still work) as I tried to improve the multi-language support. I have just pushed an update that I think fixes all of these but please let me know if any still occur that need me to look at them.

Do you have a recent backup of the Unraid flash? If you do then switching to a new flash drive with all settings is easy If not then this section of the online documentation has a process for getting back your dtive assignments Your data will be intact regardless, but if you have no backup you will probably have to set up plugins/docker containers/VMs again.

Limetech have never pre-announced a release date so hoping to get one is optimistic.

The way to clear the log is to reboot. More to the point what is causing your log to end up full - it could well indicate an underlying problem. You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post.

Yes - Unraid can run on any hardware - server or desktop grade does not really matter.

Not quite sure what you are asking? If you boot Unraid on any PC then it is the OS that will allow that machine to function as a NAS.

If the disk is being emulated then it will show as this on the Main tab and the system will act as if it were still present. If it shows as mounted you can then examine its contents. Whatever shows up there is what you will end up with after a rebuild.

That is optional as long as you end up with the correct assignments before starting the array I normally recommend using it to minimise the number of changes required when you return to the Main tab thus reducing the chances of making an error in the assignments.

UnRaid is not multi-monitor aware so I suspect it is going to be a case of trial and error. when the GPU is passed through to a VM it will control all 3 monitors anyway - as far as I know you cannot have one used by Unraid and 2 by the VM if they are all on the same GPU.

Currently looking at tidiest way to eliminate that happening without breaking the multi-language support.

Had a report of this happening after the latest update of the plugin a few days ago. Currently looking at tidiest way to eliminate it.

It did that because the disk was not part of any User Share.

No. The CRC error count is stored internally in the drive and never resets. It typically indicates a connection issue (e.g. power and/or SATA cabling) rather than a problem with the drive, and if that is rectified the best you can do is make it stop increasing.

Only 1 of the Sabrent devices is showing up in the SMART information so the other one is offline. There is no sign in the syslog that was ever seen at all as the system was booting so it may well have failed. It might be worth power-cycling the server to see if it comes back online, and if it does try starting the array and posting new diagnostics. FYI: the diagnostics includes the syslog so normally no need to post it separately.

That would explain things as the parity drive has no file system on it

I'll have another good look. At first glance I am not seeing this on my 6.10.0 test system but I guess there must be an issue somewhere with multiple reports. I want to do some code tidying anyway

If the preclear is still running this could be interfering with the file system check I think