Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Many Syslog Error 2027 "'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. "

Featured Replies

  • Community Expert

There are entries of the form:

Oct 26 18:52:33 Server kernel: BTRFS error (device md1p1): incorrect extent count for 52643758080; counted 49, expected 2147483697
Oct 26 18:52:33 Server kernel: BTRFS error (device md1p1): incorrect extent count for 56938725376; counted 212, expected 2147483860

 

This suggests a problem with disk1.   Probably need to run a check filesystem on it to rectify this.   The full diagnostics might give a better value.

  • Community Expert

There appear to be issues with multiple filesystems, reboot and post the diagnostics after array start.

  • Community Expert

Btrfs is detecting data corruption on all 3 disks, run memtest first and then scrub all the disks.

  • Author

HDD1:

Error summary: csum=12 Corrected: 0 Uncorrectable: 12 Unverified: 0

 

HDD2:

Error summary: no errors found

 

HDD3:

Error summary: no errors found

 

---> So this is the result. Memtest test was fine

  • Community Expert
29 minutes ago, 3498BoyZ said:

So this is the result. Memtest test was fine

Keep in mind that memtest is only definitive if it finds errors

 

Look in the syslog for the list of corrupt files from disk1 and delete them, restore from a backup, then reset the stats for all filesystems and keep monitoring, if more corruptions are found, there's still a problem.

  • 1 month later...
  • Author

@JorgeB this is my output for the command "sudo dmesg". I dont know how to look for the corrupted files :/

 

"[121687.913454] BTRFS error (device md1p1): incorrect extent count for 56938725376; counted 213, expected 2147483861
[121687.913477] BTRFS: error (device md1p1: state A) in convert_free_space_to_bitmaps:333: errno=-5 IO failure
[121687.913504] BTRFS info (device md1p1: state EA): forced readonly
[121687.913512] BTRFS: error (device md1p1: state EA) in add_to_free_space_tree:1051: errno=-5 IO failure
[121687.913532] BTRFS: error (device md1p1: state EA) in do_free_extent_accounting:2854: errno=-5 IO failure
[121687.913552] BTRFS error (device md1p1: state EA): failed to run delayed ref for logical 57541230592 num_bytes 8192 type 184 action 2 ref_mod 1: -5
[121687.913565] BTRFS: error (device md1p1: state EA) in btrfs_run_delayed_refs:2150: errno=-5 IO failure
[121687.913632] BTRFS info (device md1p1: state EA): balance: ended with status: -5
[121698.217335] loop: Write error at byte offset 844722176, length 4096.
[121698.217349] loop: Write error at byte offset 845230080, length 4096.
[121698.217377] I/O error, dev loop2, sector 1649848 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
[121698.217390] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 30, gen 0
[121698.217416] I/O error, dev loop2, sector 1650840 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
[121698.217426] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 30, gen 0
[121710.636041] loop: Write error at byte offset 862814208, length 4096.
[121710.636083] I/O error, dev loop2, sector 1685184 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2
[121710.636097] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 30, gen 0
[121714.560286] loop: Write error at byte offset 4346892288, length 4096.
[121714.560321] I/O error, dev loop2, sector 8490024 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
[121714.560336] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 30, gen 0
[121719.217026] loop: Write error at byte offset 343932928, length 4096.
[121719.217041] loop: Write error at byte offset 75497472, length 4096.
[121719.217047] loop: Write error at byte offset 343785472, length 4096.
[121719.217053] loop: Write error at byte offset 75350016, length 4096.
[121719.217058] loop: Write error at byte offset 343687168, length 4096.
[121719.217063] loop: Write error at byte offset 75251712, length 4096.
[121719.217068] loop: Write error at byte offset 337641472, length 4096.
[121719.217073] loop: Write error at byte offset 69206016, length 4096.
[121719.217078] loop: Write error at byte offset 336560128, length 4096.
[121719.217083] loop: Write error at byte offset 68124672, length 4096.
[121719.217112] I/O error, dev loop2, sector 671744 op 0x1:(WRITE) flags 0x1800 phys_seg 5 prio class 2
[121719.217126] I/O error, dev loop2, sector 147456 op 0x1:(WRITE) flags 0x1800 phys_seg 5 prio class 2
[121719.217136] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 30, gen 0
[121719.217148] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 30, gen 0
[121719.217206] I/O error, dev loop2, sector 671456 op 0x1:(WRITE) flags 0x1800 phys_seg 9 prio class 2
[121719.217216] I/O error, dev loop2, sector 147168 op 0x1:(WRITE) flags 0x1800 phys_seg 9 prio class 2
[121719.217224] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 30, gen 0
[121719.217232] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 30, gen 0
[121719.217267] I/O error, dev loop2, sector 671264 op 0x1:(WRITE) flags 0x1800 phys_seg 12 prio class 2
[121719.217275] I/O error, dev loop2, sector 146976 op 0x1:(WRITE) flags 0x1800 phys_seg 12 prio class 2
[121719.217283] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 30, gen 0
[121719.217291] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 30, gen 0
[121719.217341] I/O error, dev loop2, sector 659456 op 0x1:(WRITE) flags 0x1800 phys_seg 6 prio class 2
[121719.217349] I/O error, dev loop2, sector 135168 op 0x1:(WRITE) flags 0x1800 phys_seg 6 prio class 2
[121719.217356] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 11, rd 0, flush 0, corrupt 30, gen 0
[121719.217365] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 12, rd 0, flush 0, corrupt 30, gen 0
[121719.217399] I/O error, dev loop2, sector 657344 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 2
[121719.217407] I/O error, dev loop2, sector 133056 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 2
[121719.217415] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 13, rd 0, flush 0, corrupt 30, gen 0
[121719.217423] BTRFS error (device loop2): bdev /dev/loop2 errs: wr 14, rd 0, flush 0, corrupt 30, gen 0
[121719.217571] BTRFS: error (device loop2) in btrfs_commit_transaction:2496: errno=-5 IO failure (Error while writing out transaction)
[121719.217602] BTRFS info (device loop2: state E): forced readonly
[121719.217610] BTRFS warning (device loop2: state E): Skipping commit of aborted transaction.
[121719.217617] BTRFS: error (device loop2: state EA) in cleanup_transaction:1994: errno=-5 IO failure
[121772.630253] BTRFS info (device md1p1: state EA): scrub: started on devid 1
[121772.630259] BTRFS info (device md1p1: state EA): scrub: not finished on devid 1 with status: -30
[121843.552563] BTRFS info (device md1p1: state EA): scrub: started on devid 1
[121843.552569] BTRFS info (device md1p1: state EA): scrub: not finished on devid 1 with status: -30"

  • Community Expert
