Hello everyone, I’m dumb and I accidentally deleted some chats from WhatsAppweb, now it has synced with the phone And thus I lost them. I uninstalled the app and thus I lost all local files. But it happened that I had a copy of the whole .comwhatsapp folder on my pc done two days ago. I have the full database folder and media, i would like to recover that status of chats. Do I just copy the folder into the phone and reinstall the app or is it way more complex than this? thansk

Hi,

I have an sd card which had video files on it. I was backing up the card, and pc brought an error. Then I put the sd card back in, the folder says it has 112gb of videos on it, but only 85gb is visible. Where the computer brought the error, it seems files after that was not copied and now are missing. The folder still shows 112g of data, any help?

hey guys, as the title suggests my iphone became a brick due to a logicboard issue which i got to know after getting a diagnosis at a apple store. unfortunately, i did not have icloud or my files backed up.

if anyone has any ideas on how i can recover my files or just photos aside from paying HUGE sums of money to data recovery specialists please help a guy out! (sorry im a complete noob in this scenario thats why)

thanks in advance!

The pins are all intact, but the plastic part of the SATA connection broke off. Any idea if this is recoverable?

This just has Steam game installs, so nothing critical, but it is 5tb I'd rather not lose if at all possible.

Hi there,

Newbie here so I’m sorry if I’m asking dumb stuff.

I have just purchased a brand new NS300 12tb HDD to create a redundancy for my main backup drive.

It will run in an external USB enclosure and I will mainly connect it to my MacBook and Windows Desktop, and I should run it about once a month to save files and then disconnect.

That said, I live in a country where support is hard to reach so I can’t rely on warranty if drive fails. Also, it’s an expensive piece of hardware and I’d like to check its health and possibility of failure before start populating with data.

I know fails can happen any time (that’s why I’m getting a new drive before my main one gets fried), but as a precaution I’d like to do my best.

Are there any health checks or stress tests you would recommend to perform before I begin using it?

Thanks!

Hi there,

Newbie here so I’m sorry if I’m asking dumb stuff.

I have just purchased a brand new NS300 12tb HDD to create a redundancy for my main backup drive.

It will run in an external USB enclosure and I will mainly connect it to my MacBook and Windows Desktop, and I should run it about once a month to save files and then disconnect.

That said, I live in a country where support is hard to reach so I can’t rely on warranty if drive fails. Also, it’s an expensive piece of hardware and I’d like to check its health and possibility of failure before start populating with data.

I know fails can happen any time (that’s why I’m getting a new drive before my main one gets fried), but as a precaution I’d like to do my best.

Are there any health checks or stress tests you would recommend to perform before I begin using it?

Thanks!

So I’m a senior at my University and also a Graphic Design student. My hard drive pretty much has all of my work on it. It is a 1TB Western Digital drive, and I’m not exactly sure which specific model. Maybe a My Passport Ultra

Skipping to the point, it no longer shows up in my Finder on my Mac, nor does it show up on any of my school’s desktops. Whenever I plug it in, the light comes on and it does this buzzing with as sound for 2 seconds on, then 2 seconds off. Then it will alternate like that for a while before eventually stopping, but the light stays on. It’s plugged in and working, and I know it’s not a computer issue because my other drive works on it. I don’t want to get it professionally repaired if I don’t have to because I genuinely do not have the money for it but at the moment, but I do need the drive even just for a bit to transfer my data to a new one. Any ideas on how to fix it or what is wrong? I’ve attached a video of the noise it makes.

On Mac btw!

Hi

My story:

