After array rebuild, zfs disk error: "Unmountable: Unsupported or no file system"

[virtubit]

I shut down the server. Then I replaced my Disk 4 (22TB, zfs encrypted) in the array with a new 24TB hard drive. Booting up. Select the new hard drive as a replacement in the main window, started the array and let the rebuild finish.

 

After rebuilding it, though, the data on disc 4 seems to be missing. The new hard drive just says "Unmountable: Unsupported or no file system."

Any ideas why the rebuild didn't work?

Thank you!

oasis-diagnostics-20240804-2023.zip

Edited August 4 by virtubit

[virtubit]

I would also like to mention that I selected the zfs encrypted filesystem for the new disc before the array start and there was/is an option to format during and after the rebuild (which I did not do). Maybe it was my mistake to specify the file system before the rebuild?

Edited August 4 by virtubit

[JorgeB]

Is the old disk4 still connected or not? Also, with the array started post the output of:

zpool import

[JorgeB]

And don't format the disk.

[virtubit]

Thank you for your help. No, the old hard drive of disk 4 is not connected and no, I'm not formatting anything. Here is the output of zpool import:

 

I could replace disc 4 with another new hard drive and run the rebuild again. Or would that be a waste of time? 🙂

 

[JorgeB]

2 hours ago, virtubit said:

Or would that be a waste of time?

Most likely, if you still have the old disk, reconnect it and post the same output

[virtubit]

Thank you. Unfortunately, I no longer have the old hard drive. I will probably try the rebuild with another new hard drive without specifying the file system before the rebuild. That certainly won't help, but you never know. And I don't know of any other option at the moment.
Still very strange, I don't know what I could have done wrong.

[JorgeB]

1 hour ago, virtubit said:

I will probably try the rebuild with another new hard drive without specifying the file system before the rebuild.

Not sure what you mean, the filesystem has to be the same as the previous one, was it not zfs before? If not post the output of

blkid

 

[virtubit]

I have now replaced disc 4 with a new hard drive, but after the rebuild this did not produce any different results (as expected).

 

Here I specified the file system the first time before starting the array and before the first rebuild of the new hard drive (but without formatting of course).

 

It was previously zfs encrypted, like all discs in the array. And as I understand it, the rebuild happens at block level, there shouldn't have been a problem either way. Here is the output from blkid.

 

I would at least like to know what went wrong. Maybe I'll swap out another disc with a new hard drive soon and make a video - in the unlikely event that the problem occurs again with another disc in the same array.

Thank you!

Edited August 7 by virtubit

[JorgeB]

13 minutes ago, virtubit said:

And as I understand it, the rebuild happens at block level, there shouldn't have been a problem either

Correct, and because of that there's no need to be changing that setting, that's why I asked.

 

Disk4 is being detected as zfs, but there's no UUID, so possibly parity wasn't 100% valid, or there were some errors during the rebuild.

 

 

[virtubit]

I had a valid parity check a few days before and the rebuild ended with Message "Data-Rebuild finished (0 errors)" and "Disk 4 returned to normal operation".

 

Anyway, I think we'll stop troubleshooting here and I'll try another disc in the next few days. Then maybe we'll know more.

 

Many thanks for your help! Stay tuned

Edited August 7 by virtubit