Question

3

Recover partition after GParted resizing interrupted by unexpected shutdown

rated 0 times [ 3] [ 0] / answers: 1 / hits: 7410 / 1 Year ago, sat, january 7, 2023, 12:48:17

As I was resizing my partitions using GParted, my laptop battery ran out, and the process was interrupted.

Now, I am unable to mount the partition which I was trying to resize. I get the following error when I click to mount the partition on nautilus:

Error mounting:

mount: wrong fs type, bad option, bad superblock on /dev/sda3,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

How can I go about recovering my data? Is there a safe way to attempt to force-mount the partition in question? Any help towards recovering my data is sincerely appreciated.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

oileweaty

Add To Favorites

Follow

Total Points: 337

Total Questions: 108

Total Answers: 105

Location: Western Sahara

Member since Mon, May 3, 2021

3 Years ago

oileweaty questions

1 How to check if preload is running or not?

Thu, Jul 1, 21, 01:57, 3 Years ago

1 What does "LMA" stand for?

Wed, Nov 24, 21, 11:48, 2 Years ago

1 Intel AX200 Wifi card abruptly stopped working on Dual Boot system with Ubuntu 20.04 and Windows 10

Mon, Jun 13, 22, 04:01, 2 Years ago

1 How to change/remove the file extensions of a group of files

Sat, Dec 24, 22, 16:51, 1 Year ago

1 Screen snip (win+shift+s) alternative for Ubuntu

Sat, May 14, 22, 00:50, 2 Years ago

View All

answered 1 Year ago zombieptu · Accepted Answer

Some months ago, @psusi said:
"Your data is pretty much toast. At this point you need to restore from backup..."

I didn't believe it. My computer has only about 4GB of RAM, and the partition being moved was around 350GB. If we assume that the "move partition" operation of GParted is correct, 4GB should be a limit on the amount of data that could have been lost. (Otherwise, the "move partition" operation likely could not complete without loss of data).

Indeed, I was able to recover my directory tree, albeit a bit shuffled (since the move operation had been interrupted, a strange directory configuration resulted, where about half of my home directory was inside one folder).

The answer was testdisk, which was able to detect the filesystem in question. After this was detected, I copied the files onto an external HD. This learning experience has brought me closer to enlightenment via http://www.taobackup.com/.