itimpi

At this stage Unraid has already failed to mount the drive so you need to run with the -L option.

The message is correct as in the syslog the parity shows as Oct 5 13:03:57 Tower kernel: mdcmd (1): import 0 sdg 2048 3907017540 0 WDC_WD40EFAX-68JH4N1_WD-WX42D81H76FR Oct 5 13:03:57 Tower kernel: md: import disk0: (sdg) WDC_WD40EFAX-68JH4N1_WD-WX42D81H76FR size: 3907017540 whereas disk4 for instance reports as Oct 5 13:03:57 Tower kernel: mdcmd (5): import 4 sde 64 3907018532 0 WDC_WD40EFAX-68JH4N1_WD-WX42D914AEYX Oct 5 13:03:57 Tower kernel: md: import disk4: (sde) WDC_WD40EFAX-68JH4N1_WD-WX42D914AEYX size: 3907018532 an HPA on the parity disk would be the obvious suspect but you say you have checked for that so not sure what else to suggest.

Not sure what you mean by this? When you add a disk that is not pre-cleared before adding it then Unraid will perform a ‘Clear’ operation it to set it all zeroes. This is not an array rebuild.

You have to be able to pass through the USB drive to be able to run it under any emulator as the licence is tied to the USB drive. Not sure if Hyper-V can do this? You can successfully run Unraid under other emulators such as VirtualBox.

Those error messages normally indicate connection issues rather than a problem with the drive itself, so you should carefully check the power and SATA cabling to the drive is well seated.

You want to install the Unassigned Devices plugin via the Apps tab in Unraid. You will quite likely also want to install the Dynamix File Manager plugin as well if you want file management facilities integrated into the Unraid GUI.

No diagnostics zip file was attached

The rebuild process is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

Did you try restoring your docker container binaries via Apps->Previous Apps? This would be the normal next step which you seem to have omitted.

Technically the disk is shown as 'Disabled' rather than failed. This will happen if a write to it fails for any reason so that the data disks and parity are no longer in sync. You need to rebuild the disk to clear the disabled status.

The process is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

Every 5 seconds or so you are getting a message of the form: Oct 3 09:55:51 NasTerminal1 kernel: usb 9-2: new low-speed USB device number 15 using uhci_hcd Oct 3 09:55:51 NasTerminal1 kernel: hid-generic 0003:0764:0501.0011: hiddev96,hidraw2: USB HID v1.10 Device [CPS EC850LCD] on usb-0000:00:1d.3-2/input0 Oct 3 09:55:59 NasTerminal1 kernel: usb 9-2: USB disconnect, device number 15 Do you know what device this is?

Your syslog is being flooded with messages relating to USB device CPS EC850LCD which makes it impossible to use them to find anything useful in them.

Exclusive mode bypasses the Fuse layer in User Shares to give the same performance you can expect from using Disk shares, but with the advantage of still being able to use User Share features.

I do not think that Limetech have a way to do this other than go via Support once the years allowance is used up.

Once a new image is created then you can tick them off under Apps->Previous Apps to get all the ones earlier installed via the Apps tab automatically reinstalled with the previously used settings.

You have to have enabled Exclusive shares under Settings->Global Share settings, and addition there must be no remaining files and/or folders relating to the share on anything other than the pool set as Primary Storage.

There is (optionally) a step 8 where the appdata share is set to use Exclusive mode to improve performance..

That is weird If you can get to the login screen I would not have thought that it made any difference if you got there via hostname or IP address.

Have you changed any disks relatively recently and used the Parity Swap procedure to increase the size of the parity drive? If so then there have been reports of the process not correctly zeroing the part of the parity drive beyond the size of the largest data drive and it takes a correcting parity check to rectify this. FYI: When you run a correcting check then Unraid reports each sector corrected as an 'error' in the error count filed. The next check (of either type) should subsequently report 0 errors.

Support via the forums is primarily from other users - not from Unraid staff.

As far as I know at the moment if this happens you have to reboot to get things back to a working state.

Yes it might - difficult to tell. The tool I mentioned will change the permissions back to those Unraid expects.

I am surprised that it was needed to change the IP6 settings to be honest 😊

The ‘nobody’ user is normally the correct user. Have you tried running Tools->New Permissions against a share which has these problems.