File errors NAS hard drive xfs format

Hello clever people

Linux newbie here, I am trying to get data recovered. I had a Buffalo LinkStation NAS that started to fail so I replaced it with another (dual drive this time!). I had backups of the important data on the damaged NAS but I still need to get some data off. I removed the hard drive from the LinkStation and purchased a USB drive enclosure. Then on a Windows 10 machine I created a Linux virtual machine to connect to the external drive.

In a terminal session I ran xfs_repair but it did not fix everything, I did try a few times as suggested elsewhere on the internet.

What are my next steps please? The results from blkid, fdisk ?l and xfs_repair ?n on /dev/sdb6 are shown below. Many thanks, Keith.
[font=courier]
/dev/sda1: UUID=“e8d41f99-626d-434d-ae99-4507ff445ccb” TYPE=“ext4” PARTUUID=“5153bc9d-01”
/dev/sda5: UUID=“36725bd7-f11d-48e8-ae33-ee2f2d9230e2” TYPE=“swap” PARTUUID=“5153bc9d-05”
/dev/sdb1: UUID=“7a234898-0746-4302-980a-db4c5f94a6d1” TYPE=“ext3” PARTUUID=“8c3c2bff-01”
/dev/sdb2: UUID=“d396920c-ea11-4f5f-be9e-34648c2260ed” TYPE=“xfs” PARTUUID=“8c3c2bff-02”
/dev/sdb5: TYPE=“swap” PARTUUID=“8c3c2bff-05”
/dev/sdb6: UUID=“0a6f70e7-71dc-4269-b876-940b30538e24” TYPE=“xfs” PARTUUID=“8c3c2bff-06”

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x8c3c2bff

Device Boot Start End Sectors Size Id Type
/dev/sdb1 63 2008124 2008062 980.5M 83 Linux
/dev/sdb2 2008125 12016619 10008495 4.8G 83 Linux
/dev/sdb4 12016620 1953520064 1941503445 925.8G 5 Extended
/dev/sdb5 12016683 14024744 2008062 980.5M 82 Linux swap / Solaris
/dev/sdb6 14024808 1951544069 1937519262 923.9G 83 Linux

keith@keith-Virtual-Machine:~$ sudo xfs_repair -n /dev/sdb6
Phase 1 - find and verify superblock…
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log…
- scan filesystem freespace and inode maps…
sb_fdblocks 11777209, counted 11801785
- 20:26:50: scanning filesystem freespace - 32 of 32 allocation groups done
- found root inode chunk
Phase 3 - for each AG…
- scan (but don’t clear) agi unlinked lists…
- 20:26:50: scanning agi unlinked lists - 32 of 32 allocation groups done
- process known inodes and perform inode discovery…
- agno = 30
- agno = 15
- agno = 0
- agno = 1
- agno = 31
- agno = 16
- agno = 2
- agno = 17
- agno = 3
- agno = 18
- agno = 19
- agno = 4
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 5
- agno = 6
- agno = 29
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- 20:28:35: process known inodes and inode discovery - 529536 of 529536 inodes done
- process newly discovered inodes…
- 20:28:35: process newly discovered inodes - 32 of 32 allocation groups done
Phase 4 - check for duplicate blocks…
- setting up duplicate extent list…
- 20:28:35: setting up duplicate extent list - 32 of 32 allocation groups done
- check for inodes claiming duplicate blocks…
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- 20:28:36: check for inodes claiming duplicate blocks - 529536 of 529536 inodes done
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity…
- traversing filesystem …
- traversal finished …
- moving disconnected inodes to lost+found …
Phase 7 - verify link counts…
No modify flag set, skipping filesystem flush and exiting.
keith@keith-Virtual-Machine:~$ [/font]

Running the xfs_repair with the -n does not repair.

No modify flag set, skipping filesystem flush and exiting.
According to the man pages here
-n No modify mode. Specifies that xfs_repair should not modify the filesystem but should only scan the filesystem and indicate what repairs would have been made

Hello SeZo. I only added the -n to get the results to post above. The other previous times I ran xfs_repair it was without -n. Thanks.

try this:

awesome soft. restores most popular filesystems. use photorec to restore specific files if required. there is also version for mswindows. im not sure how it will work on win10, but i assume there wont be any problems. i have used it million times before and it always worked with fat32/ntfs problems, boot restores etc etc.