Help to recover data from unallocated partition

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Message
Author
User avatar
harsha
Posts: 6
Joined: 19 Feb 2024, 11:35

Help to recover data from unallocated partition

#1 Post by harsha »

Hi,

My 1TB HDD is not visible in windows, This was a WD My Book 1TB hard disk. It was suddenly went undetectable so i removed HDD from the case and tried to connect it to my desktop as an internal drive to try accessing data. but from my bad luck it is showing as 931.50GB unallocated space in disk management and the drive is not showing in my computer also. When I run Analyze in Testdisk it tis not showing the unallocated disk space. It's a single partition.

Image

TestDisk 7.2-WIP, Data Recovery Utility, February 2023
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 11.2, Cygwin32 3001.4
ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=250059350016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=243951206400
Hard disk list
Disk \\.\PhysicalDrive0 - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - WDC WD10EADS-114BB1, S/N:WD-WCAV5L469512, FW:80.00A80
Disk \\.\PhysicalDrive1 - 250 GB / 232 GiB - CHS 30401 255 63, sector size=512 - KINGSTON SA2000M8250G, S/N:0026_B768_3E05_25C5., FW:S5Z42105

Partition table type (auto): EFI GPT
Disk \\.\PhysicalDrive0 - 1000 GB / 931 GiB - WDC WD10EADS-114BB1
Partition table type: EFI GPT

Analyse Disk \\.\PhysicalDrive0 - 1000 GB / 931 GiB - CHS 121601 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=1953525167 (expected 1953525167)
hdr_lba_start=34
hdr_lba_end=1953525134
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
check_part_gpt failed for partition
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
Current partition structure:
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]


I don't know what problem with my harddisk. :cry:
Is it still possible to recover my harddisk data?
Any advise is welcome.
Thank you for reading my problem.
Attachments
Screenshot 2024-02-19 045052.jpg
Screenshot 2024-02-19 045052.jpg (75.54 KiB) Viewed 964 times
Last edited by harsha on 26 Feb 2024, 13:04, edited 1 time in total.

recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Help to recover data from unallocated partition

#2 Post by recuperation »

Please upload your picture to this site.

User avatar
harsha
Posts: 6
Joined: 19 Feb 2024, 11:35

Re: Help to recover data from unallocated partition

#3 Post by harsha »

It is attached now

recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Help to recover data from unallocated partition

#4 Post by recuperation »

Before using TestDisk you should run smartmontools and post your log file.
I guess creating th

viewtopic.php?f=5&t=10910

If the log file shows signs of a dying disk you should rather clone your disk using ddrescue as described in the manual.

Otherwise you would continue running TestDisk to see if partitions can be found.
https://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

What file system did you use to format your single partition on that disk?

User avatar
harsha
Posts: 6
Joined: 19 Feb 2024, 11:35

Re: Help to recover data from unallocated partition

#5 Post by harsha »

I haven't formatted the partition, It was showing Unallocated when I connected the drive to my system, then I remember it was showing as not initialized in disk management. Then I just Initialized the partition.

recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Help to recover data from unallocated partition

#6 Post by recuperation »

There is no "initializing of partitions". Microsoft operation systems initialize the complete disk by writing the MBR, in case of GPT disks they write a "Microsoft reserved partition" into the partition table. If you did something particular that may have even destroyed your data you should describe that correctly.

User avatar
harsha
Posts: 6
Joined: 19 Feb 2024, 11:35

Re: Help to recover data from unallocated partition

#7 Post by harsha »

Please see below log

Code: Select all

