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.

Unable to Mount Two Disks

Featured Replies

I have two disks that I can't get mounted. I don't recall these two disks being unmounted in the past. I just happened to look in the Main tab in Unraid today and noticed both of these weren't mounted.

The log tells me that I should run xfs repair on the disk. That doesn't appear to help anyone from what I've been able to read in the comments. The Mount button is greyed out on the other disk ("Dev 2") so I don't know how I can even attempt to mount it.

Any idea how I can get these two drives mounted? Also, did I lose any data or was all of the data recovered using my other drives?

Below are screenshots showing the unmounted disks and the error I receive when I attempt to mount "Dev 1." I've also attached the Unraid log.

image.png

image.png

adamnas-syslog-20250917-0122.zip

  • Community Expert

Post the output from blkid

  • Author
3 hours ago, JorgeB said:

Post the output from blkid

Is this correct?

root@AdamNAS:~# blkid
/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2736-60C3" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdy1: UUID="2a2cca95-85bc-499d-a01d-5bc27078dddd" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="7e31c44b-f123-40dd-a67e-5992250dac55"
/dev/sdf1: UUID="75f9d0ec-3a38-433e-b12b-7c0cddc37b44" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="139e5605-cf3f-462a-bae1-0699343b183e"
/dev/md9p1: UUID="01d2b033-56eb-4a92-8140-e7a2c67c723e" BLOCK_SIZE="512" TYPE="xfs"
/dev/md24p1: UUID="5cbca378-bebc-4350-b0ae-9a25b89694ef" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdab1: UUID="5cbca378-bebc-4350-b0ae-9a25b89694ef" BLOCK_SIZE="512" TYPE="xfs"
/dev/nvme0n1p1: UUID="344c99ee-b4f3-4f0f-b5e7-7aaee08452db" UUID_SUB="909b61da-ebe7-48df-b330-3b9ef31d34a2" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/md15p1: UUID="a35a64da-1fc6-4f28-be6a-a8be2635cfa5" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdo1: UUID="a2c39444-e2c1-4e83-9774-2d256d5731c6" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="feeb342c-6327-49f2-a12d-1fb2bbc211a4"
/dev/sdw1: UUID="c824f10f-5b50-48ab-9a98-5b2bee9959ec" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="c70a31ee-1968-4173-848d-147c33045def"
/dev/sdd1: UUID="7a894f21-5d44-4d0a-9c3b-baa0b302946a" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="9d94fbfe-f13a-45b4-837b-82667e5ecafe"
/dev/md2p1: UUID="5c3f92e6-0b17-4086-809b-f72ce2324007" BLOCK_SIZE="512" TYPE="xfs"
/dev/md18p1: UUID="47686ff8-cb47-46fc-8f1d-a6936eab73cc" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdm1: UUID="b8947b2a-5d63-4579-a200-64ff0edd0b4c" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="d32a0e1e-1bb5-4b81-bbf5-bc56ae66488e"
/dev/sdu1: UUID="939316bb-0aee-4c42-a23f-3839a624e325" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="41f4fe70-c973-427f-9791-2a652067d59a"
/dev/sdb1: UUID="7cac0bbb-7684-4770-81eb-a895d087e38d" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="4ffe5da3-d79c-417e-aa6b-4740c6f092ec"
/dev/md5p1: UUID="a97b1e67-ef02-4cb2-b8d2-8127b90269af" BLOCK_SIZE="512" TYPE="xfs"
/dev/md20p1: UUID="fa6c6f67-cd60-4455-8be1-e75f19bbda88" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdk1: UUID="adf5de3b-0356-4037-8014-e5589c82c679" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e4e6b69b-e60c-4848-a1eb-63a7540c2f5b"
/dev/md11p1: UUID="612ec3b3-438d-4dc6-a970-d93ccbe3d49d" BLOCK_SIZE="512" TYPE="xfs"
/dev/sds1: UUID="a35a64da-1fc6-4f28-be6a-a8be2635cfa5" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="667314ed-7221-4313-a555-07b7e1aea25f"
/dev/md8p1: UUID="319360c3-4cf1-4169-a0eb-ba7a59bde24d" BLOCK_SIZE="512" TYPE="xfs"
/dev/md23p1: UUID="5e0928e9-591a-4557-a88b-02bc2512b85e" BLOCK_SIZE="512" TYPE="xfs"
/dev/md14p1: UUID="c8a417b0-ac7b-43a3-9c1b-602a6660f499" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdi1: UUID="01d2b033-56eb-4a92-8140-e7a2c67c723e" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="41e27694-0d4e-4533-b2df-dcc5a4c335ee"
/dev/sdq1: UUID="c8a417b0-ac7b-43a3-9c1b-602a6660f499" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="32d2d244-ad46-44b7-8800-c4681355d25c"
/dev/md1p1: UUID="75f9d0ec-3a38-433e-b12b-7c0cddc37b44" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdz1: UUID="82df71e7-39c0-496a-a478-2e993805fe84" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="61dd3ba6-23a7-4a9d-aa39-557b1a5d4838"
/dev/md17p1: UUID="939316bb-0aee-4c42-a23f-3839a624e325" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdg1: UUID="dc259314-267a-4920-a063-c4da71bb36c9" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="a8706993-478e-4e4b-a2a9-4924e3bf6de6"
/dev/md4p1: UUID="b8947b2a-5d63-4579-a200-64ff0edd0b4c" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop0: TYPE="squashfs"
/dev/sdx1: UUID="fa6c6f67-cd60-4455-8be1-e75f19bbda88" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="f342fc87-40a9-4e1e-9f4d-42a054aaaf6e"
/dev/sdaa1: UUID="5e0928e9-591a-4557-a88b-02bc2512b85e" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="4795e3a7-7c38-4e16-b077-2033ded1ea3a"
/dev/md10p1: UUID="dc259314-267a-4920-a063-c4da71bb36c9" BLOCK_SIZE="512" TYPE="xfs"
/dev/md7p1: UUID="adf5de3b-0356-4037-8014-e5589c82c679" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdn1: UUID="9bc821c4-c5ce-4ea1-8a4d-9bbc38ab963f" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="5380f5c8-95cb-4b07-a58c-3ca630ea44c0"
/dev/md22p1: UUID="2a2cca95-85bc-499d-a01d-5bc27078dddd" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdv1: UUID="47686ff8-cb47-46fc-8f1d-a6936eab73cc" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="13461bc2-ce77-42b8-8283-24f95b6cb381"
/dev/sdl1: UUID="a97b1e67-ef02-4cb2-b8d2-8127b90269af" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="9446ecdc-334b-46a8-ab1b-957ca576b7ac"
/dev/sdt1: UUID="5039051f-fbf5-4a89-bc8a-d051d362681c" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="592f0896-bd2e-4b74-a617-864794da6b81"
/dev/md16p1: UUID="82df71e7-39c0-496a-a478-2e993805fe84" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdj1: UUID="319360c3-4cf1-4169-a0eb-ba7a59bde24d" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="f0f7ef4d-fe93-41d0-bbad-2faf7200fe4f"
/dev/md3p1: UUID="7cac0bbb-7684-4770-81eb-a895d087e38d" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdr1: UUID="612ec3b3-438d-4dc6-a970-d93ccbe3d49d" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="8d261e3e-6664-4167-8004-20ee2410e00f"
/dev/md19p1: UUID="9bc821c4-c5ce-4ea1-8a4d-9bbc38ab963f" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdh1: UUID="5c3f92e6-0b17-4086-809b-f72ce2324007" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="d1c02c79-3e45-4804-8ec9-be020223bb68"
/dev/md6p1: UUID="7a894f21-5d44-4d0a-9c3b-baa0b302946a" BLOCK_SIZE="512" TYPE="xfs"
/dev/md21p1: UUID="c824f10f-5b50-48ab-9a98-5b2bee9959ec" BLOCK_SIZE="512" TYPE="xfs"
/dev/md12p1: UUID="a2c39444-e2c1-4e83-9774-2d256d5731c6" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop2: UUID="3d262e10-4bbb-4e31-81d3-9fd8d2ea4482" UUID_SUB="cae900b1-0a19-4150-bcd1-ef25d0a4575b" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sde1: PARTUUID="14d387da-b710-49d3-8a91-345dcf9458fb"
/dev/sdc1: PARTUUID="dfe0aca6-eac0-4d67-b17c-a27e44e4e4af"
/dev/loop3: UUID="80d91b4d-599f-409f-a343-e5e028ac3f84" UUID_SUB="685c96dd-d859-4b16-9386-d6f5d193702c" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdp1: PARTUUID="c2b135b9-8332-11ed-9f01-841b7729c4a2"
root@AdamNAS:~# 
  • Community Expert

