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.

Unmountable: Wrong or no file system

Featured Replies

Please help! Disk1 showing as Unmountable: Wrong or no file system

 

I got a free Dell R710 a few months ago. I added 8 brand new 5TB 2.5" drives which are setup as one virtual disk (Disk1) on the server and Unraid sees all the drives as one 40TB drive (disk 1 in array - btrfs). It has been working fine for about 3? months and then a day or two ago it is showing up as "unmountable: wrong or no file system". When I stop the array and attempt to mount the disk1 unassigned device it does not mount.

 

I am not sure what to look for or what to try. Any help is welcomed and greatly appreciated. 

 

Diagnostics ZIP is included. Please let me know if you need anything else to help troubleshoot.

 

Logs added below:

 

Disk1 log (after starting array):

 

Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] 78131494912 512-byte logical blocks: (40.0 TB/36.4 TiB)
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Write Protect is off
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Mode Sense: 1f 00 00 08
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  6 14:55:16 2sh33ts kernel: sdb: sdb1
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Attached SCSI disk
Feb  6 14:55:16 2sh33ts kernel: BTRFS: device fsid 38e06390-d984-4869-a705-134c421a015e devid 1 transid 124059 /dev/sdb1 scanned by udevd (1149)
Feb  6 14:56:15 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 14:56:15 2sh33ts kernel: mdcmd (2): import 1 sdb 64 39065747404 0 PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d
Feb  6 14:56:15 2sh33ts kernel: md: import disk1: (sdb) PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d size: 39065747404 
Feb  6 14:56:15 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:00:34 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:00:50 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 15:00:50 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:00:54 2sh33ts unassigned.devices: Adding partition 'sdb1'...
Feb  6 15:00:54 2sh33ts unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks/DELL_PERC_H700'...
Feb  6 15:00:54 2sh33ts unassigned.devices: Mount drive command: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime,space_cache=v2 '/dev/sdb1' '/mnt/disks/DELL_PERC_H700'
Feb  6 15:00:54 2sh33ts kernel: BTRFS info (device sdb1): using free space tree
Feb  6 15:00:54 2sh33ts kernel: BTRFS info (device sdb1): has skinny extents
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): parent transid verify failed on 11898137198592 wanted 124059 found 123412
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): parent transid verify failed on 11898137198592 wanted 124059 found 123412
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): failed to read block groups: -5
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): open_ctree failed
Feb  6 15:01:16 2sh33ts unassigned.devices: Mount of 'sdb1' failed: 'mount: /mnt/disks/DELL_PERC_H700: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '
Feb  6 15:18:53 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 15:18:53 2sh33ts kernel: mdcmd (2): import 1 sdb 64 39065747404 0 PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d
Feb  6 15:18:53 2sh33ts kernel: md: import disk1: (sdb) PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d size: 39065747404 
Feb  6 15:18:53 2sh33ts  emhttpd: read SMART /dev/sdb

 

 

 

btrfs check status:

 

parent transid verify failed on 11898137198592 wanted 124059 found 123412

parent transid verify failed on 11898137198592 wanted 124059 found 123412

parent transid verify failed on 11898137198592 wanted 124059 found 123412

Ignoring transid failure

parent transid verify failed on 11898135134208 wanted 124059 found 123411

parent transid verify failed on 11898135134208 wanted 124059 found 123411

parent transid verify failed on 11898135134208 wanted 124059 found 123411

Ignoring transid failure

ERROR: child eb corrupted: parent bytenr=11898052608000 item=17 parent level=2 child bytenr=11898135134208 child level=0
ERROR: failed to read block groups: Input/output error

ERROR: cannot open file system Opening filesystem to check...

 

 

