Arch Linux

jfb3

Member

Registered: 2011-08-20

Posts: 68

EXT4-fs error on boot? [resolved, I hope]

On boot, after everything is done except the login prompt I get:

Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
Give root password for maintenance
(or type Control-D to continue)

If I "Crontol-D" and login, then "journalctl -xb" at the end is:

EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2947, 29365 clusters in bitmap, 29809 in gd; block bitmap corrupt.
Jun 03 19:30:01 Dell15z kernel: JBD2: Spotted dirty metadata buffer (dev = sda3, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
Jun 03 19:30:01 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2944, 23842 clusters in bitmap, 23846 in gd; block bitmap corrupt.
Jun 03 19:30:02 Dell15z kernel: JBD2: Spotted dirty metadata buffer (dev = sda3, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
Jun 03 19:30:26 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 3089, 16946 clusters in bitmap, 16951 in gd; block bitmap corrupt.
Jun 03 19:30:43 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2984, 22332 clusters in bitmap, 25470 in gd; block bitmap corrupt.
Jun 03 19:30:44 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2985, 24156 clusters in bitmap, 27958 in gd; block bitmap corrupt.
Jun 03 19:30:45 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2986, 29338 clusters in bitmap, 31572 in gd; block bitmap corrupt.
Jun 03 19:30:46 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2987, 18034 clusters in bitmap, 32744 in gd; block bitmap corrupt.
Jun 03 19:30:46 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2988, 24812 clusters in bitmap, 32715 in gd; block bitmap corrupt.
Jun 03 19:30:47 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2989, 17353 clusters in bitmap, 32767 in gd; block bitmap corrupt.
Jun 03 19:30:48 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2990, 31758 clusters in bitmap, 32528 in gd; block bitmap corrupt.
Jun 03 19:30:49 Dell15z kernel: EXT4-fs error (device sda3): ext4_mb_generate_buddy:756: group 2991, 32493 clusters in bitmap, 32749 in gd; block bitmap corrupt.

Does this mean my hard drive is FUBAR?   
Is there something I should run to fix this? 
The only things I can find that relate to this are bugs and patches to the kernel...

Last edited by jfb3 (2014-06-05 01:36:49)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: EXT4-fs error on boot? [resolved, I hope]

did you try fsck.ext4?

Pse

Member

Registered: 2008-03-15

Posts: 413

Re: EXT4-fs error on boot? [resolved, I hope]

If this happened after no crash or warning, I'd be taking out that drive and imaging it as soon as possible. Once you have an image in a safe place, I'd format it and run some tests on it (beginning with SMART self tests).

sekret

Member

Registered: 2013-07-22

Posts: 287

Re: EXT4-fs error on boot? [resolved, I hope]

After the kernel update to 3.14.5 I couldn't boot, because my boot device - formatted with ext2, but run by the ext4 driver - couldn't be mounted. I then used my second kernel (realtime- and obviously my backup-kernel) which went fine. The next time I tried to use the default Arch kernel the boot went smoothly as always.

So this COULD be temporary. I don't know what happened here this one time, but it's possible that it was the same you experienced.

jfb3

Member

Registered: 2011-08-20

Posts: 68

Re: EXT4-fs error on boot? [resolved, I hope]

I went ahead and fsck'd /dev/sda3 and let it do whatever it wanted.  It comes up clean and there is no "lost+found" so I guess it's ok.  I'm going to assume it got confused when it ran out of battery when suspended. (I had the flu and didn't use my laptop for a few days.) 

I'm always leery of letting fsck "fix" things because it doesn't tell you what it's fixing.  Oh, it mentions node numbers and block numbers and such but it sure would help if it associated those to file/directory names.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: EXT4-fs error on boot? [resolved, I hope]

It would probably be a good idea to use the fsck hook in your initramfs.  Either that or remove the 'rw' from the kernel command  line.  That way you'll at least get consistency checks during boot.