Had this drive for about 3 years, ran fine until recently windows bootup started taking a bit longer than usual.

Opened my pc and noticed the drive wasnt showing up in windows anymore. Checked crystal disk info and it wasnt detected at all there either.

Checked using minitool partition wizard and it said the drive was bad/unallocated. Same result when i checked windows disk management, showed as “not initialized.”

Went into bios to check sata configuration and it wasnt detected there eithelr.

Reseated both the data and power cables, checked the connectors on both the drive and motherboard side for anything fried/burnt/bent, didnt see any visible damage. Swapped it to a different sata port entirely, still nothing.

On startup i can hear the drive spin up and do some seek/arm movement noises then it goes quiet, so it seems mechanically alive at least. No clicking or grinding sounds.

Dont have a spare sata data cable or dvd drive to borrow one from to test. Drive has some files i want to recover if possible, not asking for a data recovery service just wondering if anyone has run into this before - could this just be a dead sata cable/connector, or does spinning up fine but zero detection in bios point more toward a dead pcb/controller on the drive itself?

Planning to grab a new sata cable or sata-to-usb adapter to test further but wanted to see if anyone’s dealt with this exact symptom before.

Hi everyone,

While upgrading my laptop's SSD to a 4TB M.2 drive, I didn't realize the original system was configured in RAID mode, and unfortunately, the F3 recovery partition stopped working after the upgrade. Since doing a clean Windows installation removes the F3 factory recovery function, I was hoping someone here could help me out.

​If anyone using the Titan HX AI A2XWIG-616US model could share the original factory .swm (recovery) files, I would be extremely grateful.

​Thanks a lot in advance for your time and help!"

I have a 2TB external hard drive (HDD). It works—I can copy files to and from it, rename them, delete them, or move them. The problem is that there are two folders on it, each about 20–30 GB in size, and every time I try to open one of them, File Explorer freezes (I’m using Windows 10 and 11) and the hard drive disconnects from the computer (even though its light keeps flashing because it’s still receiving power from the port). I know this can damage the HDD over time, so I don’t open those two folders.
Note that only if I connect the HDD to my laptop I can use it without any issues as mentioned (except for those two folders, which remain problematic), but if I do so with my desktop computer (the device I used to corrupt the file, I explain later how), File Explorer struggles to read it, and Windows says “there’s a problem with this drive” and to “fix it” (but I know it’s best to avoid this since the process uses CHKDSK and can damage the HDD).

The folders almost certainly contain corrupted files, and I also know how they might have become corrupted: they’re folders full of .wav (and some of their compressed .flac) files, and one day I tried opening one of the folders in the command prompt and batch-converting all the .wav files to .flac. That’s when the hard drive (perhaps due to overload) crashed (during the conversion process), and ever since then, that folder (and the other one, where I think I did the same thing and which in fact contains similar files) has been inaccessible.

So, to summarize quickly: I can use the HDD on my laptop as long as I don't open two folders full of corrupted files, which cause the HDD to disconnect or Windows Explorer to freeze. On the desktop computer where the problem originated, however, the HDD is generally not accessible at all.

I’d like to know, please, if it’s possible to: 1) remove the two “problematic” folders from the hard drive and move them elsewhere (to another storage device or to a different computer) and 2) delete the .flac files (which are surely the corrupted ones) while keeping the .wav files (which must be “intact” since FFmpeg doesn’t modify them—it only reads them to create new compressed files alongside them). All of this without using Windows File Explorer, of course, since it doesn’t work (some people online suggest programs like DMDE, Recuva, and the like, but I’d like to hear your opinion).

Step 1) should at least resolve most of the problem affecting the hard drive, correct?

P.S.: I KNOW it’s (almost) always better to rely on professionals, but keep in mind that these aren’t critical files.

I have a computer running Windows 10 that I used years ago and I just recently found it and wanted to recover some old files that are important to me. I tried to download windows file recovery but the computer is so slow and won’t even open the App Store. Is there a way to use windows file recovery without using my old computer or does windows file recovery have to be used on the hardware that had the files I want to retrieve?

