- Minor
Since these devices are 4K and the file system is created as 512B, you are unable to mount these file systems outside of the unraid array.
If I just click mount via unassigned devices:
Apr 29 09:25:42 Tower unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/HGST_HUH721010AL4200_direct' '/mnt/disks/HGST_HUH721010AL4200_direct'
Apr 29 09:25:42 Tower kernel: XFS (dm-8): device supports 4096 byte sectors (not 512
Here is me doing it manually in console on temp server to test this:
root@Tower:~# /usr/sbin/cryptsetup luksOpen /dev/sdd1 HGST_HUH721010AL4200_direct
Enter passphrase for /dev/sdd1: PASSWORD ENTERED HERE
root@Tower:~# mkdir /tmp/test
root@Tower:~# /sbin/mount -o rw,noatime,nodiratime /dev/mapper/HGST_HUH721010AL4200_direct /tmp/test
mount: /tmp/test: mount(2) system call failed: Function not implemented.
root@Tower:~# tail -5 /var/log/syslog
Apr 29 09:25:42 Tower kernel: XFS (dm-8): device supports 4096 byte sectors (not 512)
Apr 29 09:25:42 Tower unassigned.devices: Mount of 'HGST_HUH721010AL4200_direct' failed: 'mount: /mnt/disks/HGST_HUH721010AL4200_direct: mount(2) system call failed: Function not implemented. '
Apr 29 09:25:42 Tower unassigned.devices: Partition 'HGST_HUH721010AL4200_direct' cannot be mounted.
Apr 29 09:27:48 Tower kernel: XFS (dm-8): device supports 4096 byte sectors (not 512)
Drive in question:
root@Tower:~# blockdev --report /dev/sdd*
RO RA SSZ BSZ StartSec Size Device
rw 256 4096 4096 0 10000831348736 /dev/sdd
rw 256 4096 4096 64 10000831295488 /dev/sdd1
A few other devices that were from the same original array:
root@Tower:~# blockdev --report /dev/md*
RO RA SSZ BSZ StartSec Size Device
rw 256 512 4096 0 10000831295488 /dev/md1
rw 256 512 4096 0 10000831295488 /dev/md2
rw 256 512 4096 0 10000831295488 /dev/md3
That device:
I built a brand new server and this is what I see:
O RA SSZ BSZ StartSec Size Device
rw 256 512 512 0 32080200192 /dev/sdb
rw 256 512 512 2048 32079151616 /dev/sdb1
O RA SSZ BSZ StartSec Size Device
rw 256 512 4096 0 18000207884288 /dev/md1
See the thread that triggered this bug report: