Ask Your Question

fedora 22 resize or overheat fail

asked 2015-09-01 13:40:37 -0500

brandonabandon gravatar image

updated 2015-10-17 22:33:23 -0500

mether gravatar image

Hello community. I installed f22 recently, arranged the system to my liking, and downloaded 40+ GB of code when irealized my disk was nrly full. My disk is 120. Half of the disk was root, so I did a -35 resize with lvresize. Soon after, my laptop overheated due to excessive use. A while later when I power on, I'm prompted emergency I booted an Ubuntu live disc and did this `ubuntu@ubuntu:~$ sudo fsck /dev/mapper/fedora-root fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) Error reading block 6324224 (Invalid argument). Ignore error<y>? no /dev/mapper/fedora-root: Invalid argument while reading block 6324224

/dev/mapper/fedora-root: Invalid argument reading journal superblock

fsck.ext4: Invalid argument while checking ext3 journal for /dev/mapper/fedora-root

/dev/mapper/fedora-root: ** WARNING: Filesystem still has errors **

ubuntu@ubuntu:~$ sudo fsck /dev/mapper/fedora-root fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) Error reading block 6324224 (Invalid argument). Ignore error<y>? yes Force rewrite<y>? yes Superblock has an invalid journal (inode 8). Clear<y>? yes * ext3 journal has been deleted - filesystem is now ext2 only *

Superblock has_journal flag is clear, but a journal inode is present. Clear<y>? yes The filesystem size (according to the superblock) is 13107200 blocks The physical size of the device is 3932160 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes Error writing block 6324224 (Invalid argument). Ignore error<y>? yes

/dev/mapper/fedora-root: FILE SYSTEM WAS MODIFIED

` This appears to not have helped me rebooting into fedora, if its of any help, in Ubuntu live, the /dev/mapper/fedora-root partition is unable to mount, however it appears as a partition on file wiindow side panel. I am a complete noob at fedora, 2 days exp. But a few years Ubuntu exp. Any ideas how to fix this issue?

edit retag flag offensive close merge delete



I'm speculating that you did an lvm resize without the --resizefs option, and either missed the filesystem resize or miscalculated the boundaries. Glad you found a solution.

randomuser gravatar imagerandomuser ( 2015-09-04 08:27:27 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2015-09-01 17:27:47 -0500

brandonabandon gravatar image

updated 2015-09-04 04:55:46 -0500

Goteem. I just did a resize with lvextend to the original size with an Ubuntu livecd. Its amazing how hours of research, prove no results. I also had to copy cat /proc/mounts to /dev/etc/fstab. i noticed the fstab.empty file during the fiasco. now to figure out how to properly resize.

Edit. I followed @hammis guide to resize with livecd, rebooted, and installed system-config-lvm. I should research more when modifying the system, as the original guide I followed, didn't include booting livecd or the e2fsck command. Like trying to take off yer shoes without lifting yer feet off the ground

Edit. This guide was helpful for resizing home partition. Since I resized my root partition more small than I should.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2015-09-01 13:40:37 -0500

Seen: 298 times

Last updated: Sep 04 '15