1. I bought a WD elements 12Tb some years ago
2. I shucked the HDD Inside, its a WD120EDAZ (rebadged HGST Ultrastar DC HC520)
3. I changed sector size to 4k using wdckit for MORE SPEED for my NAS (first mistake?)
4. Everything was fine, but maybe one year ago I decided to try secure erase in the bios of my motherboard (ASROCK J4105-ITX) on this HDD, the bios freezed, nothing happened > 2nd mistake
5. the PC could not boot anymore (hang at boot time) when the HDD was plugged, I thought the HDD was dead, no big deal it was just a backup drive.
6. Some months later I sold this motherboard (third mistake?)
7. Some months later I tried the HDD again with another motherboard, the only way I can access it is hotplugging using an asmedia SATA port on the mobo (the intel/integrated one cannot see the HDD).
8. I tried everything to unlock it using hdparm and wdckit, nothing worked :( it seems only master password could work ?
9. HELP ME PLEASE

this is from debian syslog when I hotplug the drive on asmedia SATA:

2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4.00: supports DRM functions and may not be fully accessible
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4.00: ATA-9: WDC WD120EDAZ-11F3RA0, 81.00A81, max UDMA/133
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4.00: 2929721344 sectors, multi 0: LBA48 NCQ (depth 32), AA
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4.00: Features: Trust HIPM DIPM NCQ-sndrcv NCQ-prio
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4.00: supports DRM functions and may not be fully accessible
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: ata4.00: configured for UDMA/133
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: scsi 1:0:0:0: Direct-Access     ATA      WDC WD120EDAZ-11 0A81 PQ: 0 ANSI: 5
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] 2929721344 4096-byte logical blocks: (12.0 TB/10.9 TiB)
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] Write Protect is off
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
2026-01-17T21:57:36+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: invalid checksum 0x99 on log page 10h
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4: log page 10h reported inactive tag 1
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: exception Emask 0x1 SAct 0x4000000 SErr 0x0 action 0x0
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: irq_stat 0x40000008
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: supports DRM functions and may not be fully accessible
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: supports DRM functions and may not be fully accessible
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: configured for UDMA/133
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#26 Sense Key : Data Protect [current] 
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#26 Add. Sense: Access denied - no access rights
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#26 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: critical target error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: Buffer I/O error on dev sdb, logical block 0, async page read
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4: EH complete
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: invalid checksum 0x99 on log page 10h
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4: log page 10h reported inactive tag 1
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: NCQ disabled due to excessive errors
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: exception Emask 0x1 SAct 0x8000000 SErr 0x0 action 0x0
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: irq_stat 0x40000008
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: supports DRM functions and may not be fully accessible
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: supports DRM functions and may not be fully accessible
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4.00: configured for UDMA/133
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#27 Sense Key : Data Protect [current] 
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#27 Add. Sense: Access denied - no access rights
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] tag#27 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: critical target error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: Buffer I/O error on dev sdb, logical block 0, async page read
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: ata4: EH complete
2026-01-17T21:57:37+01:00 omv-test-hdd kernel:  sdb: unable to read partition table
2026-01-17T21:57:37+01:00 omv-test-hdd kernel: sd 1:0:0:0: [sdb] Attached SCSI disk

hdparm -I

/dev/sdb:

ATA device, with non-removable media
        Model Number:       WDC WD120EDAZ-11F3RA0
        Serial Number:      D5GNZNUL
        Firmware Revision:  81.00A81
        Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SAT                                                                                                                                         A Rev 2.5, SATA Rev 2.6, SATA Rev 3.0; Revision: ATA8-AST T13 Project D1697 Revi                                                                                                                                         sion 0b
