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.

CACHE DISK POSSIBLY CORRUPTED

Featured Replies

I recently built a new server and wanted to move my cache pool of 2 ssds to a new one of 2 NVMes. I first booted the server and started the array with just one of the 2 ssd installed. There was a lot of activity on the disk and I then went to stop the array. It told me there was a btrfs operation in progress and would not let me. So I waited for it to finish. Once finished I stopped the array and followed instructions here.

 

After following these instructions, if I recall correctly, nothing happened. I know that sounds bad, like I wasn't paying attention, but at this point I've tried so many things and what feels like an eternity has passed that I can't remember. So I then stopped the array yet again. I thought ok I'll just go back to the original ssd. When I picked it from the list it told me this device was wrong. I started the array anyways and it tells me it's unmountable.

 

I then tried all the commands here. Which all resulted in the following: 

mount: /temp: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.

 

When running btrfs check --repair /dev/sda1 I get the following: 

Starting repair.
Opening filesystem to check...
No valid Btrfs found on /dev/sda1
ERROR: cannot open file system

 

Finally, I ran the command btrfs check -s 1 /dev/sda1 as suggested here and got the following: 

using SB copy 1, bytenr 67108864
Opening filesystem to check...
warning, device 2 is missing
Checking filesystem on /dev/sda1
UUID: 6e29690f-b1c4-44e7-82ea-69b91542a53f
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 79680425984 bytes used, no error found
total csum bytes: 37951400
total tree bytes: 188710912
total fs tree bytes: 75956224
total extent tree bytes: 55312384
btree space waste bytes: 37890887
file data blocks allocated: 389775470592
 referenced 70950273024

 

At this point I don't know what else to try. Before send ing this I did reboot the server and try all the commands but there was no change. I do still have both disks but at this point they've both been through the exact same processes.

 

Edit: I have just plugged in both SSDs and tried to mount the only mountable one by clicking mount with Unassigned Devices. I got the following: 

Feb  3 20:59:04 DuckyServer unassigned.devices: Mount of 'sdi1' failed: 'mount: /mnt/disks/WD-WCC4M0429617: mount(2) system call failed: Structure needs cleaning.        dmesg(1) may have more information after failed mount system call. '
Feb  3 20:59:04 DuckyServer unassigned.devices: Partition 'WD-WCC4M0429617' cannot be mounted.

AND IN THE LOG

[  665.697291] XFS (sdi1): Corruption detected. Unmount and run xfs_repair
[  665.697653] XFS (sdi1): log has mismatched uuid - can't recover
[  665.697657] XFS (sdi1): empty log check failed
[  665.697658] XFS (sdi1): log mount/recovery failed: error -117
[  665.697844] XFS (sdi1): log mount failed

 

duckyserver-diagnostics-20230203-2054.zip

Solved by Kameechewa

  • Author
  • Solution

Great news! I got it! I ran this command btrfs-select-super -s 1 /dev/sdj1 from here and was able to mount the disk! After mounting I just copied all the folders from it to my new cache pool, rebooted, and bam! Everything loaded up like before and was happy.

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.