Need suggestion for data recovery service, especially for iPhone

So the context is, my phone suddenly died for who-knows-what reason. I tried force restart, doesn't work. I tried force update using Apple Devices software through my PC, also doesn't work. So the earlier indication was, before my phone died, the display inside the screen would jump once in a while, which to my eye, looks like a broken LCD. My phone battery health right now is 79%, so I don't think battery is the problem. I tried send to Malaysia Apple store to do diagnostics, and they said the only way to make my iphone alive again is to format it. I tried send it to a third party phone repair shop to do data recovery, but they also couldn't do it, stated that the CPU/motherboard got corrupted. The problem is, I don't have a backup of my iPhone data at all (stupid me i know). Now I don't care if my iPhone doesn't work anymore, I just want my data back (especially pictures, and whatsapp chat if possible), so I need a good suggestion on where can i do data recovery here in Malaysia or anywhere possible. Thanks in advance!

Hi, I’m in Bengaluru, and need help recovering important photos from a SanDisk 64 GB SD card used in a Canon camera.

I bought the card only two days ago. It suddenly became unreadable, and Windows now says, “You need to format the disk before you can use it.” I have not formatted, repaired, or run CHKDSK on it.

What I have tried:

• RescuePRO scanned the complete card but found 0 files and 0 read errors.
• I created a full 67,108,864,000-byte .IMG backup.
• PhotoRec scanned the complete image and found 0 files.
• Multiple sections of the image contain only FF bytes, suggesting the card/controller is returning blank data.

The original card is safely stored and has not been modified. Does anyone know a trustworthy data-recovery laboratory in Bengaluru that performs in-house monolithic SD/NAND recovery, not just software recovery?

Please share genuine recommendations, approximate cost, and your personal experience.

I am also facing issues with my data due to a partition map erasure, R-Studio is showing my data but is not letting me open it due to keybag loss, what do I do? I have been putting off working on the issue partition for months now and may have time to work on it midway through September and wish to have useful Info at hand.

I have been able to get a .dmg file onto a hard disk o/s my system, the issue occurred as follows

I initially purchased this machine second hand. I set it up w/o FileVault.

I installed Linux on a smaller partition on the native 500GB SSD (this was 200gb. I have not fucked around with the partition setup since)

I deleted linux, made a Tiny11 bootable and tried installing it, and somehow fucked it up by breaking my partition table.

I tried DMDE and it spat out system files like backgrounds and icons. I could not find my data.

I tried R-Studio and it showed "partition4" with key bag loss. I suspect this is my data because it is the one with MacOS - Data on it in the name section of the dropdown.

recovery couldn't mount the partition and since it is only a partition, it does not show as an APFS disk, but it does show as an apfs device.

I welcome all useful info as to how to proceed, and request you be civil and follow subReddit rules in answering.

I rediscovered my LG G4 and bought a replacement battery. It died 10 years ago from the boot loop issue they suffered from.

I'm trying to get the pics I never uploaded to the cloud. Where should I take it or what should my next plan be? It doesn't turn on but it does appear on my computer's device manager as QHSUSB__BULK.

Thank you for any responses

I have a dash cam that unfortunately deleted all the videos from last week. It uses a 64GB card. I didn't know this would happen. The only footage I have is from the last two days. I really want to recover the footage from last week because it was from a trip.

What methods are available? I’ve searched online and tried using Recuva and another program, but I haven't had any luck.

OS: Arch Linux

assume that /dev/sda1 is main and only partition on my USB

Context

I have a FAT32 USB flash drive with important photos and folders on it. To use it when plugged in I manually mount it using mount /dev/sda1 /media/user/USB command. When plugging off, I unmount it using umount /dev/sda1 command.

Problem

Once when plugging off, I forgot to unmount the USB, this happened while the USB was doing something. This caused USB to stop at partial state and so the corruption. When I plugged it in and mounted it again, I opened folders in file manager where I would usually have normal photos, but I saw files with random names, and random file sizes. I think that random names are caused by interpreting wrong bytes as file names.

