Hi,

I'm planning on migrating to a zfs pool instead of the unRAID array, but am a bit hesistant due to some lacking features in the unRAID-interface.

First, I was flabbergasted to see that unRAID does NOT in any way warn or even indicate when there's a drive failure in the pool, which in my eyes is a absolute requirement. It can't be that hard for the system to do a "zpool status" now and then and act on that!?

But lets assume you are aware of a failed drive, how do you know which drive it is?

As long as unRAID keeps showing the pool and all its drives as online as it is now, it's possible to map the /dev/sdX to the drive identification, but I'm not 100% sure this can be trusted to stay. So how do you that do use ZFS do to be sure of which drive to replace when you get a failure? Do you have document mapping sdX->serial for all drives?

20 minutes ago, Ancan said:

I was flabbergasted to see that unRAID does NOT in any way warn or even indicate when there's a drive failure in the pool, which in my eyes is a absolute requirement.

Yep, I've been asking for that for many years. The last info I have is that it will be finally included with 7.3

20 minutes ago, Ancan said:

So how do you that do use ZFS do to be sure of which drive to replace when you get a failure?

For now, you can use a script:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

33 minutes ago, JorgeB said:

Yep, I've been asking for that for many years. The last info I have is that it will be finally included with 7.3

For now, you can use a script:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

ZFS and Unraid ? ZFS Master for example is since 2024.12.08 not more maintained and was Feb 25 the monthly spotlight . Could hear nothing to integrate it native in the OS.

44 minutes ago, JorgeB said:

Yep, I've been asking for that for many years. The last info I have is that it will be finally included with 7.3

For now, you can use a script:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

I don't think the scripts show the serial of the drive, so you're still left with pairing /dev/sdX to the physical drive.

I guess keeping the output of "lsblk -o NAME,SERIAL" somewhere safe could be a workaround.

EDIT: I don't know if there's a reason unRAID doesn't create zpools using /dev/disk/by-id instead of /dev/sdX. Would have made the identification part so much easier.

Edited February 4Feb 4 by Ancan

1 hour ago, Ancan said:

Hi,

I'm planning on migrating to a zfs pool instead of the unRAID array, but am a bit hesistant due to some lacking features in the unRAID-interface.

First, I was flabbergasted to see that unRAID does NOT in any way warn or even indicate when there's a drive failure in the pool, which in my eyes is a absolute requirement. It can't be that hard for the system to do a "zpool status" now and then and act on that!?

But lets assume you are aware of a failed drive, how do you know which drive it is?

As long as unRAID keeps showing the pool and all its drives as online as it is now, it's possible to map the /dev/sdX to the drive identification, but I'm not 100% sure this can be trusted to stay. So how do you that do use ZFS do to be sure of which drive to replace when you get a failure? Do you have document mapping sdX->serial for all drives?

Quoting myself so I can reply: The identification of a removed drive does not persist through a reboot. It's impossible to start the array as long as a pool is missing an assigned drived to you have to remove it from the pool. You end up with "Not installed" on that slot, and no way to see the serial of the drive that used to be on that location. I guess you could locate all the good drives by their serial, but that could be some work.

1 hour ago, Ancan said:

I don't think the scripts show the serial of the drive, so you're still left with pairing /dev/sdX to the physical drive

You can see that on main, it will still list the failed drive there, including sdX and serial.