thebeae

I did try that already and it unfortunately did not like the previously jbod 'd drives. Sorry I should have mentioned that Sent from my Pixel using Tapatalk

So when I originally setup my server I didn't look into what RAID cards would give me smart data and have been using an Adaptec ASR-5805 256MB with the drives in jbod mode. And I finally want to properly upgrade (the performance on this raid card has been awful as well) I got a new LSI card which I know works however I want to avoid having to do a fully parity sync since I know the drives are still good at this point (only 3 of my drives are on this card the parity/cache and two others are on the on board controller). Would going to a new config be the best way to go about this? Or would removing the parity drive starting the array and then stopping the array and adding everything back in that way be the easiest/safest? Just curious on what people think would be the best way to go at this point.

@FreeMan See the above quote on those instructions from earlier in the thread.

Just updated my docker and am getting this while attempting to start it: Ive reverted back a version already but just thought Id report what I saw. Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2017-12-07 08:24:04.362925 [info] Host is running unRAID 2017-12-07 08:24:04.403486 [info] System information Linux b2e4a88fdb68 4.9.30-unRAID #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017 x86_64 GNU/Linux 2017-12-07 08:24:04.463534 [info] PUID defined as '99' 2017-12-07 08:24:04.517825 [info] PGID defined as '100' 2017-12-07 08:24:04.583641 [warn] UMASK not defined (via -e UMASK), defaulting to '000' 2017-12-07 08:24:04.628122 [info] Permissions already set for volume mappings 2017-12-07 08:24:04.693152 [info] CONTEXT_PATH defined as '/' 2017-12-07 08:24:04.776092 [info] Starting Supervisor... 2017-12-07 08:24:05,049 CRIT Set uid to user 0 2017-12-07 08:24:05,049 INFO Included extra file "/etc/supervisor/conf.d/libresonic.conf" during parsing 2017-12-07 08:24:05,053 INFO supervisord started with pid 7 2017-12-07 08:24:06,055 INFO spawned: 'start-script' with pid 47 2017-12-07 08:24:06,056 INFO reaped unknown pid 8 2017-12-07 08:24:06,078 DEBG 'start-script' stdout output: [info] transcoder binaries already in /config/transcode... 2017-12-07 08:24:06,078 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-12-07 08:24:06,087 DEBG 'start-script' stderr output: Error: Unable to access jarfile /opt/libresonic/libresonic.war 2017-12-07 08:24:06,087 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47774687669496 for <Subprocess at 47774687669784 with name start-script in state RUNNING> (stdout)> 2017-12-07 08:24:06,087 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47774696970432 for <Subprocess at 47774687669784 with name start-script in state RUNNING> (stderr)> 2017-12-07 08:24:06,087 INFO exited: start-script (exit status 1; not expected) 2017-12-07 08:24:06,088 DEBG received SIGCLD indicating a child quit