------- Comment From <email address hidden> 2018-06-13 15:24 EDT-------
Hi, I'm still getting the result:
./grub-probe: error: disk `mduuid/b184ce73be4a91ec1b586dcce8ee7f9b' not found.
One thing that I noticed is that we have some sector lengths hardcoded for 512 bytes. Yet, it seems that grub is facing some problems when trying to find magic number for 1.0 metadata.
I did dump the variables returned by the disk read when the mdraid1x_linux.c tries to find the magic number and its getting the wrong position.
When I finally changed the hardcoded sector lenghts for 4k instead, the mdraid1x_linux.c was able to find the magic number, although it wasn't able to successful find the disk yet.
I'm still investigating this problem and hope I find something in a couple of days.
------- Comment From <email address hidden> 2018-06-13 15:24 EDT-------
Hi, I'm still getting the result:
./grub-probe: error: disk `mduuid/ b184ce73be4a91e c1b586dcce8ee7f 9b' not found.
One thing that I noticed is that we have some sector lengths hardcoded for 512 bytes. Yet, it seems that grub is facing some problems when trying to find magic number for 1.0 metadata.
I did dump the variables returned by the disk read when the mdraid1x_linux.c tries to find the magic number and its getting the wrong position.
When I finally changed the hardcoded sector lenghts for 4k instead, the mdraid1x_linux.c was able to find the magic number, although it wasn't able to successful find the disk yet.
I'm still investigating this problem and hope I find something in a couple of days.
Thank you