> Unhandled Error
> End_request: I/o Error, Dev Sdb, Sector
End_request: I/o Error, Dev Sdb, Sector
The time now is 04:04 AM. Thanks for advices! No data corruption reported. Replacing the Seagate drives looks to be the real solution.
Which towel will dry faster? We have not seen them in our tools or kernel. > 2. I read somewhere (can't remember where, sorry) that it might have something to do with an Nvidia SATA controller sharing an IRQ with one of the USB controllers. I solved it by going to RSYNC instead of snapshots, however this workaround didn't work for the SuperMicro server. #11 check-ict, Jan 12, 2012 daveo Member Joined: Jan 6, 2012 go to this web-site
End_request: I/o Error, Dev Sdb, Sector
Both systems are running md softraid (level 1 raid) with LVM. pulseaudio a 12453 F.... Can the editor of a book add citations of individual chapters to his own citation count? Which towel will dry faster?
- Should multipath be retrying or should it be queueing due to not having any paths?
- Can we keep the thread open, just in case something happens?
- Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log
When I checked /mnt/backup1, wich isn't used for snapshot back-ups, i noticed it was also mounted as read-only. Maybe this is the samen problem I have now. When it tried to re-read, it got I/O error. Is there more to the log?
For the harzard tool when path is lost due to firmware core on target side we see the following error. Terminate Command Early Due To Bad Response To Iec Mode Page more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed I/O error, dev sda, sector 1. http://www.linuxquestions.org/questions/linux-kernel-70/i-o-error-on-device-sdb-939178/ Here's what I'm getting in dmesg over and over again...
Changed in linux (Ubuntu): importance: Medium → Wishlist status: Confirmed → Won't Fix See full activity log To post a comment you must log in. At any rate, I added 'noapic' to my kernel boot line in grub, and the error hasn't recurred since, though obviously a few days need to pass before any reliable conclusion Registration is quick, simple and absolutely free. Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK Aug 2.
Terminate Command Early Due To Bad Response To Iec Mode Page
Changed in linux (Ubuntu): status: New → Confirmed James Harris (james-harris-1-h) wrote on 2013-01-02: #6 Download full text (4.6 KiB) Not sure if it is related but the following has happened https://bugs.launchpad.net/bugs/1092883 Here is a graph that might help the understanding: The system is now stable, and has a WD Caviar Blue with a Hitachi drive where there were 2 Seagates (ST500DM002-1BD142) End_request: I/o Error, Dev Sdb, Sector Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 14 Thread: Hard drive problems Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Here is the analysis from Hazard Tool Team --------------------------------------------------- Here is a snippet of simplified view a Hazard process that detected a corruption.
Jul 4 20:27:36 host-37 kernel: [413644.743354] XFS (sdf1): xfs_log_force: error 5 returned. Getting scsi errors 'Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK' in. . Register If you are a new customer, register now for access to product evaluations and purchasing capabilities. George Law replied Aug 23, 2012 The latest RHEL5 kernel is the one he is running.
The sector number does increase but I'm not sure whether the disk driver is really trying to access the disk. Fix attempts I wasn't clever enough to think of these myself, this is just a list of things that other folk with similar errors said worked for them. Search this Thread 04-10-2012, 09:09 PM #1 thexder1 LQ Newbie Registered: Nov 2011 Posts: 4 Rep: I/O error on device sdb I have an old IBM X345 server that Disk IO errors on all sata disks, disks dropped out Discussion in 'Proxmox VE 1.x: Installation and configuration' started by check-ict, Nov 11, 2011.
Thanks in advance.  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/ Changed in linux (Ubuntu): importance: Undecided → Medium status: Confirmed → Incomplete James Harris (james-harris-1-h) wrote on 2013-01-07: #8 Will try to test the upstream kernel Udo #2 udo, Nov 11, 2011 check-ict Member Joined: Apr 19, 2011 Messages: 77 Likes Received: 0 proxmox01:/mnt# smartctl --all /dev/sdb smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen Are you seeing dm multipath fail the IO or retry it?
I have just replaced one of them (about the same time as forcing 1.5Gbps) with an Hitachi but the other is still in there.
Some application can cause the issue. Linux SCSI Errors - Toolbox for IT Groups. Status 0xd. 0)kernel: [9. . Maybe just 2 paths?
Comment 9 Dinesh Surpur 2012-01-30 15:15:27 EST Closing this issue as the issue was on the target iSCSI driver causing corruption and is fixed and not a host side issue. To continue, add one or more '-T permissive' options. schedule_timeout+0xb7/0xe7 Nov 11 02:14:56 proxmox01 kernel:  bdi_writeback_task+0x43/0x118 Nov 11 02:14:56 proxmox01 kernel:  ? Jul 4 20:24:36 host-37 kernel: [413464.345590] XFS (sdf1): xfs_log_force: error 5 returned.
up vote 4 down vote favorite Today I wasn't able to access one of my hard drives, after reboot it seems to work now, but i'm worried it's going to die The setup has multiple hosts and each host has either a QLogic 8242 CNA, Emulex CN1000E CNA and a HP 10G Nic running RH6.1 or RH 5.7 and connected through the bdi_start_fn+0x0/0xdf Nov 11 02:14:56 proxmox01 kernel:  bdi_start_fn+0x7a/0xdf Nov 11 02:14:56 proxmox01 kernel:  ? Read more...
Virtual I/O Example The problem with iSCSI Toolbox for IT My Home Topics People Companies Jobs White Paper Library Collaboration Tools Discussion Groups Blogs Follow Toolbox.com Toolbox for IT on Twitter In between each of these lines, there are many more lines logged by sd driver in kernel of I/O errors. The Seagates clearly keep the CPU's waiting for over 2 seconds for IO to return where as the Hitachi doesn't. kthread+0x0/0x8a Nov 11 02:14:56 proxmox01 kernel:  ?
Unhandled error code Aug 2.