Please help me, unreadable partition (translated from Italian)

Please help me, unreadable partition (translated from Italian)

After trying to stretch the partition, I can't get into it anymore even though I tried to restore it.
For the most part, I copy and paste the answer given by Gparted:

GParted 1.2.0

configuration --enable-libparted-dmraid --enable-online-resize

libparted 3.4

=======================================
Device: / dev / sda
Model: ATA Hitachi HTS54323
Serial number:
Sector size: 512
Total sectors: 625142448

Heads: 255
Sectors / Track: 2
Cylinders: 1225769

Partition table: msdos

Partition Type Start End Flag Partition Name File system Label Mount point
/ dev / sda1 Primary 2048 5163005 linux-swap
/ dev / sda3 Primary 5163008 87965695 ext4 rootMX19
/ dev / sda2 Primary 166002688 625141357 ext4 /

=======================================
File system check and repair (ext4) on / dev / sda3 00:00:19 (ERROR)
     
Calibration of / dev / sda3 00:00:01 (SUCCESS)
     
path: / dev / sda3 (partition)
Start: 5163008
End: 87965695
Size: 82802688 (39.48 GiB)
Check the file system on / dev / sda3 for errors and fix them if necessary 00:00:18 (ERROR)
     
e2fsck -f -y -v -C 0 '/ dev / sda3' 00:00:18 (ERROR)
     
rootMX19: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Inode 2536 has an invalid extent node (blk 7507481, lblk 0)
Clear? yes

Inode 2536 extent tree (at level 1) could be shorter. Optimize? yes

HTREE directory inode 2536 has an invalid root node.
Clear HTree index? yes

Inode 2536 is a zero-length directory. Clear? yes

Inode 5727 has an invalid extent node (blk 7507553, lblk 0)
Clear? yes

Inode 5727 extent tree (at level 1) could be shorter. Optimize? yes

Inode 5727, i_blocks is 720, should be 0. Fix? yes

Inode 5818 has an invalid extent node (blk 7507561, lblk 0)
Clear? yes ....

HTREE directory inode 371595 has an invalid root node.
Clear HTree index? yes

Inode 2097153 passes checks, but checksum does not match inode. Fix? yes

Inode 2359297 passes checks, but checksum does not match inode. Fix? yes

Running additional passes to resolve blocks claimed by more than one inode ...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block (s) in inode 2359297: 9442518
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)

File / srv (inode # 2359297, mod time Thu Jan 1 01:00:00 1970)
has 1 multiply-claimed block (s), shared with 1 file (s):
<filesystem metadata>
Clone multiply-claimed blocks? yes

Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Invalid inode number for '.' in inode directory 2359297.
Fix? yes

Entry '..' in ??? (2359297) references inode 1885710 in group 230 where _INODE_UNINIT is set.
Fix? yes

rootMX19: ***** FILE SYSTEM WAS MODIFIED *****

rootMX19: ***** FILE SYSTEM WAS MODIFIED *****
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_read_inode: Inode checksum does not match inode while reading inode 1885710 in check_filetype
e2fsck: aborted

Hoping for a solution,
good peace to all of us.

Maurizio Rama