Posts by dougdee123

That does indeed seem to be the problem.

Thanks very much for your comment. I am most grateful to all who tried to help.

I'm now scanning some libraries and we'll see if normal service is resumed.

I don't think I did.

It does seem likely that you are right.

I'll be trying to fix that.

Update to the problem I'm having.

The jellyfin logs are not helping at the moment. They refer to scanning the libraries in less than a minute meaning that the instance of the server is not accessing the real array.

The problem seems to be in the configuration of the server.

A version of Jellyfin is running

root@newbox:~# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

1fa1cb3efea9 lscr.io/linuxserver/jellyfin:latest "/init" 4 months ago Up 12 hours 0.0.0.0:8096->8096/tcp, [::]:8096->8096/tcp, 8920/tcp jellyfin

However if I look at the services - compose -containers I find that the disks mounted refer to the previous, older and smaller, RAID Array. The UUID is different.

jellyfin
lscr.io/linuxserver/jellyfin:latest
running
Up 12 hours
link
0.0.0.0:8096->8096/tcp

[::]:8096->8096/tcp

8920/tcp
fe40ec79816f808eacc367f358be3579a1d6744242341136811fd2b470775413

/srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/configs

/srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/Multimedia/Movies

/srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/Multimedia/Music

/srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/Multimedia/TV Shows

By contrast the storage shared folders are

Multimedia /dev/md0 Multimedia/ /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/Multimedia/ Available

appdata /dev/md0 appdata/ /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/appdata/ Available

compose /dev/md0 compose/ /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/compose/ Available

configs /dev/md0 configs/ /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/configs/ Available

I can't see how to correct the reference in the GUI so I take it that I'll have to do it in the CLI.

Thanks once again for your help. It really is much appreciated.

I corrected the '/configs' to 'config' but unfortunately it wasn't the only problem.

I then executed

root@newbox:~# systemctl status docker

● docker.service - Docker Application Container Engine

Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)

Drop-In: /etc/systemd/system/docker.service.d

└─waitAllMounts.conf

Active: active (running) since Mon 2026-02-09 20:15:24 GMT; 6min ago

TriggeredBy: ● docker.socket

Docs: https://docs.docker.com

Main PID: 717 (dockerd)

Tasks: 24

Memory: 144.3M

CPU: 2.148s

CGroup: /system.slice/docker.service

├─ 717 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

├─1865 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8096 -container-ip 172.18.0.2 -container-port 8096 -use-listen-fd

└─1871 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8096 -container-ip 172.18.0.2 -container-port 8096 -use-listen-fd

Feb 09 20:15:16 newbox dockerd[717]: time="2026-02-09T20:15:16.498222865Z" level=info msg="Deleting nftables IPv4 rules" error="exit status 1"

Feb 09 20:15:16 newbox dockerd[717]: time="2026-02-09T20:15:16.517755257Z" level=info msg="Deleting nftables IPv6 rules" error="exit status 1"

Feb 09 20:15:21 newbox dockerd[717]: time="2026-02-09T20:15:21.686914881Z" level=info msg="sbJoin: gwep4 ''->'69220a3445fa', gwep6 ''->''" eid=69220a3445fa ep=jellyfin net=jellyfi>

Feb 09 20:15:22 newbox dockerd[717]: time="2026-02-09T20:15:22.543206511Z" level=info msg="Loading containers: done."

Feb 09 20:15:24 newbox dockerd[717]: time="2026-02-09T20:15:24.199179404Z" level=info msg="Docker daemon" commit=6bc6209 containerd-snapshotter=false storage-driver=overlay2 versi>

Feb 09 20:15:24 newbox dockerd[717]: time="2026-02-09T20:15:24.207235501Z" level=info msg="Initializing buildkit"

Feb 09 20:15:24 newbox dockerd[717]: time="2026-02-09T20:15:24.597400493Z" level=info msg="Completed buildkit initialization"

Feb 09 20:15:24 newbox dockerd[717]: time="2026-02-09T20:15:24.658920563Z" level=info msg="Daemon has completed initialization"

Feb 09 20:15:24 newbox dockerd[717]: time="2026-02-09T20:15:24.659848656Z" level=info msg="API listen on /run/docker.sock"

Feb 09 20:15:24 newbox systemd[1]: Started docker.service - Docker Application Container Engine.

That seems to be ok.

However

systemctl status compose

Unit compose.service could not be found.

So clearly there is a problem with compose.

I saw that Cterm is a requirement so I checked and the plugin

openmediavault-cterm 7.8.7 is installed.

Also the plugin

openmediavault-compose 7.6.13 is installed.

I recently asked for help with increasing the size of my RAID5 array and thankfully , through the generous time donated by mods and others, I was able to grow the array as required.

I then had an extended period of reloading about 4.5 Tb of media from rather flakey drives and as a result was unable to test the Jellyfin server that is the raison d'etre of the whole system.

