Daylend

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by Daylend

  1. On 10/3/2023 at 4:11 AM, JorgeB said:

    Thanks for the reply!

    I ran the xfs_repair through the UI after putting the system in maintenance mode and get the following output:
     

    Quote

    Phase 1 - find and verify superblock...
    Phase 2 - using internal log - zero log...
    ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

    So I ran

    mkdir /mnt/tmp
    mount /dev/sdd1 /mnt/tmp

    But I get
     

    Quote

    mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error.


    I noticed the wiki specifically talks about /dev/mdx devices but mine are all /dev/sdx still so I'm wondering if I'm missing something?

     

     

    Thanks so much for your help.

  2. Hello,

     

    I updated from Unraid 6.11.5 to 6.12.4 the other day and noticed one of my disks has the following error: "Unmountable: Unsupported or no file system". I did a full reboot but unfortunately that didn't fix the issue. I ran the system update from the Firefox browser (which I guess I won't do anymore lol). Diagnostics attached.

     

    Thanks so much for your help.

    tower-diagnostics-20231002-2340.zip

  3. Interesting, what you got is how it's supposed to work with invalid credentials. And it's what I get on my local machine as well, which is good. When I try to run it on my unraid server, I get the following:
     

    Linux 4.19.56-Unraid.
    root@Tower:~# docker run -ti --rm -e clientid=test -e clientsecret=test -e username=test -e password=test daylend/redditcnn
    Using TensorFlow backend.
    root@Tower:~# 

     

  4. Hi!

     

    I decided it would be a fun project to turn a python script I made into a docker container, so I could deploy it on my unraid server to run 24/7. I managed to get the script running flawlessly in a docker image I built on my local machine from my dockerhub repo (literally copy pasted the command from unraid). However, after I successfully install the container in unraid, it immediately stops with no docker logs.

     

    Any ideas what could be causing an issue like this?

    firefox_LMtAnT3gfQ.png

    firefox_BMtPYW8joN.png

  5. So I went through everything you said, making sure it was all set up correctly... Everything looked good. But it still wasn't working.

     

    I noticed your fstab didn't have the lines "noauto,nobootwait", so I removed those, and rebooted.

    Now it works like a charm!

     

    Thanks for the help! ?

  6. So I created a new Ubuntu Server 18.04 VM and noticed I had the option to set up an unRAID share and mount tag in the settings.

     

    image.png.2657f346fac3cc1e95be76b2ca2ced4e.png

     

    So I put in the following values. Booted into my VM, obviously the mounts weren't visible. So I did some googling and edited my fstab to what I could find:

    UbuntuServer /home/daylend/UbuntuServer 9p trans=virtio,version=9p2000.L,_netdev,noauto,nobootwait,rw 0 0

     

    Rebooted the server. Nothing appeared. Read that you had to edit some xml files but I also read that's inside the .img file now so it's not changeable? I assume that's what the unRAID share and unRAID mount tag values are for in the web UI now. I also looked through the wiki for more information on unRAID share and unRAID mount tag settings but couldn't find much.

     

    How do I get this working?

     

    Thanks!

    • Like 1
  7. I have the latest BIOS firmware (FH) installed on my motherboard and virtualization technology is enabled.
    I have checked and both my motherboard and CPU (i7-950) both support VT-d.

     

    However, unRaid still says it's Disabled (screenshot included).

    Please help! I've spent so many hours trying to get to the bottom of this already...

    chrome_2018-05-10_15-18-24.png