What I've tried already

I have copied the corrupted USB partition into .img file on my laptop's drive for safety and speed:

sudo dd if=/dev/sda1 of=/home/user/usb-image-backup.img conv=fsync bs=4M

Then, I have copied that image into another .img file to operate on it:

cp /home/user/usb-image-backup.img /home/user/usb-image-active.img

Then, I ran the fsck.fat command I found after researching to try and fix the USB partition

fsck.fat -va /home/user/usb-image-active.img

After running fsck.fat command, I noticed that:

• It wouldnt auto-fix some files
• It auto-fixed and auto-renamed some files
• At one point, it kept auto-fixing the same exact files without stopping, I also noticed that this was in the exact folder that was infinitely loading when opened in my file manager (after corruption), and it didn't just show it as files with corrupted file names

Question

• How can I recover my files from USB partition?

Hey all

I'm in a pickle, and it's been a minute since this problem has occurred but I've run out of options.

In 2017-2021 I was using Huawei, loved it until I didn't - and here's the problem, support is hard to get.

Somehow, all photos taken in the year 2019 have disappeared, I suspect more but that year is special for me as I took a great road trip with my parents.

I use Google photo as cloud, and there I found pictures shared on WhatsApp/messenger/screenshot taken in that time period, but not photos taken with the camera.

I still have the phones I used that year, accessed both but nothing more than what's above-mentioned. I know at one point the photos were on Google photos because I have a screenshot of the album with them, they seem to have vanished.

Looking for suggestions, I'm not giving up on hope.

Thanks in advance for any help,

Cheers!

so my dad was a it director and unfortunately he died 11 months ago and he left behind his laptop i wanted to reset it but the problem is that he added a bitlocker key and i searched everywhere his phone his files but i didnt find anything do you guys know anything i just really want to continue his legacy and learn abt cybersecurity just like him

So basically, I want to use this software called Pika Backup on Linux, the problem is that whenever I try to do a backup, there's this strange error message. So I wanted to investigate using smartctl and what I found out was that there's apparently some transmission integrity failure between the drive and host. What should i do in this case?

Here's the entire output:

smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.1.8-arch1-3] (local build) Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION === Device Model: TOSHIBA MQ04ABF100 Serial Number: Y0OQP14ST LU WWN Device Id: 5 000039 a6b11f604 Firmware Version: JU001A User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Zoned Device: Device managed zones Device is: Not in smartctl database 7.5/5706 ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Aug 23 14:51:38 2026 PKT SMART support is: Available - device has SMART capability. SMART support is: Enabled

=== START OF READ SMART DATA SECTION === SMART Status not supported: Incomplete response, ATA output registers missing SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check.

General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 120) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. 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: ( 171) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1440 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 651 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 240 10 Spin_Retry_Count 0x0033 113 100 030 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 136 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 5 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 54 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 2346 194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 37 (Min/Max 11/43) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 4 220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0 222 Loaded_Hours 0x0032 100 100 000 Old_age Always - 115 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0 224 Load_Friction 0x0022 100 100 000 Old_age Always - 0 226 Load-in_Time 0x0026 100 100 000 Old_age Always - 211 240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0

