Errors with GPT on RAID 0 ATARAID array
For years I have been maintaining an Asus laptop that comes equipped with two SSD M2 configured by the manufacturer as a RAID0 array.
Every time GParted is executed or every time an operation is performed (like making changes to any partition flag) there is a long waiting period that ends up with a pop-up window showing the error:
"Invalid argument during seek for read on /dev/sda"
after clicking Ignore then there is another waiting period and this other error appears:
"The backup GPT table is corrupt, but the primary appears OK, so that will be used."
As both disks are members of a RAID0 array, some volumes in the partition table have starting positions above the physical boundaries of /dev/sda and /dev/sdb and therefore GParted shows the mentioned errors.
One way to workaround this is to run GParted from the command line like this:
but although there are no more error pop-up windows, GParted omits the rest of the devices connected to the machine in its device list.
I'd suggest different solutions:
check this particular case (an existing RAID0 array) when scanning the available devices to avoid the error pop-up windows,
implement a command line option that allows you to exclude specific devices from device scanning, and run GParted like this: