nexusmaniac

Members
  • Posts

    247
  • Joined

  • Last visited

Converted

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

Recent Profile Visitors

1424 profile views

nexusmaniac's Achievements

Explorer

Explorer (4/14)

9

Reputation

  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 stopped rotating. # ## See --nocheck in the man pages for smartctl. # ## smartctl version 5.41 and 5.42 have faulty detection of # ## power mode and might require changing this value to # ## "never" depending on your disks. # nocheck = "standby"
  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.githubusercontent.com/bergware/dynamix/a088b81081160482030019ccd61790428bbb805c/unRAIDv6/dynamix.system.autofan.plg Jul 2 22:27:18 Raptor root: plugin: running: anonymous Jul 2 22:27:18 Raptor root: plugin: creating: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.autofan.txz Jul 2 22:27:18 Raptor root: plugin: checking: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - MD5 Jul 2 22:27:38 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:38 Raptor root: plugin: running: anonymous Jul 2 22:27:38 Raptor root: plugin: creating: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.autofan.txz Jul 2 22:27:39 Raptor root: plugin: checking: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - MD5 Jul 2 22:29:26 Raptor login[15500]: ROOT LOGIN on '/dev/pts/0' Jul 2 22:30:48 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install /boot/config/plugins/dynamix.system.autofan.plg Jul 2 22:30:48 Raptor root: plugin: running: anonymous Jul 2 22:30:48 Raptor root: plugin: creating: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.autofan.txz Jul 2 22:30:48 Raptor root: plugin: checking: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - MD5 Jul 2 22:32:35 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install /boot/config/plugins/dynamix.system.autofan.plg Jul 2 22:32:35 Raptor root: plugin: running: anonymous Jul 2 22:32:35 Raptor root: plugin: creating: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.autofan.txz Jul 2 22:32:35 Raptor root: plugin: checking: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - MD5 Jul 2 22:34:02 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin_rm /boot/config/plugins-error/dynamix.system.autofan.plg Jul 2 22:34:22 Raptor emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.sh install https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.autofan.plg Jul 2 22:34:23 Raptor root: plugin: running: anonymous Jul 2 22:34:23 Raptor root: plugin: creating: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.autofan.txz Jul 2 22:34:23 Raptor root: plugin: checking: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz - MD5 Jul 2 22:34:23 Raptor root: plugin: running: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz Jul 2 22:34:23 Raptor root: plugin: creating: /tmp/start_service - from INLINE content Jul 2 22:34:23 Raptor root: plugin: setting: /tmp/start_service - mode to 0770 Jul 2 22:34:23 Raptor root: plugin: running: anonymous Jul 2 22:34:54 Raptor ool www[16948]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:35:02 Raptor ool www[16948]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:35:22 Raptor ool www[16061]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:35:28 Raptor ool www[16948]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:35:28 Raptor autofan: autofan process ID 17353 started, To terminate it, type: autofan -q -c /sys/class/hwmon/hwmon2/pwm1 -f /sys/class/hwmon/hwmon2/fan1_input Jul 2 22:35:33 Raptor autofan: Highest disk temp is 31C, adjusting fan speed from: FULL (100% @ 0rpm) to: OFF (0% @ 0rpm) Jul 2 22:35:41 Raptor ool www[17099]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:35:54 Raptor ool www[17289]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:36:41 Raptor ool www[17099]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:37:01 Raptor ool www[17289]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jul 2 22:37:01 Raptor autofan: autofan process ID 18017 started, To terminate it, type: autofan -q -c /sys/devices/platform/nct6775.656/hwmon/hwmon2/pwm2 -f /sys/devices/platform/nct6775.656/hwmon/hwmon2/fan4_input Jul 2 22:37:01 Raptor autofan: autofan excluding drives sdd,sde,sdf,sdi,sdj,sdk,sdl,sdg,sdh from max temp calculations Jul 2 22:37:06 Raptor autofan: Highest disk temp is 0C, adjusting fan speed from: FULL (100% @ 1400rpm) to: OFF (0% @ 508rpm) Error log doesn't seem to appear in the folder either ๐Ÿ‘€ root@Raptor:/boot/config/plugins-error# ls -lah total 16K drwx------ 2 root root 8.0K Jul 2 22:34 ./ drwx------ 8 root root 8.0K Jul 2 22:30 ../ root@Raptor:/boot/config/plugins-error# Can't get autofan to run against PWM 2 - it tries to save but never completes, defaults to PWM 1 and setting the plugin to "Disabled" doesn't disable it haha! Let me know if I can do anything to help out! - I tried to install an old plugin version from GitHub but it doesn't think the MD5 matches but I know the issue didn't exist in older versions of the plugin
  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 โŒ - Checked the SMART data on the disk, seemed fine - Rebooted... I got another email to say "Subject: Notice [RAPTOR] - array turned good" - Still got a lovely emulated disk - Grabbed a diag dump & headed straight here โค๏ธ What should I do next? - I believe disk 3 to be healthy - I don't have physical access at the moment ๐Ÿ˜” (I'm a couple hundred miles away) - I do have full web / SSH (VPN) access And of course, thank you in advance for being amazing!! raptor-diagnostics-20191010-1615.zip
  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, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3766, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3767, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3768, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3769, flush 0, corrupt 0, gen 0 raptor-diagnostics-20190123-0839.zip
  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 21:32: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 4, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392473600, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672800 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392608768, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4673064 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32: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 7, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 4367192064, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 8529672 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32: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 9, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392469504, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672792 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392489984, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672832 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 11, rd 0 Crap? ------- Nov 15 21:31:57 Raptor kernel: BTRFS error (device sdl1): unable to find ref byte nr 2331165265920 parent 0 root 5 owner 18608628 offset 4014080 Nov 15 21:31:57 Raptor kernel: BTRFS: error (device sdl1) in __btrfs_free_extent:6950: errno=-2 No such entry Nov 15 21:31:57 Raptor kernel: BTRFS info (device sdl1): forced readonly Nov 15 21:31:57 Raptor kernel: BTRFS: error (device sdl1) in btrfs_run_delayed_refs:3057: errno=-2 No such entry Nov 15 21:31:57 Raptor kernel: BTRFS error (device sdl1): pending csums is 3751936 /dev/sdl
  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: