#[SOLVED] Shrank a partition overnight and woke up to an error effecting the whole hard drive.

43 messages · Page 1 of 1 (latest)

peak scarab
#

I have a 2.7 TiB HDD I was originally using for my media library that I wanted to also use to host my programming work so I can access it from two different linux installs on the same machine. Using KDE Partition Manager I edited my partitions to shrink the existing media library and it was taking a long time (half an hour for a couple percentage points) so I let it run overnight, Coming home from work the next day I see that KDE Partition manager has thrown an error while attempting to shrink the disk after working for 7 hours and the two partitions exist on the drive but they're now both unmouunted and of an unknown filesystem type, presumably making my data lost. What happened that caused an error this bad? is my data recoverable? Generally at a loss here, thanks a lot in advance.

wild storm
#

yeah KDE Partition Manager sucks at erroring out gracefully

#

Broke my NTFS partition once

peak scarab
#

oh! okay

peak scarab
wild storm
#

GParted

#

It's a GUI for parted

#

It's I think GTK based so it looks off place but it works

#

And can reliably resize NTFS and such

#

Ok but to fix this damage

#

What filesystem was the drive on before you shrunk it?

peak scarab
turbid sky
peak scarab
# turbid sky Can you run the following command (which will list all your block devices) and e... 
NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                           
└─sda1                                                                        
sdb                                                                           
├─sdb1                                                                        
└─sdb2 ntfs               DCB60DE4B60DBFCE                                    
sdc                                                                           
├─sdc1 vfat   FAT32 BOOT  D4EA-E688                             273.6M     9% /boot/efi
├─sdc2 swap   1     Swap  6097bff4-8e3b-4067-a349-ce740dc18297                [SWAP]
├─sdc3 ext4   1.0         930ec6b6-1e89-48db-9f22-329442d3201b     40G    51% /
└─sdc4 ext4   1.0         20f71f3e-7608-4f22-8e07-1ddaae117e74       0    95% /home
sr0
#

A friend helped me poke around a lot with the dedicated btrfs tools and unfortunately the only thing that's worked so far is using a utility like testdisk to manually recover files

turbid sky
peak scarab
#

Sda/sda1

#

Btrfs

turbid sky
peak scarab
#

This happened overnight last night I imagine around 7 in the morning today was when it finished

turbid sky
peak scarab
turbid sky
peak scarab
#

midnight between 7/22/23 and 7/23/23 EST

turbid sky
peak scarab
#

No idea

turbid sky
# peak scarab No idea

This is after

Jul 22 23:37:25 quinndeavorOS partitionmanager[46444]: "Partition ‘/dev/sda1’ has the same position and size after resize/move. Ignoring operation.
and
Jul 22 23:45:47 quinndeavorOS partitionmanager[46444]: "Applying operations..."

peak scarab
#

Interesting. I unfortunately ended up doing my repartitions did some chmod stuff and got myself into emergency mode

turbid sky
peak scarab
#

Ahh okay. Any particular reason why kde would crash like that?

turbid sky
#

Next, you may want to consider backing up before this type of operation.

#

And run the commands in a tty instead of relying on the kde partition manager if kwin is unstable.

peak scarab
#

I got it it was very silly

#

thought I made a drive btrfs but I forgot and actually made it ext4

wild storm
#

If you really need your data PhotoRec might be the only way

#

It's pretty good at reading absolutely obliterated filesystems

peak scarab
hidden laurelBOT
#

smu1zel received a thank you cookie!

peak scarab
#

[SOLVED] Shrank a partition overnight and woke up to an error effecting the whole hard drive.

#

marking this as solved

wild storm