Edit: Sorry, this is on a fresh Debian sid installation, ldm version 0.2.5-1....
hopefully this is not a completely trivial user error on my side as to not to waste your time.
I have a dynamic disk stripe set which is freshly created in Windows 10 (22H2 / build 19045.xxxx) via the Disk Management MMC Snap-in. Disk layout is GPT. The disks are formatted as NTFS with default allocation unit size, if that matters. Although I tried leaving the array unformatted and it would result in the same issue.
Hardware wise the disks are two identical Seagate Exos E - 7E8, 4Kn (ST6000NM0125) models with 4KB native logical sector size. So no 512K emulation! These are relatively rare in use so maybe it plays a role here?!
When trying to scan for the set ldm provides following quite descriptive error message followed by an empty array (?!) marker '[]':
My uneducated guess/fear is that it could have to do with the 4K native logical sectors because that is the only "special" thing about these disks that comes into my mind at least.
I'd be happy to provide any more info that would be needed to clarify the issue's cause if deemed worthy of investigating.
Attached are the terminal output of lsblk (-t) and the output as well as the partitioning visualized in GParted.
Thank you in advance for any hint where to go from here.
Hi there,
Edit: Sorry, this is on a fresh Debian sid installation, ldm version 0.2.5-1....
hopefully this is not a completely trivial user error on my side as to not to waste your time.
I have a dynamic disk stripe set which is freshly created in Windows 10 (22H2 / build 19045.xxxx) via the Disk Management MMC Snap-in. Disk layout is GPT. The disks are formatted as NTFS with default allocation unit size, if that matters. Although I tried leaving the array unformatted and it would result in the same issue.
Hardware wise the disks are two identical Seagate Exos E - 7E8, 4Kn (ST6000NM0125) models with 4KB native logical sector size. So no 512K emulation! These are relatively rare in use so maybe it plays a role here?!
When trying to scan for the set ldm provides following quite descriptive error message followed by an empty array (?!) marker '[]':
ldm> scan /dev/sdbError scanning /dev/sdb: Didn't find TOCBLOCK at config offset 400[]ldm> scan /dev/sdcError scanning /dev/sdc: Didn't find TOCBLOCK at config offset 400[]My uneducated guess/fear is that it could have to do with the 4K native logical sectors because that is the only "special" thing about these disks that comes into my mind at least.
I'd be happy to provide any more info that would be needed to clarify the issue's cause if deemed worthy of investigating. Attached are the terminal output of lsblk (-t) and the output as well as the partitioning visualized in GParted.
Thank you in advance for any hint where to go from here.