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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Error mounting file system (Trace dump in syslog)

Swixxy
in Prerelease Support [DEPRECATED]

Featured Replies

Hey guys, so today my flash drive seems like it corrupted slightly. Server was running fine, however my flash drive became unresponsive, so i booted down, and ran chkdsk on the flash. Booted up successfully, however since then every time i try to start unraid it gives me this error in the syslog. It spins up the drives perfectly fine in maintenance mode, not sure what the error is. I've since updated to the latest version of unraid, just in case maybe an old file was corrupted however its still doing the same thing.

 

 

Any advice? seems like there hasn't been this error posted on here before, im a bit stumped with how to proceed. I thought at first it might just be disk11, however i've since tried to remove it from my array and boot, but it seems to not be related to the last disk, but rather mounting the unraid filesystem itself? I'm going to go through and reseat each cable one by one, just incase its an odd little hardware bug, however if anybody could help out, id be most grateful.

  

Jun 10 20:00:44 jbox emhttp: shcmd (109): mkdir -p /mnt/disk11
Jun 10 20:00:44 jbox emhttp: shcmd (110): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md11 /mnt/disk11 |& logger
Jun 10 20:00:44 jbox kernel: XFS (md11): Mounting V5 Filesystem
Jun 10 20:00:44 jbox kernel: XFS (md11): Starting recovery (logdev: internal)
Jun 10 20:00:55 jbox kernel: XFS (md11): _xfs_buf_find: Block out of range: block 0x7fffffff8, EOFS 0x2baa0f448 
Jun 10 20:00:55 jbox kernel: ------------[ cut here ]------------
Jun 10 20:00:55 jbox kernel: WARNING: CPU: 3 PID: 5792 at fs/xfs/xfs_buf.c:521 _xfs_buf_find+0x7f/0x28c
Jun 10 20:00:55 jbox kernel: Modules linked in: md_mod e1000e ptp pps_core coretemp kvm_intel kvm i2c_i801 i2c_smbus i2c_core ahci libahci mvsas libsas scsi_transport_sas acpi_cpufreq [last unloaded: md_mod]
Jun 10 20:00:55 jbox kernel: CPU: 3 PID: 5792 Comm: mount Not tainted 4.9.30-unRAID #1
Jun 10 20:00:55 jbox kernel: Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010
Jun 10 20:00:55 jbox kernel: ffffc900089038a8 ffffffff813a4a1b 0000000000000000 ffffffff81965360
Jun 10 20:00:55 jbox kernel: ffffc900089038e8 ffffffff8104d0d9 0000020900000008 ffff88020634e000
Jun 10 20:00:55 jbox kernel: ffff880207b1d240 ffff880207b1d240 0000000000000000 0000000000000000
Jun 10 20:00:55 jbox kernel: Call Trace:
Jun 10 20:00:55 jbox kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e
Jun 10 20:00:55 jbox kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3
Jun 10 20:00:55 jbox kernel: [<ffffffff8104d1a1>] warn_slowpath_null+0x18/0x1a
Jun 10 20:00:55 jbox kernel: [<ffffffff8129a9f3>] _xfs_buf_find+0x7f/0x28c
Jun 10 20:00:55 jbox kernel: [<ffffffff8129ac24>] xfs_buf_get_map+0x24/0x12b
Jun 10 20:00:55 jbox kernel: [<ffffffff812c0fb0>] xfs_trans_get_buf_map+0x83/0xaa
Jun 10 20:00:55 jbox kernel: [<ffffffff81276512>] xfs_btree_get_bufs+0x4b/0x4d
Jun 10 20:00:55 jbox kernel: [<ffffffff812656eb>] xfs_alloc_fix_freelist+0x197/0x317
Jun 10 20:00:55 jbox kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a
Jun 10 20:00:55 jbox kernel: [<ffffffff81265c4b>] xfs_free_extent_fix_freelist+0x5f/0x8a
Jun 10 20:00:55 jbox kernel: [<ffffffff81265cbd>] xfs_free_extent+0x47/0x115
Jun 10 20:00:55 jbox kernel: [<ffffffff812c1555>] xfs_trans_free_extent+0x28/0x65
Jun 10 20:00:55 jbox kernel: [<ffffffff812b932c>] xfs_efi_recover+0x129/0x161
Jun 10 20:00:55 jbox kernel: [<ffffffff812bbd51>] xlog_recover_process_efi+0x35/0x4d
Jun 10 20:00:55 jbox kernel: [<ffffffff812bbee7>] xlog_recover_process_intents+0x97/0x100
Jun 10 20:00:55 jbox kernel: [<ffffffff811369ca>] ? unlock_new_inode+0x57/0x5c
Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] xlog_recover_finish+0x18/0x8b
Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] ? xlog_recover_finish+0x18/0x8b
Jun 10 20:00:55 jbox kernel: [<ffffffff812b5091>] xfs_log_mount_finish+0x20/0x36
Jun 10 20:00:55 jbox kernel: [<ffffffff812ac969>] xfs_mountfs+0x63b/0x769
Jun 10 20:00:55 jbox kernel: [<ffffffff812b06a5>] xfs_fs_fill_super+0x485/0x536
Jun 10 20:00:55 jbox kernel: [<ffffffff81123ea9>] mount_bdev+0x139/0x18b
Jun 10 20:00:55 jbox kernel: [<ffffffff812b0220>] ? xfs_test_remount_options.isra.1+0x56/0x56
Jun 10 20:00:55 jbox kernel: [<ffffffff812af0c9>] xfs_fs_mount+0x10/0x12
Jun 10 20:00:55 jbox kernel: [<ffffffff81124bc1>] mount_fs+0xf/0x84
Jun 10 20:00:55 jbox kernel: [<ffffffff8113abe3>] vfs_kern_mount+0x65/0xf7
Jun 10 20:00:55 jbox kernel: [<ffffffff8113d444>] do_mount+0x744/0xa23
Jun 10 20:00:55 jbox kernel: [<ffffffff810de06c>] ? strndup_user+0x3a/0x6f
Jun 10 20:00:55 jbox kernel: [<ffffffff8113d919>] SyS_mount+0x72/0x9a
Jun 10 20:00:55 jbox kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9
Jun 10 20:00:55 jbox kernel: ---[ end trace 3680fca2721e9ba7 ]---
Jun 10 20:00:55 jbox kernel: XFS (md11): _xfs_buf_find: Block out of range: block 0x7fffffff8, EOFS 0x2baa0f448 
Jun 10 20:00:55 jbox kernel: ------------[ cut here ]------------
Jun 10 20:00:55 jbox kernel: WARNING: CPU: 3 PID: 5792 at fs/xfs/xfs_buf.c:521 _xfs_buf_find+0x7f/0x28c
Jun 10 20:00:55 jbox kernel: Modules linked in: md_mod e1000e ptp pps_core coretemp kvm_intel kvm i2c_i801 i2c_smbus i2c_core ahci libahci mvsas libsas scsi_transport_sas acpi_cpufreq [last unloaded: md_mod]
Jun 10 20:00:55 jbox kernel: CPU: 3 PID: 5792 Comm: mount Tainted: G        W       4.9.30-unRAID #1
Jun 10 20:00:55 jbox kernel: Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010
Jun 10 20:00:55 jbox kernel: ffffc900089038a8 ffffffff813a4a1b 0000000000000000 ffffffff81965360
Jun 10 20:00:55 jbox kernel: ffffc900089038e8 ffffffff8104d0d9 0000020900000008 0000000000000000
Jun 10 20:00:55 jbox kernel: ffff880207b1d240 ffff880207b1d240 ffff880205238900 ffff880205238900
Jun 10 20:00:55 jbox kernel: Call Trace:
Jun 10 20:00:55 jbox kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e
Jun 10 20:00:55 jbox kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3
Jun 10 20:00:55 jbox kernel: [<ffffffff8104d1a1>] warn_slowpath_null+0x18/0x1a
Jun 10 20:00:55 jbox kernel: [<ffffffff8129a9f3>] _xfs_buf_find+0x7f/0x28c
Jun 10 20:00:55 jbox kernel: [<ffffffff81299937>] ? xfs_buf_allocate_memory+0x161/0x2a1
Jun 10 20:00:55 jbox kernel: [<ffffffff8129ac70>] xfs_buf_get_map+0x70/0x12b
Jun 10 20:00:55 jbox kernel: [<ffffffff812c0fb0>] xfs_trans_get_buf_map+0x83/0xaa
Jun 10 20:00:55 jbox kernel: [<ffffffff81276512>] xfs_btree_get_bufs+0x4b/0x4d
Jun 10 20:00:55 jbox kernel: [<ffffffff812656eb>] xfs_alloc_fix_freelist+0x197/0x317
Jun 10 20:00:55 jbox kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a
Jun 10 20:00:55 jbox kernel: [<ffffffff81265c4b>] xfs_free_extent_fix_freelist+0x5f/0x8a
Jun 10 20:00:55 jbox kernel: [<ffffffff81265cbd>] xfs_free_extent+0x47/0x115
Jun 10 20:00:55 jbox kernel: [<ffffffff812c1555>] xfs_trans_free_extent+0x28/0x65
Jun 10 20:00:55 jbox kernel: [<ffffffff812b932c>] xfs_efi_recover+0x129/0x161
Jun 10 20:00:55 jbox kernel: [<ffffffff812bbd51>] xlog_recover_process_efi+0x35/0x4d
Jun 10 20:00:55 jbox kernel: [<ffffffff812bbee7>] xlog_recover_process_intents+0x97/0x100
Jun 10 20:00:55 jbox kernel: [<ffffffff811369ca>] ? unlock_new_inode+0x57/0x5c
Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] xlog_recover_finish+0x18/0x8b
Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] ? xlog_recover_finish+0x18/0x8b
Jun 10 20:00:55 jbox kernel: [<ffffffff812b5091>] xfs_log_mount_finish+0x20/0x36
Jun 10 20:00:55 jbox kernel: [<ffffffff812ac969>] xfs_mountfs+0x63b/0x769
Jun 10 20:00:55 jbox kernel: [<ffffffff812b06a5>] xfs_fs_fill_super+0x485/0x536
Jun 10 20:00:55 jbox kernel: [<ffffffff81123ea9>] mount_bdev+0x139/0x18b
Jun 10 20:00:55 jbox kernel: [<ffffffff812b0220>] ? xfs_test_remount_options.isra.1+0x56/0x56
Jun 10 20:00:55 jbox kernel: [<ffffffff812af0c9>] xfs_fs_mount+0x10/0x12
Jun 10 20:00:55 jbox kernel: [<ffffffff81124bc1>] mount_fs+0xf/0x84
Jun 10 20:00:55 jbox kernel: [<ffffffff8113abe3>] vfs_kern_mount+0x65/0xf7
Jun 10 20:00:55 jbox kernel: [<ffffffff8113d444>] do_mount+0x744/0xa23
Jun 10 20:00:55 jbox kernel: [<ffffffff810de06c>] ? strndup_user+0x3a/0x6f
Jun 10 20:00:55 jbox kernel: [<ffffffff8113d919>] SyS_mount+0x72/0x9a
Jun 10 20:00:55 jbox kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9
Jun 10 20:00:55 jbox kernel: ---[ end trace 3680fca2721e9ba8 ]---
Jun 10 20:00:55 jbox kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000f8
Jun 10 20:00:55 jbox kernel: IP: [<ffffffff812c12e1>] xfs_trans_binval+0x7/0x89
Jun 10 20:00:55 jbox kernel: PGD 23363a067 
Jun 10 20:00:55 jbox kernel: PUD 2058db067 
Jun 10 20:00:55 jbox kernel: PMD 0 
Jun 10 20:00:55 jbox kernel: 
Jun 10 20:00:55 jbox kernel: Oops: 0000 [#1] PREEMPT SMP
Jun 10 20:00:55 jbox kernel: Modules linked in: md_mod e1000e ptp pps_core coretemp kvm_intel kvm i2c_i801 i2c_smbus i2c_core ahci libahci mvsas libsas scsi_transport_sas acpi_cpufreq [last unloaded: md_mod]
Jun 10 20:00:55 jbox kernel: CPU: 3 PID: 5792 Comm: mount Tainted: G        W       4.9.30-unRAID #1
Jun 10 20:00:55 jbox kernel: Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010
Jun 10 20:00:55 jbox kernel: task: ffff8802341b9700 task.stack: ffffc90008900000
Jun 10 20:00:55 jbox kernel: RIP: 0010:[<ffffffff812c12e1>]  [<ffffffff812c12e1>] xfs_trans_binval+0x7/0x89
Jun 10 20:00:55 jbox kernel: RSP: 0018:ffffc900089039c8  EFLAGS: 00010246
Jun 10 20:00:55 jbox kernel: RAX: 0000000000000000 RBX: ffffc90008903ae0 RCX: 0000000000176b03
Jun 10 20:00:55 jbox kernel: RDX: 0000000000000008 RSI: 0000000000000000 RDI: ffff88020634e000
Jun 10 20:00:55 jbox kernel: RBP: ffffc900089039d8 R08: 000000000001b750 R09: ffffffff8129a3e2
Jun 10 20:00:55 jbox kernel: R10: ffffea0008148e00 R11: ffffffff81de6f0c R12: ffff88020634e000
Jun 10 20:00:55 jbox kernel: R13: ffff8802337e1200 R14: 0000000000000002 R15: ffff880205ecc000
Jun 10 20:00:55 jbox kernel: FS:  00002ae949f9ce40(0000) GS:ffff88023fcc0000(0000) knlGS:0000000000000000
Jun 10 20:00:55 jbox kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 10 20:00:55 jbox kernel: CR2: 00000000000000f8 CR3: 0000000233643000 CR4: 00000000000006e0
Jun 10 20:00:55 jbox kernel: Stack:
Jun 10 20:00:55 jbox kernel: ffffc90008903ae0 ffff88020634e000 ffffc90008903ad0 ffffffff812656f6
Jun 10 20:00:55 jbox kernel: 0000000608903a28 ffffffff8167c00e ffff88020509d680 0000000000000000
Jun 10 20:00:55 jbox kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jun 10 20:00:55 jbox kernel: Call Trace:
Jun 10 20:00:55 jbox kernel: [<ffffffff812656f6>] xfs_alloc_fix_freelist+0x1a2/0x317
Jun 10 20:00:55 jbox kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a
Jun 10 20:00:55 jbox kernel: [<ffffffff81265c4b>] xfs_free_extent_fix_freelist+0x5f/0x8a
Jun 10 20:00:55 jbox kernel: [<ffffffff81265cbd>] xfs_free_extent+0x47/0x115
Jun 10 20:00:55 jbox kernel: [<ffffffff812c1555>] xfs_trans_free_extent+0x28/0x65
Jun 10 20:00:55 jbox kernel: [<ffffffff812b932c>] xfs_efi_recover+0x129/0x161
Jun 10 20:00:55 jbox kernel: [<ffffffff812bbd51>] xlog_recover_process_efi+0x35/0x4d
Jun 10 20:00:55 jbox kernel: [<ffffffff812bbee7>] xlog_recover_process_intents+0x97/0x100
Jun 10 20:00:55 jbox kernel: [<ffffffff811369ca>] ? unlock_new_inode+0x57/0x5c
Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] xlog_recover_finish+0x18/0x8b
Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] ? xlog_recover_finish+0x18/0x8b
Jun 10 20:00:55 jbox kernel: [<ffffffff812b5091>] xfs_log_mount_finish+0x20/0x36
Jun 10 20:00:55 jbox kernel: [<ffffffff812ac969>] xfs_mountfs+0x63b/0x769
Jun 10 20:00:55 jbox kernel: [<ffffffff812b06a5>] xfs_fs_fill_super+0x485/0x536
Jun 10 20:00:55 jbox kernel: [<ffffffff81123ea9>] mount_bdev+0x139/0x18b
Jun 10 20:00:55 jbox kernel: [<ffffffff812b0220>] ? xfs_test_remount_options.isra.1+0x56/0x56
Jun 10 20:00:55 jbox kernel: [<ffffffff812af0c9>] xfs_fs_mount+0x10/0x12
Jun 10 20:00:55 jbox kernel: [<ffffffff81124bc1>] mount_fs+0xf/0x84
Jun 10 20:00:55 jbox kernel: [<ffffffff8113abe3>] vfs_kern_mount+0x65/0xf7
Jun 10 20:00:55 jbox kernel: [<ffffffff8113d444>] do_mount+0x744/0xa23
Jun 10 20:00:55 jbox kernel: [<ffffffff810de06c>] ? strndup_user+0x3a/0x6f
Jun 10 20:00:55 jbox kernel: [<ffffffff8113d919>] SyS_mount+0x72/0x9a
Jun 10 20:00:55 jbox kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9
Jun 10 20:00:55 jbox kernel: Code: 00 89 d6 83 ce 0a 80 e2 80 89 b0 80 00 00 00 75 12 55 89 ca 44 89 ce 48 89 c7 48 89 e5 e8 1f 77 ff ff 5d c3 55 48 89 e5 41 54 53 <48> 8b 9e f8 00 00 00 f6 83 80 00 00 00 04 75 6d 49 89 fc 48 89 
Jun 10 20:00:55 jbox kernel: RIP  [<ffffffff812c12e1>] xfs_trans_binval+0x7/0x89
Jun 10 20:00:55 jbox kernel: RSP <ffffc900089039c8>
Jun 10 20:00:55 jbox kernel: CR2: 00000000000000f8
Jun 10 20:00:55 jbox kernel: ---[ end trace 3680fca2721e9ba9 ]---
Jun 10 20:00:55 jbox emhttp: err: shcmd: shcmd (110): exit status: -119
Jun 10 20:00:55 jbox emhttp: mount error: No file system (-119)
Jun 10 20:00:55 jbox emhttp: shcmd (111): umount /mnt/disk11 |& logger
Jun 10 20:00:55 jbox root: umount: /mnt/disk11: not mounted
Jun 10 20:00:55 jbox emhttp: shcmd (112): rmdir /mnt/disk11
Jun 10 20:00:55 jbox emhttp: shcmd (113): mkdir -p /mnt/cache
Jun 10 20:00:56 jbox emhttp: shcmd (114): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdb1 /mnt/cache |& logger
Jun 10 20:00:56 jbox kernel: BTRFS info (device sdb1): disk space caching is enabled
Jun 10 20:00:56 jbox kernel: BTRFS info (device sdb1): has skinny extents
Jun 10 20:00:56 jbox kernel: BTRFS info (device sdb1): detected SSD devices, enabling SSD mode
Jun 10 20:00:56 jbox emhttp: shcmd (115): sync

Edited by Swixxy

  • Quote
    4 minutes ago, Swixxy said:

    I thought at first it might just be disk11,

    It is

    4 minutes ago, Swixxy said:

    tried to remove it from my array and boot,

    Won't make a difference because the parity system will emulate the removed disk (and the corruption)

     

    You need to Check Disk Filesystem on disk 11

  • Quote
    • Author

    Ah wicked thank you for the reply. So what do i do if the drive itself were to be dead? is there a way for me to force a repair on the parity disk emulated version, or will i have to reset all disks and rebuild parityfrom scratch

  • Quote

    If you've pulled the drive (and haven't rebuilt it), then the instructions will repair the emulated version and you'll then have to rebuild the drive.

     

    If you haven't pulled the drive (ie: Main doesn't show the disk as being redballed / missing), then the instructions will repair the drive and update parity at the same time.

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    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.