Problem with second hard drive.
Here's what mount has to say: [root@pacman kjones]# mount -l -t ext3 /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) /dev/hdb1 on /boot type ext3 (rw) [/boot] /dev/hdb1 on /mnt/HDB1 type ext3 (rw) [/boot] /dev/hdb2 on /mnt/HDB2 type ext3 (rw) <==== [root@pacman kjones]# --------------------------------- Here's what is in dmesg. [root@pacman graphics]# ls -l /var/log/dmesg -rw-r--r-- 1 root root 11691 Sep 15 22:26 /var/log/dmesg [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. Thanks everyone!! Ken
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
No, I'm guessing he showed the right messages. His messages had SELinux in them, which to me spells headache and heartbreak. Try flipping off SELinux: http://www.crypt.gen.nz/selinux/disable_selinux.html If that gets things working, then you need to either decide to become and SELinux expert and then post your root password on the internet like so many others, or you need to permanently disable it. Having it in permissive mode though will allow you to see what SELinux roles need what permissions in the logs for what you are doing, if you decide to go the way of heartbreak and headache. Good luck. Randall Mason * * * * On Sat, Sep 17, 2011 at 5:17 AM, Chuck Anderson <cra@wpi.edu> wrote:
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 _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
participants (3)
-
Chuck Anderson -
Ken Jones -
Randall Mason