Jump to content

TristanP

Members
 View Profile  See their activity

  • Posts

    21

  • Joined

  • Last visited

 Content Type 

Posts posted by TristanP

    Stuck at "verifying bzroot checksum ..." but no errors on console

    in General Support

    Posted · Edited by TristanP
    Additional info

    I'll give it a shot. I thought the license was tied to some unique id on the USB stick though,

     

    So I downloaded the USB creator, created a new flash drive with the correct version (6.11.5) and copied the old /config folder onto the USB /config.

     

    Unfortunately it seems to have gotten worse. There are now dozens of listings after this text:

    Quote

    There are differences between boot sector and its backup

    This is mostly harmless. Differences: (offset:original/backup)

     

    instead of just the one prior. And there it sits.

     

    It's wondering what is going on that annoys me. Sigh

    Stuck at "verifying bzroot checksum ..." but no errors on console

    in General Support

    Posted · Edited by TristanP

    I shutdown my unRAID machine to remove two unneeded disks and reroute cables. That went smoothly and the SAS controllers showed the right drives on the right interface.

     

    While booting it spit out the following:

    Quote

    Checking /dev/sda1

    fsck.fat 4.2 (2021-01-31)

    There are differences between boot sector and its backup

    This is mostly harmless. Differences: (offset:original/backup)

    65:01/00

    Not automatically fixing this

    Dirty bit is set. Fs was not properly unmounted and some data may be lost

    Automatically removing dirty bit.

    /dev/sda1: 616 files, 92166/1874991 clusters

    mount: /dev/sda1 mounted on /boot.

    Verifying bzimage checksum ...

    Verifying bzroot checksum ...

     

    And there it sits. Pushing 30 minutes now.

     

    Any ideas what may be going on? Do I interrupt it or let it run.

     

    I am using unRAID v6.11.5.

     

    Thanks.

    [Support] A75G Repo

    in Docker Containers

    Posted · Edited by TristanP
    Update after post

    19 hours ago, LTM said:

    You have to create your own and mount it. What I ended up doing is creating 2 folders on the host:

    .../vikunja/data

    .../vikunja/config

     

    I mounted the config as so:

    Host: .../vikunja/config/

    Container: /etc/vikunja

     

    Config can be found here: https://kolaente.dev/vikunja/api/src/commit/dcddaab7b58ab2e03e0d0f3f0b771a1e6ec0dbce/config.yml.sample

     

    Name it "config.yml" and place it in .../vikunja/config on the host.

     

    You're not kidding that the documentation is crappy. But I did as you suggested. Now off to see if I can tweak the api docker.

     

    EDIT: Once I did this and restarted the API docker it created /app/vikunja/files/[config|data] directories and created the default config.yml file.

     

    Now I have two :D

     

    But which one gets precedence? I wonder if I can unmount /etc/vikunja and it'll use the files and directories it just created.

    [Support] A75G Repo

    in Docker Containers

    Posted

    I have two questions about the vikunja-api container.

     

    Thanks to LTM I have the front end and API dockers working and talking to each other.

     

    The first is: how does one create an admin account? I can create normal users but not an admin account

     

    The second is: There's no config.yml anywhere in the api docker image. If I create a new one where does the docker image expect it to be?

    Docker is not uninstalling Jellyfin properly - Still thinks it's installed

    in Docker Engine

    Posted

    Running unRAID 6.9.2

     

    I goofed up my Jellyfin docker config (Linixserver version) so I uninstalled  the docker and deleted the directory in appdata.

     

    However on reinstall the docker container said there was an existing server on unRAID and would not kick of the first time install script. I repeated the above process and used a different jellyfin docker image (Jellyfin's direct official image) and now I have two. Each instance is using an unique string (I'd say GUID but it's not the official MS format) that doesn't seem to exist anywhere on disk.

     

    What can I do to convince the docker engine to remove these "ghost" servers? I tried rebooting unRAID to no effect.

     

    [Support] Linuxserver.io - Jellyfin

    in Docker Containers

    Posted

    Running unRAID 6.9.2

     

    I have removed the Jellyfin docker image and the directory in /mnt/user/appdata. However after reinstalling the image instead of going through the usual initialization process it asks for a server. I give it the IP and port of itself and shockingly it is unable to log in.

     

    What am I missing to convince Jellyfin to go through it's initialization process?

    Unable to mount CIFS shares hosted by unRAID

    in General Support

    Posted

    I have been mounting several CIFS shares from an unRAID (v6.8.3) instance on a Centos VM for months without issue. With the new kernel and package update (Called 8.2) all I get from trying to mount the share is the following:

     

    domain=cargo.<personal domain>

    mount.cifs kernel mount options: ip=1q92.168.1.118, unc=\\cargo.<personal domain>\Video,vers=3.0,sec=ntlmsspi,file_mode=0777,user=<valid share user>,domain=cargo.<personal domain>,pass=*********

    mount error(13): Permission denied

     

    The share can still easily be mounted on a Windows machine and via smbclient without error. The behavior has changed with this update.

    Does anyone have any insight what may have changed and what I should look at to try and determine what specifically is wrong? Also it looks like the SMB logs are turned off on unRAID. What's the proper changes to get Samba to log logon failures?

     

    Here's other info:

    Output of uname -or:

    4.18.0-193.19.1.el8_2.x86_64 GNU/Linux

     

    fstab line:

    //cargo.<personal domain>/Video /mnt/movies cifs vers=3.0,credentials=/root/creds_smb_library_core,sec=ntlmsspi,file_mode=0777,dir_mode=0777 0 0

     

    credential file:

    username=<valid share user>

    password=<valid password>

    [Support] Linuxserver.io - Nextcloud

    in Docker Containers

    Posted

    Can someone tell me where the Nextcloud error logs are located? This latest version reports that the "Community Document Server" and "Talk" fail to install when the docker image is installed. However after login I see both listed under Apps but when I click on "Remove" Nextcloud reports "an error occured".

     

    Can't diagnose when the error message is "It's broken". :D

    [Support] Linuxserver.io - Nextcloud

    in Docker Containers

    Posted · Edited by TristanP

    I've installed the latest docker image and attached it to a mariadb but when I go to apps I do not see the openoffice app. Isn't that installed by default?

     

    EDIT:I have two unRAID servers (Both 6.8.2 and have the local mariadb set up for Nextcloud as per SpaceInvader One's video) and I got different installation results after some testing.

     

    On machine #1 (GIGABYTE GA-7PESH2 w/2 E5-2630L v2 @ 2.40GHz and 128G Memory) the docker downloads, I put in the mariadb info, I can see some spinning as it works through to the document server, and the the web page throws a timeout. Refreshing the page I can log in with the admin account, but there's no sign of openoffice

     

    On machine #2 (ASUSTeK COMPUTER INC. P8Z77-V PRO w/i5-2500K CPU @ 3.30GHz and 16G Memory) the docker downloads, i put in the mariadb info, it spins through all the apps but complains that the Community Document Server and Talk fail to download/install. In this case OpenOffice can be seen.

     

    Any ideas why I'm seeing different install issues (Neither are error free)

    [Support] Linuxserver.io - Kodi-Headless

    in Docker Containers

    Posted

    Dumb question time:

     

    I'm seeing "lost websocket connection" when I connect to the docker image via the 8080 web server and the Kodi documentation talkas about web sockets sitting on port 9090. But 9090 isn't defined in the docker image.

     

    Am I missing something on web sockets for this build of Kodi (Latest available) or did I somehow goof up the docker install?

×
×
  • Create New...