I just replaced my cache drive from a 1TB drive to a new 2TB drive. Both drives were formatted for ZFS. I followed the steps in the SpaceInvaderOne guide to replace the cache drive and used mover to move the files and then move them back. Most of my Docker containers and all of my VMs started with no issue. The exception was Jellyfin and Nextcloud. These would show as started in the GUI, but would not allow access to the WEBUI. I checked the folders on the cache and they were empty. Jellyfin logs were giving a "insufficient permisions, unable to write to /config ..." type error. 

 

In an attempt to resolve the issue, I first ran the New Permissions Tool, when that didn't resolve the issue, I removed the Jellyfin container and attempted to rebuild. I attempted to remove the full container and files by using the CA Appdata cleanup tool and it would allow the process but would referesh and the folder would remain. 

 

After rebooting the system, the cache drive is now showing as unmountable and it's asking to format.

Am I able to remount the drive as it was without formatting? If not, how can I retreive the files that are currently on the drive so I don't have to rebuild all of my containers and VMs?

 

Diagnostics are attached. 

lovenest-diagnostics-20250428-1534.zip

Post the output of:

zpool import

 

1 hour ago, JorgeB said:

Post the output of:

zpool import

 

It says "no pools available to import"

According to that, there are no zfs pool to import, post the output from

blkid

and

fdisk -l /dev/nvme0n1

 

5 hours ago, JorgeB said:

According to that, there are no zfs pool to import, post the output from

blkid

and

fdisk -l /dev/nvme0n1

 

 

It does appear to be zfs, though it's using the old layout, that should not happen with a new pool, maybe the pool is already imported? If not, it may be damaged, does 

zpool status

show anything?

1 minute ago, JorgeB said:

It does appear to be zfs, though it's using the old layout, that should not happen with a new pool, maybe the pool is already imported? If not, it may be damaged, does 

zpool status

show anything?

Nope, it says no pools available. This is a brand new drive that went from the box to the system.

And the pool was created using the GUI, with a fairly recent Unraid release?

 

Also try:

 

zpool import -d /dev/nvme0n1p1

and

zdb -l /dev/nvme0n1p1

 

Yes, I had to remove the old pool and create a new one to allow the drive to format. Using 7.0.1.

It doesn't look like there's any data left on the drive, should be around 900GB. I'm going to have to rebuild everything...

Something is missing I think, a new pool using an SSD, should always have the partition start on sector 2048, not 64, but the main issue is that the zfs label/superblock appears to be damaged.

 

13 minutes ago, kal-el681 said:

I'm going to have to rebuild everything...

I'm afraid so.

Rebuilt the cache from backups. Not sure what happened. Works great now. 

 

Thanks for the suggestions.