GNOME Bugzilla – Bug 609097
Error while moving unmounted ext4 partition (ex. /boot) on running system
Last modified: 2010-02-05 19:58:28 UTC
Created attachment 153088 [details] gparted details System: Xubuntu 9.10 Kernel: 2.6.31-18-generic Partition type: GPT GParted 0.4.5 Libparted 1.8.8.1.159-1e0e Was: sda2 bios-grub sda3 swap sda4 ext4 /boot sda5 ext4 / sda6 ext4 /home empty sda1 ext4 (media) I made swapoff. I shrank swap 1.12 -> 1 GiB. Success by moving the end. I made swapon. I made unmount of /boot. I tried to enlarge boot using emptied space by moving start. And receive error (report attached). Now sda4 (/boot) not available.
Thank you Denis for your interest in GParted. From the attachment you provided I translated the following libparted message: "The kernel was unable to read information about the changes in section / dev/sda4 - Device or resource busy. This means that you made changes to / dev/sda4 is not available for Linux to reboot - that is, you should not install or use it in other ways to reboot." This is a known problem that occurs when using GParted (<= 0.5.1) and Parted with newer GNU/Linux kernels (2.6.31+) and udev(138+). See bug #604298 for more details. The most commonly reported problem has been when resizing NTFS file systems. If you do not have a backup of your data, you could try using PhotoRec to recover your data. http://www.cgsecurity.org/wiki/PhotoRec GParted 0.5.1 contains a work around to reduce the chance of this problem problem occurring. GParted 0.5.1 is available on GParted Live 0.5.1-1 (CD/USB). We highly recommend that you make a backup of all your important data before editing partitions. Would you be able to try out GParted 0.5.1? If not then I will mark this report as a duplicate of bug #604298.
Thanks a lot Curtis for such a quick answer! A have already solved the problem: partition wasn't damaged just not accessible, so I reinstalled GRUB using LiveCD. Unfortunately Ubuntu repository contains such an old GParted version, so I can't try new one. Thanks again for good tool, Denis
*** This bug has been marked as a duplicate of bug 604298 ***