smartctl 7.4 2023-08-01 r5530 [x86_64-w64-mingw32-w10-22H2] (sf-7.4-1)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green
Device Model:     WDC WD10EADS-114BB1
Serial Number:    WD-WCAV5L469512
LU WWN Device Id: 5 0014ee 20550bc6e
Firmware Version: 80.00A80
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database 7.3/5528
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu Feb 29 02:41:21 2024 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Disabled
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(21480) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 209) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   199   199   051    -    708
  3 Spin_Up_Time            POS--K   149   136   021    -    5516
  4 Start_Stop_Count        -O--CK   090   090   000    -    10676
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   197   197   000    -    26
  9 Power_On_Hours          -O--CK   089   089   000    -    8066
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   090   090   000    -    10586
192 Power-Off_Retract_Count -O--CK   197   197   000    -    2894
193 Load_Cycle_Count        -O--CK   171   171   000    -    89277
194 Temperature_Celsius     -O---K   115   091   000    -    32
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    3
198 Offline_Uncorrectable   ----CK   200   200   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 25882 (device log contains only the most recent 24 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 25882 [9] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 af 40 00  Error: UNC at LBA = 0x71005b07af = 485337270191

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 03 00 68 00 71 00 5b 07 af 40 00     01:58:53.657  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:53.655  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:53.655  READ LOG EXT
  60 00 06 00 58 00 71 00 5b 07 a9 40 00     01:58:50.959  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:50.957  IDENTIFY DEVICE

Error 25881 [8] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a9 40 00  Error: UNC at LBA = 0x71005b07a9 = 485337270185

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 06 00 58 00 71 00 5b 07 a9 40 00     01:58:50.959  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:50.957  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:50.957  READ LOG EXT
  60 00 01 00 48 00 71 00 5b 07 a8 40 00     01:58:48.270  READ FPDMA QUEUED
  60 00 01 00 40 00 71 00 5b 07 a7 40 00     01:58:48.270  READ FPDMA QUEUED

Error 25880 [7] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 01 00 48 00 71 00 5b 07 a8 40 00     01:58:48.270  READ FPDMA QUEUED
  60 00 01 00 40 00 71 00 5b 07 a7 40 00     01:58:48.270  READ FPDMA QUEUED
  60 00 01 00 38 00 71 00 5b 07 a6 40 00     01:58:48.270  READ FPDMA QUEUED
  60 00 01 00 30 00 71 00 5b 07 a5 40 00     01:58:48.269  READ FPDMA QUEUED
  60 00 01 00 28 00 71 00 5b 07 a4 40 00     01:58:48.269  READ FPDMA QUEUED

Error 25879 [6] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 f8 00 71 00 5b 07 a1 40 00     01:58:45.549  READ FPDMA QUEUED
  60 00 01 00 f0 00 71 00 5b 07 a0 40 00     01:58:45.531  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:45.530  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:45.529  READ LOG EXT
  60 00 10 00 e0 00 71 00 5b 07 a0 40 00     01:58:42.841  READ FPDMA QUEUED

Error 25878 [5] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 e0 00 71 00 5b 07 a0 40 00     01:58:42.841  READ FPDMA QUEUED
  60 00 01 00 d8 00 71 00 5b 07 9f 40 00     01:58:42.823  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:42.821  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:42.821  READ LOG EXT
  60 00 10 00 c8 00 71 00 5b 07 9f 40 00     01:58:36.114  READ FPDMA QUEUED

Error 25877 [4] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 c8 00 71 00 5b 07 9f 40 00     01:58:36.114  READ FPDMA QUEUED
  60 00 10 00 c0 00 71 00 63 07 9e 40 00     01:58:36.105  READ FPDMA QUEUED
  60 00 10 00 b8 00 71 00 5c 07 1c 40 00     01:58:36.104  READ FPDMA QUEUED
  60 00 10 00 b0 00 71 00 5b 07 ed 40 00     01:58:36.104  READ FPDMA QUEUED
  60 00 03 00 a8 00 71 00 5b 07 dd 40 00     01:58:36.097  READ FPDMA QUEUED

Error 25876 [3] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 ae 40 00  Error: UNC at LBA = 0x71005b07ae = 485337270190

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 03 00 98 00 71 00 5b 07 ae 40 00     01:58:33.315  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:33.314  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:33.283  READ LOG EXT
  60 00 05 00 88 00 71 00 5b 07 a9 40 00     01:58:27.769  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:27.767  IDENTIFY DEVICE

Error 25875 [2] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a9 40 00  Error: UNC at LBA = 0x71005b07a9 = 485337270185

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 05 00 88 00 71 00 5b 07 a9 40 00     01:58:27.769  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:27.767  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:27.766  READ LOG EXT
  60 00 01 00 78 00 71 00 5b 07 a8 40 00     01:58:20.964  READ FPDMA QUEUED
  60 00 01 00 70 00 71 00 5b 07 a7 40 00     01:58:20.964  READ FPDMA QUEUED

Error 25874 [1] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 01 00 78 00 71 00 5b 07 a8 40 00     01:58:20.964  READ FPDMA QUEUED
  60 00 01 00 70 00 71 00 5b 07 a7 40 00     01:58:20.964  READ FPDMA QUEUED
  60 00 01 00 68 00 71 00 5b 07 a6 40 00     01:58:20.964  READ FPDMA QUEUED
  60 00 01 00 60 00 71 00 5b 07 a5 40 00     01:58:20.964  READ FPDMA QUEUED
  60 00 01 00 58 00 71 00 5b 07 a4 40 00     01:58:20.964  READ FPDMA QUEUED

Error 25873 [0] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 28 00 71 00 5b 07 a0 40 00     01:58:17.857  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:17.855  IDENTIFY DEVICE
  60 00 01 00 18 00 71 00 5b 07 9f 40 00     01:58:17.847  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:17.846  READ LOG EXT
  60 00 10 00 10 00 71 00 5b 07 9f 40 00     01:58:15.149  READ FPDMA QUEUED

Error 25872 [23] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 10 00 71 00 5b 07 9f 40 00     01:58:15.149  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:15.147  IDENTIFY DEVICE
  60 00 01 00 f8 00 71 00 5b 07 9e 40 00     01:58:15.138  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:15.138  READ LOG EXT
  60 00 10 00 f0 00 71 00 5b 07 9e 40 00     01:58:10.651  READ FPDMA QUEUED

Error 25871 [22] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 f0 00 71 00 5b 07 9e 40 00     01:58:10.651  READ FPDMA QUEUED
  60 00 10 00 e8 00 71 00 63 07 9d 40 00     01:58:10.644  READ FPDMA QUEUED
  60 00 10 00 e0 00 71 00 5c 07 1b 40 00     01:58:10.644  READ FPDMA QUEUED
  60 00 10 00 d8 00 71 00 5b 07 ec 40 00     01:58:10.643  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:10.641  IDENTIFY DEVICE

Error 25870 [21] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 ad 40 00  Error: UNC at LBA = 0x71005b07ad = 485337270189

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 03 00 c0 00 71 00 5b 07 ad 40 00     01:58:07.936  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:07.934  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:07.934  READ LOG EXT
  60 00 04 00 b0 00 71 00 5b 07 a9 40 00     01:58:02.963  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:02.962  IDENTIFY DEVICE

Error 25869 [20] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a9 40 00  Error: UNC at LBA = 0x71005b07a9 = 485337270185

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 04 00 b0 00 71 00 5b 07 a9 40 00     01:58:02.963  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:58:02.962  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:58:02.961  READ LOG EXT
  60 00 01 00 a0 00 71 00 5b 07 a8 40 00     01:58:00.274  READ FPDMA QUEUED
  60 00 01 00 98 00 71 00 5b 07 a7 40 00     01:58:00.274  READ FPDMA QUEUED

Error 25868 [19] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 01 00 a0 00 71 00 5b 07 a8 40 00     01:58:00.274  READ FPDMA QUEUED
  60 00 01 00 98 00 71 00 5b 07 a7 40 00     01:58:00.274  READ FPDMA QUEUED
  60 00 01 00 90 00 71 00 5b 07 a6 40 00     01:58:00.274  READ FPDMA QUEUED
  60 00 01 00 88 00 71 00 5b 07 a5 40 00     01:58:00.274  READ FPDMA QUEUED
  60 00 01 00 80 00 71 00 5b 07 a4 40 00     01:58:00.274  READ FPDMA QUEUED

Error 25867 [18] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 48 00 71 00 5b 07 9f 40 00     01:57:57.543  READ FPDMA QUEUED
  60 00 01 00 40 00 71 00 5b 07 9e 40 00     01:57:57.536  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:57.534  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:57:57.533  READ LOG EXT
  60 00 10 00 30 00 71 00 5b 07 9e 40 00     01:57:54.834  READ FPDMA QUEUED

Error 25866 [17] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 30 00 71 00 5b 07 9e 40 00     01:57:54.834  READ FPDMA QUEUED
  60 00 01 00 28 00 71 00 5b 07 9d 40 00     01:57:54.816  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:54.814  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:57:54.814  READ LOG EXT
  60 00 10 00 18 00 71 00 5b 07 9d 40 00     01:57:52.125  READ FPDMA QUEUED

Error 25865 [16] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 18 00 71 00 5b 07 9d 40 00     01:57:52.125  READ FPDMA QUEUED
  60 00 10 00 10 00 71 00 63 07 9c 40 00     01:57:52.116  READ FPDMA QUEUED
  60 00 10 00 08 00 71 00 5c 07 1a 40 00     01:57:52.116  READ FPDMA QUEUED
  60 00 10 00 f8 00 71 00 5b 07 eb 40 00     01:57:52.115  READ FPDMA QUEUED
  60 00 03 00 f0 00 71 00 5b 07 db 40 00     01:57:52.108  READ FPDMA QUEUED

Error 25864 [15] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 ac 40 00  Error: UNC at LBA = 0x71005b07ac = 485337270188

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 03 00 e0 00 71 00 5b 07 ac 40 00     01:57:49.401  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:49.398  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:57:49.398  READ LOG EXT
  60 00 03 00 d0 00 71 00 5b 07 a9 40 00     01:57:46.702  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:46.700  IDENTIFY DEVICE

Error 25863 [14] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a9 40 00  Error: UNC at LBA = 0x71005b07a9 = 485337270185

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 03 00 d0 00 71 00 5b 07 a9 40 00     01:57:46.702  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:46.700  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:57:46.700  READ LOG EXT
  60 00 01 00 c0 00 71 00 5b 07 a8 40 00     01:57:44.013  READ FPDMA QUEUED
  60 00 01 00 b8 00 71 00 5b 07 a7 40 00     01:57:44.013  READ FPDMA QUEUED

Error 25862 [13] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 01 00 c0 00 71 00 5b 07 a8 40 00     01:57:44.013  READ FPDMA QUEUED
  60 00 01 00 b8 00 71 00 5b 07 a7 40 00     01:57:44.013  READ FPDMA QUEUED
  60 00 01 00 b0 00 71 00 5b 07 a6 40 00     01:57:44.013  READ FPDMA QUEUED
  60 00 01 00 a8 00 71 00 5b 07 a5 40 00     01:57:44.013  READ FPDMA QUEUED
  60 00 01 00 a0 00 71 00 5b 07 a4 40 00     01:57:44.013  READ FPDMA QUEUED

Error 25861 [12] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 60 00 71 00 5b 07 9e 40 00     01:57:41.303  READ FPDMA QUEUED
  60 00 01 00 58 00 71 00 5b 07 9d 40 00     01:57:41.286  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:41.283  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:57:41.283  READ LOG EXT
  60 00 10 00 48 00 71 00 5b 07 9d 40 00     01:57:38.584  READ FPDMA QUEUED

Error 25860 [11] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 48 00 71 00 5b 07 9d 40 00     01:57:38.584  READ FPDMA QUEUED
  60 00 01 00 40 00 71 00 5b 07 9c 40 00     01:57:38.577  READ FPDMA QUEUED
  ec 00 00 00 00 00 00 00 40 00 00 a0 00     01:57:38.575  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:57:38.575  READ LOG EXT
  60 00 10 00 30 00 71 00 5b 07 9c 40 00     01:57:35.886  READ FPDMA QUEUED

Error 25859 [10] occurred at disk power-on lifetime: 8062 hours (335 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 71 00 5b 07 a8 40 00  Error: UNC at LBA = 0x71005b07a8 = 485337270184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 30 00 71 00 5b 07 9c 40 00     01:57:35.886  READ FPDMA QUEUED
  60 00 10 00 28 00 71 00 63 07 9b 40 00     01:57:35.877  READ FPDMA QUEUED
  60 00 10 00 20 00 71 00 5c 07 19 40 00     01:57:35.876  READ FPDMA QUEUED
  60 00 10 00 18 00 71 00 5b 07 ea 40 00     01:57:35.876  READ FPDMA QUEUED
  60 00 03 00 10 00 71 00 5b 07 da 40 00     01:57:35.869  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      8018         124857296
# 2  Short offline       Completed: read failure       90%      8018         124857296
# 3  Extended offline    Completed: read failure       90%      8018         124857296
# 4  Short offline       Completed: read failure       90%      8018         124857296
# 5  Short offline       Completed without error       00%        31         -
# 6  Short offline       Completed without error       00%         1         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    32 Celsius
Power Cycle Min/Max Temperature:     30/32 Celsius
Lifetime    Min/Max Temperature:     25/56 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (290)

Index    Estimated Time   Temperature Celsius
 291    2024-02-28 18:44    32  *************
 292    2024-02-28 18:45    35  ****************
 ...    ..(  2 skipped).    ..  ****************
 295    2024-02-28 18:48    35  ****************
 296    2024-02-28 18:49    36  *****************
 ...    ..(  3 skipped).    ..  *****************
 300    2024-02-28 18:53    36  *****************
 301    2024-02-28 18:54    37  ******************
 ...    ..(  3 skipped).    ..  ******************
 305    2024-02-28 18:58    37  ******************
 306    2024-02-28 18:59    38  *******************
 ...    ..(  4 skipped).    ..  *******************
 311    2024-02-28 19:04    38  *******************
 312    2024-02-28 19:05    39  ********************
 ...    ..(  6 skipped).    ..  ********************
 319    2024-02-28 19:12    39  ********************
 320    2024-02-28 19:13    40  *********************
 ...    ..( 27 skipped).    ..  *********************
 348    2024-02-28 19:41    40  *********************
 349    2024-02-28 19:42    41  **********************
 ...    ..( 26 skipped).    ..  **********************
 376    2024-02-28 20:09    41  **********************
 377    2024-02-28 20:10    42  ***********************
 ...    ..( 15 skipped).    ..  ***********************
 393    2024-02-28 20:26    42  ***********************
 394    2024-02-28 20:27     ?  -
 395    2024-02-28 20:28    25  ******
 396    2024-02-28 20:29    25  ******
 397    2024-02-28 20:30    25  ******
 398    2024-02-28 20:31    26  *******
 399    2024-02-28 20:32    26  *******
 400    2024-02-28 20:33    26  *******
 401    2024-02-28 20:34    27  ********
 402    2024-02-28 20:35    28  *********
 403    2024-02-28 20:36    28  *********
 404    2024-02-28 20:37    29  **********
 405    2024-02-28 20:38    29  **********
 406    2024-02-28 20:39    29  **********
 407    2024-02-28 20:40    30  ***********
 408    2024-02-28 20:41    30  ***********
 409    2024-02-28 20:42    31  ************
 410    2024-02-28 20:43    31  ************
 411    2024-02-28 20:44    32  *************
 ...    ..(  3 skipped).    ..  *************
 415    2024-02-28 20:48    32  *************
 416    2024-02-28 20:49    33  **************
 ...    ..(  2 skipped).    ..  **************
 419    2024-02-28 20:52    33  **************
 420    2024-02-28 20:53    34  ***************
 421    2024-02-28 20:54    34  ***************
 422    2024-02-28 20:55    34  ***************
 423    2024-02-28 20:56    35  ****************
 424    2024-02-28 20:57    35  ****************
 425    2024-02-28 20:58    36  *****************
 ...    ..(  8 skipped).    ..  *****************
 434    2024-02-28 21:07    36  *****************
 435    2024-02-28 21:08    37  ******************
 ...    ..(  4 skipped).    ..  ******************
 440    2024-02-28 21:13    37  ******************
 441    2024-02-28 21:14    38  *******************
 ...    ..(  9 skipped).    ..  *******************
 451    2024-02-28 21:24    38  *******************
 452    2024-02-28 21:25    39  ********************
 ...    ..( 11 skipped).    ..  ********************
 464    2024-02-28 21:37    39  ********************
 465    2024-02-28 21:38    40  *********************
 ...    ..( 89 skipped).    ..  *********************
  77    2024-02-28 23:08    40  *********************
  78    2024-02-28 23:09    41  **********************
 ...    ..( 74 skipped).    ..  **********************
 153    2024-02-29 00:24    41  **********************
 154    2024-02-29 00:25     ?  -
 155    2024-02-29 00:26    30  ***********
 156    2024-02-29 00:27     ?  -
 157    2024-02-29 00:28    30  ***********
 ...    ..(  2 skipped).    ..  ***********
 160    2024-02-29 00:31    30  ***********
 161    2024-02-29 00:32    31  ************
 162    2024-02-29 00:33    32  *************
 163    2024-02-29 00:34    41  **********************
 ...    ..(102 skipped).    ..  **********************
 266    2024-02-29 02:17    41  **********************
 267    2024-02-29 02:18     ?  -
 268    2024-02-29 02:19    25  ******
 269    2024-02-29 02:20     ?  -
 270    2024-02-29 02:21    26  *******
 271    2024-02-29 02:22     ?  -
 272    2024-02-29 02:23    26  *******
 ...    ..(  2 skipped).    ..  *******
 275    2024-02-29 02:26    26  *******
 276    2024-02-29 02:27    27  ********
 277    2024-02-29 02:28    28  *********
 278    2024-02-29 02:29    28  *********
 279    2024-02-29 02:30    29  **********
 ...    ..(  2 skipped).    ..  **********
 282    2024-02-29 02:33    29  **********
 283    2024-02-29 02:34    30  ***********
 284    2024-02-29 02:35    31  ************
 285    2024-02-29 02:36    31  ************
 286    2024-02-29 02:37    31  ************
 287    2024-02-29 02:38    32  *************
 ...    ..(  2 skipped).    ..  *************
 290    2024-02-29 02:41    32  *************

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x000a  2            2  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x8000  4          342  Vendor specific

recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Help to recover data from unallocated partition

#8 Post by recuperation »

You have three pending sectors. There could be more which might appear when you clone the disk.

User avatar
harsha
Posts: 6
Joined: 19 Feb 2024, 11:35

Re: Help to recover data from unallocated partition

#9 Post by harsha »

So, can you please suggest my next safe step to proceed with to recover the partition? :?

recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Help to recover data from unallocated partition

#10 Post by recuperation »

Your disk might be dying. Read above.

Post Reply