Posts by Nefertiti

Well I followed the guide from @STUKguy but I am stuck right away at select pool I do not have default just saying select pool but no default in red square

I am aware it is still in beta but is there a guide somewhere?

The system disk getting almost full log is 20g and crashing not sure why?

root@openmediavault:~# du -d1 -h /var/
2.7G    /var/lib
20G     /var/log
4.0K    /var/local
124K    /var/spool
4.0K    /var/mail
4.0K    /var/opt
20M     /var/www
2.3M    /var/backups
20K     /var/tmp
130M    /var/cache
22G     /var/

ls -s log
total 20081556
      0 alternatives.log        636 daemon.log.2.gz      748 kern.log.2.gz         8 mail.log              0 monit.log                148 pihole.log.2.gz               104 syslog.2.gz
     64 alternatives.log.1      376 daemon.log.3.gz      652 kern.log.3.gz        36 mail.log.1            4 nginx                    368 pihole.log.3.gz                32 syslog.3.gz
      4 apt                     292 daemon.log.4.gz      444 kern.log.4.gz         4 mail.log.2.gz         4 openmediavault           836 pihole.log.4.gz                20 syslog.4.gz
     92 auth.log                 40 debug                  8 lastlog               4 mail.log.3.gz         4 php7.3-fpm.log           804 pihole.log.5.gz                24 syslog.5.gz
    336 auth.log.1               24 debug.1                4 lighttpd              4 mail.log.4.gz         4 php7.3-fpm.log.1           4 pihole_updateGravity.log       96 syslog.6.gz
     16 auth.log.2.gz            20 debug.2.gz             4 mail.err              8 mail.warn             4 php7.3-fpm.log.2.gz        4 private                        16 syslog.7.gz
     28 auth.log.3.gz            12 debug.3.gz            16 mail.err.1           36 mail.warn.1           4 php7.3-fpm.log.3.gz        4 proftpd                         4 tallylog
     20 auth.log.4.gz            12 debug.4.gz             4 mail.err.2.gz         4 mail.warn.2.gz        4 php7.3-fpm.log.4.gz        0 rsync.log                       8 user.log
      0 bootstrap.log            16 dpkg.log               4 mail.err.3.gz         4 mail.warn.3.gz        4 pihole                   796 rsync.log.1.gz                 32 user.log.1
      0 btmp                    420 dpkg.log.1             4 mail.err.4.gz         4 mail.warn.4.gz       40 pihole-FTL.log            56 rsync.log.2.gz                  4 user.log.2.gz
      4 btmp.1                    4 faillog                8 mail.info       6678264 messages              8 pihole-FTL.log.1         192 rsync.log.3.gz                  8 user.log.3.gz
      4 chrony                    0 fontconfig.log        36 mail.info.1         600 messages.1            4 pihole-FTL.log.2.gz        4 salt                          176 user.log.4.gz
      4 cron-apt                  4 installer              4 mail.info.2.gz      720 messages.2.gz         4 pihole-FTL.log.3.gz        4 samba                           4 watchdog
   2784 daemon.log          6678304 kern.log               4 mail.info.3.gz      628 messages.3.gz      1096 pihole.log               364 syslog                        236 wtmp
  21676 daemon.log.1            592 kern.log.1             4 mail.info.4.gz      428 messages.4.gz     10516 pihole.log.1         6677028 syslog.1

Well so far I changed the permissions for /etc/nvidia-container-runtime/config.toml and rebooted so far so good

I f I create a container Emby or Plex I can have it running with NVIDIA driver no problem but if i want to recreate the same one by modifying a parameter or sometime even not: just trying to recreate the same container, it will crash right away with errors, except if I disconnect it from NVIDIA in runtime resource tab . I spent all day trying to solve it but it is beyond me although I am thinking maybe about a permission issue at the driver level?

Any help would be appreciated

May  1 17:03:32 openmediavault dockerd[898]: time="2021-05-01T17:03:32.014912187-07:00" level=error msg="a3a1f08c3c071287c2d9741a71cf1ebbc70028b6d1fa5c7d9ab08ec5e0076d88 cleanup: failed to delete container from containerd: no such container"
May  1 17:03:32 openmediavault dockerd[898]: time="2021-05-01T17:03:32.014931051-07:00" level=error msg="Handler for POST /containers/a3a1f08c3c071287c2d9741a71cf1ebbc70028b6d1fa5c7d9ab08ec5e0076d88/start returned error: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #1:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: ldcache error: process /sbin/ldconfig.real failed with error code: 1: unknown"

