Help i cant access a partition

Ask Fedora
,
1

just installed fedora. came from mint. i had / , /home , and /media/samir/files, in the same order. most of my data was on files. i was trying to move every thing in files to /home. but i had no space to do it in one time so moved some . then booted from fedora bootable stick. to take some space from /files and add it to /home. i shrank /files. and started moving it to the end of the drive.The partition im talking about is /files (with one s) . i got this error:
kde partition manager:

Move partition ‘/dev/nvme0n1p4’ to the right by 21.60 GiB 
Job: Check file system on partition ‘/dev/nvme0n1p4’ 
Command: e2fsck -f -y -v /dev/nvme0n1p4 
Check file system on partition ‘/dev/nvme0n1p4’: Error

Checking partition ‘/dev/nvme0n1p4’ before resize/move failed. 

Move partition ‘/dev/nvme0n1p4’ to the right by 21.60 GiB: Error

gparted details file:

GParted 1.7.0

configuration --enable-libparted-dmraid

libparted 3.6

========================================

Device:	/dev/nvme0n1
Model:	KBG50ZNV512G KIOXIA
Serial:	241PH21RQH5U
Sector size:	512
Total sectors:	1000215216
 
Heads:	255
Sectors/track:	2
Cylinders:	1961206
 
Partition table:	gpt
 
Partition	Type	Start	End	Flags	Partition Name	File System	Label	Mount Point
/dev/nvme0n1p1	Primary	2048	999423	boot, esp	EFI System Partition	fat32		/boot/efi
/dev/nvme0n1p2	Primary	999424	52199423			ext4	root	/
/dev/nvme0n1p3	Primary	52199424	533481471			ext4	home	/home
/dev/nvme0n1p4	Primary	533481472	676708351			ext4	files	/media/samir/files
/dev/nvme0n1p5	Primary	721999872	1000214527			ext4	filess	/run/media/samir/filess
========================================

Device:	/dev/sda
Model:	WD My Passport 2627
Serial:	WD-WX72DA31MFKJ
Sector size:	512
Total sectors:	9767475200
 
Heads:	255
Sectors/track:	2
Cylinders:	19151912
 
Partition table:	gpt
 
Partition	Type	Start	End	Flags	Partition Name	File System	Label	Mount Point
/dev/sda1	Primary	34	262177	msftres	Microsoft reserved partition	unknown		
/dev/sda2	Primary	264192	9767475166	msftdata	Basic data partition	ntfs	Schwanz	/run/media/samir/Schwanz
========================================

Device:	/dev/sdb
Model:	Lexar USB Flash Drive
Serial:	5694259443265439
Sector size:	512
Total sectors:	60653760
 
Heads:	255
Sectors/track:	2
Cylinders:	118928
 
Partition table:	msdos
 
Partition	Type	Start	End	Flags	Partition Name	File System	Label	Mount Point
/dev/sdb1	Primary	2048	60588223	boot		exfat	Ventoy	/run/media/samir/Ventoy
/dev/sdb2	Primary	60588224	60653759	esp		fat16	VTOYEFI	
========================================

Move /dev/nvme0n1p4 to the right  00:00:00    ( ERROR )
    	
calibrate /dev/nvme0n1p4  00:00:00    ( SUCCESS )
    	
path: /dev/nvme0n1p4 (partition)
start: 533481472
end: 676708351
size: 143226880 (68.30 GiB)
check file system on /dev/nvme0n1p4 for errors and (if possible) fix them  00:00:00    ( ERROR )
    	
e2fsck -f -y -v -C 0 '/dev/nvme0n1p4'  00:00:00    ( ERROR )
    	
Error reading block 47742975 (Invalid argument). Ignore error? yes

Force rewrite? yes

Superblock has an invalid journal (inode 8).
Clear? yes

*** journal has been deleted ***

The filesystem size (according to the superblock) is 58341632 blocks
The physical size of the device is 17903360 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes

Error writing block 47742975 (Invalid argument). Ignore error? yes


files: ***** FILE SYSTEM WAS MODIFIED *****
e2fsck 1.47.2 (1-Jan-2025)

im pretty sure i didnt encrypt the parition or formate or anything like that.
i tried booting normally and trying partitioning from there the same thing.
i need the files on the partition. is there a way to get them back?

2

You cannot shrink the partition before you shrink the filesystem. You might be able to recover your files by restoring your partition to its original boundries.

3

I can’t resize or move the partition bc of this error Checking partition ‘/dev/nvme0n1p4’ before resize/move failed. Besides. what do you mean with

You cannot shrink the partition before you shrink the filesystem.

i did shrink partitions the same way i did before

4

Partitions and filesystems are two different things. Some tools might change one without changing the other. If you used one of those tools, that could have corrupted your filesystem.

You’ll need to run e2fsck to get more details about what is wrong with your filesystem.

5 
samir@samirsvictus:~$ sudo e2fsck  /dev/nvme0n1p4
e2fsck 1.47.2 (1-Jan-2025)
Error reading block 47742975 (Invalid argument).  Ignore error<y>? yes
Force rewrite<y>? yes
Superblock has an invalid journal (inode 8).
Clear<y>? yes
*** journal has been deleted ***

The filesystem size (according to the superblock) is 58341632 blocks
The physical size of the device is 17903360 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes
Error writing block 47742975 (Invalid argument).  Ignore error<y>? yes

files: ***** FILE SYSTEM WAS MODIFIED *****

what about this?

6 
Grow partition ‘/dev/nvme0n1p4’ from 68.30 GiB to 68.31 GiB 
Job: Check file system on partition ‘/dev/nvme0n1p4’ 
Command: e2fsck -f -y -v /dev/nvme0n1p4 
Check file system on partition ‘/dev/nvme0n1p4’: Error

Checking partition ‘/dev/nvme0n1p4’ before resize/move failed. 

Grow partition ‘/dev/nvme0n1p4’ from 68.30 GiB to 68.31 GiB: Error

here i tried resizing it using kde partition manager.

7

That error indicates that your filesystem is over three times larger than the partition. The error is confusing though because it states that the partition is 17903360 blocks, but the info printed earlier shows size: 143226880. I don’t know how to recover from this error. If power or connectivity was lost while the resize operation was ongoing, it might not be possible to fix the corruption.