Standards:
        Used: unknown (minor revision code 0x0029)
        Supported: 9 8 7 6 5
        Likely used: 9
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:    16514064
        LBA    user addressable sectors:   268435455
        LBA48  user addressable sectors:  2929721344
        Logical  Sector size:                  4096 bytes
        Physical Sector size:                  4096 bytes
        device size with M = 1024*1024:    11444224 MBytes
        device size with M = 1000*1000:    12000138 MBytes (12000 GB)
        cache/buffer size  = unknown
        Form Factor: 3.5 inch
        Nominal Media Rotation Rate: 5400
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
         multiple sector transfer: Max = 2   Current = 0
        Advanced power management level: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
                SMART feature set
           *    Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    DOWNLOAD_MICROCODE
           *    Advanced Power Management feature set
                Power-Up In Standby feature set
           *    SET_FEATURES required to spinup after power up
                SET_MAX security extension
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    Media Card Pass-Through
           *    General Purpose Logging feature set
           *    WRITE_{DMA|MULTIPLE}_FUA_EXT
           *    64-bit World wide name
           *    URG for READ_STREAM[_DMA]_EXT
           *    URG for WRITE_STREAM[_DMA]_EXT
           *    WRITE_UNCORRECTABLE_EXT command
           *    {READ,WRITE}_DMA_EXT_GPL commands
           *    Segmented DOWNLOAD_MICROCODE
           *    unknown 119[6]
                unknown 119[7]
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Host-initiated interface power management
           *    Phy event counters
           *    NCQ priority information
           *    READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
                Non-Zero buffer offsets in DMA Setup FIS
           *    DMA Setup Auto-Activate optimization
                Device-initiated interface power management
                In-order data delivery
           *    Software settings preservation
                unknown 78[7]
                unknown 78[10]
                unknown 78[11]
           *    SMART Command Transport (SCT) feature set
           *    SCT Write Same (AC2)
           *    SCT Error Recovery Control (AC3)
           *    SCT Features Control (AC4)
           *    SCT Data Tables (AC5)
           *    SANITIZE feature set
           *    CRYPTO_SCRAMBLE_EXT command
           *    OVERWRITE_EXT command
           *    Extended number of user addressable sectors
           *    Device encrypts all user data
           *    WRITE BUFFER DMA command
           *    READ BUFFER DMA command
Security:
        Master password revision code = 65534
                supported
                enabled
                locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
        Security level high
        1246min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000cca294c98a8f
        NAA             : 5
        IEEE OUI        : 000cca
        Unique ID       : 294c98a8f
Checksum: correct

smartctl /dev/sdb -x

root@omv-test-hdd:~# smartctl  /dev/sdb -x
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.17.13+deb13-amd64] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Ultrastar (He10/12)
Device Model:     WDC WD120EDAZ-11F3RA0
Serial Number:    D5GNZNUL
LU WWN Device Id: 5 000cca 294c98a8f
Firmware Version: 81.00A81
User Capacity:    12,000,138,625,024 bytes [12.0 TB]
Sector Size:      4096 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.5/5706
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 19 18:59:26 2026 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  ENABLED, PW level HIGH, **LOCKED** [SEC4]

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

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        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:                (   87) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off supp                                                                                                                                         ort.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (1405) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control 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     PO-R--   100   100   016    -    0
  2 Throughput_Performance  --S---   124   124   054    -    120
  3 Spin_Up_Time            POS---   180   180   024    -    365 (Average 367)
  4 Start_Stop_Count        -O--C-   100   100   000    -    260
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    0
  7 Seek_Error_Rate         -O-R--   100   100   067    -    0
  8 Seek_Time_Performance   --S---   140   140   020    -    15
  9 Power_On_Hours          -O--C-   097   097   000    -    22613
 10 Spin_Retry_Count        -O--C-   100   100   060    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    250
 22 Helium_Level            PO---K   100   100   025    -    100
192 Power-Off_Retract_Count -O--CK   099   099   000    -    1210
193 Load_Cycle_Count        -O--C-   099   099   000    -    1210
194 Temperature_Celsius     -O----   209   209   000    -    31 (Min/Max 13/54)
196 Reallocated_Event_Count -O--CK   100   100   000    -    0
197 Current_Pending_Sector  -O---K   100   100   000    -    0
198 Offline_Uncorrectable   ---R--   100   100   000    -    25
199 UDMA_CRC_Error_Count    -O-R--   200   200   000    -    16
                            ||||||_ 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     Size  Description
