On Sun, Apr 11, 2010 at 3:00 PM, Geoff Galitz <geoff@xxxxxxxxxx> wrote:
>
>
> Check dmesg. The kernel may be reporting disk or filesystem IO problems
> that are not going to syslog.
>
> -geoff
>
>
>
> ---------------------------------
>
Thanx Geoff,
Already checked that, without any decent lead either:
[root@intranet ~]# tail -f /var/log/dmesg
md: ... autorun DONE.
device-mapper: multipath: version 1.0.5 loaded
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 8388600k swap on /dev/nas/swap. Priority:-1 extents:1 across:8388600k
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 304 bytes per conntrack
device vif0.0 entered promiscuous mode
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
r8169: peth0: link up
device peth0 entered promiscuous mode
xenbr0: topology change detected, propagating
xenbr0: port 2(peth0) entering forwarding state
virbr0: no IPv6 routers present
r8169: eth1: link up
eth0: no IPv6 routers present
eth1: no IPv6 routers present
fuse init (API version 7.10)
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwidth (but not more than
200000 KB/sec) for reconstruction.
md: using 128k window, over a total of 104320 blocks.
md: syncing RAID array md2
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwidth (but not more than
200000 KB/sec) for reconstruction.
md: using 128k window, over a total of 244195904 blocks.
md: md2: sync done.
RAID1 conf printout:
--- wd:1 rd:2
disk 1, wo:0, o:1, dev:sda1
md: md0: sync done.
RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:hda1
disk 1, wo:0, o:1, dev:hdb1
usb 1-1: new high speed USB device using ehci_hcd and address 3
usb 1-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
Vendor: Kingston Model: DT Mini Slim Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdc: 31506432 512-byte hdwr sectors (16131 MB)
sdc: Write Protect is off
sdc: Mode Sense: 23 00 00 00
sdc: assuming drive cache: write through
SCSI device sdc: 31506432 512-byte hdwr sectors (16131 MB)
sdc: Write Protect is off
sdc: Mode Sense: 23 00 00 00
sdc: assuming drive cache: write through
sdc: sdc1
sd 3:0:0:0: Attached scsi removable disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
SCSI device sdc: 31506432 512-byte hdwr sectors (16131 MB)
sdc: Write Protect is off
sdc: Mode Sense: 23 00 00 00
sdc: assuming drive cache: write through
sdc:
SCSI device sdc: 31506432 512-byte hdwr sectors (16131 MB)
sdc: Write Protect is off
sdc: Mode Sense: 23 00 00 00
sdc: assuming drive cache: write through
sdc:
/dev/sdc is a faulty USB memory stick,which I just put in before
posting this, hence the errors. But this has happened before I put it
in even.
--
Kind Regards
Rudi Ahlers
SoftDux
Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
