[Unraid OS version 6.12.0-rc7 available]

9 hours ago, JorgeB said:

This is a known issue with mostly Ivy Brige or older CPUs when auto importing a btrfs pool, you can get around it by clicking on the pool and setting the fs to btrfs, or if you are creating a new pool like it looked you can also just erase the devices.

 

Hello @JorgeB, thanks for the info that it is a known issue.

Yes, I created a new pool, but all disks where empty without any partitions. If I set it to BTRFS like you described, it works as well with empty disks.

 

CPU is a Celeron N5105. Not that old. Which is I think Tremont/Jasper Lake.
Issue does not exists with stable 6.11.

[Unraid OS version 6.12.0-rc7 available]

I see the following in rc6 and rc7 on a fresh setup.

 

- configure a cache pool with 2 slots

- assign a SSD to each slot 

- start the array

 

It will stay with "Array starting" forever and it says for "Cache" *Mounting*.

In the logs the following is visible.

 

Jun  7 16:48:55 Tower emhttpd: mounting /mnt/cache
Jun  7 16:48:55 Tower emhttpd: shcmd (334): mkdir -p /mnt/cache
Jun  7 16:48:55 Tower emhttpd: /sbin/btrfs filesystem show /dev/sdb1 2>&1
Jun  7 16:48:55 Tower emhttpd: ERROR: not a valid btrfs filesystem: /dev/sdb1
Jun  7 16:48:55 Tower emhttpd: cache: invalid config: total_devices 0 num_misplaced 0 num_missing 0
Jun  7 16:48:55 Tower kernel: emhttpd[11562]: segfault at 107 ip 0000147f142f658a sp 0000147f139f5be0 error 4 in libc-2.37.so[147f1427e000+169000] likely on CPU 0 (core 0, socket 0)
Jun  7 16:48:55 Tower kernel: Code: 48 8d 3d 91 27 11 00 e8 c4 ba ff ff 0f 1f 40 00 48 85 ff 0f 84 bf 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 6e d8 14 00 <48> 8b 47 f8 64 8b 2b a8 02 75 5b 48 8b 15 fc d7 14 00 64 48 83 3a

 

At that point, I can only do a reboot. 

The way to get it working is to assign only 1 disk to the cache pool and ones configured add a second one.

It seems to be consistently reproducable.