Jump to content

Res74

Members
 View Profile  See their activity

  • Posts

    12

  • Joined

  • Last visited

 Content Type 

Posts posted by Res74

    Binhex-Sickchill Won't Start

    in General Support

    Posted

    Running latest version of Unraid.

    Updated last night to the latest binhex-sickchill and now I get this:
    2024-04-11 07:16:42.826957 [info] Host is running unRAID

    2024-04-11 07:16:42.863553 [info] System information Linux 6c361a1311b4 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux

    2024-04-11 07:16:42.909022 [info] PUID defined as '99'

    2024-04-11 07:16:42.985121 [info] PGID defined as '100'

    2024-04-11 07:16:43.068677 [info] UMASK defined as '000'

    2024-04-11 07:16:43.108697 [info] Permissions already set for '/config'

    2024-04-11 07:16:43.159001 [info] Deleting files in /tmp (non recursive)...

    2024-04-11 07:16:43.409382 [info] Starting Supervisor...

    2024-04-11 07:16:43,818 INFO Included extra file "/etc/supervisor/conf.d/sickchill.conf" during parsing

    2024-04-11 07:16:43,818 INFO Set uid to user 0 succeeded

    2024-04-11 07:16:43,823 INFO supervisord started with pid 7

    2024-04-11 07:16:44,826 INFO spawned: 'start-script' with pid 47

    2024-04-11 07:16:44,827 INFO reaped unknown pid 8 (exit status 0)

    2024-04-11 07:16:45,567 DEBG 'start-script' stderr output:

    /home/nobody/start.sh: line 7: 49 Illegal instruction "${install_path}/bin/sickchill" --config /config/config.ini --datadir /config

     

    2024-04-11 07:16:45,567 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

    2024-04-11 07:16:45,568 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23167379153616 for <Subprocess at 23167381214736 with name start-script in state RUNNING> (stdout)>

    2024-04-11 07:16:45,569 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23167379445712 for <Subprocess at 23167381214736 with name start-script in state RUNNING> (stderr)>

    2024-04-11 07:16:45,569 WARN exited: start-script (exit status 132; not expected)

    2024-04-11 07:16:45,569 DEBG received SIGCHLD indicating a child quit

    Device Disabled Contents Emulated Question

    in General Support

    Posted

    So I have a drive that has failed after finally 12 years (thing does not owe me anything at that age). I am wondering what is the easiest way to identify it (as I was an idiot and did not setup labels). Also, since my parity is valid, once I identify the device, do I just remove it from the array, take it out, put in new drive, preclear and then assign as the new "Disk 1" or what?

     

    Appreciate all the information and apologies if this is a noob question but never had this issue before.

×
×
  • Create New...