MinimServer: no valid content directory found

[fantasia]

Dear Simon

I'm happy to tell you that I'm setting up a new media server.

but somehow my excitement has sunk to a crawl.

Problem:
The server doesn't perform an automatic rescan after starting up.

A manual rescan solves the problem, but that can't be a solution for long-term use!

The MinimServer starts automatically on Ubuntu Desktop 24.04 LTS.
The music SSD is correctly mounted and in operation.
The path of the audio files is also correct.
A delayed start of 15s unfortunately didn't improve things.

Now I'm dependent on your support.
Attached are the log from the server.

Best regards
fantasia

[mminga]

Sometimes the volumes may be not mounted.
You could use a startup delay.

[simoncn]

To delay MinimServer startup by 10 seconds when you reboot your system, set the delayStart property to 10. You can adjust this value up or down as needed. This should solve the problem.

[fantasia]

(22-08-2024 21:00)simoncn Wrote:  To delay MinimServer startup by 10 seconds when you reboot your system, set the delayStart property to 10. You can adjust this value up or down as needed. This should solve the problem.

Hello

Many thanks for the tip, which I tried before opening this thread.

Unfortunately, a start delay of 10s doesn't help at all.

Perhaps it would be better to store the music archive on the system SSD instead of a separate second SSD?

I won't give the minimserver much more time, as this very annoying problem has already taken up far too much time and nerves.....

[simoncn]

My apologies for not noticing that you had already tried delaying startup by 15 seconds.

I think this means you need a longer delay time. Please try increasing the delay time to 60 seconds to see if the music SSD is available after this time. If this works, you can reduce the time to find out how much delay is needed. How is the music SSD attached? Is it a USB connection?

Also, I think your other suggestion of putting the music library on the system SSD should solve the problem.

[fantasia]

(23-08-2024 21:03)simoncn Wrote:  My apologies for not noticing that you had already tried delaying startup by 15 seconds.

I think this means you need a longer delay time. Please try increasing the delay time to 60 seconds to see if the music SSD is available after this time. If this works, you can reduce the time to find out how much delay is needed. How is the music SSD attached? Is it a USB connection?

Also, I think your other suggestion of putting the music library on the system SSD should solve the problem.

Thank you very much for your great motivation and support, I really appreciate it!

The installed music SSD is a WD Black SN770 2TB in M.2 format. Before installing it, I installed the latest firmware.

The test with the WD tool was positive, so you can assume that it is 100% OK.

the SSD is listed in the file browser and is always available when accessing the folder.

Unfortunately, a start delay of 30 seconds does not improve things.

The server cannot find the album path even with a rescan.

With the help of an audio professional, we have come to the conclusion that the problem is most likely due to the Ubuntu server 24.04 LTS - a bug, so to speak!!

But perhaps it could also be due to the minimserver, which does not work satisfactorily with the latest version 24.04 LTS?!

Perhaps you could test the minimserver on the latest Ubuntu version to solve the problem?


I would be delighted to receive your feedback.

Best regards

[simoncn]

I do have a test installation of Ubuntu 24.04 LTS. This is working for me with the music library on the main system disk. I don't have a machine that supports M.2 drives but I could try adding a second SATA drive to see whether that works.

Your earlier post said a manual rescan after booting was working. In your latest post I think you are saying this is not working. Please clarify.

What is the exact path you are using in contentDir for your music folder on the M.2 drive?

Is it possible that the music folder on your M.2 drive doesn't have the right permssions to make it accessible by the MinimServer process?

[fantasia]

(24-08-2024 12:59)simoncn Wrote:  I do have a test installation of Ubuntu 24.04 LTS. This is working for me with the music library on the main system disk. I don't have a machine that supports M.2 drives but I could try adding a second SATA drive to see whether that works.

Your earlier post said a manual rescan after booting was working. In your latest post I think you are saying this is not working. Please clarify.

What is the exact path you are using in contentDir for your music folder on the M.2 drive?

Is it possible that the music folder on your M.2 drive doesn't have the right permssions to make it accessible by the MinimServer process?

Hello Simon

Hmm, that's very interesting that it works for you with version 24.04!

If you have a second SSD, you could test whether it would work as a music archive.

Yes, it's tricky, at the beginning the manual rescan worked but somehow it doesn't work anymore.

Perhaps you could test my NUC server via Teamviewer?

The path is as follows.
/media/andre/audio

The permissions are set as on the print screen that the server specified during installation.

[simoncn]

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.

[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.

Thank you very much for the tip.

I deliberately formatted the SSD as an exfat partition so that I can access the files on the music drive in Windows via a samba network share to copy or delete new music.

perhaps reformatting with mbr could actually solve the problem?!

mbr is quite possible under the 2TB limit.

The proof of the pudding is in the eating.

If it works with exfat, I would have solved the problem, including the samba share with Windows.

Since ext4 is a pure Linux format, it should only be used for Linux-based systems, that's my opinion.

Best regards