bfeist

Members
  • Posts

    135
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • URL
    http://benfeist.com
  • Location
    Toronto Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bfeist's Achievements

Apprentice

Apprentice (3/14)

1

Reputation

  1. Great plugin! Chrome randomly reloads the tab clearing the stats history. I'd love it if the stats were kept on the server rather than in my browser so the graphs were always available upon page load. Cheers!
  2. Hi everyone, I'm a long-time user (over 10 years at this point) and I'm still using Supermicro AOC-SASLP-MV8 controller cards (two of them) plus my motherboard's onboard SATA connections, of course. I'm in the process of rebuilding a bad parity drive and I'm getting about 65MB/s across 16 drives. Are there newer cards out there that will do better than this? Just wondering if my somewhat ancient hardware is still relevant. Thz
  3. I have the same issue. What is the proper support threat?
  4. After reading all of these terrifying posts about how Promise controllers are deprecated, I decided to try to upgrade anyway. It was completely uneventful, and the 16 promise-based drives I have in the array are none the wiser. Thanks for continuing to push this great software.
  5. Hello. My cache drive is throwing "no space left on device". When I do a df -h, I get: Filesystem Size Used Avail Use% Mounted on /dev/sdb1 239G 85G 0 100% /mnt/cache It's running btrfs. I have done a trim, did a btrfs scrub. No luck. Any thoughts?
  6. This gets even more mysterious. I installed sqlite3 in the linuxserver docker itself and restored the db from dump, then ran the integrity check within the same docker and get a disk I/O error. # sqlite3 com.plexapp.plugins.library.db < dump.sql # sqlite3 com.plexapp.plugins.library.db "PRAGMA integrity_check" Error: disk I/O error ----> update Turns out mapping the folder /mnt/user/appdata/Plex instead of /mnt/cache/appdata/Plex was the issue. No clue why.
  7. Thanks for the suggestion. I completed those steps. Integrity passed. Dumped to .sql then back to .db file. No change. 1.14.1.5488 (needo container) launches Plex fine. 1.15.4.919 (linuxserver container) gives SQLITE3:(nil), 5386, os_unix.c:37072: (19) mmap(/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm) - No such device
  8. Yes, except if I start plex 1.14.1.5488 (needo container) it works perfectly.
  9. New help request. I'm attempting to move from the needo plex docker to linuxserver plex docker. I've pointed the config of the new linuxserver docker to the same /config location as needo. I get a fatal error and nothing will come up. Here's the entire log file when I try to start. Any help would be appreciated. Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Plex Media Server v1.15.4.919-8e2884e4b - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT -04:00 Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Linux version: 4.18.20-unRAID, language: en-US Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Processor AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - /usr/lib/plexmediaserver/Plex Media Server Apr 13, 2019 19:19:54.141 [0x14bf7d583780] ERROR - SQLITE3:(nil), 5386, os_unix.c:37072: (19) mmap(/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm) - No such device Apr 13, 2019 19:19:54.141 [0x14bf7d583780] ERROR - SQLITE3:(nil), 5386, disk I/O error in "PRAGMA cache_size=2000" Apr 13, 2019 19:19:54.142 [0x14bf7d583780] ERROR - Database corruption: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 Apr 13, 2019 19:19:54.142 [0x14bf7d583780] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE)
  10. Not really a support question but could find the appropriate board for this question. I just finished a dual parity rebuild of parity on my majority 8tb (two 4tb) 16 disk system (including both parity drives) and noticed that the rate was quite slow compared to a verify or even a disk rebuild. Not complaining at all. This product rocks! My 4 core cpu was at a consistent 68% on the unraid process during rebuild. Is this expected due to the computationally expensive process, or am I running into some kind of SMR issue? Thanks.
  11. Thanks for the suggestion. I’m not using ECC memory. Perhaps it’s an actual fault with the CPU? I’ve never heard of a partial CPU failure like this.
  12. Hi all, I'm scratching my head about this one. I'm using Unbalance to empty an older drive and moving the contents to a new drive. When I do this it causes all drives to read as though a parity sync of some sort is happening. No drive's contents should be being reconstructed with this operation. Any thoughts on what's going on?
  13. Fix Common Problems recommended that I post my syslog and seek help. Can someone please have a look? thx syslog