Jump to content

SkinnySkelly

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by SkinnySkelly

  1. Hello

     

    Ok so i'll try to explain as best as i can. First I wanted to replace one of my parity drives for a larger size 12tb -> 20tb the other parity is still 12tb but after all that finished i saw my 4tb drive was showing issues in smart in scrutiny. i thought ok no biggie i have an extra 12tb to replace it. so i replace the drive and start the array up. first thing i noticed is every single drive was suddenly unmountable. so i stop everything and reboot. ok now everything is back and the rebuild is underway for the bad 4tb onto the 12tb. ok fine. I noticed my plex was taking a long time to reboot so i venture over to my docker tab and everything is gone. i'll provide my diag file as i'm at a loss for what to do. a ton of my of docker containers are lots of custom entries so manually re-adding everything is a last resort as i hardly remember everything i even had customized. I see the appdata folder and everything appears to be intact. 

     

     

    Edit: if installing from previous apps saves my custom entries how can i tell what apps i had installed. i'm sorry but i have terrible memory. I see my previous apps but i experiment with random ones and i see TONS i know i don't have anymore.

    nukavictory-diagnostics-20231209-1233.zip

  2. Everytime i run OCR i run into this error: 

     

    ERROR/ForkPoolWorker-2] Task papermerge.core.tasks.ocr_page[057fc098-78d3-4867-9e8e-5d5f85121030] raised unexpected: OperationalError('database is locked')

     

    not sure what i'm doing wrong. When setting up the docker container it does not ask for any database info.

  3. On 6/18/2021 at 6:43 PM, NLS said:

     

    No you are wrong.
    It shows the password as many times as needed if service is rebooted, at least until you change the password (I haven't checked after that).

     

    Sorry but you are wrong. Don't believe me? Boot up a fresh container and then look at the logs. As you can see the password is there. Now reboot the container and look at the logs again. The password is gone.

  4. On 5/25/2021 at 5:15 AM, binhex said:

    not necessary, im running it non privileged.

     

    not necessary, the logs folder should be created for you (it was for me) once you walk through the initial setup.

     

    agian not necessary, if you walk through the initial setup then it creates this file for you on a successful start of the server.

     

    you can do this, but you can do this through the web ui by going to files and using the web ui text editor built into crafty - see steps 6 and 7. below.

     

    my guess with all your issues is that you didnt go through the initial setup of the first server correctly and thus folders and files were not created, on restart of the container the initial wizard is then not presented and you are then left not going what to do, am i right?.

     

    i have just gone through a clean install of this to verify i didnt have anything that i had hand created that could mask any issues, and for me it went through without any issues, here are the only steps i took:-

     

    1. start container

    2. check /config/supervisord.log for initial login credentials and login to web ui

    3. initial wizard - download minecraft jar file, for me this was the bog standard minecraft_server.jar and place in /config/crafty/servers/

    4. initial wizard - change the name of the jar to match step 2.

    5. initial wizard - save and finish

    6. Go to Dashboard/files and click magnifying glass on eula.txt and change from 'eula=false' to 'eula=true'

    7. save file and start server

    8. go back to dashboard and note the server is running.

     

    i will write up the following in a more formal state as a FAQ when i get some time.

     

    for reference here is the screenshot of the initial wizard screen after i have configured it:-

    image.png.b27b1f64c11433b8920b39236dd60bbb.png

     

     

    Ok i just did a complete fresh install of crafty and yet again same exact issues. I don't know why yours is working and mine is not. No big deal i guess. Not much extra work to get it working.

    one thing i noticed is it only is doing it with the first initial server. adding more after that the issues do not arise.

  5. Ok after SEVERAL grusome hours i have fixed it.

     

    First: change to Privileged mode in the unraid settings for the crafty container

    2nd: make sure to make the logs folder and put the latest.log file in it (it can be blank)

     

    so in your folder you made for your server it will be SERVERNAME/logs/latest.log

     

    3rd made a server.properties file (also blank)

     

    put this in the main SERVERNAME folder

     

    4th make a eula.txt file and put this in it : eula=true

     

    put this in the main SERVERNAME folder

     

    it SHOULD boot right up after that.

     

    wish i knew how broken this application was before trying it out. Not rocket science to have all these items premade no idea why the crafty developers don't already do this.

  6. ok been trying to get this working for hours now.

     

    everytime i go to start the server it kicks over to the console and displays:

     

    Unable to find file to tail: /config/crafty/servers/logs/latest.log

     

    manually adding the file will make the message go away but the the server still does not start.

  7. 10 hours ago, jj_uk said:

    In crafty, \config\ is mapped the appdata folder for this container, so create 2 folders in your appdata as follows:

     

    ...\appdata\binhex-crafty\crafty\servers\

    ...\appdata\binhex-crafty\crafty\backups\

     

    In the relevant places in crafty, when it requires a location, use:

     

    \config\crafty\servers\

    or

    \config\crafty\backups\

     

     

    glad you got it wokring. my issue is the server won't start i keep getting: Unable to find file to tail: /config/crafty/servers/logs/latest.log manully adding it does not solve the issue

  8. For anyone using this be sure to choose the correct Redis container in the CA store. I was having issues with paperless not connecting to my redis container (even though i set the ip correctly in paperless) and found out the redis i was using was not working. The one that ended up working for me was the one by jj9987

  9. 7 hours ago, JorgeB said:
    
    Mar  5 15:20:05 Tower kernel: pm80xx 0000:09:00.0: pm80xx: driver version 0.1.38
    Mar  5 15:20:05 Tower kernel: pm80xx 0000:09:00.0: Refused to change power state, currently in D3
    Mar  5 15:20:05 Tower kernel: pm80xx pm8001_pci_probe 1047:pm8001_request_irq failed [ret: -28]
    Mar  5 15:20:05 Tower kernel: pm80xx: probe of 0000:09:00.0 failed with error -28

     

    Controller is failing to initialize, you can try a different slot if available, but there have been other issues with this controller, e.g., also known to stop working after updating to v6.9, would recommend using an LSI instead, you'll need a new cable though.

    Going to try the LSI SAS 9200-8e it seems a few people have used this model.

  10. So I put the Card into my R710

    Plugged the QSFP+ cable into the Netapp Card and JBOD

    Upon booting the server I do not notice it seeing the drives either from the dell bootup OR unraid. These drives are old ones I had in the server previously so they are not 520 sector

    Looked into the logs and see nothing relating to netapp as I see this user does: https://forums.unraid.net/topic/89444-how-to-configure-a-netapp-ds4243-shelf-in-unraid/

     

    I'm using the same card as he is in the photo with the same cable

     

    I can feel the card is warm to the touch so it's working as far as i can tell.

    plugged the cable into the Circle and Square with no luck. Tried both of the IOM6 controllers. Tried all 4 ports of the card as well.

     

    is the card dead? Did I buy the wrong card?

    Attaching my log file

     

    EDIT: Ok i see netapp in the logs:

    Tower kernel: scsi 2:0:4:0: Enclosure NETAPP DS424IOM6 0191 PQ: 0 ANSI: 5

     

    but a little after i see a red error like so:

     

    Tower kernel: pcieport 0000:00:06.0: Device recovery from fatal error successful Mar 5 15:20:09

    Tower kernel: pcieport 0000:00:06.0: AER: Uncorrected (Fatal) error received: 0000:00:06.0

    Tower kernel: pcieport 0000:00:06.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, (Requester ID)

    Tower kernel: pcieport 0000:00:06.0: device [8086:340d] error status/mask=00004000/00318000

     

    Is this related to the Disk shelf?

     

     

    tower-syslog-20210305-2047.zip

  11. How do i give access to multiple folders while restricting access to 1?

     

    I have a folder called Folder A, Folder B, and Folder C Inside of Folder D

     

    I only want that user to have access to Folder A and B but not C

     

    putting /mnt/Folder D gives them access to folders A,B,C

     

    Edit: Figured it out

    I added this to my config file at flash/config/plugins/ProFTPd/proftpd.conf

     

    MAKE SURE YOU EDIT THE .conf AND NOT THE .cfg! both the same name but one is all lowercase and one is a mix of upper and lower :)

     

    <Directory /mnt/user/Folder D>

      <Limit ALL>

          AllowUser User

          DenyAll

      </Limit>

    </Directory>

     

    Now only the User "User" can see Folder C while others users do not see the folder at all :)

  12. I just replaced 2 drives and re-ran the scrutiny-collector-metrics run command and it shows the new drives BUT the old drive data still exists. anyway to remove those?

     

    Edit: I also noticed it's not updating the powered on area which leads me to believe it's not properly keeping drive data updated.

  13. 2 hours ago, jonathanm said:

    Do you have 2 full licenses?

    No I just had an extra usb stick laying around that I lost. Just an empty usb stick is all. The backups I have are the ones you get when making a backup from the unraid webui that I store on my PC.

     

    Am I correct in assuming all I do is just copy the contents from the backup file to the new usb stick and delete the super.dat file? Then i'm good to go? Or do I need to do the key renewal steps as well?

  14. 18 minutes ago, jonathanm said:

    You can safely use that old backup IF YOU DELETE the super.dat file from the USB stick config folder before you boot Unraid with it.

     

    Use your latest array status email to assign your drives.

    Thank you! Will report back in a couple days with my results. The USB drive I thought I had laying around for backups for this situation appears to have gotten lost :(.

  15. I received a email stating my unraid server no longer had access to the usb drive:

     

    Event: USB flash drive failure
    Subject: Alert [TOWER] - USB drive is not read-write
    Description: Cruzer_Fit (sda)
    Importance: alert

     

    Then the server became unresponsive and can no longer boot into the OS.

    Tried putting the USB into windows and copying the files to a new drive but the USB drive shows as it needing formatted. I clicked no and now i'm at this stage and slightly panicking as my backup I have is over 5 months old. Now I would just use this backup BUT I can't remember if I have since upgraded from a 4tb parity to a 10tb parity from that backup or not.

     

    What I mean is my backup is either from a 4tb parity or my new 10tb parity. I can't remember which. Is it ok to still use this backup?

     

    I have since added new docker containers but i'm ok with adding those again if need be.

     

    I also had a VM created since then. Will this be gone? Or just need recreated and pointed at the vdisk I made for it?

     

    Sorry for noob questions my brain is on overload as I have YEARS of data on these drives and I was in the process of starting uploading all of it to the cloud for backups as I just got gigabit internet.

     

    Also any recommendations for USB drives that can take heat? like over 90F rooms?

     

    Edit: Also the usb drive shows in the boot settings on my dell r710 but won't boot to it

     

    Edit: Can confirm it's my old 4tb config by looking at the order date of my 10tb drives. Still possible to recover?

     

    Edit: Should also point out my unraid is setup to not start the array immediately. I always manually start it after every reboot.

     

    Edit: Finding out which drive is which is easy since I have parity check emails sent to me daily.

×
×
  • Create New...