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 & no pool uuid errors

Featured Replies

Good Morning,

 

I am hoping someone can help, I appreciate your time. I have 2 12TB disks and 2 500GB disks in an external enclosure hooked up to unraid. They worked fine, 1 12TB parity, one 12TB disk and both 500gb setup in a "cache" pool as per space invader's tutorial. I have nextcloud installed and it's been great for months. I decided to move the 12TBs to the actual PC and that's where the issues started. I hit "New Configuration" and put the parity, data, and cache in correct slots. The parity and data loaded up, but the cache drives showed Unmountable: No pool uuid. I attempted to remove the cache pool drives, boot the array, stop array, add again, and boot with no success. I moved the drives back to the enclosure and now I have, in addition to the no pool uuid, Unmountable: Wrong or no file system for my 12TB data drive. Parity is showing green. Data says Device is disabled contents emulated. I've spent hours trying to fix it and scouring these forms. Attached is the diagnostics for the unraid box. I thought I had a backup off appdata on the disk but apparently the software I installed to backup off cache did not run so I do not have a backup of appdata. I have not wiped any disks and am hoping to recover the data.

 

https://drive.google.com/file/d/1NIaeyll3cmMJIDw16lvTzLh5h28XC8F6/view?usp=sharing

 

Thank you!

 

  • Community Expert

Not all USB bridges are transparent, one of the reasons we don't recommend using them, for now post the output of:

blkid

and 

fdisk -l /dev/sdc

 

P.S. next time please attach the diags directly to the forum

  • Author

Certainly. Thank you for your help!

 

blkid

/dev/sdb1: UUID="ef6f7470-eb21-4f29-b2a1-1a64f161d8aa" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="c30dbdf4-75fb-4fd7-9621-bea57caef9f2"
/dev/sde1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda1: UUID="ef6f7470-eb21-4f29-b2a1-1a64f161d8aa" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="fb90b082-2506-4052-8b5d-297d8412d5f7"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: LABEL="Recovery" BLOCK_SIZE="512" UUID="0A9A5EFA9A5EE1AD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="78f5e766-1bd3-4d79-a0ee-94d3d72914d3"
/dev/sdf4: BLOCK_SIZE="512" UUID="7428632D2862ED94" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6a0da973-0310-4fed-ab83-78b038390d6f"
/dev/sdf2: UUID="125F-3EFA" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="8d3df424-20b2-489c-9d64-000275052455"
/dev/loop0: TYPE="squashfs"
/dev/md1: UUID="ef6f7470-eb21-4f29-b2a1-1a64f161d8aa" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdf3: PARTLABEL="Microsoft reserved partition" PARTUUID="141a4f70-d254-4d75-8712-d4abed124476"
/dev/sdd1: PARTUUID="b101f880-01"
/dev/sdc1: PARTUUID="b101f886-01"

 

fdisk -l /dev/sdc

Disk /dev/sdc: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Generic DISK03  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb101f886

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1          64 976773167 976773104 465.8G 83 Linux

 

  • Community Expert
5 minutes ago, vmann said:
/dev/sdd1: PARTUUID="b101f880-01"
/dev/sdc1: PARTUUID="b101f886-01"

No valid filesystem is being detected, the pool was originally working in this enclosure right?

 

If possible also post the output of blkid with the pool devices connected to SATA.

  • Author

Yes, it was working previously in the enclosure. This is with sata connected:

 

/dev/sde1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: LABEL="Recovery" BLOCK_SIZE="512" UUID="0A9A5EFA9A5EE1AD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="78f5e766-1bd3-4d79-a0ee-94d3d72914d3"
/dev/sdf4: BLOCK_SIZE="512" UUID="7428632D2862ED94" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6a0da973-0310-4fed-ab83-78b038390d6f"
/dev/sdf2: UUID="125F-3EFA" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="8d3df424-20b2-489c-9d64-000275052455"
/dev/loop0: TYPE="squashfs"
/dev/sdd1: UUID="ef6f7470-eb21-4f29-b2a1-1a64f161d8aa" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="c30dbdf4-75fb-4fd7-9621-bea57caef9f2"
/dev/sdc1: UUID="ef6f7470-eb21-4f29-b2a1-1a64f161d8aa" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="fb90b082-2506-4052-8b5d-297d8412d5f7"
/dev/sdf3: PARTLABEL="Microsoft reserved partition" PARTUUID="141a4f70-d254-4d75-8712-d4abed124476"

 

Edited by vmann

  • Community Expert

I assume they are not appearing in the list above? Post the sfdisk -l output of one of them

  • Author

Weird, they do not appear when connected via sata.

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.