Unraid problems

[trurl]

You didn't drill down far enough in your second screenshot, you missed one click, the

1 hour ago, trurl said:

Then click on shares.

Doesn't matter though, the other screenshot tells me what I wanted to know.

 

The cfg file is actually for a share named Tv Serier (which does not exist). The share you have is actually named TV SERIER, and it doesn't have a cfg file. Linux is case sensitive, so these are not the same thing.

 

Try this from the command line:

cd /boot/config/shares
ren Tv\ Serier.cfg TV\ SERIER.cfg
ls -lah

and post a screenshot of those results.

 

[Kjetil]

Is that one commant, or 3 separate commands ?

 

[itimpi]

2 minutes ago, Kjetil said:

Is that one commant, or 3 separate commands ?

 

3 commands

[Kjetil]

Thanks. This is the result. See photo enclosed.

[Frank1940]

Try this:

mv Tv\ Serier.cfg TV\ SERIER.cfg

 

[Kjetil]

Linux 4.19.88-Unraid.
Last login: Sun Dec 15 11:37:18 +0100 2019 on /dev/pts/0.
root@FederalReserve:~# mv Tv\ Serier.cfg TV\ SERIER.cfg
mv: cannot stat 'Tv Serier.cfg': No such file or directory
root@FederalReserve:~# 
 

[Frank1940]

My mistake.  (I forgot you are a total novice at comand line)

 

cd /boot/config/shares
mv Tv\ Serier.cfg TV\ SERIER.cfg

 

[Kjetil]

Sadly I am yes. Used to use Synology which have worked well without any knowledge of command line. 

Here is the new result.

[Frank1940]

I googled the error message/problem and it appears to be an issue with how the mounting is handled.  You are going to have to shut the server down, pull the flash drive, plug it into a PC and change the name there.  Watch the Capitalization when you do this!!!   (At the OS kernel  level, Linux recognizes 'case' and Windows does not!!!  So the names of 1.Txt and 1.txt are two different files to Linux and one file to Windows!)  You have to end up with that file being named  TV SERIER.cfg

Edited December 15, 2019 by Frank1940

[Kjetil]

Hi Frank. Shut down server, pull the 250gb SSD flash drive and connect to a pc - so far so good. Can I use a MAC for this or does it have to be a Windows machine ? Is it the file Tv Serier.cfg that needs to be renamed to TV SERIER.cfg ? Just find this file in OSX Finder and rename it ? Its my most important share, and I am super scared of doing something wrong, so that I loose this share... Is there anything that can go wrong ? Should I backup the Flash drive first ?

[Frank1940]

36 minutes ago, Kjetil said:

Should I backup the Flash drive first ?

Make the backup.  Doing that will guarantee that you never will need it!   😁  (One of Mr. Murphy's Laws)

36 minutes ago, Kjetil said:

Is it the file Tv Serier.cfg that needs to be renamed to TV SERIER.cfg

Yes

36 minutes ago, Kjetil said:

Can I use a MAC for this or does it have to be a Windows machine ?

I don't have a MAC but I assume it should work.  (With my limited knowledge of the orgin of the MAC OS, I suspect that it behaves much the same as Linux does.)  We are not doing brain surgery.  We are renaming that file.  If a mistake is made with a rename operation, One simply renames it again. 

 

The difference between how the Linux and Windows handles file names is at the OS level.  Windows masks (or ignores) the high order sixth bit in the byte for each character.  Thus at the Windows OS level, the file name you see as Media.iso, Windows will see as MEDIA.ISO.  Back in the DOS days (and Windows 3.1), you would type media.iso and it was actually stored as MEDIA.ISO.  The permitted file format was 8.3  ---  Eight characters for the file name and 3 characters for the extension.  When 'Long file names' were introduced, the whole thing was handled by smoke and mirrors as the actual/true file name was still (and being stored that way) in the 8.3 format.

Edited December 15, 2019 by Frank1940
Memory failing me these days...

[Kjetil]

Ok, I will give it a go

[Kjetil]

Mac says "this disc is not readable on this computer"

[Kjetil]

Cant MAC Osx read the flash disc ?

[Frank1940]

56 minutes ago, Kjetil said:

Hi Frank. Shut down server, pull the 250gb SSD flash drive and connect to a pc - so far so good.

What did you pull?  You want the UBS flash drive that you made when you created the boot drive.  (I suspect that you have is the server cache drive.)

Edited December 15, 2019 by Frank1940

[Kjetil]

Oh, sorry. Yes, pulled the cache. Now I have renamed Tv Series.cfg to TV SERIES.cfg. What to do next ?

[Kjetil]

The share TV SERIER still show a warning triangle with a ! inside (after rebooting again)

Edited December 15, 2019 by Kjetil

[Frank1940]

24 minutes ago, Kjetil said:

Oh, sorry. Yes, pulled the cache. Now I have renamed Tv Series.cfg to TV SERIES.cfg. What to do next ?

 

2 hours ago, Kjetil said:

Sadly I am yes. Used to use Synology which have worked well without any knowledge of command line. 

Here is the new result.

So what name did this file end up with?

[trurl]

Sorry I have been away. Yes I made a mistake trying to get that file renamed.

44 minutes ago, Kjetil said:

The share TV SERIER still show a warning triangle with a ! inside (after rebooting again)

Forget about the warning triangle on your shares for now. It just means some of their files have no redundancy because they are on cache instead of the parity array. When we get done you will still have some of those unless you install an additional cache drive.

 

Lets do this command again to see where we are:

ls -lah /boot/config/shares

 

[Kjetil]

[Kjetil]

This is what's show up now.

[trurl]

OK, that looks good. Post a new diagnostic so we will have the latest to work from.

[Kjetil]

Here is the latest diagnostics.

federalreserve-diagnostics-20191215-1918.zip

[Kjetil]

I don't understand about the cache. It says its 207GB of free space. So why would I need more cache drive (s) ?

[trurl]

Just now, Kjetil said:

I don't understand about the cache. It says its 207GB of free space. So why would I need more cache drive (s) ?

It is not about space, it is about redundancy. You can setup a mirrored cache pool. Then you wouldn't get those warning yellow triangles. Whether or not it is important to you we can decide later.