My experience with aisonic/ airsonic it will fail if you do not assign folder for music podcast ,playlist,and config of couse as example I do not care about playlist or podcast but if you do have the volumes pointing at the folder even empty, it wont work.

The only small issue remaining and slowing down the booting process I got

so I think some library missing oh well

Quote from macom

To revert the delay of docker:

systemctl revert docker.service

root@openmediavault:~# systemctl revert docker.service
Removed /etc/systemd/system/docker.service.d/override.conf.
Removed /etc/systemd/system/docker.service.d.

Quote from cubemin

Now make sure you check the /lost+found folder on your drive, as any files you may find missing will be there.

3 pieces one big I just added .mkv to the name #75825883 and it became a 2 h movie.

Very cool everything is fixed

Now the disk is mounting automatically no need for delay anymore and I leaned a lot great

root@openmediavault:~# fsck /dev/sdd1
fsck from util-linux 2.33.1
e2fsck 1.46.2 (28-Feb-2021)
WD-10TB_8 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 75825882
Connect to /lost+found<y>? yes
Inode 75825882 ref count is 2, should be 1.  Fix<y>? yes
Unattached inode 75825883
Connect to /lost+found<y>? yes
Inode 75825883 ref count is 2, should be 1.  Fix<y>? yes
Unattached inode 75825884
Connect to /lost+found<y>? yes
Inode 75825884 ref count is 2, should be 1.  Fix<y>? yes
Unattached inode 75825885
Connect to /lost+found<y>? yes
Inode 75825885 ref count is 2, should be 1.  Fix<y>? yes
Unattached inode 75825886
Connect to /lost+found<y>? yes
Inode 75825886 ref count is 2, should be 1.  Fix<y>? yes
yyPass 5: Checking group summary information

WD-10TB_8: ***** FILE SYSTEM WAS MODIFIED *****
WD-10TB_8: 25149/305201152 files (0.1% non-contiguous), 1141008771/2441608955 blocks
root@openmediavault:~#

Actually and I don't know if it is related in the log, for the disk in question witch is not the boot drive, I got

so How do I fix it It?

and I tried:

Quote from macom

Probably. You can start docker with a delay:

systemctl edit docker.service

paste

Code

[Service]
ExecStartPre=/bin/sleep 30
StartLimitIntervalSec=300s

save

Exactly what I need it .

Thank you

Yes this is working perfectly

What I don't understand why I do it manually in files system it mount without asking to confirm the yellow warning?

Edit

Well doing this way I am loosing the permissions for Emby to see the files. First time it got changes to owner root second it did not change but I have to recreate the container in order for Emby to see the files I think maybe the container start before the disk got mounted?

Yes I am using wild card for more than 2 years with no issues

Still having the issue after reboot I need to go right away to files system to mount the drive manually , this is a big problem since I got some media files on it and if Emby container would not see the drive it erase the library! so in the meantime I had to setup its restart policy to none

Any solutions?

Well after few try, I succeed to upgrade the driver doing the installation again, at some point got a mismatch kernel, I let it finish the step of the install, rebooted right after, and finished the rest of the install witch went perfectly.

Got more NVIDIA upgrade in the upgrade management so I clicked install and even after rebooting it was no issue what so ever.

Case closed

Well Actually regarding Emby it was a permission issue and I took care of it, but the remaining problem, the drive does not mount at reboot?

Out of the blue one of my disk became unmounted so I clicked mount it show mounted right away but the yellow sign "The configuration has been changed. You must apply the changes in order for them to take effect." does not show up. Although I can access it with smb Emby cannot scan the directory on it

So what is the problem there ?

I installed the NVIDIA drivers by following the guide [HowTo] Nvidia hardware transcoding on OMV 5 in a Plex docker container was working perfect, until the update management decided to upgrade the driver from Nvidia driver 460.39 to 460.67 after reboot the drivers is not working anymore Emby containers stopped with driver not loaded the only way to make it work is to change back runtime from nvdia to runc

I got a backup I can go back should I disable the

#Busterter-backports

deb http://deb.debian.org/debian buster-backports main contrib non-free

to avoid this issue?

Essaye dans network ajoute a la section DNS 8.8.8.8 ou 1.1.1.1

Moi j'acheterai un nouveau disque