Ubuntu :: Gparted Frozen - Stuck On The "shrink File System...resize2fs"
Feb 8, 2011
I'm trying to use GParted from a liveusb to resize my ext4 Ubuntu partition, but it's been stuck on the "shrink file system...resize2fs" for two days straight. The progress bar is still going back and forth, and top shows a lot of CPU activity, but it won't move past this point. I know it's a bad idea to stop GParted while it's resizing, what I can do, maybe a way to check to see if it's actually busy resizing the partition?
I needed to shrink a filesystem so I could take a drive out of a RAID5 array. I unmounted the fs, then ran e2fsck on it and it found 5.9% non contiguous files but no errors. Then I ran resize2fs -f /dev/whatever 1300G (initial size was 2500G, used space was at this time only 1136G). It started operating and after some hours I received a lot of messages on the output as mdadm started resync in the background. Now the resync is done but nothing moves. Here is the output I received in the terminal window where resize2fs was ran :
Code:
computer:/# e2fsck /dev/stold/storold e2fsck 1.41.3 (12-Oct-2008) /dev/st/stor a �t� mont� 68 fois sans avoir �t� v�rifi�, v�rification forc�e. Passe*1*: v�rification des i-noeuds, des blocs et des tailles
[code]....
I understand that it doesn't do nothing anymore, as it doesn't consume any CPU cycles anymore. What can I do now ? It's running near 24 hours now ! How can I try to escape from this situation without loosing all data ?
I have a machine running Arch Linux (2010, I believe) with a 6TB RAID-5 array hooked up to a Highpoint RocketRaid 2320. I've been having issues with the RAID controller's drivers and the latest Linux kernels thanks to the driver not being open-source, and as a result I am migrating the system to Windows Server.Problem is that the 6TB disk originally was comprised only of an ext4 partition.I shrunk the partition down as much as I could, and added a NTFS partition in the empty space so I could start moving files. That went fine. Problem is that now I need to shrink the ext4 partition again, move files, shrink again, etc. The second run through resize2fs is taking way longer than the first pass.It seems to be getting stuck at pass 3:
[root@nar-shaddaa rc.d]# resize2fs -p /dev/sdb3 863000000 resize2fs 1.41.14 (22-Dec-2010) Resizing the filesystem on /dev/sdb3 to 863000000 (4k) blocks.
I've been trying to use GParted Live CD to shrink my Windows XP partition and allocate this space to /home.
On GParted I shrank my /dev/sda1 (Windows) from 36GB to 26 GB. Then I had 10 GB of unallocated space. I didn't know how I could use this unallocated space to increase the size of /dev/sda7 (/home). How do you do this?
I removed my Ubuntu 10.04 partition from my hard disk with GParted because it didn't install properly and there were no solutions available. After I removed it, I set it up to extend my Vista partition into the unallocated space. It's been going for three hours so far (which I expected) but the progress bar is now stuck. The timer's stopped and everything; it's not increasing infinitely like when your internet cuts out when downloading something, it's just stopped. Here's a screenshot:[URL]..
I know to resist the allure of the Cancel button, but I don't really know what to do here. It's been sitting here for about half an hour with no sign of budging.
I have GParted installed, running openSUSE 11.3 with GNOME. When running GParted, it always grayed out most file system actions, supporting only hfs fully. This made no sense, as I had all the required packages installed for other file system support. However, I recently figured out how to get it to work. Using the installed menu button doesn't work, running "gnomesu /usr/sbin/gparted" doesn't work; to get it to work, I have to open up a terminal, type "su -" to log in as root, and then run gparted. The menu button and gnomesu both prompt for a password, so it should be running as root, but launching it through the root terminal is the only way to actually get it to work. Is one root different from another?
I was in the process of installing Ubuntu 11.10, but got stuck choosing which file system to use. ext3 and ext4; which is better for a personal desktop? If ext4 is better, will it work well on my old PC (bought 3 years ago), or perhaps ext4 is not actually compatible with an old hard disk?
I need to install Fedora on 4GB SDHC card, so the space is limited.My question is what files (documents, manuals, temporary files, logs, unused packages etc) I can remove, without harming the system?So far I cleaned /tmp, /var/log, trash what else?
I have ubuntu 10.10 in my pc, and when we try to boot, it gets frozen. In the terminal it says: [ 30.14682] [<ffffffff810121b2>] ? system_call_fastpath+0x1610b16 What does that mean?
I am reinstalling ubuntu mavericks as I could not get the first install to work right. I installed from a CD that I burned. 3/4 of the way through the "installing system" process the screen went dead. The cursor does not respond nor does anything happen with the keyboard. Be aware that I don't know very many things about what a keyboard can do. The screen has been frozen for about a half hour now.
In the last couple of days when I start Kontact it gets frozen on FEEDS. I have tried to start all of the applications within Kontact separately and they all start fine except for Akregator i.e. Feeds. I have been looking for a debug howto or a log file location to try diagnose where/what the problem is. Opensuse 11.2, KDE 4.3.5.
Is running fsck -f sufficient to ensure my data is OK? Heres what's happenedy system crashed during a gparted operation. I was pretty sure however, that the data was OK since given the size of the drive and the amount of data and were it was when it crashed, I figured the crash occurred while moving empty space.Bottom line is I think the data is OK, but I am wondering what else I can do to check it.When I first ran fsck after re-booting the system it said it was clean. I then did fsck -f and it found and fixed errors in phase 5 (group summary). Now when I run fsck -f I think it's clean?fsck from util-linux-ng 2.17.2e2fsck 1.41.12 (17-May-2010)
i tried to install ubuntu on my company notebook, where already xp is installed and I have to work with on monday again ;(I have to partitions 60+60GB with XP and Data. I tried to resize the Boot one to 50 to gain some space for ubuntu. Gparted rezided and moved partition (10unallocated+50boot+60data). I guess thats when the bootloader was destroyed. Now I can not start XP anymore. JaiiXXX! But i have to.
Question now is:
-Would it help to resize again with gparted so that i have 60+60 again and can start working?
-Should i continue installing ubuntu from usb. It is recognizing all partitions correctly and asking to install in dualboot. howeber i guess, when bootloader for xp is not working now, will it work after installation of ubuntu on the 10gb or will it make things more complicated?
-My tummy says first to repair windows xp an then install ubuntu. I have no xp cd since it is company computer. will repair morde work with another xp cd? i would prefer that. i saw that there is another way b reinstalling the xp by bootloader, but it sounds to complicated to me and i am little nervous now.p.s. i recognized that now data partition is flagged with boot . dont know why but put it back to the right partition, nothing changed.
I have 3 Ubuntu installations & a PCLINUXOS, plus Windows XP installed on one hard disk. I still can boot to each one of them and can mount each one using Ubuntu.
The problem "may" have occurred when I reduced the size of some linux partitions using gparted. I still have plenty of space in each of those partitions.
When I started gparted all of the HD was unallocated. I did that from each ubuntu installation and the PCLINUX installation, plus LIVECDs. All indicated the space was unallocated.
When I did an fdisk -l from a Puppy Linux LiveCD I got a normal start and ends of each partition.
When I tried it from Ubuntu installation or live cd, I received the following types of responses:
Code: ubuntu@ubuntu:~$ sudo fdisk -l /dev/sda5
Disk /dev/sda5: 28.5 GB, 28566397440 bytes 255 heads, 63 sectors/track, 3473 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System ubuntu@ubuntu:~$ sudo fdisk -u /dev/sda5
The number of cylinders for this disk is set to 3473.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Plus the Windows partition seems to go over its limits.
Since all of my OS installations are still working, I don't know how critical this is. From reading another post, I understand this might be able to be fixed by making some changes in fstab.
I'm trying to resize tmp file using gparted. So I used gparted live cd and then i resized the tmp file but delete the old /tmp partition without backup. Now, my pc do not start. I have Debian 8.
I got a really bad virus on my main computer and decided I should just install Ubuntu like I previously had installed on a laptop. Anyway, I used an old 7.10 install disk that I usually use and I upgraded from 7.10 to 8.4 LTS (that went off without a hitch), but when I upgraded from 8.4 LTS to 10.4LTS the install hung up at one point. The system was stuck 7 minutes from completion trying to set up the rsyslog. I left the dialog box up for 3 hours to no avail. I proceeded to reformat the drive to try again and it ended the same way. I currently have the system with the install dialog up and stopped at the setting up of the rsyslog. Here is a picture of the install window:
I'm currently in the process of remove a drive from an lvm. I am following this guide
[URL]
and to be honest I have also posted this question at [URL] but I have a fair amount of data at stake here and really need to make sure I'm acting safely. This is certainly not a place to button mash or guess.this is the 2nd drive that I am removing, the first one went off without a problem.However, I just received this error
Code:
resize2fs: Can't read next inode while trying to resize /dev/vg0/lvol0
and I'm not sure what it means or where to go from here. The entire output is
Code:
root@dude:/mnt# resize2fs -p /dev/vg0/lvol0 4466524456k resize2fs 1.41.4 (27-Jan-2009) Resizing the filesystem on /dev/vg0/lvol0 to 1116631114 (4k) blocks.
i m doing certification in RHCE. i have learn much more in Linux. now i m going towards LInux hardware programming.i had solved enough questions about internal working of commands that r used in Linux. bt i m not understand hows resize2fs command actually work.i kknow this command is used to shrink or extend the partion or file system.but hows that possible.wat is the internal woring of that command.
I'm somewhat a newbie at LVM and have encountered a real problem for me. During resize2fs after extending my LV i ended up with a crash. Now I'm worried I have lost all my old data. How can I proceed to get the volume in working order?
NoFear ~ # e2fsck -f /dev/vgftp/lvftp e2fsck 1.41.10 (10-Feb-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/vgftp/lvftp: 308343/505479168 files (18.3% non-contiguous), 1006593162/1010942976 blocks NoFear ~ # resize2fs /dev/vgftp/lvftp resize2fs 1.41.10 (10-Feb-2009) Resizing the filesystem on /dev/vgftp/lvftp to 1115800576 (4k) blocks. ** CRASH / HANG **
25hours waiting and nothing happens. No disk I/O going on or anything. I have no backups or anything of this volume. What can I do do revert the process to get the disks back? I have not done anything at all after the crash/hang in fear of destroying something.
I have been a happy Ubuntu user for several years. But I am stuck with version 9.10 because of a persistent problem with random lockups with both mouse and keyboard. A search on the forums both within and without the Ubuntu community shows that a lot of other people have this same problem. There have been a lot of suggestions given and I have tried everything I could find, but without success. I have tried clean installs of vs. 10.04, 10.10, and 11.04 but all have the same problem.
The computer will work fine for a few minutes to a few hours and then just lock up. The only way out is a hard reset. Someone suggested that the latest versions of Ubuntu have a problem with some of the newer Intel chipsets, but I don't know enough to be able to say one way or the other. I am running an ASUS P7P55D motherboard with a 4 core Intel i5 processor and an Nvidia graphics card. I have tried the latest version of the bios for the P7P55D but that hasn't helped either. Vs 9.10 is no longer supported and I am being left behind.
I am running Oracle Enterprise Linux x64 5.5 on an HP Proliant DL380 G6 attached to various SAN's via fibre channel. I have setup multipath, edited multipath.conf, lvm.conf, and after some trial and error, everything behaves and looks as it should in regard to multipath. However, when I try to resize a multipath ext3 lvm filesystem, The operation runs for a while, but then dies and I get the above error. I then see this error in /var/log/messages:
-I am only using the /dev/mapper/ paths to the filesystem (ie, resize2fs /dev/mapper/testvol-lvol1 128G) -if I unmount the filesystem, resize2fs works fine -Have tried removing and re-adding journal file via tune2fs with no luck -The VG has plenty of room in it and is composed of a 100GB and 200GB partition. -Inode resize is on in the filesystem
I am wondering if online resize2fs is only for small filesystems or not recommended as a best practice or just not generally done??? As I mentioned, the operation works fine offline if I unmount the filesystem, but this won't be an option once system is in production.
I have been using various operating systems on this computer. At the moment I am using AntiX Mepis. I switched to Linux because my Windows used to freeze all of a sudden after a few hourse or even minutes. Now my Linux was quite stable for a few days but again, it freezes in a few minutes when I use a Window Manager. In the terminal without using any Window Manager it never freezes. Can anyone tell me the solution to this? code...
I bought a new SD card which I intend to put some MP3s on - except that I can't write to it because it tells me the destination is Read Only. No-probs thinks I: I'll just reformat it.
"Error creating file system: helper exited with exit code 1: cannot open /dev/mmcblk0p1: Read-only file system"
Various chmod commands all result in Read-only file system. I tried umount then mount commands, but it couldn't find it to mount once I'd unmounted it using the same /media/ file path (I assume it's the only one).
I downloaded ubuntu 11.04 and did the usual shizz and it was all going well. I went to get a drink and by the time i got back my computer had completely crashed. I cant move the mouse or anything and it is stuck on 'Installing System'.
Ive restarted my computer (unplug), i had to format the harddrive i was installing it on (luckily it was empty already).
i dont know what has happened but my smplayer gets stuck when i play any kind of mkv file.. it was working file til yesterday, and today, i had to restart my computer manually 10-15 times! heres the log for smplayer :
My Redhat Enterprise Linux 4 with 6x partitions (/, /boot,/home, /usr, /var, /tmp) of 6.0 GB IDE Hardisk was working quite fine. I decided to create LVM on /home and /var partitions but due to some errors occured and I delete the /home partitions. That's why partition table altered. I then delete 4,5,and 6th partitions (/home, /var, /tmp) partitions and now try to create one by one but following error is coming:-
[Code]....
The Super block could not be read or do not describe a clear ext2 file system. E2fsck b 8193 <device> I have tried following commands,but could not successful:- e2fsck -p /dev/hda7 (where hda7 was created but afterthat it was deleted) e2fsck -a /dev/hda7
