OMV6 Issues

If you create a task, cannot select the WDC drive WD20EFRX-68EUZN0 that is in /dev/sdb?

Okay, let's do it in CLI.

type

smartctl -a /dev/sdb

and post the output.

Quote from BigWinnie

how can I copy the output to my local clipboard?

Select the text with the mouse and press ctrl+c

Then paste it into the code box with the mouse or with ctrl+v

There is something that escapes me. The results returned by smart appear to be fine, however in the GUI image the status is warning.

Ok, I know what it is. I assume you have rebooted. That disk is now in /dev/sda.

Repeat the command with

smartctl -a /dev/sda

and post the result again

Quote from lyned

I am not really concerned about DLNA as I prefer to use network share access - it works better

How

Quote from lyned

In this case software has not moved forward, it has moved backwards

Solely based on the fact that your TV cannot locate the shares on the network

Quote from lyned

There is a fundamental change between OMV5 and OMV6 which has blocked my previous happy system

You are basing that on what, you are failing to understand just because your 'happy system' in V5 doesn't function the same in V6 it's down to OMV when in fact your problem is Samba (SMS/CIFS) something that omv has no control over.

Quote from lyned

If nobody can offer a solution or at least some ideas to try I will revert to OMV5 with which I had no problems

V5 is EOL as is Debian 10 which it is based upon.

________________________________________________________________________

Suggestion, not a solution, have a look in the SMB/CIFS section on here, there is possibly an option that can be added to extra options in OMV's SMB settings, as the probability is that your TV cannot communicate with the current Samba version being used on OMV.

The issue here is, no one knows anything about your "SMART TV".

Here's a bit of speculation on this topic:
Most of these "smart" devices are "propriety" so the OEM's don't feel obligated to publish tech spec's. They, instead, publish an overview of features to hook consumers into buying them. After that, they don't care. (And at the time of purchase, an overwhelming percentage of consumers don't care either.)
I do know that, rarely (if ever) do the OEMs put out firmware upgrades for these devices and it's even more rare for users to apply them. So,,, the software/firmware tends to go out of date in a few years. Since the software world doesn't stand still, before long, these SMART devices are in the computing stone age.
____________________________________________________________

Here's a speculative fix, that may or may not work, because nothing of substance is known about the TV.

Under Services, SMB/CIF, Settings, at the bottom there's an extra options field.

Try the following:

max protocol = SMB3

Then, on the CLI:

service smbd restart

If it's an SBC:

sudo service smbd restart

Or you can simply reboot.
___________________________________________________________

If the above doesn't work, you might try:

max protocol = SMB2

Quote from crashtest

The issue here is, no one knows anything about your "SMART TV"

Surely the issue here is that our crystal balls haven't been updated