Looking at what I knew about the issue, I could identify the following possible causes: A bug in the Linux kernel was triggering cascading failures of RAID rebuilds (bug in either Changed in linux (Ubuntu): importance: Medium → Wishlist status: Confirmed → Won't Fix See full activity log To post a comment you must log in. Say Thanks Found anything on my blog or any of my applications useful? May 13 16:52:24 server1 kernel: [ 988.581316] sd 0:0:1:0: [sda] Unhandled error code May 13 16:52:24 server1 kernel: [ 988.581319] sd 0:0:1:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK May 13 16:52:24 server1 kernel: website here
You'll see bad sectors if the drive was broken. Maybe this is the samen problem I have now. Affecting: linux (Ubuntu) Filed here by: James Harris When: 2012-12-21 Completed: 2013-12-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started
The more I look the less consensus there seems to be, but for me this worked - I'm now 2 days in, 2 raid rebuilds and 12 LVM snapshotted backups (during After kicking out the disk from the array, that rebuild time dropped to 5 hours, which is a pretty compelling argument for using enterprise disks to have them die quicker and This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. End_request: I/o Error, Dev Sdb, Sector By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
check-ict Member Joined: Apr 19, 2011 Messages: 77 Likes Received: 0 Hello all, I'm running Proxmox 1.8 on a Supermicro server with 8 hot-swap bays with hardware raid and 2 normals Unhandled Error Code Result Hostbyte=did_error Driverbyte=driver_ok Tango Icons © Tango Desktop Project. Reply Jethro Carr says: April 30, 2014 at 23:17 How frustrating :-( I think this whole incident reflects poorly on Highpoint too, I would expect RAID card vendors to do more https://access.redhat.com/solutions/1405103 I'm having the same problem Here's my thread: http://ubuntuforums.org/showthread.p...6#post11420126 Adv Reply Page 1 of 2 12 Last Jump to page: Quick Navigation Hardware Top Site Areas Settings Private Messages Subscriptions
Nov 13 10:15:41 phobos kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 13 10:15:41 phobos kernel: ata14.00: irq_stat 0x00060002, device error via D2H FIS Nov 13 10:15:41 Smartctl Want to know if that peripheral is compatible with Linux? What are the German equivalents of â€śFirst World Warâ€ť, â€śWorld War Iâ€ť, and â€śWWIâ€ť? Marvell Chipset-based controller (left) and replacement SiI based controller (right).
It's worth noting that these controllers are actually PCI-X cards with an onboard PCI-X to PCIe-1x converter chip which is more than fast enough for hard disks, but could be a Then noticed your post turned into a giant rant about Marvell controllers. Result: Hostbyte=did_error Driverbyte=driver_ok Integer function which takes every value infinitely often Why do we need blockchains? Exception Emask 0x0 Sact 0x0 Serr 0x0 Action 0x6 Frozen I have two proxmox systems with several ST32000644NS drives (all with firmware SN11) with supermicro mainboards.
I have 5 750GB hard drives, 1 has / and swap on it, the others are for data, but I am only using the first to at the moment. http://crimsonskysoftware.com/unhandled-error/unhandled-error-code-164.html That handling could be as simple as reporting what was wrong but if Linux doesn't recognise the error code it can never know if it is handling it correctly. Commit interval 5 seconds Nov 11 02:10:54 proxmox01 kernel: EXT3-fs (dm-3): using internal journal Nov 11 02:10:54 proxmox01 kernel: EXT3-fs (dm-3): mounted filesystem with ordered data mode Nov 11 02:13:12 proxmox01 Adv Reply June 8th, 2010 #8 Mspirit View Profile View Forum Posts Private Message Spilled the Beans Join Date May 2010 Beans 12 Re: Hard drive problems Installed Lucid couple Terminate Command Early Due To Bad Response To Iec Mode Page
I close this report --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad tags: added: hardware-error Changed in linux (Ubuntu): status: Confirmed → Invalid James Harris (james-harris-1-h) wrote on 2013-01-02: #4 This shouldn't Try looking at the S.M.A.R.T. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. have a peek here Jul 4 20:23:35 host-37 kernel: [413404.212943] XFS (sdf1): xfs_log_force: error 5 returned.
In this case, /dev/sde attached to the host AMD controller failed and I decided to hold off replacing it for a couple of months as it's internal to the case and Can anyone tell me what I can try to recover those drives? default_spin_lock_flags+0x9/0xe Nov 11 02:14:56 proxmox01 kernel: [
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
kthread+0x0/0x8a Nov 11 02:14:56 proxmox01 kernel: [
Need access to an account?If your company has an existing Red Hat account, your organization administrator can grant you access. I have to say either Marvell or HighPoint (possibly both) are just crap. Randomly I get drive errors while the promox backup task (with LVM snapshots) is running. http://crimsonskysoftware.com/unhandled-error/unhandled-error-code-did-bad-target.html Frustratingly I didn't have any further time to work on it whilst I was in NZ in May, so I rebuilt the minimum array possible using the onboard AMD controller to
At least an informative log report would help. 4) What happened instead The response seems to have confused badblocks. Return address = 0xffffffffa0141af1 May 13 16:52:24 server1 kernel: [ 988.573460] sd 0:0:1:0: [sda] Unhandled error code May 13 16:52:24 server1 kernel: [ 988.573461] sd 0:0:1:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK May MayÂ 4 16:54:05 phobos kernel: md: md2: recovery done. Ext4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities1Failed install of ubuntu 16.04 & 15.10 with error message “following file did not match its source copy…”0How to change data parameter
Truly useless hardware. My guess is that something was changed in the APIC code. Open Source Communities Comments Helpful Follow Unhandled error code Solution Unverified - Updated 2015-04-06T10:13:07+00:00 - English No translations currently exist. Will try with an earlier version and report back.
Can you view the BIOS for your RAID card and see if it is reporting any errors? This is a common recommendation, but I still know numerous people who treat RAID as an infallible storage solution and don't take adequate precautions for failure of the storage array. How do I find out what?314.04 System hangs and IO errors2Why does my Ubuntu 14.04 desktop lock up when I do large data transfers between hard drives?0ext4 I/O Error after suspend You may have to register before you can post: click the register link above to proceed.