10 hours ago, 3498BoyZ said:

[121843.552569] BTRFS info (device md1p1: state EA): scrub: not finished on devid 1 with status: -30"

The scrub is aborting, recommend backing up and reformatting.

  • Author

@JorgeB do you can tell me a good solution to move all items from disk1 to disk2 and disk3? I am trying to do this with the plugin "unabalanced", but when i select all the items from disk1 the calculation at step2 takes too long.

image.png

  • Community Expert

I would recommend upgrading to v7-rc.2, you can then use the new mover function to empty an array disk.

  • Community Expert

v7 cannot have a pool with unassigned devices, just remove the pool for now, you can add it back later.

  • Author

root@Server:~# mover start -e disk1 |& logger &  
[1] 165045

 

root@Server :~# tail -f /var/log/syslog
Dec 23 17:09:16 Server crond[1731]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix.day.night/scripts/dynamix.day.night &> /dev/null
Dec 23 17:10:08 Server crond[1731]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix.day.night/scripts/dynamix.day.night &> /dev/null
Dec 23 17:11:09 Server root: mover: started
Dec 23 17:11:16 Server crond[1731]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix.day.night/scripts/dynamix.day.night &> /dev/null
Dec 23 17:11:47 Server root: move: /mnt/disk1/Media/Filme/Wo.mkv Read-only file system
Dec 23 17:12:15 Server root: move: /mnt/disk1/Media/Filme/Wi.mkv Read-only file system
 

 

root@Server :~# tail -f /var/log/syslog
Dec 23 17:15:00 Server root: Fix Common Problems Version 2024.12.19a
Dec 23 17:15:01 Server root: Fix Common Problems: Warning: Share Backup is an implied array-only share, but files / folders exist on the cache
Dec 23 17:15:01 Server root: Fix Common Problems: Error: Default docker appdata location is not a cache-only share
Dec 23 17:15:01 Server root: Fix Common Problems: Warning: Deprecated plugin ca.backup2.plg
Dec 23 17:15:07 Server webgui: File_put_contents_atomic failed to write / rename /mnt/disk1/684286639.tmp
Dec 23 17:15:07 Server root: Fix Common Problems: Error: Unable to write to disk1
Dec 23 17:15:14 Server root: Fix Common Problems: Other Warning: Background notifications not enabled
Dec 23 17:15:16 Server crond[1731]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix.day.night/scripts/dynamix.day.night &> /dev/null
Dec 23 17:16:07 Server root: move: /mnt/disk1/Media/Filme/An.mp4 Read-only file system
Dec 23 17:16:16 Server crond[1731]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix.day.night/scripts/dynamix.day.night &> /dev/null


--> disk1 is read only :/

Edited by 3498BoyZ

  • Community Expert

If it's read-only you can still copy the data, the mover should still work, just won't be able to delete it, or do it manually.

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
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.