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 Pool] Unmountable: No file system on cache power outage [SOLVED]

Featured Replies

Hi Guys,

 

I am suffering Cache Pool Error: Unmountable: No file system

 

It happens after a power outage, and when I start the system, the cache pool show up this error.

 

Looks like all my docker and VM are gone, do they on cache pool only?

 

My Cache Pool has two drives

 

Any idea how can i get it back working? I guess the btrfs FS corrupted.

 

Something I have attempted:

Swap disk 1 and disk 2 in the cache pool, start the pool and same error.

New Config with preserve all. 

 

Diag file attached. 

Linux 4.19.56-Unraid.
root@ytwytw-UnRaid:~# btrfs fi show
Label: none  uuid: d2d575b7-f239-4017-9656-a135dfb74dfc
        Total devices 1 FS bytes used 1.60TiB
        devid    1 size 2.73TiB used 1.66TiB path /dev/md1

Label: none  uuid: 810a7385-3a47-408d-81c1-f048223867be
        Total devices 1 FS bytes used 1.54TiB
        devid    1 size 2.73TiB used 1.54TiB path /dev/md2

Label: none  uuid: efe3befc-29f9-4f9b-a790-0cf7684ba7c7
        Total devices 2 FS bytes used 61.89GiB
        devid    1 size 1.86TiB used 123.01GiB path /dev/sdg1
        devid    2 size 931.51GiB used 122.00GiB path /dev/sdf1

root@ytwytw-UnRaid:~# blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" TYPE="vfat" PARTUUID="bf0bd612-01"
/dev/sr0: UUID="2019-05-10-17-35-16-00" LABEL="FREENAS" TYPE="iso9660" PTTYPE="PMBR"
/dev/sr1: UUID="4cae832f0000fbc9" LABEL="SMI_IMAGE" TYPE="udf"
/dev/sr2: UUID="2019-03-24-11-53-12-00" LABEL="M-SM-EM-FM-tM-MM-(" TYPE="iso9660"
/dev/sdb1: UUID="d2d575b7-f239-4017-9656-a135dfb74dfc" UUID_SUB="82c005dd-a475-4c7e-b612-91e0acbf664a" TYPE="btrfs" PARTUUID="043dc239-ac42-448a-b9b5-9159a6e94701"
/dev/sdc1: UUID="810a7385-3a47-408d-81c1-f048223867be" UUID_SUB="df2d5a45-2d58-412e-83d2-9502fccb5ed3" TYPE="btrfs" PARTUUID="b8c704a4-b71f-4997-9dac-df9b96fe5e4c"
/dev/sdf1: UUID="efe3befc-29f9-4f9b-a790-0cf7684ba7c7" UUID_SUB="01e7ab78-4a29-433c-a34a-551946b72f02" TYPE="btrfs"
/dev/sdg1: UUID="efe3befc-29f9-4f9b-a790-0cf7684ba7c7" UUID_SUB="8c6c2fef-227e-4025-be8c-b85678bcac22" TYPE="btrfs"
/dev/md1: UUID="d2d575b7-f239-4017-9656-a135dfb74dfc" UUID_SUB="82c005dd-a475-4c7e-b612-91e0acbf664a" TYPE="btrfs"
/dev/md2: UUID="810a7385-3a47-408d-81c1-f048223867be" UUID_SUB="df2d5a45-2d58-412e-83d2-9502fccb5ed3" TYPE="btrfs"
/dev/sde1: PARTUUID="eb3a79e1-70b9-4d6f-aabc-8eed48aad437"
/dev/sdd1: PARTUUID="5898881b-7b10-42cb-9fb6-1f25b1c07cbd"
root@ytwytw-UnRaid:~# btrfs fi show efe3befc-29f9-4f9b-a790-0cf7684ba7c7
Label: none  uuid: efe3befc-29f9-4f9b-a790-0cf7684ba7c7
        Total devices 2 FS bytes used 61.89GiB
        devid    1 size 1.86TiB used 123.01GiB path /dev/sdg1
        devid    2 size 931.51GiB used 122.00GiB path /dev/sdf1

 

ytwytw-unraid-diagnostics-20191103-1800.zip

Edited by ytwytw

  • Community Expert

There is a hardware problem with cache1:

Nov  3 09:45:35 ytwytw-UnRaid kernel: ata6.00: status: { DRDY DF ERR }
Nov  3 09:45:35 ytwytw-UnRaid kernel: ata6.00: error: { ABRT }
Nov  3 09:45:35 ytwytw-UnRaid kernel: ata6.00: configured for UDMA/33
Nov  3 09:45:35 ytwytw-UnRaid kernel: scsi_io_completion_action: 9 callbacks suppressed
Nov  3 09:45:35 ytwytw-UnRaid kernel: sd 7:0:0:0: [sdg] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov  3 09:45:35 ytwytw-UnRaid kernel: sd 7:0:0:0: [sdg] tag#18 Sense Key : 0x5 [current]
Nov  3 09:45:35 ytwytw-UnRaid kernel: sd 7:0:0:0: [sdg] tag#18 ASC=0x21 ASCQ=0x4
Nov  3 09:45:35 ytwytw-UnRaid kernel: sd 7:0:0:0: [sdg] tag#18 CDB: opcode=0x2a 2a 00 00 3b 27 30 00 00 10 00
Nov  3 09:45:35 ytwytw-UnRaid kernel: print_req_error: 9 callbacks suppressed
Nov  3 09:45:35 ytwytw-UnRaid kernel: print_req_error: I/O error, dev sdg, sector 3876656

 

Replace cables and post new diags if still unmountable.

  • Author

I can confirm the cache1 drive is completely dead. 

 

Is it possible to recover data from cache2?

 

Thanks, 

  • Community Expert
27 minutes ago, ytwytw said:

Is it possible to recover data from cache2?

It should be if pool was redundant, note that there's a bug with v6.7 that if the pool was created there it won't be.

 

Try starting the array with just cache2 an post new diags if unmountable.

  • Community Expert

Filesystem is corrupt, there are some recovery options here, you can try those.

  • Author

Thanks, I got the data out of the disk. 

 

How can I restore my docker config and VM config? Is there any procedure I can follow?

 

Thanks, 

  • Community Expert

For dockers see here, for VMs you need the libvirt.img and the vdisks, if you don't have libvirt.img you can try recreating the VM as it was and point to the existing vdisk.

  • Author

Thanks so much, everything is back working now again.

Archived

This topic is now archived and is closed to further replies.

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.