Now output from:

xfs_repair -v /dev/sdt1

and

wipefs /dev/sdp1

  • Author
12 hours ago, JorgeB said:

Now output from:

xfs_repair -v /dev/sdt1

and

wipefs /dev/sdp1

Will this clear anything on the drive if there was something? Just want to know before I try running them.

  • Community Expert
6 hours ago, Dinglestains said:

Will this clear anything on the drive if there was something?

Not as written, it will just show if there are any filesystem signatures on the disk; blkid won't show them if there's more than one.

  • Author
3 hours ago, JorgeB said:

Not as written, it will just show if there are any filesystem signatures on the disk; blkid won't show them if there's more than one.

Thanks. Here's what I get when I enter those two commands.

root@AdamNAS:~# xfs_repair -v /dev/sdt1
Phase 1 - find and verify superblock...
        - block cache size set to 12287368 entries
Phase 2 - using internal log
        - zero log...
* ERROR: mismatched uuid in log
*            SB : 5039051f-fbf5-4a89-bc8a-d051d362681c
*            log: 1f85b4a8-9091-00d4-8094-6d04e9d2bca1
zero_log: head block 412672 tail block 2262025269
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
root@AdamNAS:~# wipefs /dev/sdp1
root@AdamNAS:~# 
  • Community Expert

