Home > Failed To > Result Hostbyte=did_bad_target Driverbyte=driver_ok

Result Hostbyte=did_bad_target Driverbyte=driver_ok

Contents

Is it Inspiring ? Power Supply - I replaced the few year old power supply in the server with a newer higher spec good quality model. Adv Reply August 8th, 2008 #3 mortalic View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date May 2007 Beans 21 Re: ERROR: ata1.00 FAILED TO IDENTIFY Logged My Google Code Pagehttps://github.com/WeebotechIf you propose to speak, THINK and ask yourself... Check This Out

Now, we are getting some problem, disks are not being > recognized,. But anyways, I think we can just disable >> them altogether. In the same way that software developers code assuming malicious input, hardware vendors need to design for the worst possible signals from other devices. Next question?

Result Hostbyte=did_bad_target Driverbyte=driver_ok

Is it Inspiring ? Leave it Dead. Some explanation/data sheet from the HW vendor would be helpful at this point. > Seagate Model: ST3750640AS > Firmware: 3.AAK > > Hitachi Model:HDS721075KLA330 > Firmware: Not sure Both of these

I also consider a kernel bug to be a vendor fault anyway. Logged My Google Code Pagehttps://github.com/WeebotechIf you propose to speak, THINK and ask yourself... Continue? (Y/N) y \ Format completed successfully. 19046800448 kilobytes total disk space. The original commit comment isn't > specific about exactly which HW had problems: > http://www.mail-archive.com/git-commits-head [at] vger/msg24335.html > > "Some links on some PMPs locks up on SRST and/or report incorrect

Having a problem logging in? Smartctl Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search Now, I am using Fedora 12 (kernel 2.6.31.12). Can you confirm this?

Now, we are getting some problem, disks are not being >> recognized,. >> > Ouch... > > >> So, I connected it to Fedora 12 (To correct if it is >> In my drives (all hot swappable), each has two LEDs: one for power (green light) and another (orange light) probably showing the activity of the drive and it is related with Reply Leave a Reply Cancel reply Search for: Subscribe / Chat / Follow Subscribe via Email Because you're too cool for RSS. I have to say either Marvell or HighPoint (possibly both) are just crap.

  • If it is, this sounds like a broken implementation to me.
  • Is it Helpful ?
  • Thanks!
  • Can you do it with xfs?
  • What about Enterprise vs Consumer disks I've looked into the differences between Enterprise and Consumer grade disks before.
  • Is it Inspiring ?
  • Doesn't seem to be.
  • In case you missed it from above, we show it again: [ 116.267723] microcode: CPU2: new patch_level=0x010000dc [ 115.648023] CPU2 is up [ 115.405184] smpboot: Booting Node 0 Processor 3 APIC
  • dfs019 View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by dfs019 03-15-2010, 02:08 PM #10 troop Member Registered: Feb 2010 Distribution: gentoo,
  • As the owner of a Highpoint RocketRaid 2760 which I have spent 3 months off and on trying to get working with greater than 8 disks (even the Bios fails with

Smartctl

Thanks, Chandra On 2/4/10 12:59 PM, Grant Grundler wrote: > On Wed, Feb 3, 2010 at 7:24 PM, Tejun Heo<tj [at] kernel> wrote: > >> On 02/04/2010 11:37 AM, Grant Grundler https://www.jethrocarr.com/2013/11/24/adventures-in-io-hell/ At this time, I had lost sde, sdf and sdh - all three disks belonging to a single RAID controller, as shown by /sys/block/sd, and all of them Seagate Barracuda disks. Result Hostbyte=did_bad_target Driverbyte=driver_ok Having gone through the pain and effort to recover and rebuild this system, I had to ask myself a few questions about my design decisions and what I could do to Without digging into the Marvell driver code, it looks very much like the hardware is failing in some fashion and dropping the disks.

Also, this problem didn't exist in FC6 ( prob because of different driver ). http://bashprofile.net/failed-to/failed-to-write-breakin-packet-to-target-win32-error-0n2.html However, disk connected to "direct sata" (no disks on PMP) is fine. The disks connected to PMP are not being > recognized. Perfect - thanks for posting those.

Like, what make & model of motherboard is this? As far as I know jfs is not used real often, I wonder if there is something wrong with the driver of this file system. The original commit comment isn't > specific about exactly which HW had problems: > http://www.mail-archive.com/git-commits-head [at] vger/msg24335.html > > "Some links on some PMPs locks up on SRST and/or report incorrect this contact form Hi, I am fairly new to linux but I'm building one of the backblaze storage pods: blog.backblaze.com/2009/09/01/petabytes-on-a-budget-how-to-build-cheap-cloud-storage/ I have followed the specs they give exactly and i have almost completed it

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 more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results.

After nearly two weeks, it's time I give up and just RMA the drive.

Ah ok. If it is, this sounds like a broken implementation to me. Last edited by mc4man; August 8th, 2008 at 04:19 AM. The time now is 01:44 PM.

Should take another day.Then a smart -t long to verify how things panned out. What emergency gear and tools should I keep in my vehicle? Sense: No additional sense information [ 127.124395] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 127.124412] dpm_run_callback(): scsi_bus_resume+0x0/0x30 [scsi_mod] returns -5 [ 127.124420] pm80xx mpi_sata_completion 2041:SAS Address of navigate here May  4 16:54:05 phobos kernel: ata18: EH complete May  4 16:54:05 phobos kernel: sd 17:0:0:0: [sdm] Unhandled error code May  4 16:54:05 phobos kernel: sd 17:0:0:0: [sdm] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK May 

I greatly appreciate your help. When back in Wellington in May, I removed all three disks that had previously exhibited problems and installed the three new replacements. I thought 0x1095/0x3726 was a Silicon Image part. May  4 16:54:05 phobos kernel: md: md2: recovery done.

I doubt this is the problem Chandra is seeing but it could be related. After nearly two weeks, it's time I give up and just RMA the drive. Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest At this point, the only thing that helps is the reset button or the PSU power switch.

SiI 3124 PCI-X Serial ATA Controller (rev 02) These controllers use the "sata_sil24" kernel driver and are configured as simple JBOD controllers in the exact same fashion as the Marvell cards. The sata host controller is >> sil3124. Thanks Manojg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo [at] vger More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the I'm seeing this in sata_pmp_quirks() since ATA_LFLAG_NO_SRST was introduced: 337 static void sata_pmp_quirks(struct ata_port *ap) 338 { 339 u32 *gscr = ap->link.device->gscr; 340 u16 vendor = sata_pmp_gscr_vendor(gscr); 341 u16 devid =

May  4 16:54:05 phobos kernel: md/raid:md2: Operation continuing on 5 devices. Please login or register.Did you miss your activation email? 1 Hour 1 Day 1 Week 1 Month Forever Login with username, password and session length Home Help Search Login Register