MinimServer: no valid content directory found

[simoncn]

If you are accessing the files in Windows via a samba network share hosted on your Linux system (the normal practice), the disk should be formatted for Linux and not for Windows. If you want to attach the disk directly to a Windows machine, you would need exFAT for that.

When copying files between Windows and Linux, you need to be careful with accented characters in filenames. Linux needs these to be encoded using UTF-8. Windows might be using Windows-1252 for the encoding.

[fantasia]

(24-08-2024 22:00)simoncn Wrote:  If you are accessing the files in Windows via a samba network share hosted on your Linux system (the normal practice), the disk should be formatted for Linux and not for Windows. If you want to attach the disk directly to a Windows machine, you would need exFAT for that.

When copying files between Windows and Linux, you need to be careful with accented characters in filenames. Linux needs these to be encoded using UTF-8. Windows might be using Windows-1252 for the encoding.

Hello Simon

ah ok, then I will format the hard drive with ext4 as this works within the Linux server.

then install the samba server.

I will let you know whether the minimserver runs perfectly after the reformatting.

see you soon.

[fantasia]

(24-08-2024 18:21)simoncn Wrote:  I have done this test and it is working for me. My second drive is formatted as Master Boot Record, Contents Ext4, Partition Linux (Bootable). From your screenshot, your drive is GUID Partition Table, Contents Unknown, Partition Type Microsoft Reserved. Also, the partition is only 17 MB in size.

I suggest you reformat the 2TB disk from scratch as a 2TB Ext4 partition, removing all current contents and copying them back after the reformat.

In the meantime I have formatted the SSD with ext4 and unfortunately the minimserver still doesn't work.

Now I have discovered something strange.

No matter how the created folder is labeled, the same folder path is given in the file browser, that can't be right!!

What could be the reason for this?

[stefano_mbp]

(25-08-2024 09:21)fantasia Wrote:  No matter how the created folder is labeled, the same folder path is given in the file browser, that can't be right!!

What could be the reason for this?

The path for both folders is the same …
In your example you have
- media
— andre
—- audio
—— Music
—— test
Therefore the path for both Music and test folders is /media/andre/audio

[fantasia]

(25-08-2024 10:09)stefano_mbp Wrote:  

(25-08-2024 09:21)fantasia Wrote:  No matter how the created folder is labeled, the same folder path is given in the file browser, that can't be right!!

What could be the reason for this?

The path for both folders is the same …
In your example you have
- media
— andre
—- audio
—— Music
—— test
Therefore the path for both Music and test folders is /media/andre/audio

Hello Stefano

ak ok so that's normal.

Now the search continues....

I'm going to test whether the server can find the path on the installation SSD!

This is connected via m.2 SATA.

If that works then it could be the NVMe interface?!

[fantasia]

bingo

The server finds the music archive on the system SSD straight away without any startup delay!

This could be due to the NVMe interface or the limited access to NVMe drives.

It would be interesting to know whether access to a 2TB 2.5" SATA SSD would be possible?!

Maybe someone knows how to proceed?

Many thanks in advance.

[simoncn]

My test used a 500 GB SATA 2.5" HDD. I am confident that a 2TB 2.5" SATA SSD would also work if formatted correctly.

[fantasia]

Hello Simon

I also think that a 2TB 2.5" SSD will work.

However, the future belongs to M.2 nvme SSDs.

Since the 2tb nvme ssd works perfectly in Ubuntu, I have to assume that the MinimServer has trouble recognizing such SSDs!

That's why I'm asking you to optimize MinimServer in this regard.

I'm happy to test an update and give you my feedback.

For the time being, I won't remove the nvme ssd, as I bought it specifically for this purpose.

I'm really looking forward to your feedback and even more to the update.

All the best

[simoncn]

MinimServer uses standard Linux API calls to access directories and files. The operating system (Ubuntu) is responsible to making these APIs work correctly on different types of hardware.

In post #6 you said that MinmServer runs perfectly with Ubuntu 22.04 LTS. If Ubuntu 22.04 LTS works when MinimServer accesses your M.2 NVMe drive, this shows that MinimServer does not have a problem accessing NVMe drives.

One possible cause of this problem is a bug in Ubuntu 24.04 LTS as you suggested in post #6. Another possibility is that some configuration setting on your Ubuntu 24.04 LTS installation (either in Ubuntu or MinimServer) is causing the problem.

Please post your MinimServer configuration settings for the contentDir property with your music library on the NVMe drive on Ubuntu 24.04 LTS. When I have this information, I will suggest further steps for problem determination.

[fantasia]

Hello Simon

I believe you that the minimserver works with nvme ssds.

I've tested it again and found that the manual rescan rarely works.

But after a short time it stopped working (next boot)

I'm now pretty sure that the problem is with Ubuntu 24.04.

I haven't tested version 22.04, but I'm an audiophile user, but I have an external USB HDD.

If you have time, you could take a look at it via teamviewer.

I could send you the number and password via PM