Previously the server worked and served to a chrome browser, a Roku 4K and an LG 4k TV. Since the fixing the storage issues I am not able to make any of these work.

Under the GUI it says that Jellyfin Server is up and running.

The server works in a docker container installed by Compose. The yaml file is as below.

---

version: "2.1"

services:

jellyfin:

image: lscr.io/linuxserver/jellyfin:latest

container_name: jellyfin

environment:

- PUID=1000

- PGID=100

- TZ=Europe/London

volumes:

- /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/configs:/configs

- /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/Multimedia/TV Shows:/data/tvshows

- /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/Multimedia/Movies:/data/movies

- /srv/dev-disk-by-uuid-a57c4783-5c3d-46f9-bf7e-62ceed7e6cf2/Multimedia/Music:/data/music

ports:

- 8096:8096

restart: unless-stopped

This is similar to the previous file that worked correctly except for the alteration to point at the revised disks.

On both chrome client and the LG TV you can log into the server and select a movie but get a message that says 'Playback error This Client is not compatible with the media and the server is not sending a compatible media format.' If I attempt to rescan all the media it jumps to 98.6 % but does not actually change anything. I suspect that it is finding a residual database from the earlier installation. I also find that the error message is associated with transcoding and that the server should find jellyfin-ffmpeg at /usr/lib but it is not there.

If anyone can cast some light on this I will be very grateful. I had understood that running the yaml file did install the latest version but clearly not.

Doug

ThTThishis Thi Ths client isn't compatible with the media and the server isn't sending a compatible media format.client isn't compatible with the media and the server isn't sending a compatible media format.

I thought I would provide an update on this because, although I'm making progress, I'm not there yet. Partly because of the problem and and partly because I had a hardware failure of the machine I was using to access the server. I had a PSU failure and yes, of course, that was the machine that I had the server backups on.

Anyway, I installed the new disks in the server then wiped each of them and formatted them to EXT4. That took about 1.5 hours for each disk.

I then discovered that after previously upgrading to 7.x the plug in for Multi disk was missing. I reinstalled that and set it off to create the array using all four of the disks. That then took about 15 hours to resync and left me with the message in Multiple Device

/dev/md0 clean Raid5 16.37Tib /dev/sda

/dev/sdb

/dev/sdc

/dev/sdd

I then mounted md0 in the File systems and it now shows as mounted but not referenced. In addition I have an entry for an unnamed device that is showing as referenced but not mounted. I cant see how to remove that either but I may be able to get rid of it when I have the shared folders rpointing at the correct

I did then change the shared folders and pointed them at the new /dev/md0 .

And I find that, on checking that the shares are available on the network and that it must have worked.

Thanks again to those that gave their time to helping. It really is very much appreciated. For myself I'm finding that I just don't try things frequently enough to be able to do this with out the hand holding that people on the forum generously provide.

Doug

That's a good idea.

I had not thought of that because I haven't had the experience.

I'll give that a try. At worst I may still have to clone but if it is as simple as you say then it will save a lot of time and effort.

I'll let you know what happens.

Doug

Hi,

Thanks also for your help.

No, I made a backup of all the data before I started since I realised that it could all go wrong very easily.

I also upgraded to 7.x so there was even more incentive to have method of retrieving the situation if necessary. I was and am not confident in reconfiguring the system disk such that everything continues to work but if necessary I could do it all over. I thought naively that it would be simpler to maintain the existing config rather than start again.

I take your point over keeping the old disks safe.

I have decided to take the low risk approach of cloning the old disks to the new disks off line and then adjusting the partitions and then growing them.

Doug

On consideration I'm wondering whether it might be better to clone the disks in the array using clonezilla or some other variant. It would be a complete pain and take forever but might be less of a risk.

I would still prefer Plan A (I think).

Hi,

Thanks for responding.

(1)The whole reason for the post is that I can't find such a control in the GUI for Ver 7.x. Hence the thought about removing a disk. I have every intention of doing so in a controlled manner that doesn't damage anything. Where is the control in your installation?

(2) I also do realise that the HP is not hot swap and I'm not going to risk damaging anything . I was hoping, however, that by powering off and then rebooting that it would detect the empty disk and realise that it was a replacement. I can wipe the new disk from the GUI. Will that let me designate the new disk as part of the array?

Hardware is HP N54 microserver

I am facing the perennial problem of replacing the disks in my Raid 5 array because I'm running out of capacity.

The existing disks are 4 x 2Tb Western Digital types that have been installed for 5 years. The array has an 80% utilisation. I want to replace them with 4 x 8Tb Toshibas.

I see in various threads that discuss Raid5 the need to 'fail' one of the discs causing the array to be degraded. Other references suggest that this can be done by selecting a disk and failing it under the GUI. I can't see how that can be done.

