File system is NOT clean. Error mounting volume

eliassal · 10-24-2010, 02:09 PM

I have 2 hard drives on mu box
1st one is 500.0 MB ext4 Volume where I have my syste FC 13
and a 2nd one where I put my database files as follows
78.1 GB ext4 Volume usage = filesystem, format ext4

ih file browser, I can see an icon for a 80GB hard drive but whenever I double click I get the following

Quote:

Error mounting volume
An error occured while performing an operation on data Partition 1 of ATA Maxtor <: <the operation failed

clicking details

Quote:

Error mounting: mount exited with exit code 1: helper failed with:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

when I type

Quote:

dmesg | tail

I get

Quote:

# dmesg | tail
[drm] nouveau 0000:01:00.0: Allocating FIFO number 3
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 3
[drm] nouveau 0000:01:00.0: Allocating FIFO number 4
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
EXT4-fs (sda1): ext4_check_descriptors: Checksum for group 343 failed (14677!=8565)
EXT4-fs (sda1): group descriptors corrupted!
EXT4-fs (sda1): ext4_check_descriptors: Checksum for group 343 failed (14677!=8565)
EXT4-fs (sda1): group descriptors corrupted!
EXT4-fs (sda1): ext4_check_descriptors: Checksum for group 343 failed (14677!=8565)
EXT4-fs (sda1): group descriptors corrupted!

What is very strange is that mysql works fine.
In disk utility, it indicates that disk is healthy, but when I click check file system i get

File system check on "data" (Partition 1 of ATA MAXTOR STM380215A) completed
File system is NOT clean

honeybadger · 10-24-2010, 02:52 PM

Hi there,
Check the man page for shutdown. I think you have to run 'shutdown -r -F now' and fdisk will start. However this is possible if the mount point is in fstab.
Another thing you can do is unmount the drive (if you can) and run fdisk directly on it.
Honestly I prefer the first option. Always worked for me.
Hope this helps.

ozegoods · 10-24-2010, 03:02 PM

What is the output from running "fdisk -ul" as root?

What does your "/etc/fstab" file look like?

Have you tried using e2fsck on the potentially unclean file system?

eliassal · 10-24-2010, 03:46 PM

Thanks for your responses, Here is the output of
fdisk -ul /dev/sda

Quote:

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001a024

Device Boot Start End Blocks Id System
/dev/sda1 63 156296384 78148161 83 Linux

and the fstab is as follows

Quote:

#
# /etc/fstab
# Created by anaconda on Wed Jun 16 00:58:19 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=ae72b7f7-2a24-4797-9be6-dd079a3e713a / ext4 defaults 1 1
UUID=bd2e2fe1-9c09-4804-916f-8e8cadd20550 /boot ext4 defaults 1 2
UUID=28bbcfcb-b69d-48fc-9356-1d7af846b828 swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/sda1 /media/sda1 ext4 users 0 0

eliassal · 10-24-2010, 03:51 PM

I ran
e2fsck -n /dev/sda
here is the output

Quote:

e2fsck 1.41.10 (10-Feb-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

My disk is ext4 and not ext2, so how should I run it
Thanks in advance

ozegoods · 10-24-2010, 04:13 PM

First run "mount" or "df" to make sure that /dev/sda1 is not mounted. Then use "e2fsck -v /dev/sda1" to check the ext4 file system. If it seems clean you add the f option to force checking:

Code:

e2fsck -vf /dev/sda1

eliassal · 10-24-2010, 04:41 PM

I ran the 1st one, it asked me
One or more block group descriptor checksums are invalid. Fix<y>? yes
respondes by yes and ended by several other requests like this and funally

Quote:

Free inodes count wrong for group #1 (0, counted=8192).
Fix<y>? yes

Free inodes count wrong for group #343 (0, counted=8192).
Fix<y>? yes

Free inodes count wrong (4874153, counted=4890537).
Fix<y>? yes

data: ***** FILE SYSTEM WAS MODIFIED *****

87 inodes used (0.00%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 77
355764 blocks used (1.82%)
0 bad blocks
1 large file

72 regular files
6 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
78 files

So many thanks

eliassal · 10-24-2010, 04:45 PM

by the way are other users have the right to see the contents of this device
I log with my user and I want to have all privileges as well on the device

eliassal · 10-24-2010, 05:35 PM

ozegoods, I rebooted, and mysql does not start any more
I get

Quote:

[root@salamlinux ~]# service mysqld start
MySQL Daemon failed to start.
Starting mysqld:

IN the log file I have

Quote:

/usr/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
101025 0:21:53 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
101025 0:21:53 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.
101025 00:21:53 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

This resides on the disk that was fixed

Any idea what might went wrong

ozegoods · 10-24-2010, 06:04 PM

Well, the message says; "The error means mysqld does not have the access rights to the directory."

Access to files and directories is restricted according to permissions set with chmod and ownership set with chown, however I have never known e2fsck to change permissions or ownership.

H_TeXMeX_H · 10-25-2010, 04:03 AM

You haven't really provided any background info. Did the computer crash before this happened ?

I am not convinced that the drive is in good working order, I would run some low-level tests or at least a SMART long test, and badblocks.

eliassal · 10-25-2010, 03:05 PM

Yes ozegoods, all db storage has root as owber abd user after I ran e2fsck, I chnqged it manually and mysql came back to life