Jump to content

nexusmaniac

Members
 View Profile  See their activity

  • Posts

    251

  • Joined

  • Last visited

 Content Type 

Report Comments posted by nexusmaniac

    [6.11.0] No space left on device

    in Stable Releases

    Posted

    It's happened again 👀

     

    We can rule out csrf_token as the cause too, that's another symptom of the problem, it would seem 😰

     

    • Typing diagnostics command runs but it's very upset (output & ZIP attached... It's just empty files because nothing can be written to the destination).
    • Lots of mentions of smbd & NT_STATUS_DISK_FULL
      • The boot USB has 745MB used, so that's not full
      • Memory is being heavily used but it's cached memory rather than processes so that's not actually 'full'
    • Dockers are still mostly up - they just struggle to write to anything
    • Disks are all detected, accessible and have 10's of GB of free space (50GB+ on all disks with ~87% usage on the entire array)

     

    I've attached some files with various outputs but I can't get diagnostics to run or save so that's a no-go unfortunately 😔

    diagnostics.txt free-m.txt syslog.txt diagnostics.zip

    [6.11.0] No space left on device

    in Stable Releases

    Posted

    By that point in the logs (the first occurrence of csrf token), unraid had already caught fire, so to speak. I had a couple of tabs open on the same machine after seeing all of the issues. Closing all of them and starting afresh stopped any further csrf warnings but didn't predate the 'undetermined' state of the array, nor the vanishing disks on the dashboard/main tabs.

     

    I'll have to wait for it to happen again, unfortunately 😭 I rebooted so that I could be sure all of my overnight actions would run successfully (appdata & usb backup, mover, trim, etc.) Completely forgot about manual diagnostics via SSH 🤦‍♀️ it's been a long while since anything has gone horribly wrong 😅 which is a silver lining I suppose!

     

    • Like 1

    Unraid OS version 6.9.0-rc1 available

    in Prereleases

    Posted

    1 hour ago, limetech said:

    That's the proper solution.

    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"

     

    • Like 1
    • Thanks 1

    Unraid OS version 6.9.0-rc1 available

    in Prereleases

    Posted · Edited by nexusmaniac

    image.thumb.png.3419fa5660a0de3c453e5ce4c6f8efe5.pngSMART 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.

    [6.7.0-rc1] kernel: BTRFS error

    in Prereleases

    Posted · Edited by nexusmaniac

    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

     

    Unraid OS version 6.6.0-rc1 available

    in Prereleases

    Posted

    Well... I enabled (and subsequently disabled) ACS override.

     

    I rebooted after disabling and BOOM, flash drive wiped clean!! :(

     

    I'm baffled, guess all I can do is re-image the USB with 6.6 and grab the disk backup off my array and hope for the best?! Never actually tested a fresh USB on my existing unRAID :S

     

    image.thumb.png.cb050ca1de040d2ab535bd6968123663.png

×
×
  • Create New...