jamse

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by jamse

  1. Alright, just to make sure I do not destroy my data this is what I am going to do. New Config -> Assign 10tb Drives in the first 5 slots (1 Parity + 4 array), then assign my 6tb drives (6 array) in my remaining slots with existing data -> Start my array I already pre-cleared all the 10tb drives, and the old 6tb parity drive. Then my 'main' in unRAID's ui will reflect the relative position of each drive in my case.
  2. No I have no parity at the moment. I applied a new config to remove my parity drive to replace my current 6tb parity drive with a 10tb drive, and then add that 6tb drive to my array. Now I want to apply a new config to put the new 10tb drive as my parity drive then add 4 x 10tb drives to my array while changing the device disk slots to match the physical location in my case.
  3. Will I have an issue with the possibility of data loss if I setup a New Config and re-arrange my drives in Main to reflect the position they are in my computer case? I know its a bit OCD, but I want to be able to look at my drives in my array in Main and then easily swap out drives in the corresponding location in my case if/when a drive fails. I have a Fractal Design Define R6, so its not a huge pain in the ass to pull drives, but its not as easy to do like a hotswapable bay.
  4. ahh okay. well im trying to separate my cache pool from my nvme, since I have 2 x 1tb sata ssd for that, and that is constantly being hit with data from four rtorrent docker containers. in my other unraid server if I max out my cache pool it stops all my docker containers, and I have my cache pool writing to the array once it hits 25% full it still cant keep up.
  5. Is it a bad idea to mix ssd and hdd in my unraid array? Also, will there be an issue if my ssd is an nvme ssd? I have 5 x 10 tb drives and 1 x 250gb nvme ssd, which I plan to exclude from every other share except for appdata and domains for docker & vms. If it is a bad idea, should I just use unassigned devices, so I can utilize it for appdata and domains?
  6. Does anyone know how to do a fresh install and restore plugins/os data? Unraid is having minor issues with updating, preclearing drives will pause and start continuously during the zeroing of the drive, and when I use the GUI interface there are artifacts everywhere. The last time two updates will either fail to download and i have to retry till it downloads and installs, or it will fail during the install and then I have to restore my flash drive with a backup and attempt again till it works. The preclear pause and start issue happens only in the zeroing phase and its happened with two different drives. My gui issue is only when I login locally with a monitor instead of using the webui. This happens if I pull my drive and put it in another computer and boot as well, so I know its not a graphics card issue. I am tired of trying to figure out what the issues are and trying to fix them, and would rather just fresh install on a drive and move over the necessary info.
  7. woops, sorry I inserted the wrong screenshot. I updated my original post, and I am having issues with binhex deluge as well, so I am assuming its a permissions issue? *solved the issues I was pointing the downloads folder in deluge to the absolute path that I had setup in the docker unraid settings. I did not realize that once it was mounted in the container it would show up as a relative path inside the container.
  8. My deluge container will not write to my nas. It is connectable to outside my network and through my local network, but everytime I add a torrent it starts downloading, but progress will not increase. Then deluge will drop the connected computer, because no data is being written to my array. im using a cache drive and my array is using btrfs. all app data is written to the ssd only and my mnt/user/media/ share has cache drive enabled. *edit I inserted the correct screenshot*
  9. I am trying to get ghost blog to start, but I am having user auth issues with mysql. 'ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client' Does anyone have any thoughts on fixing this issue? [2018-08-18 00:33:03] [31mERROR[39m [31m [31mNAME: RollbackError[39m [31mCODE: ER_NOT_SUPPORTED_AUTH_MODE[39m [31mMESSAGE: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client[39m [37mlevel:[39m[37mnormal[39m [37mOuterError: The server has encountered an error.[39m [37mRollbackError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client at RollbackError.KnexMigrateError (/var/lib/ghost/versions/1.25.5/node_modules/knex-migrator/lib/errors.js:7:26) at new RollbackError (/var/lib/ghost/versions/1.25.5/node_modules/knex-migrator/lib/errors.js:32:26) at /var/lib/ghost/versions/1.25.5/node_modules/knex-migrator/lib/index.js:212:23 at tryCatcher (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:689:18) at Async._drainQueue (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/async.js:133:16) at Async._drainQueues (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5) Error: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client at Handshake.Sequence._packetToError (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/sequences/Sequence.js:52:14) at Handshake.ErrorPacket (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/sequences/Handshake.js:130:18) at Protocol._parsePacket (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/Protocol.js:279:23) at Parser.write (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/Parser.js:76:12) at Protocol.write (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/Protocol.js:39:16) at Socket.<anonymous> (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/Connection.js:103:28) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at TCP.onread (net.js:597:20) -------------------- at Protocol._enqueue (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/Protocol.js:145:48) at Protocol.handshake (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/protocol/Protocol.js:52:23) at Connection.connect (/var/lib/ghost/versions/1.25.5/node_modules/mysql/lib/Connection.js:130:18) at /var/lib/ghost/versions/1.25.5/node_modules/knex/lib/dialects/mysql/index.js:109:18 at Promise._execute (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/debuggability.js:303:9) at Promise._resolveFromExecutor (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:483:18) at new Promise (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:79:10) at Client_MySQL.acquireRawConnection (/var/lib/ghost/versions/1.25.5/node_modules/knex/lib/dialects/mysql/index.js:104:12) at create (/var/lib/ghost/versions/1.25.5/node_modules/knex/lib/client.js:283:23) at tryPromise (/var/lib/ghost/versions/1.25.5/node_modules/tarn/lib/Pool.js:366:22) at tryPromise (/var/lib/ghost/versions/1.25.5/node_modules/tarn/lib/utils.js:57:20) at Promise (/var/lib/ghost/versions/1.25.5/node_modules/tarn/lib/Pool.js:366:5) at Promise._execute (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/debuggability.js:303:9) at Promise._resolveFromExecutor (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:483:18) at new Promise (/var/lib/ghost/versions/1.25.5/node_modules/bluebird/js/release/promise.js:79:10) at callbackOrPromise (/var/lib/ghost/versions/1.25.5/node_modules/tarn/lib/Pool.js:357:10)[39m [39m [90m[39m [2018-08-18 00:33:36] [31mERROR[39m [31m [31mNAME: RollbackError[39m [31mCODE: ER_NOT_SUPPORTED_AUTH_MODE[39m [31mMESSAGE: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client[39m [37mlevel:[39m[37mnormal[39m