fsck utility on the affected partition to repair the journal and fix structural errors. If the filesystem is ext4, this process often restores integrity without data loss.
Immediate Safety Steps
The moment you encounter a "Disk Read Error" in GParted, stop all operations immediately. Do not attempt to click "Apply" again, as this can cascade corruption into adjacent partitions or the Master Boot Record (MBR). The power outage likely interrupted a write operation, leaving the filesystem in an inconsistent state where the superblock or inode tables do not match the actual data on the disk.
First, shut down the computer completely and wait for at least 30 seconds before powering it back on. This allows capacitors to discharge and ensures that any lingering electrical faults are cleared. When you restart, do not try to access the desktop environment where GParted resides if the system feels unstable. Instead, prepare to boot from a USB stick or installation media. This isolates the problematic drive from the running operating system, preventing further writes that could overwrite recovering data.
Booting into a Live Environment
You need a clean environment to diagnose the issue because the host OS may have locked the partition or cached corrupted metadata. Insert your Ubuntu, Fedora, or other Linux live USB drive and boot from it. During the boot menu, select "Try Ubuntu" or equivalent to load the OS entirely into RAM without mounting the internal hard drives permanently. Once the desktop loads, open a terminal window. You will need root privileges to perform low-level repairs, so prefix your commands with sudo.
Identify the affected partition using the lsblk command. Look for the partition size and label that matches the one you were trying to resize. It might appear as sda1, nvme0n1p2, or similar. Write this identifier down carefully. Using the wrong device name during repair can destroy data on a different partition. If you are unsure which partition is which, check the sizes displayed by lsblk against your known partition layout.
Running Filesystem Checks
The core of the solution lies in using the fsck (filesystem check) tool. For ext4 partitions, which are standard on most Linux systems, the command is sudo fsck -f /dev/sdXN, replacing /dev/sdXN with your specific partition identifier. The -f flag forces a check even if the filesystem appears clean, which is crucial after a crash. The tool will scan the superblock, inode tables, and directory structures for inconsistencies.
If the filesystem is NTFS or exFAT, use ntfsfix or fsck.vfat respectively. However, GParted primarily manipulates Linux-native formats, so ext4 is the most likely candidate. During the process, fsck will ask questions about how to handle discrepancies. Generally, answering "yes" to all prompts is safe for repairing structural damage, as these tools prioritize filesystem integrity over individual file recovery in the initial pass. If the tool reports "Filesystem was modified," it means it successfully fixed errors. Reboot the system and try accessing the files normally.
Re-attempting the Resize Operation
Once the filesystem is healthy, you can return to GParted. However, do not simply resume the previous operation. The previous move/resize task may have left partial changes that are now invisible or conflicting. Open GParted and refresh the view. Check if the partition table shows unallocated space or misaligned boundaries. If the partition looks correct but you still need to adjust its size, apply the change again. Ensure that no other processes are accessing the disk during this phase.
If the error persists despite successful fsck runs, the issue might be deeper, involving the partition table itself rather than just the filesystem contents. In such cases, refer to our guide on GParted Won't Let You Extend Partition? Here's How to Fix It for advanced partition table corrections. Always create a backup of critical data before attempting further structural changes, as partition manipulation carries inherent risks.
Preventing Future Power Outage Damage
To mitigate future risks, consider enabling periodic filesystem checks via cron jobs if the system is a server. For desktop users, ensure that large operations like resizing are scheduled when stable power is guaranteed. Using an Uninterruptible Power Supply (UPS) can provide enough time to save work and shut down gracefully during brief outages. Additionally, always verify that your BIOS/UEFI settings allow for proper shutdown signals, preventing abrupt power cuts that leave disks in a half-written state.
If you are dealing with dual-boot setups, remember that Windows partitions (NTFS) require careful handling. A failed resize can break the bootloader chain. For related issues regarding boot failures after partition changes, see Resolving Boot Device Not Found Issue After Deleting Windows Partition with GParted. Regular backups remain the only true insurance against catastrophic data loss from hardware failures or software errors.
Frequently Asked Questions
Can I recover data if fsck fails?
If fsck cannot repair the filesystem, do not attempt further repairs as they may overwrite recoverable data. Use specialized data recovery tools like TestDisk or PhotoRec to extract files from the raw disk sectors before formatting or reinstalling the system.
Is a disk read error always caused by a bad sector?
No, it is frequently caused by logical corruption due to unsaved writes during a crash. Physical bad sectors usually present as persistent I/O errors across multiple applications, whereas GParted errors often resolve after a filesystem check.
Should I use GParted on a mounted partition?
Never modify a mounted partition. Always unmount it first or boot from a live USB. Modifying active partitions leads to immediate data corruption and unpredictable system behavior.
What if my partition is NTFS?
GParted can resize NTFS partitions, but power outages often corrupt the NTFS journal. Use ntfsfix from a Linux live environment to clear the dirty flag and repair basic inconsistencies before retrying the resize.
How do I check if my hard drive is physically failing?
Run SMART diagnostics using the smartctl command from the smartmontools package. Look for reallocated sector counts or pending errors, which indicate physical degradation requiring drive replacement.