Jump to content
  • [6.9.0 beta 35] Cache Drive Errors


    nickp85
    • Closed

    Been on 6.9 since beta 30 and today I started having cache drive errors repeatedly and going into read only mode.  When I upgraded to 6.9 I changed to the different partition format for SSDs and rebuilt my cache.  I have 2 Samsung 960 Pro 512GB in the cache and they both have about 120TBW, rated for 500GB.

     

    I was in the middle of using my Windows 10 VM to play a game when the VM locked up, then I tried to navigate around the Unraid GUI and found that also to be giving me problems.  I ended up triggering a reboot from the web GUI and it had to force shut down and restart.  After reboot I have a lot of errors showing.

     

    Attaching any logs I could find.

    nicknas2-diagnostics-20201128-1550.zip syslog-127.0.0.1.log

     

    UPDATE: Ended up using mover to get everything off my cache to the array and then erase/format and then move back.  It was able to move everything off but was definitely haven't trouble deleting it after it was moved.  Also had to restart the array a couple times to get mover to move everything.  All smooth since the format.




    User Feedback

    Recommended Comments

    JorgeB

    Posted

    This was a filesystem problem:

    Nov 28 15:16:22 nicknas2 kernel: BTRFS: error (device nvme0n1p1) in __btrfs_free_extent:3066: errno=-2 No such entry
    Nov 28 15:16:22 nicknas2 kernel: BTRFS info (device nvme0n1p1): forced readonly

     

    If you reformatted cache you already did what needed to be done, closing this since it's a general support issue.

     

    JorgeB

    Posted

    Changed Status to Closed

    Changed Priority to Other

    nickp85

    Posted

    4 hours ago, JorgeB said:

    This was a filesystem problem:

    
    Nov 28 15:16:22 nicknas2 kernel: BTRFS: error (device nvme0n1p1) in __btrfs_free_extent:3066: errno=-2 No such entry
    Nov 28 15:16:22 nicknas2 kernel: BTRFS info (device nvme0n1p1): forced readonly

     

    If you reformatted cache you already did what needed to be done, closing this since it's a general support issue.

     

    I’m not so sure this is general support. I just rebuilt my cache after initially going to 6.9 a couple months back to get the new benefits. All I use the cache for is Docker/Libvirt images, a windows 10 VM C drive image and appdata. I also use it to speed up processing of downloaded content to the array.

     

    would it be normal that the file system would die after such a short period of time?

    JorgeB

    Posted

    It can happen with for example an unclean shutdown, or some hardware issue like bad RAM, and at most could be a btrfs issue, not Unraid.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...