itimpi

Not quite sure why this is happening, but the names displayed in the screenshot on the Mac are the sort you get when the long filenames cannot be displayed and it reverts to the old DOS 8.3 version of the names.

Your 'system' share has files on disk1. This will keep disk1 and the parity drive spun up as disk1 is where the docker.img file is currently located. To get best performance you want this to be on the 'cache' pool. To get move to move these files to the 'cache' pool you need to follow the procedure documented 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. The Unraid OS->Manual section covers most aspects of the current Unraid release. Once you have all of the 'system' share on the 'cache' pool you can then set the Secondary storage for that share to 'None' and enable Exclusive Shares under Settings->Global Share settings to get best performance.

You can frequently get away with even less such as a small flash drive if you do not intend to store anything on it.

Are all of the machines having problems by any chance WiFi connected to the LAN? Asking because some routers have a setting that will stop WiFi connected devices from talking to wired connected devices.

It depends whether the onboard disk controller is a RAID one or not. If it is not then the drives should transfer transparently to a LSI card. If the current controller is a RAID one then you may have to do more work to get the data transferred to LSI connected dries.

5 Reallocated_Sector_Ct PO--CK 100 100 005 - 169 196 Reallocated_Event_Count -O--CK 100 100 000 - 169 These are never a good sign. If the number remains stable then you are probably OK, but if it keeps increasing then the drive will need replacing.

Yes - as long as all new checks keep reporting 0 errors.

This is expected as the Correcting check reports as 'errors' every sector it corrects. You might want to consider installing the Parity Check Tuning plugin. Even if you do not make use of its other features the Parity History entries will start being enhanced to give more information about the check such as whether it was correcting or not.

Click on the settings icon for a mount and set the Share option you may also need to set the global share options under Settings->Unassigned Devices.

You should raise this in the UD support thread then - I am sure it used to work.

Have you tried starting on the Shares tab and going from there and working exclusively with User Shares? The Dynamix File Manager will not let you use User Shares while you are in disk mode (and vice versa) This is by design to stop you doing things that can lead to data loss if you mix disk shares and user shares in the same operation.

You have something creating the ‘users’ folder under /mnt. You need to identify what is doing this and correct it.

Is there any reason it cannot be mounted via Unassigned Devices? If it can then that would enable it be shared.

There should basically be little problem assuming you have sufficient SATA ports to have all drives connected and you are within your Unraid licence limits (the 3 new drives takes you to 8). The only caveat is that since no data drive can be larger than the smallest parity drive you would need to make the 5TB drive a parity drive (releasing the 4TB it replaces). This section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page will probably help. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

You should get an automated acknowledgement if your request got through, so if you did not you need to try again.

There is no GUI support for disabling a plugin without uninstalling. you can do it manually by renaming the relevant .plg file on the config/plugins folder on the flash drive to have a different file extension (e.g .plgx) and then rebooting.. Reversing the process re-enables the plugin. Advantage is any downloaded files and/or settings for the plugin remain intact on the flash drive.

5 Reallocated_Sector_Ct PO--CK 096 096 010 - 19368 197 Current_Pending_Sector -O--C- 100 100 000 - 56 198 Offline_Uncorrectable ----C- 100 100 000 - 56 These definitely do not look good so the disk should be replaced. You should be able to as it looks as though disk1 is being emulated successfully by the combination of disk2 + parity. Note that if another array drive fails before a successful replacement you could end up with data loss, so what is the state of your backups? Surprised, also, by how little data there is on your drives as you say it has been running Unraid for some time.

What type of SMART errors? Some errors (e.g. CRC errors) can mean the disk itself is fine but there is an issue with the cabling or power.

It probably is when we can spot the culprit 🙂

What type of SMART errors? You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. Also which drive are you talking about?

Never seen that message reported before. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

In the status bar at the bottom. i have said for a long time it should be added to the icons at the top right of the GUI to make it more prominent and missed less often.

Pressing the option in the GUI to get to the online manual is available but nobody seems to want to use it.

With trial keys you have to reassign all the drives if you want to get the config on another drive. This means do not copy the super.dat file in the config folder from the old flash drive to the new one.

The CRC errors are connection errors rather than disk errors and as long as they stay basically stable can be ignored (they never get reset to 0).