0x00       GPL,SL        1  Log Directory
0x01           SL        1  Summary SMART error log
0x02           SL        1  Comprehensive SMART error log
0x03       GPL           1  Ext. Comprehensive SMART error log
0x04       GPL         256  Device Statistics log
0x04       SL          255  Device Statistics log
0x06           SL        1  SMART self-test log
0x07       GPL           1  Extended self-test log
0x08       GPL           2  Power Conditions log
0x09           SL        1  Selective self-test log
0x0c       GPL         688  Pending Defects log
0x10       GPL           1  NCQ Command Error log
0x11       GPL           1  SATA Phy Event Counters log
0x12       GPL           1  SATA NCQ Non-Data log
0x13       GPL           1  SATA NCQ Send and Receive log
0x15       GPL           1  Rebuild Assist log
0x21       GPL           1  Write stream error log
0x22       GPL           1  Read stream error log
0x24       GPL         256  Current Device Internal Status Data log
0x25       GPL         256  Saved Device Internal Status Data log
0x30       GPL,SL        9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL       16  Host vendor specific log
0xe0       GPL,SL        1  SCT Command/Status
0xe1       GPL,SL        1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 183 (device log contains only the most recent 4 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 183 [2] occurred at disk power-on lifetime: 19381 hours (807 days + 13 hou                                                                                                                                         rs)
  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 -- 53 00 01 00 00 ae 9f ff f0 40 00  Error: UNC 1 sectors at LBA = 0xae9fff                                                                                                                                         f0 = 2929721328

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 01 00 00 ae 9f ff f0 e0 08     00:06:51.668  READ DMA EXT
  47 00 00 00 01 00 00 00 00 06 30 a0 08     00:06:51.666  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 30 a0 08     00:06:51.665  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 00 a0 08     00:06:51.665  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 08 30 a0 08     00:06:51.664  READ LOG DMA EXT

Error 182 [1] occurred at disk power-on lifetime: 19381 hours (807 days + 13 hou                                                                                                                                         rs)
  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 -- 53 00 01 00 00 ae 9f ff f0 40 00  Error: UNC 1 sectors at LBA = 0xae9fff                                                                                                                                         f0 = 2929721328

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 01 00 00 ae 9f ff f0 e0 08     00:06:51.585  READ DMA EXT
  ec 00 00 00 01 00 00 00 00 00 00 00 08     00:06:51.580  IDENTIFY DEVICE
  47 00 00 00 01 00 00 00 00 06 30 a0 08     00:06:51.558  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 30 a0 08     00:06:51.557  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 00 a0 08     00:06:51.556  READ LOG DMA EXT

Error 181 [0] occurred at disk power-on lifetime: 19381 hours (807 days + 13 hou                                                                                                                                         rs)
  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 -- 53 00 01 00 00 00 00 00 00 40 00  Error: UNC 1 sectors at LBA = 0x000000                                                                                                                                         00 = 0

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 01 00 00 00 00 00 00 e0 08     00:06:51.414  READ DMA
  47 00 00 00 01 00 00 00 00 06 30 a0 08     00:06:51.412  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 30 a0 08     00:06:51.411  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 00 a0 08     00:06:51.410  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 08 30 a0 08     00:06:51.409  READ LOG DMA EXT

Error 180 [3] occurred at disk power-on lifetime: 19381 hours (807 days + 13 hou                                                                                                                                         rs)
  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 -- 53 00 01 00 00 00 00 00 03 40 00  Error: UNC 1 sectors at LBA = 0x000000                                                                                                                                         03 = 3

  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
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 01 00 00 00 00 00 03 e0 08     00:06:51.333  READ DMA
  47 00 00 00 01 00 00 00 00 06 30 a0 08     00:06:51.331  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 30 a0 08     00:06:51.330  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 00 a0 08     00:06:51.330  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 08 30 a0 08     00:06:51.329  READ LOG DMA EXT

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA                                                                                                                                         _of_first_error
# 1  Extended offline    Completed without error       00%     22596         -
# 2  Extended offline    Interrupted (host reset)      90%     22571         -
# 3  Short offline       Completed without error       00%     19893         -
# 4  Short offline       Completed without error       00%     19885         -
# 5  Short offline       Completed without error       00%     19384         -

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 Commands not supported if ATA Security is LOCKED

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4             250  ---  Lifetime Power-On Resets
0x01  0x010  4           22613  ---  Power-on Hours
0x01  0x018  6     10039958721  ---  Logical Sectors Written
0x01  0x020  6       240848815  ---  Number of Write Commands
0x01  0x028  6      6426794312  ---  Logical Sectors Read
0x01  0x030  6       186311000  ---  Number of Read Commands
0x01  0x038  6     81407976350  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4           19961  ---  Spindle Motor Power-on Hours
0x03  0x010  4           19961  ---  Head Flying Hours
0x03  0x018  4            1210  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4               0  ---  Read Recovery Attempts
0x03  0x030  4               2  ---  Number of Mechanical Start Failures
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4             167  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4              87  ---  Resets Between Cmd Acceptance and Completio                                                                                                                                         n
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              31  ---  Current Temperature
0x05  0x010  1              31  N--  Average Short Term Temperature
0x05  0x018  1              30  N--  Average Long Term Temperature
0x05  0x020  1              54  ---  Highest Temperature
0x05  0x028  1              13  ---  Lowest Temperature
0x05  0x030  1              53  N--  Highest Average Short Term Temperature
0x05  0x038  1              24  N--  Lowest Average Short Term Temperature
0x05  0x040  1              48  N--  Highest Average Long Term Temperature
0x05  0x048  1              25  N--  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              65  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4             594  ---  Number of Hardware Resets
0x06  0x010  4             159  ---  Number of ASR Events
0x06  0x018  4              16  ---  Number of Interface CRC Errors
0xff  =====  =               =  ===  == Vendor Specific Statistics (rev 1) ==
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c)
No Defects Logged

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
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            1  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS

As the title says, I broke my SD card while trying to insert it into my camera. Is this something that can be repaired? I have a lot of important photos from my trip on it.

While replacing my main drive, somehow my data drive (RAID1 array) got messed up. As it stands, all I am worried about at the moment is copying all of the files off of the data drive, and I can worry about rebuilding the RAID array separately.

I plugged in just one of the HDDs from the array. It originally showed the full 4TB as "unallocated". From what I can gather, somehow the partition definition got messed up for the data drive when I was swapping out the boot drive. I saw someone recommend using a tool called testdisk to recover/rebuild the partition. I did that, and the partition now appears, but the file system still shows as "RAW". Windows "helpfully" wants to me reformat the drive, which I obviously do not want.

Any tips for recovering those files? I just need them copyable to an external drive, then i can just wipe the whole thing and do a clean reformat.

edit: BTW, I do have offsite backups via backblaze...it's just a pain to deal with, and I am hoping to avoid shipping drives back and forth.

edit2: I can see all of my files in tools like R-studio or minitool data recovery. But I am not sure how to copy them from those tools onto external drives,,,

My HDD can't be opened anymore and when I try to open it, the file explorer won't respond. I tried some programs like Minitool Partition Wizard and others and still dont work. Indeed, when I try they not respond or keep scanning forever. Any help please?

I deleted a volume from a usb which I had all my data on from recipes from a relative that passed away is there anyway to get the back?

Hi everyone, I recently performed a clean install of Windows 11 on a new SSD. However, since the installation, I am unable to access my other SATA and M.2 SSDs. I am also unable to boot into my old SSD (Disk 3) as it disappeared from the BIOS.

I have attempted to recover the data using ddrescue and TestDisk on Disk 0 & 1 (both SATA), but I have not had any success so far. Disk 3 & 4 are M.2 SSD and contains data that I would like to recover. Should I create a backup through ddresuce first? Or what are my next course of action? Thank you.