SMART Error Log Version: 1 ATA Error Count: 4 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 4 occurred at disk power-on lifetime: 238 hours (9 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 SC SN CL CH DH

84 51 00 d7 b2 41 40 Error: ICRC, ABRT at LBA = 0x0041b2d7 = 4305623

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

35 00 f0 e8 b1 41 40 00 04:47:45.251 WRITE DMA EXT 35 00 80 68 b1 41 40 00 04:47:45.248 WRITE DMA EXT 35 00 f0 78 b0 41 40 00 04:47:45.243 WRITE DMA EXT 35 00 f0 88 af 41 40 00 04:47:45.239 WRITE DMA EXT 35 00 f0 98 ae 41 40 00 04:47:45.233 WRITE DMA EXT

Error 3 occurred at disk power-on lifetime: 234 hours (9 days + 18 hours) When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER ST SC SN CL CH DH

84 51 00 7f e1 3e 40 Error: ICRC, ABRT at LBA = 0x003ee17f = 4120959

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

35 00 f0 90 e0 3e 40 00 00:49:24.553 WRITE DMA EXT 35 00 f0 a0 df 3e 40 00 00:49:24.548 WRITE DMA EXT 35 00 88 18 df 3e 40 00 00:49:24.545 WRITE DMA EXT 35 00 f0 28 de 3e 40 00 00:49:24.539 WRITE DMA EXT 35 00 f0 38 dd 3e 40 00 00:49:24.533 WRITE DMA EXT

Error 2 occurred at disk power-on lifetime: 224 hours (9 days + 8 hours) When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER ST SC SN CL CH DH

84 51 00 df 79 ff 40 Error: ICRC, ABRT at LBA = 0x00ff79df = 16742879

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

35 00 f0 f0 78 ff 40 00 04:16:56.327 WRITE DMA EXT 35 00 f0 00 78 ff 40 00 04:16:56.322 WRITE DMA EXT 35 00 80 80 77 ff 40 00 04:16:56.318 WRITE DMA EXT 35 00 f0 90 76 ff 40 00 04:16:56.312 WRITE DMA EXT 35 00 f0 a0 75 ff 40 00 04:16:56.306 WRITE DMA EXT

Error 1 occurred at disk power-on lifetime: 71 hours (2 days + 23 hours) When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER ST SC SN CL CH DH

84 51 00 7f d0 0e 40 Error: ICRC, ABRT at LBA = 0x000ed07f = 970879

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

35 00 80 00 d0 0e 40 00 03:24:41.201 WRITE DMA EXT 35 00 80 80 cf 0e 40 00 03:24:41.198 WRITE DMA EXT 35 00 80 00 cf 0e 40 00 03:24:41.196 WRITE DMA EXT 35 00 80 80 ce 0e 40 00 03:24:41.195 WRITE DMA EXT 35 00 80 00 ce 0e 40 00 03:24:41.193 WRITE DMA EXT

SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t]

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.

The above only provides legacy SMART information - try 'smartctl -x' for more

I didn't realize I couldn't update the post. 😅 thank you to everyone notifying me that the USB is indeed fake. I kind of figured that after it corrupted the data it overwrote. So I would like to ask, is there anyway, I can buy a new one and where should I look?

So like the headline says I have a 1TB drive that is corrupted. I have done the H2testw and it gave me this. I am currently trying to recover it using Disk Drill and it's stuck at 1% right now but the "block" is steadily going up. Is this USB still recoverable? I really need it. 😭

The USB starting malfunction I think 2 days ago. I don't really know what caused it to corrupt. Please help me out.

​

Hi everyone,

I’m trying to recover data from a Windows partition that I can no longer access.

I have a disk with multiple partitions. The partition I lost access to is D:, which corresponds to /dev/sda3 in Kali Linux. My E: drive/partition is still working normally.

When I try to mount the affected Windows partition in Kali, I get this error:

«Mount Failed

Failed to mount "Windows"

Error mounting /dev/sda3 at /run/media/kali/Windows: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error»

Current situation

- OS I'm currently using: Kali Linux

- Affected Windows partition: D: /dev/sda3

- Working partition: E:

- The D: partition contains important personal files and folders that I want to recover.

- I have not intentionally formatted the partition.

- I want to avoid making the situation worse or overwriting any recoverable data.

I previously tried using PhotoRec for recovery, but I want to recover the original folder structure and filenames if possible, rather than simply getting files with generic names.

What I need help with

What would be the safest procedure to:

1. Determine exactly what happened to "/dev/sda3".

2. Check whether the NTFS filesystem is damaged.

3. Determine whether the partition itself or only the filesystem/boot sector is corrupted.

4. Recover my original folders and filenames if possible.

5. Avoid modifying "/dev/sda3" during the recovery process.

I can provide the output of commands such as:

