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.

xfs drive "Unmountable: Unsupported or no file system" after move to new server.

Featured Replies

I recently moved my drives to a new server and one of my disks is not mounting "Unmountable: Unsupported or no file system" I have attempted to xfs_repair -L /dev/md4p1 but all I get is 

 

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock... and then endless periods (......... etc)

Am I out of luck?


here are my diagnostics
alecstormz-diagnostics-20241105-1239.zip


I ran fdisk -l /dev/sdk
 

Disk /dev/sdk: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD6003FFBX-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: DFC2B7FF-66A4-4612-838E-DF3498F945C9

Device     Start         End     Sectors  Size Type
/dev/sdk1     64 11721045134 11721045071  5.5T Linux filesystem



and I ran blkid
 

/dev/sdd1: LABEL="easystore14" BLOCK_SIZE="512" UUID="BCE44B73E44B2F48" TYPE="ntfs" PARTLABEL="easystore" PARTUUID="08dec140-4c3d-40b9-bb67-55780231c5aa"
/dev/sdb1: LABEL="easystore12" BLOCK_SIZE="512" UUID="62DA13FCDA13CAE5" TYPE="ntfs" PARTLABEL="easystore" PARTUUID="29d3e6a5-5bfb-4303-95e7-c2ca993819c1"
/dev/sde1: LABEL="easystore18" BLOCK_SIZE="512" UUID="9094D9D194D9BA44" TYPE="ntfs" PARTLABEL="easystore" PARTUUID="9c53af12-0f47-46d5-8726-44acd7ed7cd3"
/dev/sdc1: LABEL="My_Passport" BLOCK_SIZE="512" UUID="F474B7AA74B76DCC" TYPE="ntfs" PARTUUID="98b2df82-01"
/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: UUID="a4075403-34b9-4c9d-a300-f5b52dfc81b5" UUID_SUB="ef79d78c-2793-4ae8-a6c3-e729c054b70a" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/nvme0n1p1: UUID="a4075403-34b9-4c9d-a300-f5b52dfc81b5" UUID_SUB="a5157f58-37ae-46a9-93ad-a8fad727de0f" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdi1: UUID="41345b43-42a1-43fe-adde-c6bbc0aebcb1" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="bcffc674-6b50-4d88-8532-7a908fe1ed45"
/dev/sdg1: UUID="fb92734c-0777-4d4b-bd41-f8cc9f40eb27" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="955a34c5-c8ca-4e78-90e3-0987f7a4489b"
/dev/loop0: TYPE="squashfs"
/dev/sdj1: UUID="2f1f49f0-da75-43fd-b4e6-4ed604ff534a" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="0486784c-f748-4394-900c-e3e8feb4f9d0"
/dev/sdh1: UUID="fce2b400-bda0-4fed-814a-b7f50a85a5d6" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="704d604a-f864-443f-98c5-f59270ea1ce3"
/dev/md2p1: UUID="fb92734c-0777-4d4b-bd41-f8cc9f40eb27" BLOCK_SIZE="512" TYPE="xfs"
/dev/md1p1: UUID="41345b43-42a1-43fe-adde-c6bbc0aebcb1" BLOCK_SIZE="512" TYPE="xfs"
/dev/md3p1: UUID="2f1f49f0-da75-43fd-b4e6-4ed604ff534a" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdk1: PARTUUID="50a4ecc7-6c1f-4b83-ae4d-78b3ac040cb5"
/dev/loop2: UUID="51a4be1c-948f-4bb0-9c4a-68fb26850e99" UUID_SUB="dba694f8-5db4-46e7-8aa8-8621ef084775" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/loop3: UUID="4e4da922-889e-449e-b64f-681514fe10f9" UUID_SUB="098e8ed9-bb30-4dd4-814e-ae2ea6adefb6" BLOCK_SIZE="4096" TYPE="btrfs"



Thank you for any assistance!

Edited by nicodog11
formatting

  • Community Expert

Was that disk previously connected to a RAID controller or USB enclosure?

  • Author

It was previously connected to a Raid controller. I actually followed some of your other suggestions in previous threads and had to do data rebuilds on my other drives. My other 4 drives rebuilt no problem, just took about 8 hours a piece, but for some reason this one says active, normal operation and unmountable after the rebuild.

  • Community Expert

If parity is valid you can try to see if the disk can be emulated, if not, best bet may be using a file recovery app, like UFS explorer.

  • Author

Thank you! Parity is valid. Are there any specific steps to emulate the disk? I ask because when I’ve had drives fail it emulates automatically.

  • Community Expert

You just stop the array, unassign the disk, start the array.

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.