The only other way I can see of doing this is to power down the server and remove one of the discs. The array would then, on power up, presumably be there in a degraded state hopefully without errors (clean). If I then fit the shiny new disc will it start to rebuild itself or is there something else I need to do? Can I fit the new disk immediately after removing the old one or is it necessary for the system to reconfigure itself in the degraded mode before fitment.

I understand that the method would have to be repeated for the remaining old disks after recovery and finally to grow the array to take advantage of the new space.

I recognise the possibility that I'm over thinking this and would welcome some guidance.

Doug

Thanks very much to all.

I understand now that the problem was with the definitions of the folders for the storage of the config files and backup \nd the statement of the top level of the data folder. The thing that gave rise to the issue was me being confused by the reference to shared folders when , as far as I knew , I already had shared folders that had media content.

Operator Error once again.

I will now try and do the installation.

Yes, I have read it.

I will read it again. I find that there are folders remaining from an earlier installation of docker that used portainer. However I have indeed enabled the docker repo and when running docker info find that it is installed but there are no existing containers.

Thanks for taking an interest in my problem.

Unfortunately the immediate problem of 500 - Internal Server Error means that I am unable so far to run the script to install Jellyfin and can't therefore can't show the items noted. It isn't installed so they don't exist.

What I need to start with is resolving the error.

Hi,

I am trying to install Jellyfin in a docker container.

The system is an HP Microserver with a Raid Array (Raid 5) and a flash drive for the system drive. I had a power failure and was unable to access the system disc either through the web interface or by putty. I therefore did a new install by disconnecting the raid disks , installing the system software and then reconnected the Raid drive. All the data survived. It was and is backed up elsewhere.

The problem now arises that I'm trying to install Jellyfin using Compose. If I try to Compose - > Files I get an error message 500 - Internal Server Error. Please Set Shared Folder for Storage. I'm not even slightly clear what this relates to. The Raid drive (and all the content) is shared and visible on the network. I have a configs folder that I was expecting to hold the configuration although this was created from the network. Although I have modified the Jellyfin scriptfile to reflect my raids name and absolute path and media Folder Names I am unable to execute it because the same 500 - Internal Server Error message is repeated.

For information Here are the shared folders defined. Not all are related to this Jellyfin attempt.

Multimedia outershare Multimedia/ /srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/Multimedia

appdata outershare appdata/ /srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/appdata

configs /dev/sde1 configs/ /configs

henrybox outershare henrybox/ /srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/henrybox

media outershare media/ /srv/dev-disk-by-uuid-8fc91b13-eebb-4b11-a928-5df2860e3bc1/media

I would really be very grateful for any help.

After deleting Ouroboros everything stay up so clearly that was the problem.

Thanks for the suggestions.

Doug

I'm trying to install Jellyfin Media Server. I also previously tried to install Plex.

I'm trying to use Portainer but it exits by itself at approximately 2.00 am. This is arrived at indirectly. The system message for Portainer says that it exited '14 hours ago' putting it at about 2.00 am. Also the Jellyfin log shows that it is attempting various trigger fired updates. Jellyfin itself is not working because the configuration is not yet solved.

Unfortunately, when Portainer exits it appears to get rid of its logs or at least I can't find them. The only thing I can then do is to install Portainer again. When it re-installs I can again access the docker containers..

If anyone has suggestions I'll be most grateful.

It might be worth saying that I installed Ouroboros so it may be trying to update containers. I'm going to stop it now to see if that also stops Portainer exiting.

D

Thank you very much.

That has worked exactly as you suggest and the recovery percentage is inching up. Hopefully tomorrow will see it fixed.

I really am most grateful. Otherwise I would have had to go back to the start and re-install from scratch with some backups that are a wek or two out of date.

Best Regards,

Doug

I tried assembling with Sdb, Sdc and Sdd.

root@newbox:~# mdadm --assemble /dev/md127 /dev/sd[bcd]

mdadm: Unknown keyword INACTIVE-ARRAY

mdadm: /dev/sdb is busy - skipping

mdadm: /dev/sdc is busy - skipping

mdadm: /dev/sdd is busy - skipping

Best Regards,

Doug

Thanks very much for your input. I see what you are saying. and I changed the input strings but unfortunately they both still fail because there is no superblock on sda.

root@newbox:~# mdadm --assemble /dev/md127 /dev/sd[abcd]

mdadm: Unknown keyword INACTIVE-ARRAY

mdadm: no recogniseable superblock on /dev/sda

mdadm: /dev/sda has no superblock - assembly aborted

root@newbox:~# mdadm --assemble --force /dev/md127 /dev/sd[abcd]

mdadm: Unknown keyword INACTIVE-ARRAY

mdadm: no recogniseable superblock on /dev/sda

mdadm: /dev/sda has no superblock - assembly aborted

I might, however, try it using the remaining three disks sdb, sdc and sdd. That might then re-instate the array albeit in a degraded state.

Thanks again,

Doug