You are not logged in.
I have LVM on LUKS NVME disk , maybe due to force shutdown I can't mount data on it.
I'm still able to unlock LUKS with password and activate logical volumes (root, home, swap)
But I can't mount it
sudo mount /dev/mapper/HynixVolGroup-home Documents/
mount: /home/lex/Documents: can't read superblock on /dev/mapper/HynixVolGroup-home.
dmesg(1) may have more information after failed mount system call.When tried to moung with
mount -o roalso no luck
If I tried to mount with no journal like
mount -o ro,noloadIt actually mounted and I'm able to observe directories and files. But when try to copy them "the disk is freezing"
lsblk output
nvme0n1 259:4 0 953.9G 0 disk
├─nvme0n1p1 259:5 0 4G 0 part
└─nvme0n1p2 259:6 0 949.9G 0 part
└─cryptlvm 252:0 0 949.9G 0 crypt
├─HynixVolGroup-swap 252:1 0 8G 0 lvm
├─HynixVolGroup-root 252:2 0 80G 0 lvm
└─HynixVolGroup-home 252:3 0 861.4G 0 lvm I've tried to restore superblocks with no luck
Ukrainian
Offline
If I do ddrescue may I use it like
ddrescue -d /dev/mapper/HynixVolGroup-home image.img mapfileof should I clone only partition in my case nvme0n1p2? Because in this case I have the same 1TB spare drive and the failed partition won't fit
Ukrainian
Offline
Are there errors in smartctl -a for this disk or read errors / filesystem errors reported in dmesg?
If the disk is faulty, then ddrescue is your only hope. Also make sure to disable fstrim.timer and all other forms of trim/discard when dealing with SSDs or loopmounting filesystem images. You don't want trim to run while the filesystem is in an undefined state.
It's fine to clone just the home LV provided LVM metadata is good; but you should backup LUKS header and LVM metadata separately, just in case those vanish too, at that point it's game over.
For recovery attempts, you can use overlays https://archive.kernel.org/oldwiki/raid … erlay_file
That way you can experiment and undo any changes without having to go back to ddrescue to make a new image.
If it's ext4 you can try your luck with debugfs too, sometimes that allows you to access files where mounting fails.
Last edited by frostschutz (2026-05-09 15:48:57)
Offline
smartctl -a says
Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Input/output errorBut with GUI I can find such smart
=== START OF INFORMATION SECTION ===
Model Number: SKHynix_HFS001TEJ4X112N
Serial Number: 5YC8N044114108V01
Firmware Version: 51030C31
PCI Vendor/Subsystem ID: 0x1c5c
IEEE OUI Identifier: 0xace42e
Controller ID: 1
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1,024,209,543,168 [1.02 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: ace42e 003ad1d26e
Local Time is: Sat May 9 17:55:18 2026 EEST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 86 Celsius
Critical Comp. Temp. Threshold: 87 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 4.5000W - - 0 0 0 0 100 100
1 + 3.0000W - - 1 1 1 1 200 200
2 + 0.6000W - - 2 2 2 2 400 400
3 - 0.0150W - - 3 3 3 3 2000 2000
4 - 0.0030W - - 4 4 4 4 5000 10000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- media has been placed in read only mode
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x08
Temperature: 31 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 1%
Data Units Read: 8,053,232 [4.12 TB]
Data Units Written: 43,646,599 [22.3 TB]
Host Read Commands: 126,263,331
Host Write Commands: 733,458,278
Controller Busy Time: 12,077
Power Cycles: 8,029
Power On Hours: 8,500
Unsafe Shutdowns: 169
Media and Data Integrity Errors: 1,839
Error Information Log Entries: 16
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 35 Celsius
Temperature Sensor 2: 31 Celsius
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed without error 8420 - - - - -
1 Short Completed without error 8419 - - - - -
2 Short Completed without error 3668 - - - - -Last edited by webcapcha (2026-05-09 15:57:32)
Ukrainian
Offline
Either ddrescue (best option, if you have the space) or create overlay on that SSD directly (risky option, might work if reads are still reliable regardless) and hope that makes it mountable after fsck.
Good luck...
Offline