On Fri, Sep 16, 2011 at 09:50:36PM -0400, Ken Jones wrote:
> [root@pacman graphics]# tail /var/log/dmesg
> md: autorun ...
> md: ... autorun DONE.
> EXT3 FS on dm-0, internal journal
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on hdb1, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> SELinux: initialized (dev hdb1, type ext3), uses xattr
> SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
> Adding 524280k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1
> across:524280k
> SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses
> genfs_contexts
> [root@pacman graphics]#
>
> -----------------------
> I have no idea what dmesg is talking about. The data seems to
> match the 'mount' statement and yesterday's date, Sept 15th.
Yes, but was does "dmesg | grep hdb" say? That will search the entire
dmesg output for anything related to hdb, rather than just showing the
last 10 lines of dmesg which you posted above. dmesg shows all
"recent" kernel log messages. They may also be in /var/log/messages,
so you can show that too:
grep hdb /var/log/messages
Another thing to try is a S.M.A.R.T. test on the hard drive:
Install the package:
yum install smartmontools
Post this output:
smartctl -a /dev/hdb
smartctl -l selftest /dev/hdb
Perform a short test:
smartctl -t short /dev/hdb
(wait until short test is completed--it will say on the screen when
that will be)
Show test results again:
smartctl -l selftest /dev/hdb