Add -L 

xfs_repair -vL /dev/sdt1

The other disk doesn't have a valid filesystem signature, so there's no way to mount it. You can try a file recovery app like UFS Explorer; the free trial should show if it can recover anything.

  • Author

The output of that one was too large where I couldn't scroll to the beginning. Any idea where I can find the full output of the command to share?

  • Community Expert
xfs_repair -v /dev/sdt1

Run it again without -L and post that output.

  • Author
3 hours ago, JorgeB said:
xfs_repair -v /dev/sdt1

Run it again without -L and post that output.

Here's the output for this one.

root@AdamNAS:~# xfs_repair -v /dev/sdt1
Phase 1 - find and verify superblock...
        - block cache size set to 12287368 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 0 tail block 0
        - scan filesystem freespace and inode maps...
clearing needsrepair flag and regenerating metadata
sb_icount 204160, counted 32
sb_ifree 186, counted 29
sb_fdblocks 3646991750, counted 2929199533
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 2
        - agno = 6
        - agno = 4
        - agno = 10
        - agno = 1
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 3
        - agno = 5
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
SB summary counter sanity check failed
Metadata corruption detected at 0x47c2cb, xfs_sb block 0x0/0x200
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1
SB summary counter sanity check failed
Metadata corruption detected at 0x47c2cb, xfs_sb block 0x0/0x200
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1
xfs_repair: Releasing dirty buffer to free list!
xfs_repair: Refusing to write a corrupt buffer to the data device!
xfs_repair: Lost a write to the data device!

fatal error -- File system metadata writeout failed, err=117.  Re-run xfs_repair.
root@AdamNAS:~# 
  • Community Expert

Xfs_repair is unable to completely repair the filesystem, UFS explorer is likely also the best option to try and recover anything from that disk.

  • Author
22 minutes ago, JorgeB said:

Xfs_repair is unable to completely repair the filesystem, UFS explorer is likely also the best option to try and recover anything from that disk.

Thanks for trying to help me out. I've searched Unraid apps and don't see one named UFS Explorer. Is this an app I'll need to use on a Windows PC and pull the drive out of the server to check out?

Also, any idea how I can get the other drive mounted?

  • Author

Thanks. I'll check it out.

Is there a way to get these two drives mounted if I'm not worried about recovering any data that may have been on them?

  • Community Expert
14 hours ago, Dinglestains said:

Is there a way to get these two drives mounted if I'm not worried about recovering any data that may have been on them?

Yes, you would just need to reformat them.

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.