Submitted by hatchetheavyhaul on Sat, 12/08/2012 - 21:28
I am not sure how or if there is a fix for this. I am on a 500MB internet connection . But when it gets heavy loads . The file system turns into read only I/O Error
I have changed hard drive . Still no luck so I think it in the software or the OS . Please shed some light on this for me thanks
Status:
Active
Comments
Submitted by andreychek on Sat, 12/08/2012 - 21:46 Comment #1
That does sound like a hardware problem of some sort... if you run the command "dmesg", do you see any errors towards the end of the output?
Submitted by hatchetheavyhaul on Sat, 12/08/2012 - 21:50 Comment #2
tg3 0000:02:03.0: PCI INT A -> GSI 27 (level, low) -> IRQ 27 tg3 0000:02:03.0: eth0: Tigon3 [partno(BCM95702A20) rev 1002] (PCI:66MHz:32-bit) MAC address 00:50:45:5f:6c:9e tg3 0000:02:03.0: eth0: attached PHY is 5703 (10/100/1000Base-T Ethernet) (WireS peed[1], EEE[0]) tg3 0000:02:03.0: eth0: RXcsums[0] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] tg3 0000:02:03.0: eth0: dma_rwctrl[763f0000] dma_mask[64-bit] tg3 0000:02:04.0: PCI INT A -> GSI 27 (level, low) -> IRQ 27 tg3 0000:02:04.0: eth1: Tigon3 [partno(BCM95702A20) rev 1002] (PCI:66MHz:32-bit) MAC address 00:50:45:5f:6c:9f tg3 0000:02:04.0: eth1: attached PHY is 5703 (10/100/1000Base-T Ethernet) (WireS peed[1], EEE[0]) tg3 0000:02:04.0: eth1: RXcsums[0] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] tg3 0000:02:04.0: eth1: dma_rwctrl[763f0000] dma_mask[64-bit] sd 2:0:0:0: Attached scsi generic sg0 type 0 sd 4:0:0:0: Attached scsi generic sg1 type 0 parport_pc 00:0b: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] ppdev: user-space parallel port driver EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: Adding 10289144k swap on /dev/mapper/vg_ns1-lv_swap. Priority:-1 extents:1 acro ss:10289144k NET: Registered protocol family 10 lo: Disabled Privacy Extensions tg3 0000:02:03.0: firmware: requesting tigon/tg3_tso.bin ADDRCONF(NETDEV_UP): eth0: link is not ready tg3 0000:02:04.0: firmware: requesting tigon/tg3_tso.bin ADDRCONF(NETDEV_UP): eth1: link is not ready tg3 0000:02:03.0: eth0: Link is up at 1000 Mbps, full duplex tg3 0000:02:03.0: eth0: Flow control is off for TX and off for RX ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready IPv6 over IPv4 tunneling driver sit0: Disabled Privacy Extensions sit1: Disabled Privacy Extensions powernow-k8: Found 2 Dual Core AMD Opteron(tm) Processor 280 (4 cpu cores) (vers ion 2.20.00) powernow-k8: 0 : fid 0x10 (2400 MHz), vid 0xc powernow-k8: 1 : fid 0xe (2200 MHz), vid 0xe powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x10 powernow-k8: 3 : fid 0xa (1800 MHz), vid 0x10 powernow-k8: 4 : fid 0x2 (1000 MHz), vid 0x12 powernow-k8: 0 : fid 0x10 (2400 MHz), vid 0xc powernow-k8: 1 : fid 0xe (2200 MHz), vid 0xe powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x10 powernow-k8: 3 : fid 0xa (1800 MHz), vid 0x10 powernow-k8: 4 : fid 0x2 (1000 MHz), vid 0x12 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. eth0: no IPv6 routers present icmpv6_send: no reply to icmp error UDP: bad checksum. From 189.143.104.98:34829 to 69.71.0.130:62413 ulen 111
Submitted by andreychek on Sat, 12/08/2012 - 22:04 Comment #3
Hmm, I don't see any errors in there, but that would likely be the case if your filesystem weren't currently marked as read-only.
Next time that occurs, run the command "dmesg", and see what output is listed there.
Also, you may want to see if any older "dmesg" files exist in /var/log. There may be a "dmesg.old" file in there now.
Outside of a hardware issue though, the other thing you may want to take a look at is to make sure you're running the most recent kernel available to your distro.
For CentOS 6, I believe that's "2.6.32-131.12.1". You can determine the kernel you're running with the command "uname -a".
Submitted by hatchetheavyhaul on Thu, 12/13/2012 - 17:14 Comment #4
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837596 offset 0 sd 4:0:0:0: [sdb] Unhandled error code sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 9e 01 09 50 00 00 08 00 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837596 offset 0 sd 4:0:0:0: [sdb] Unhandled error code sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 9e 01 09 50 00 00 08 00 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837596 offset 0 sd 4:0:0:0: [sdb] Unhandled error code sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 9e 01 09 50 00 00 08 00 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837596 offset 0 end_request: I/O error, dev sdb, sector 2650868224 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838027 offset 0 end_request: I/O error, dev sdb, sector 2650868224 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838027 offset 0 end_request: I/O error, dev sdb, sector 2650868224 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838027 offset 0 end_request: I/O error, dev sdb, sector 2650868224 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838027 offset 0 end_request: I/O error, dev sdb, sector 2650869160 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837594 offset 0 end_request: I/O error, dev sdb, sector 2650869160 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837594 offset 0 end_request: I/O error, dev sdb, sector 2650868232 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838167 offset 0 end_request: I/O error, dev sdb, sector 2650868232 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838167 offset 0 end_request: I/O error, dev sdb, sector 2650868232 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838167 offset 0 end_request: I/O error, dev sdb, sector 2650868232 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838167 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868368 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837847 offset 0 end_request: I/O error, dev sdb, sector 2650868872 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838784 offset 0 end_request: I/O error, dev sdb, sector 2650868872 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838784 offset 0 end_request: I/O error, dev sdb, sector 2650868872 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838784 offset 0 end_request: I/O error, dev sdb, sector 2650868872 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838784 offset 0 end_request: I/O error, dev sdb, sector 2650869240 end_request: I/O error, dev sdb, sector 2650868432 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82838039 offset 0 end_request: I/O error, dev sdb, sector 2650868168 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837839 offset 0 end_request: I/O error, dev sdb, sector 2650868168 EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837839 offset 0 UDP: bad checksum. From 201.127.111.28:52748 to 69.71.0.130:51413 ulen 70 UDP: bad checksum. From 201.127.102.106:25872 to 69.71.0.130:51413 ulen 70 __ratelimit: 27 callbacks suppressed sd 4:0:0:0: [sdb] Unhandled error code sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 9e 01 09 08 00 00 08 00 __ratelimit: 27 callbacks suppressed EXT4-fs error (device sdb1): ext4_find_entry: reading directory #82837506 offset 0 sd 4:0:0:0: [sdb] Unhandled error code sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 9e 04 f0 00 00 00 10 00 sd 4:0:0:0: [sdb] Unhandled error code sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 9e 04 f0 00 00 00 08 00
Submitted by JamieCameron on Thu, 12/13/2012 - 18:48 Comment #5
Those look like disk errors - it looks like your disk is dying and will need to be replaced.
Submitted by hatchetheavyhaul on Thu, 12/13/2012 - 19:06 Comment #6
Ok thanks not sure why it keeps eating drives ..
This is 2 drives in the last 3 months
this one only has 1588 hrs on it .
Do you know of any good seagate ata drives 2tb
Submitted by JamieCameron on Thu, 12/13/2012 - 22:34 Comment #7
I've been using four of model ST32000641AS for a year or more now.