Attempting to mount the unassigned device log:

 

Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] 78131494912 512-byte logical blocks: (40.0 TB/36.4 TiB)
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Write Protect is off
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Mode Sense: 1f 00 00 08
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  6 14:55:16 2sh33ts kernel: sdb: sdb1
Feb  6 14:55:16 2sh33ts kernel: sd 1:2:0:0: [sdb] Attached SCSI disk
Feb  6 14:55:16 2sh33ts kernel: BTRFS: device fsid 38e06390-d984-4869-a705-134c421a015e devid 1 transid 124059 /dev/sdb1 scanned by udevd (1149)
Feb  6 14:56:15 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 14:56:15 2sh33ts kernel: mdcmd (2): import 1 sdb 64 39065747404 0 PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d
Feb  6 14:56:15 2sh33ts kernel: md: import disk1: (sdb) PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d size: 39065747404 
Feb  6 14:56:15 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:00:34 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:00:50 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 15:00:50 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:00:54 2sh33ts unassigned.devices: Adding partition 'sdb1'...
Feb  6 15:00:54 2sh33ts unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks/DELL_PERC_H700'...
Feb  6 15:00:54 2sh33ts unassigned.devices: Mount drive command: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime,space_cache=v2 '/dev/sdb1' '/mnt/disks/DELL_PERC_H700'
Feb  6 15:00:54 2sh33ts kernel: BTRFS info (device sdb1): using free space tree
Feb  6 15:00:54 2sh33ts kernel: BTRFS info (device sdb1): has skinny extents
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): parent transid verify failed on 11898137198592 wanted 124059 found 123412
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): parent transid verify failed on 11898137198592 wanted 124059 found 123412
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): failed to read block groups: -5
Feb  6 15:01:14 2sh33ts kernel: BTRFS error (device sdb1): open_ctree failed
Feb  6 15:01:16 2sh33ts unassigned.devices: Mount of 'sdb1' failed: 'mount: /mnt/disks/DELL_PERC_H700: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '
Feb  6 15:18:53 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 15:18:53 2sh33ts kernel: mdcmd (2): import 1 sdb 64 39065747404 0 PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d
Feb  6 15:18:53 2sh33ts kernel: md: import disk1: (sdb) PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d size: 39065747404 
Feb  6 15:18:53 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:27:28 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 15:31:34 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 16:27:13 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 16:27:35 2sh33ts  emhttpd: PERC_H700_005d8d2c1f20cdfe2a001f6ede90f648_36848f690de6e1f002afecd201f2c8d5d (sdb) 512 78131494912
Feb  6 16:27:35 2sh33ts  emhttpd: read SMART /dev/sdb
Feb  6 16:27:41 2sh33ts unassigned.devices: Adding partition 'sdb1'...
Feb  6 16:27:41 2sh33ts unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks/DELL_PERC_H700'...
Feb  6 16:27:41 2sh33ts unassigned.devices: Mount drive command: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime,space_cache=v2 '/dev/sdb1' '/mnt/disks/DELL_PERC_H700'
Feb  6 16:27:41 2sh33ts kernel: BTRFS info (device sdb1): using free space tree
Feb  6 16:27:41 2sh33ts kernel: BTRFS info (device sdb1): has skinny extents

2sh33ts-diagnostics-20230206-1635.zip

Edited by 2sh33ts
add details

  • Community Expert

RAID controllers are NOT recommended for many reasons

  • Author

@trurl so what is recommended? Have each disk presented separately in the array and just divide up what shares should use certain disks? If that is the recommended design then I can approach that option after (hopefully) I am able to recover and back up my data in the current format.

 

Do you have any suggestions on how to proceed considering my current situation?

 

 

  • Community Expert

Why did you try to mount disk1 as an Unassigned Device? Don't do that. Unassigned Devices can't mount unmountable filesystems either. Fortunately Unraid still considers it enabled in the array.

 

Unfortunately, btrfs is harder to repair than xfs. I don't really have any experience but here is the FAQ on that, maybe @JorgeB will join in the morning.

 

 

 

  • Community Expert
11 hours ago, 2sh33ts said:

I added 8 brand new 5TB 2.5" drives which are setup as one virtual disk (Disk1) on the server and Unraid sees all the drives as one 40TB drive

This is a very bad idea.

 

11 hours ago, 2sh33ts said:

parent transid verify failed on 11898137198592 wanted 124059 found 123412

This error is fatal, it means some writes were lost, it can happen if a storage device lies about flushing it's write cache, this is usually a drive (or controller) firmware problem, most likely the controller in this case.

 

Btrfs restore (option #2 here) is the best bet to try and recover some data for this, then the device will need to be formatted and the data restore.

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.