mariabackup-10.3.22 restore normal, but start service failed- InnoDB Trying to read page number 1858 in space 3, space name innodb_undo003, which is outside the tablespace bounds

Hi, all
Today, we use MariaDB full backup and increment backup file to restore:
– full restore
mariabackup --use-memory=8G --prepare --target-dir /data3/cluster04/data/

– incr restore
mariabackup --use-memory=8G --prepare --target-dir /data3/cluster04/data/ --incremental-dir /data3/incr/

both full restore and incr restore are normal, but start MariaDB failed,
error log:
2019-07-13 17:28:38 0 [ERROR] [FATAL] InnoDB: Trying to read page number 978 in space 3, space name innodb_undo003, which is outside the tablespace bounds. Byte offset 0, len 16384
190713 17:28:38 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We try to restore full and incrment backup again, error log show:
[ERROR] [FATAL] InnoDB: Trying to read page number 727 in space 2, space name innodb_undo002, which is outside the tablespace bounds. Byte offset 0, len 16384

after upgrade mariabackup version to 10.3.16, same error too.

if only restore full backup, MariaDB 10.3 server can start normal. MDEV-18194 fix similar question, Please help us to confirm , how to resolve the question ?

Thanks.