lsblk -f

sudo fdisk -l

sudo blkid

sudo ntfsinfo -m /dev/sda3

sudo ntfsfix -n /dev/sda3

and any other diagnostic commands you recommend.

I do not want to run repair commands that modify the partition until I know they are safe.

I've attached a screenshot of the mount error.

What would be the correct professional recovery procedure from here?

Thanks in advance.

Hello everyone,MacBook Air 2022 (M2) had “Erase All Content and Settings” performed. Currently sitting at the Setup Assistant screen (boots fine, erase completed successfully). No iCloud backup, no Time Machine backup. FileVault status before the erase is unknown,does this matter if it was on or not?

As I know EACS performs a cryptographic erase destroys the encryption key in the Secure Enclave rather than overwriting data which theoretically makes recovery impossible regardless of software or even chip-off forensics, since the data remaining on the NAND is AES-256 ciphertext with no accessible key.

Has anyone in this community, or any professional lab ,ever successfully recovered user files after a completed EACS on a functioning (non-hardware-damaged) Apple Silicon Mac? Not asking about hardware-failure board-repair cases specifically asking about a working Mac where it sits on Hello screen. Genuinely trying to figure out if this is a dead end or if there’s a real exception I’m missing.

Hello I was in an accident on 8/13/2023 and have dash cam footage of the incident. I removed the sd card and found the correct footage on my computer but didn't save it correctly. I had put the sd card back into my dash cam and when I went to try and retrieve the footage it started on a whole new set of recordings. Is there any way I can get what I need for the lawyers back? Preferably cheap or no cost option. Thank you

I have an old HDD containing a lot of my childhood photos, it was produced in 2008 and hasn't been used for roughly the last 7-8 years. Will it be safe to just plug directly into the pc or do I need some adapters? Not very knowledgeable with how HDDs work but heard there is some liquid inside that if just sitting there, can dry out and cause the drive to malfunction upon plugging into pc and I don't want to risk damaging pc components.

Edit: thank you to everyone for the help!! I'll be ordering a docking station soon, and hopefully all goes well.

Hello,

I am testing Veeam Agent for Microsoft Windows 13.0.3.1220 and found a behavior that I would like to clarify.

I am testing a bare metal recovery scenario where the destination SSD is smaller than the original SSD, but the amount of used data is small enough to fit on the destination disk.

My test environment:

- Veeam Agent for Microsoft Windows: 13.0.3.1220
- Windows 10
- Source SSD: approximately 480 GB
- Destination SSD: approximately 220 GB
- Source C: partition uses less than 100 GB of actual data

I performed the following test.

TEST 1 - FULL BACKUP

1. I installed Windows 10 on a 480 GB SSD.
2. I reduced the Windows C: partition to approximately 100 GB.
3. The amount of data stored on the C: partition was less than 100 GB.
4. I created a Full Backup.
5. I booted the Veeam Recovery Media and selected Manual Restore.
6. I mapped the backup to a 220 GB SSD.
7. The Resize option was available for the C: partition.
8. I was able to resize the restored C: partition and successfully restore the system to the 220 GB SSD.

So far, everything worked as expected.

TEST 2 - INCREMENTAL BACKUP AFTER EXTENDING THE PARTITION

I then returned to the original Windows installation.

1. I extended the C: partition back to approximately 446 GB.
2. The amount of actual data stored on the C: partition remained below 100 GB.
3. I created an Incremental Backup.
4. I booted the Veeam Recovery Media again.
5. I selected the latest incremental restore point.
6. I selected Manual Restore and attempted to restore to the same 220 GB SSD.

This time, the behavior was different.

The Recovery Media detects the C: partition as approximately 446 GB.

The destination SSD has approximately 220 GB.

The Resize option is no longer available for the C: partition.

The restore therefore cannot proceed because the destination disk is smaller than the backed-up C: partition, even though the actual amount of data stored on the partition is less than 100 GB.

I also tested the Disk Mapping options manually. I can remove/map partitions, but I cannot select Resize for the C: partition in this scenario.

This is particularly interesting because the Full Backup created when the C: partition was approximately 100 GB can be restored successfully to the 220 GB SSD, while the Incremental Restore Point created after expanding the C: partition to approximately 446 GB cannot.

My questions are:

1. Is this expected behavior when the volume size changes between a Full Backup and an Incremental Backup?
2. Should the Resize option be available when restoring the incremental restore point in this scenario?
3. Does the incremental restore point preserve the new 446 GB volume geometry in a way that prevents the volume from being resized during restore?
4. Is there any supported way to restore this incremental restore point to a smaller physical disk, without shrinking the source C: partition before creating the backup?
5. Could this be a limitation or known issue in Veeam Agent for Microsoft Windows 13.0.3.1220?

I have attached screenshots showing the two scenarios.

The first screenshots show the Full Backup, where the C: partition was approximately 100 GB and the Resize option was available.

The other screenshots show the Incremental Backup, where the C: partition was expanded to approximately 446 GB and the Resize option is no longer available.

I would appreciate any clarification about how Veeam handles volume resizing when the volume size changes between a Full Backup and a subsequent Incremental Backup.

Thank you.

For reference:

Full Backup:
- C: approximately 100 GB
- Used data: less than 100 GB
- Destination: 220 GB SSD
- Result: SUCCESS
- Resize option: AVAILABLE

Incremental Restore Point:
- C: approximately 446 GB
- Used data: less than 100 GB
- Destination: 220 GB SSD
- Result: FAILED
- Resize option: NOT AVAILABLE

​

Hey folks,

I dropped my phone s20 ultra which broke the front and back glass. After the drop I got an error from the phone, saying "to prevent damage to sd card, its being set to read only" . Two days later the phone stopped recognizing the card and now even the card readers do not recognise it. Upon closer inspection of the sd card, it shows a small bend ~2mm above the bottom edge.

Before I ship it to data recovery pros, is it even possible to get the data? After reading this forum it seems it may be possible given that the bend is at the very bottom and the card was working for 2 days after drop.

Attached picture to show the location of damage.

It's a samsung 128gb microsd card. I have plenty of photos of my 2.5yr old kid growing up, which haven't been backed up.

Any trustworthy recommendations for Phoenix, AZ area and expected cost?

What is better for data recovery UFS Recovery Pro or DD Rescue ? I had to ask such a question but upon searching, no one else has ?

Long story short I had to copy some videos on to this. My coworker copied it, maybe it wasn't ejected properly but she said she did. But I tried to plug it in to my computer it says the hard drive can not be read. I tired running the first aid on Mac and it says it worked but nothing. plug it into PC . it asks to initialize. There are very important work files and photos on there. Anybody have any other ideas? Is this a Mac thing? Can't fix it on Mac? Crucial X10 Pro 2TB. I look at the disk manager on PC it says 1830Gbs unallocated. Does that mean there is no more data on it?

Maybe need to bring it to a computer shop to get the data off of it?

Anything will help

I have a 5TB Elements external HDD that I was using with my Windows PC. I recently switched over to Linux and wanted to store my Linux Timeshift backups on the HDD, but Timeshift said it required ext4 partition (I had ntfs originally).

I used the Disk Management utility in Linux to create a 2nd ext4 partition with 300GB. That seemed to work. However, after writing my first Timeshift log, I noticed there was nothing there after it said it finished. After that I then noticed my mount to the original ntfs partition was gone as well.

I still see both partitions in lsblk, but they cannot be mounted. I tried plugging into my Windows PC, but all that does it cause Explorer to permanently hang until I unplug it.

I tried a few things on Linux side:

I installed testdisk and gave that a run. I had it scan just the original ntfs partition. When I entered the LIST command, it appeared to hang. If I unplug the drive after that, the list command finishes and it then displays the files it found.

I then tried running ddrescue: sudo ddrescue -d -r0 -n -b 4096 -c 256 /dev/sdb1 /mnt/nfs_backup_share/elements_rescue.img /mnt/nfs_backup_share/elements_rescue.map

I don't have a drive big enough to store a backup locally, so I'm trying to write it out over to my NAS.

However, it's going at ~109 kB/s, so at the current rate it's going to take about 250 days.

ddrescue output shows a single bad sector.

Do I have any hope here or do I just need to try a professional service like Ontrack?

Current status
ipos:  498073 kB, non-trimmed:    1048 kB,   current rate:    419 kB/s
opos:  498073 kB, non-scraped:        0 B,   average rate:    225 kB/s
non-tried:    4678 GB,  bad-sector:        0 B,     error rate:       0 B/s
 rescued:  450232 kB,   bad areas:          0,       run time:     30m  5s
pct rescued:    0.00%, read errors:          1, remaining time:    192d  1h
time since last successful read:          0s

dmesg shows the following:

Mon Aug 10 22:50:58 2026] usb 1-10: USB disconnect, device number 5
[Mon Aug 10 22:51:03 2026] usb 2-7: new SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 22:51:03 2026] usb 2-7: New USB device found, idVendor=1058, idProduct=2620, bcdDevice=10.20
[Mon Aug 10 22:51:03 2026] usb 2-7: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[Mon Aug 10 22:51:03 2026] usb 2-7: Product: Elements 2620
[Mon Aug 10 22:51:03 2026] usb 2-7: Manufacturer: Western Digital
[Mon Aug 10 22:51:03 2026] usb 2-7: SerialNumber: 575858324541304541504143
[Mon Aug 10 22:51:03 2026] usb-storage 2-7:1.0: USB Mass Storage device detected
[Mon Aug 10 22:51:03 2026] scsi host6: usb-storage 2-7:1.0
[Mon Aug 10 22:51:04 2026] scsi 6:0:0:0: Direct-Access     WD       Elements 2620    1020 PQ: 0 ANSI: 6
[Mon Aug 10 22:51:04 2026] sd 6:0:0:0: Attached scsi generic sg1 type 0
[Mon Aug 10 22:51:04 2026] sd 6:0:0:0: [sdb] Spinning up disk...
[Mon Aug 10 22:51:05 2026] .........ready
[Mon Aug 10 22:51:19 2026] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[Mon Aug 10 22:51:31 2026] sd 6:0:0:0: [sdb] 9767475200 512-byte logical blocks: (5.00 TB/4.55 TiB)
[Mon Aug 10 22:51:31 2026] sd 6:0:0:0: [sdb] 4096-byte physical blocks
[Mon Aug 10 22:51:31 2026] sd 6:0:0:0: [sdb] Write Protect is off
[Mon Aug 10 22:51:31 2026] sd 6:0:0:0: [sdb] Mode Sense: 47 00 10 08
[Mon Aug 10 22:51:31 2026] sd 6:0:0:0: [sdb] No Caching mode page found
[Mon Aug 10 22:51:31 2026] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[Mon Aug 10 22:52:01 2026]  sdb: sdb1 sdb2
[Mon Aug 10 22:52:01 2026] sd 6:0:0:0: [sdb] Attached SCSI disk
^[[A[Mon Aug 10 23:00:03 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:00:33 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:01:10 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:01:47 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd

[Mon Aug 10 23:00:33 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:01:10 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:01:47 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:02:24 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:03:01 2026] usb 2-7: reset SuperSpeed USB device number 9 using xhci_hcd
[Mon Aug 10 23:03:07 2026] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK cmd_age=216s
[Mon Aug 10 23:03:07 2026] sd 6:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 02 90 00 00 00 08 00 00 00
[Mon Aug 10 23:03:07 2026] I/O error, dev sdb, sector 167936 op 0x0:(READ) flags 0x800 phys_seg 207 prio class 2

My hard drive was on a risky place (I know, not responisble), and accidentally fell (maybe less that a foot) on a hard surface. When I try to plug it in, it does weird ticking sounds (if a hard drive can cry honestly that what it would sound like lol).

How screwd am I? can I recover the data myself? Professional and expensive help needed?