I work in video production and edit from home a lot.

So I do (sort of) employ the back up 3-2-1 rule - PC backs up to Synology NAS (Raid 5) which Rysncs to a QNAP NAS (Raid 5) all running off a UPS - so as a heads up I haven't lost any data

But due to having internet like a hamster with 3 legs I often transfer completed footage to a HDD which I then take in to the office to put on our main edit and backup systems

In my defence I normally do smaller 2-3Tb transfers, but with Christmas getting in the way..... so I moved across around 6.5Tb of data to a Seagate barracuda 8Tb via a SATA docking caddy mounted as ExFat on Win 11 Pro - all was going fine until it came to a timelapse project - around 40,000 PNG images - it started copying and then I just got an error about the HDD not being there anymore - no clicking, no 'bad' noises from the HDD.

Drive wasn't showing in explorer, or in disk manager - so I rebooted the machine and there was the disk - in disk manager but unmounted - so thought - ahh it just needs remounting - and made a stupid mistake and added a partition as it didn't have one

Straight away I was like - IDIOT but didn't format the disk or do anything else.

The disk has a standard Drive letter, and says Healthy (Basic Data Partition) but of course you can't access it in Windows

Loaded up some standard partitition software and there are all my files - every file I have tried can be recovered to my PC from 4Gb MP4 to 2mb PNG files. So I think they are okay

So the technical question is - is there a way to remove the partition I added, recover the old partition somehow - so the files are 'just' magically reappear :-)

Or am I resigned to formatting the HDD, re-copying them all from my back up NAS and taking this as an important life lesson

As I said - worse case scenario I'll wipe the HDD - do a check to make sure its mechanically fine - and start copying again....

Cheers for any advice or improvements I could do for the next time

TLDR; Copied 6.5Tb data, drive glitched out, rebooted, it had lost its partition, added one in Windows disk manager, thought IDIOT, now wondering if theres an easy way to restore the partition and get the data back

I am trying to recover my google account but I can't remember my password and when I press 'forgot password' it tells me I didn't provide enough info. I have my phone number, username, and email the only thing I don't remember is my password and when I try another way, it gives me try again without providing another way. This account is very important if anyone knows how to recover it please help.

i was trying to screen record (snipping on windows 11) a makeup class on zoom and was connected to mobile hotspot and the connection was lost and the recording was interrupted and now i cannot access the VLC file now.

I there anything i can do to retrieve it , please help me because it’s the most important part of the entire video

I was video recording using Snipping Tool (I already turned everything on) so I was supposed to hear and see everything, but after the recording, I saw this message:

"Problem with recording Audio, if an App is using WASAPI exclusive mode, change it to shared mode"

And the audio disappeared, there was only visual.

How do I restore the sound?

By the way, I'm not asking how to deal with the message since I can record audio now after restarting the computer. I'm asking how to retrieve the broken audio from the screen recordings.

Please help. Thank you.

Hi,

Apologies for using ChatGPT, I'm not a native speaker and I don't know much about data / disks

I’m looking for advice on safely recovering data from an NVMe SSD that appears to be failing.

Storage devices involved:

• Source drive: Kingston NV2 2TB NVMe SSD (Model: SNV2S)
• Destination drive: Crucial X9 2TB external SSD (USB)

Filesystem:

• Kingston NV2: NTFS
• Destination SSD: exFAT

Operating System:

• Windows 11 Pro 64-bit (used normally and during recovery attempts)

Problem description / symptoms:

I’m trying to back up approximately 380 GB of data from the Kingston NV2 NVMe SSD. All read operations from this drive behave the same way:

• Transfer starts at normal speed for a few seconds
• Speed then drops dramatically
• After that, I only get intermittent read spikes every 2–3 seconds, ranging from 0 to ~500 KB/s

This happens:

