Files disappeared from mounted partition

I've just spent ages copy over my data to an NTFS partition so that it can be shared between windows and linux, including organising it all, literally all day.

I went to reboot into windows to clean stuff up from that end and got an error on shutting down about not being able to unmount the disk 'mnt/Data' and then when it restarted all of the data was gone, all I could see was the directories that were there previously.

The data must be on the drive still, but not showing in the filesystem.

Is there any way that I can recover it?

I've tried umount and then mount

I ran check filesystem in Disks and it said it was undamaged. I still ran repair filesystem anyway but that made no difference.

df -h shows:

/dev/nvme0n1p2  971G  275G  696G  29% /mnt/Data

Which is consistent with the amount of data that should be on it.

I'm at a bit of a loss as to what to do next.

Out put of smartctl if it helps:

=== START OF INFORMATION SECTION ===
Model Number:                       WD_BLACK SN770 2TB
Serial Number:                      241402803151
Firmware Version:                   731120WD
PCI Vendor/Subsystem ID:            0x15b7
IEEE OUI Identifier:                0x001b44
Total NVM Capacity:                 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,000,398,934,016 [2.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            001b44 8b4708296a
Local Time is:                      Sat Jul 13 20:15:04 2024 BST
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00df):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x7e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg *Other*
Maximum Data Transfer Size:         256 Pages
Warning  Comp. Temp. Threshold:     84 Celsius
Critical Comp. Temp. Threshold:     88 Celsius
Namespace 1 Features (0x02):        NA_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     5.40W    5.40W       -    0  0  0  0        0       0
 1 +     3.50W    3.00W       -    0  0  0  0        0       0
 2 +     2.40W    2.00W       -    0  0  0  0        0       0
 3 -   0.0150W       -        -    3  3  3  3     1500    2500
 4 -   0.0050W       -        -    4  4  4  4    10000    6000
 5 -   0.0033W       -        -    5  5  5  5   176000   25000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -    4096       0         1

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        37 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    6,513,564 [3.33 TB]
Data Units Written:                 6,984,185 [3.57 TB]
Host Read Commands:                 81,916,854
Host Write Commands:                63,982,934
Controller Busy Time:               192
Power Cycles:                       118
Power On Hours:                     68
Unsafe Shutdowns:                   21
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               47 Celsius
Temperature Sensor 2:               37 Celsius

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged

I thought maybe running windows native tools to check the disk might be an idea and lo & behold:

chkdsk d:
The type of the file system is NTFS.
Volume label is Data.

WARNING!  /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
Attribute list entry with type code 104 in file B94 is corrupt.
Attribute list for file B94 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Attribute list entry with type code 80 in file B96 is corrupt.
Deleted corrupt attribute list entry
with type code 30 in file B96.
Attribute record (30, "") from file record segment B96
is corrupt.
Attribute record (80, "") from file record segment BCD
is corrupt.
Attribute record (80, "") from file record segment 15C51
is corrupt.
Attribute record (80, "") from file record segment 176F5
is corrupt.
  163072 file records processed.
File verification completed.
 Phase duration (File record verification): 836.65 milliseconds.
File record segment B95 is an orphan.
File record segment B97 is an orphan.
File record segment BCC is an orphan.
File record segment BCD is an orphan.
  59 large file records processed.
 Phase duration (Orphan file record recovery): 2.45 milliseconds.

Errors found.  CHKDSK cannot continue in read-only mode.

Just run chkdsk /f d: and I can see the files in windows again!

But loads of the directories and does were missing so I'm doing it all from scratch again.....

How could this have happened?

How can I prevent it from happening again?

It's worrying to me that files I could see and interact with are suddenly not there after a reboot. I have never experienced anything like that before.

I am wondering if it is a partition overlap issue:

https://gparted.org/h2-fix-msdos-pt.php

Thanks, I did check that out and it wasn't an overlap issue.

It has since been fine, so hopefully a strange but worrying one off.

It is at least all backed up off site now should it reoccur.

I did have an issue once where I discovered my /home folder had disappeared under GParted. I wrote the procedure how to correct this in both unofficial manual for 15 and 17.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.