nexusmaniac

Members
  • Content Count

    246
  • Joined

  • Last visited

Community Reputation

9 Neutral

About nexusmaniac

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  • URL
    https://mnailor.wordpress.com/

Recent Profile Visitors

1114 profile views
  1. I disagree ๐Ÿ˜…๐Ÿ˜… the spinup mechanic has changed between b35 & rc1, resulting in an undesired effect - Telegraf monitoring smart temps lets me pull temperatures & smart data into Grafana - previously if disks were spun down they would not be spun up by my telegraf.conf - the only variable here was the new Unraid version ๐Ÿ‘€ now disks are spun up if a smart command grazes them ๐Ÿค” (either that or the disks are no longer reporting their standby status correctly/in the same way) # ## Skip checking disks in this power mode. Defaults to # ## "standby" to not wake up disks that have
  2. SMART checks are the trigger here, I've narrowed it down to my Telegraf container, the disks all spin up on RC1 where they didn't on Beta35 (I've tried with & without `nocheck= "standby"` commented out) Edit: I should also add that if I comment out `[[inputs.smart]]` the disks don't spin up while this container is active.
  3. Seems I'm seeing a lack of spindowns too on RC1 ๐Ÿฅด I've attached a diagnostic with all devices spun up ... then after I've manually spun the array down and all the devices have spun back up again 'on their own' (possibly due to SMART).raptor-diagnostics-20201211-1819.zipraptor-diagnostics-20201211-1814.zip
  4. Apologies, I'm on the same version as you, I only updated to it on July 1st but I've not been getting along with it haha ๐Ÿ˜…
  5. Jul 2 22:24:16 Raptor root: plugin: running: anonymous Jul 2 22:27:06 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.githubusercontent.com/bergware/dynamix/a088b81081160482030019ccd61790428bbb805c/unRAIDv6/dynamix.system.autofan.plg Jul 2 22:27:13 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove dynamix.system.autofan.plg Jul 2 22:27:13 Raptor root: plugin: running: anonymous Jul 2 22:27:18 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.
  6. https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta1-x86_64.zip
  7. All sorted @Squid ๐Ÿ˜Œ Rebuild just finished and all is good in the world ๐Ÿ™Œ Thanks again!
  8. Thank you so much Squid!! Doing that now ๐Ÿ™๐Ÿ™๐Ÿ™
  9. Howdy folks! ๐Ÿ‘‹ The last time I had a disk in a similar state, I rushed things, screwed up and lost 3TB of media... Do'h ๐Ÿคฆโ€โ™‚๏ธ So I'd love to get a lovely expert's opinion on what to do next ๐Ÿ˜ Disk 3 is still open-able, no errors in the SMART data ๐Ÿ‘Œ What I've done so far: - Went to move some recent files which would've been moved from Cache to the Array within the last few days ๐Ÿ˜ƒ - I got a couple of emails from my NAS warning me that /dev/sdg had gone bad ๐Ÿ˜ฌ - I headed to the main page & saw the lovely โŒ - Checke
  10. Exactly the same here Jan 23 04:17:25 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3761, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3762, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3763, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3764, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3765, f
  11. Is it possible to figure out the cause? Last thing I want to do is encounter the same issue again 'soon' Looks like I'd best get backing up in the meantime then
  12. Hmm... 2:16 Raptor kernel: loop: Write error at byte offset 2392465408, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672784 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 4215803904, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 8233992 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 1, corrupt 0, gen 0 Nov 15
  13. I went to fire up Plex and my server was offline... I took a look at my NAS and it was true, Plex was stopped. In fact all of my containers had stopped! All of my disks were fine but my log was full of errors. I'm attaching the diagnostics if anybody wants to take a look. Latest version of Unraid (6.6.5) No idea what the cause was, I've just rebooted now so hopefully all is good ๐Ÿคž raptor-diagnostics-20181115-2127.zip
  14. sorted Just needed a balance in the end Ty
  15. Also got this email message this morning from my Unraid: