onufry

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

2 Neutral

About onufry

  • Rank
    Newbie
  1. yet another update. for past few days i started to monitor dashboard, and i've noticed that my CPU spikes to 70% and hover around that without dropping. checked top and saw ffmpeg was a culprit. after restarting Jellyfin CPU usage went to "my system average" <15%. obviously CPU, Mobo temps also dropped. i have not had NVMe gone missing for these few days. so, i my very ignorant opinion, i suspect that (as someone mentioned elsewhere) missing cache NVMe has to do with drive controller temperature sensor triggering fail-safe. thoughts?
  2. Looking for step by step instructions to enable transcoding using APU. first disclaimer, i am a complete novice, so excuse my naivete. after weeks of searching for instruction i gave up and turned to this wonderful forum for help. my unraid uses Ryzen 3400G (no dedicated GPU). i have installed jellyfin, and made it accessible remotely through a reverse proxy. now, i would like to firstly know if it is possible to enable transcoding/hardware acceleration on my unraid, and if it is possible how? i was reading here and there about necessity of mesa drivers ins
  3. thanks, my bios has the latest version. i did already try switching to different NVMe. originally i used Sabrent and now Samsung - same issues. it seems trying unraid 6.9 RC is my next option to try.
  4. hey, any updates on this? i've experienced same "missing NVMe cache drive" situation with 1 of the 2 cache drives (in a pool) goes missing. using 2x Samsung 980_PRO 1TB. it happens often enough to be annoyed. from the log i can see these lines when it happened: Jan 20 18:32:54 JJ-NAS kernel: nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x2010 Jan 20 18:33:51 JJ-NAS login[402]: ROOT LOGIN on '/dev/pts/0' Jan 20 18:33:56 JJ-NAS kernel: nvme nvme0: I/O 16 QID 0 timeout, disable controller Jan 20 18:34:16 JJ-NAS kernel: nvme nvme0: Device not rea
  5. yet another update, after 2 weeks without any issues, one of the samsung cache drives failed as well. i have not captured diagnostics. awaiting a replacement drive. i did suspect a motherboard, but it seems my issue has happened to others using different NVMe brands (see link to another thread below). overheating seems to be a best guess what is the source of a problem, i will try again to use a heatsink with NVMe drive this time.
  6. hey, same problem. initially i had Sabrent 1TB Rocket drives in a pool, issue happened several times, so replaced Sabrents with Samsung 980 PRO 1TB, everything worked fine about 2 weeks and today same issue again, "lost" 1 of drives. i do have a line nvme_core.default_ps_max_latency_us=0. i see Cache "Not Installed" after reboots. any suggestions?
  7. Hello, I would like share my build specs, please comment, criticize, suggest improvements. - case: fractal node 804 with 7 noctua fans (replaced all 3 stock case fans, and added a few). 4 front intake (NF-A12), 2 back panel exhaust (mobo chamber - NF-A12 and NF-A14 - HDDs/PSU chamber) and another 1 top (NF-F12) panel exhaust. - PSU: corsair RM750x fan facing bottom. - mobo: ASRock X570M - RAM: corsair vengeance DDR4 3000 2x16GB - CPU: Ryzen 3400G + noctua CPU cooler (NH-U12A) - HDD: 4x Seagate IronWolf 8TB for array, 1x 12 TB Ironwold for par
  8. posting an update, maybe someone finds this info useful. my system seems to be stable after replacing both SABRENT 1TB Rocket Nvme PCIe 4.0 M.2 drives with Samsung 980 PRO SSD 1TB - M.2 NVMe. i have not had any cache drives failures for 3 days now. the only difference i have noticed is that samsung drives' temperatures are slightly higher by 3C-4C, hovering around 33C-35C.
  9. hi, yes, i've noticed the "controller down" message. anyways, i have updated bios and replaced NVMe drives with Samsung ones. so far over 12 hours without failures... fingers crossed. cheers
  10. hi again, it happened again. 1 of the 2 cache drives failed (same slot). as before after it failed, i can see it listed in a pool, but cannot see temp (only * is shown). Smart Report shows "Smartctl open device: /dev/nvme0 failed: No such device". need to say i have not updated BIOS yet. i will do it tomorrow after i swap both Sabrent cache drives to Samsung ones. in any case attaching the diagnostics, hope there is something in it that can point what is the cause of the issue. jj-nas-diagnostics-20210102-1530.zip cheers for your help.
  11. hey, added the line "nvme_core.default_ps_max_latency_us=0" as instructed. i can see now the missing NVMe drive. added back to the cache pool, hope it will stay. thanks for your help. another question, i have an option to use Sabrent Rocket Gen4 (non-PLUS) or Samsung 980 Pro drives. which one is preferred? (i do not intent to have any VMs, just storage and Media streaming).
  12. thanks for your reply. attached diagnostics, pretty sure i ran them before a reboot and removing failed drive from the pool. jj-nas-diagnostics-20210101-1710.zip
  13. hi, i have a cache pool with 2x Sabrent 1TB Rocket Nvme PCIe 4.0 M.2. (ASRock X570M, Ryzen 3400G, 32GB RAM). a few days after completing my unraid build, one of the M.2s failed. i ordered a replacement (this time with heatsink) and replaced the failed drive. again after just 2 days the replacement drive failed again (same slot). temps were/are ok (around 30C on average, never observed higher than 35C). tried to scrub/repair, but it did not work, "uncorrectable". the unraid shows missing cache 1 drive. i'm thinking of getting a different brand's drives, but not sure if it
  14. hiya, a huge thank you to many users of the unraid community for helping me a relatively painless transition from an old QNAP (b. 2008) to a brand new unraid server. i was considering a new QNAP, when just last november a friend of my told me about "unraid" alternative. after a few weeks of reading forums, ordering parts, watching tutorials and reading KB articles, i am now a proud unraid owner/user, and cannot be happier. installation had only one hiccup. i did not enable UEFI when creating an unraid boot disk, and took me a while to figure out that this cau