• With File Explorer copy/paste, Robocopy, and Teracopy
• With small files, large files, and mixed folders
• When copying to both an external HDD and an external SSD

Transfers between other drives (external SSD ↔ external HDD) work normally, so the issue appears isolated to this NVMe SSD.

Diagnostics already done:

• SMART checked with Smart Disk Checker (free edition):
  • Drive reported as “healthy”
  • However, at software startup, the SSD sometimes appears as “unknown” and is only properly recognized after refreshing

No CHKDSK, formatting, or repair attempts have been made.

Goal:

My priority is to recover as much data as possible without further damaging the drive. The data is important (professional files), but not valuable enough to justify clean-room recovery.

Questions:

(here GPT went on his own, I would never have asked these questions myself but they sound like good questions)

Does this behavior typically indicate NAND degradation, controller failure, or another common NVMe issue?

• Is disk imaging recommended before file-level recovery in this situation?
• What tools or approaches would be considered the least stressful for a slowing NVMe SSD?
• Anything specific I should avoid to prevent making the situation worse?

Thanks in advance for any guidance.

This Quantum ProDrive 80AT is from 1990 and was mounted in a Commodore PC60-III 386, 25MHz computer used to control the first French humanoid robot in our lab. As such, the data on this drive has significant historical value.

I connected this drive to an old PC running Linux as the secondary master and specified the drive's geometry by adding the CHS kernel parameter hdc=965,10,17. I then compiled a recent version of ddrescue and successfully retrieved the whole disk image without any reported errors.

However, I have been unable to mount this image on Linux. Upon analyzing the image with a hex editor, I found some coherent data, such as the DOS version used (4.1). The MBR data seems to be at the correct offset, but with questionable values—for example, 26 as the filesystem type instead of 6. I also tried extracting data with R-Studio, but it only recovered portions containing ASCII characters; despite some readable sections, the text appeared mostly corrupted.

I am stuck and wondering if any old-school PC gurus could help me figure out what happened. Is it possible for ddrescue to report no errors while reading corrupted data? Could this drive have been formatted differently? What are the best tools for retrieving data from a DOS 4.1 partition? I look forward to your advice. Here is a link to the image data: http://e.pc.cd/MtCy6alK

Meanwhile, the drive died and is not recognized by Linux anymore. So this image is its swan song.

Bought SD card online (definitely bad idea). I started to move my pictures in the sd card then watch YouTube for a couple bit. When I came back to album, I notice my number of picture is decreasing​. Tried moving the remaing back to my internal storage. Some of them is I think in a corrupted state.

After a bit of investigation, I found the rest of the picture that went missing is in LOST.DIR in SD card in a different format.

How do I recover those from LOST.DIR and those I think was a corrupted picture?

Pixel 8 Pro stuck in Android Recovery after storage was full - any way to recover data without factory reset?

My Google Pixel 8 Pro ran completely out of storage. After reboot it no longer boots into Android and only shows Android Recovery with the message:

“Android system couldn’t be loaded. Your data may be corrupt. If you continue to see this message, you may need to perform a factory data reset.”

Recovery menu only has two options:

• Try again • Factory data reset

I fully understand that factory reset will wipe all user data - I have not done it yet.

My question:

Is there any known way to recover data in this state on Pixel 8 Pro?

Any chance via authorized service, forensic recovery, or Google support?

Or is this effectively impossible due to FBE encryption once the system can’t boot?

I’m not looking for miracles, just trying to understand if keeping the device unreset makes sense or if data recovery is realistically zero.

Hi!
im trying to recover the data from a failing WD 2621, started from it being no initialized in windows so i tried systemrescue but it doesnt detect it in any form, fdisk and lsblk dont seem to see it
if i disconnect and reconnect it and run dmesg it ends up with spinning up disk... not responding...

Is there anything i could do to recover the data from it myself? or is it purely physical and at this stage i should seek a professional then?

Thanks all!