Jump to content

  • [6.11.5] BTRFS error

    NathanR

    By NathanR

      • Closed

    Power outage caused my server to shutdown gracefully.

    I turned it on normally (via IPMI) and this shows up.

    Docker & VM don't work (obviously).

     

    Not sure if safe to update to latest release or not?

    I have backups on the array so I can fix it worst case scenario.

     

    I put the array in maintenance mode and don't get any errors/warnings.

    Cache is in BTRFS mirror mode.

     

    Scrub didn't show anything.

    Filesystem check didn't show anything.

     

    I haven't updated because I plan in moving to an intel build for Intel quicksync, but haven't had time. Just left it running for last 6 months, haha :)

     

    Note: I did submit a bug report via the official GUI. But figured I could get the answer to upgrade here in the forums quicker.

      

    May 10 13:41:34 Storinator kernel: loop2: detected capacity change from 0 to 62914560
May 10 13:41:34 Storinator kernel: BTRFS: device fsid 3a50e386-e261-4e10-8246-1e28523bd03e devid 1 transid 1511578 /dev/loop2 scanned by mount (30967)
May 10 13:41:34 Storinator kernel: BTRFS info (device loop2): using free space tree
May 10 13:41:34 Storinator kernel: BTRFS info (device loop2): has skinny extents
May 10 13:41:35 Storinator kernel: BTRFS info (device loop2): start tree-log replay
May 10 13:41:35 Storinator kernel: lo_write_bvec: 4 callbacks suppressed
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 307904512, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 601376 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: btrfs_dev_stat_print_on_error: 4 callbacks suppressed
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 39469056, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 77088 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 307855360, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 601280 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 39419904, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 76992 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 307445760, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 600480 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 39010304, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 76192 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 309346304, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 604192 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 40910848, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 79904 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 308871168, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 603264 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 40435712, length 4096.
May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 78976 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
May 10 13:41:35 Storinator kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2418: errno=-5 IO failure (Error while writing out transaction)
May 10 13:41:35 Storinator kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction.
May 10 13:41:35 Storinator kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1982: errno=-5 IO failure
May 10 13:41:35 Storinator kernel: BTRFS: error (device loop2: state EA) in btrfs_replay_log:2500: errno=-5 IO failure (Failed to recover log tree)
May 10 13:41:35 Storinator root: mount: /var/lib/docker: can't read superblock on /dev/loop2.
May 10 13:41:35 Storinator root:        dmesg(1) may have more information after failed mount system call.
May 10 13:41:35 Storinator root: mount error
May 10 13:41:35 Storinator kernel: BTRFS error (device loop2: state EA): open_ctree failed

      

    Model:	Custom
M/B:	ASRockRack X570D4U-2L2T Version - s/n: 208002330000188
BIOS:	American Megatrends International, LLC. Version P1.40. Dated: 05/19/2021
CPU:	AMD Ryzen 9 5900X 12-Core @ 3700 MHz
HVM:	Enabled
IOMMU:	Enabled
Cache:	768 KiB, 6 MB, 64 MB
Memory:	64 GiB DDR4 Multi-bit ECC (max. installable capacity 128 GiB)
Network:	bond0: fault-tolerance (active-backup), mtu 1500
Kernel:	Linux 5.19.17-Unraid x86_64
OpenSSL:	1.1.1s

     

    storinator-diagnostics-20240510-1346.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    NathanR

    What I also don't get (and think something worse is borked) is none of my main screen stats work

     

    They always have?

     

    Is the USB somehow corrupt? I don't get any boot errors watching the IPMI monitor during boot.

     

    image.thumb.png.880513cb34100dbfadff07a5cb562115.png

    Link to comment
    zoggy

    zoggy 37

    Posted (edited)

    per logs it looks like your cache went poof..   guessing from above ran out of space in your docker.img

     

    btw per smart data one of the drives is 84C!!  not sure if your not using a heatsink or what..but double check to make sure it has termalpad/heatsink or some form of active cooling. 

    Model Number:                       Samsung SSD 980 1TB
Serial Number:                      S64ANJ0RA03879F
Firmware Version:                   1B4QFXO7


=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- temperature is above or below threshold

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x02
Temperature:                        84 Celsius

     

    those samsung 980 series had a bad firmware and about a year ago samsung released a fix to stop them from dieing prematurely and going read only...
    both of your drives need their firmware updated. if the drive went read only.. then you might have to just look at getting a replacement.

     

    for more info

    https://www.pcgamer.com/an-error-in-samsungs-980-pro-firmware-is-causing-ssds-to-die-id-check-your-drive-right-now-tbh/

     

     

    and if you want to know how to update your samsung firmware check out:

     

    Edited by zoggy
    Link to comment
    JorgeB

    Looks like the docker image was on disk1, and disk1 got completely full, hence the errors, check that is was recreated on the pool.

     

    P.S. this is a general support issue, not a bug, next time please use the general support forum.

    Link to comment


    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...