Re: ahd0: Invalid Sequencer interrupt occurred.
On Fri, Nov 11, 2005 at 11:10:51PM -0800, John-Mark Gurney wrote: obviously you haven't done any research or even talked with Seagate about this issue... Seagate has a Linux version of their Seagate Enterprise Utility that allows you to flash their drives... How is this relevant? Many of us have just as many production linux boxes as we do production Windows boxes. (that would be *none*) -- Joe Rhett senior geek SVcolo : Silicon Valley Colocation ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Fri, 2005-11-11 at 22:57 -0800, Ade Lovett wrote: On Nov 11, 2005, at 12:51 , Amit Rao wrote: 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). Of course, you then spend far too much time ensuring that any replacement drives are flashed appropriately (which, afaict, *requires* Windows to do), and also running the gauntlet of further problems down the road when you throw the drives into a new machine with a subtly different HBA bios. No thanks, I'll stick with option (2). A few more months, and Seagate drives will be a nice distant memory that I can look back on in a few years, and laugh nervously about. -aDe There was a flash-utility that was [hand-rolled?] able to run on FreeBSD and I did successfully flash some Seagate drives' firmware -- didn't help any as far as the error [messages] went so we dropped Seagate drives altogether a little over a year ago. Since then we have been using the IBM/Hitachi drives with no issues (much easier to change drive manufacturers than try to respec the servers we were using or do some of the borderline-absurd workarounds that Seagate suggested). Sven ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Ricardo A. Reis wrote: Hi all, The University where i work recent acquire a new server, i install FreeBSD 6.0 and update for STABLE yestarday, in dmesg i see this messages ahd0: Invalid Sequencer interrupt occurred. I've had similar problems with Dual channel U320 adaptec controller (built in on supermicro board) and Seagate U320 drives. The solution was to force the drives to U160 speed from the BIOS, and split the drives equaly on the two channels to reduce the bottleneck. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Niki, You read this ... http://lists.freebsd.org/pipermail/freebsd-stable/2005-April/013737.html I'll try on the weekend, Ricardo A. Reis UNIFESP Unix and Network Admin Ricardo A. Reis wrote: Hi all, The University where i work recent acquire a new server, i install FreeBSD 6.0 and update for STABLE yestarday, in dmesg i see this messages ahd0: Invalid Sequencer interrupt occurred. I've had similar problems with Dual channel U320 adaptec controller (built in on supermicro board) and Seagate U320 drives. The solution was to force the drives to U160 speed from the BIOS, and split the drives equaly on the two channels to reduce the bottleneck. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Ade Lovett wrote: On Nov 10, 2005, at 05:30 , Ricardo A. Reis wrote: Reducing the problem to the relevant pieces: ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2400-0x24ff,0x2000-0x20ff mem 0xdd20-0xdd201fff irq 32 at device 2.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2c00-0x2cff,0x2800-0x28ff mem 0xdd202000-0xdd203fff irq 33 at device 2.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs [...] da0 at ahd0 bus 0 target 0 lun 0 da0: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da1 at ahd0 bus 0 target 1 lun 0 da1: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a Adaptec HBAs and Seagate drives have a long and intensely painful history of not working well together. Adaptec blames Seagate. Seagate blames Adaptec. Throw in the myriad of subtly different AIC controllers that are commonplace on 1U and 2U rackmount servers, and things get even more entertaining. You essentially have 3 options 4 options. 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). -Amit 1) replace the HBA -- somewhat difficult to do if it's embedded and you need the PCIX slots for something else. 2) replace the drives -- IBM/Hitachi are fine choices here. Make sure to tell whomever you purchase systems from that you'll not accept Seagate drives in the future. 3) inside the adaptec bios, drop the drives to U160 speed, making sure that *both* packetizing *and* QAS are turned OFF. You'll lose a little bit of performance (but not all that much, Seagate drives really are garbage), and get some semblance of stability. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Nov 11, 2005, at 12:51 , Amit Rao wrote: 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). Of course, you then spend far too much time ensuring that any replacement drives are flashed appropriately (which, afaict, *requires* Windows to do), and also running the gauntlet of further problems down the road when you throw the drives into a new machine with a subtly different HBA bios. No thanks, I'll stick with option (2). A few more months, and Seagate drives will be a nice distant memory that I can look back on in a few years, and laugh nervously about. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Ade Lovett wrote this message on Fri, Nov 11, 2005 at 22:57 -0800: On Nov 11, 2005, at 12:51 , Amit Rao wrote: 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). Of course, you then spend far too much time ensuring that any replacement drives are flashed appropriately (which, afaict, *requires* Windows to do), and also running the gauntlet of further problems down the road when you throw the drives into a new machine with a subtly different HBA bios. obviously you haven't done any research or even talked with Seagate about this issue... Seagate has a Linux version of their Seagate Enterprise Utility that allows you to flash their drives... /me having had issues with the drives and successfully flashed drives w/o using Windows. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Nov 11, 2005, at 23:10 , John-Mark Gurney wrote: obviously you haven't done any research or even talked with Seagate about this issue... Seagate has a Linux version of their Seagate Enterprise Utility that allows you to flash their drives... Yes, I have done plenty of research with Seagate, Adaptec, and a number of VARs. Edit your kernel config, add: options KVA_PAGES=384 (for a 2.5G/1.5G kernel/userland split, as opposed to 2G/2G) recompile, install, watch the linuxulator explode in a frenzy. I have absolutely no interest in putting Linux (or, indeed, anything *but* FreeBSD) on my production boxes. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Nov 10, 2005, at 05:30 , Ricardo A. Reis wrote: Reducing the problem to the relevant pieces: ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2400-0x24ff, 0x2000-0x20ff mem 0xdd20-0xdd201fff irq 32 at device 2.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2c00-0x2cff, 0x2800-0x28ff mem 0xdd202000-0xdd203fff irq 33 at device 2.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs [...] da0 at ahd0 bus 0 target 0 lun 0 da0: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da1 at ahd0 bus 0 target 1 lun 0 da1: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a Adaptec HBAs and Seagate drives have a long and intensely painful history of not working well together. Adaptec blames Seagate. Seagate blames Adaptec. Throw in the myriad of subtly different AIC controllers that are commonplace on 1U and 2U rackmount servers, and things get even more entertaining. You essentially have 3 options 1) replace the HBA -- somewhat difficult to do if it's embedded and you need the PCIX slots for something else. 2) replace the drives -- IBM/Hitachi are fine choices here. Make sure to tell whomever you purchase systems from that you'll not accept Seagate drives in the future. 3) inside the adaptec bios, drop the drives to U160 speed, making sure that *both* packetizing *and* QAS are turned OFF. You'll lose a little bit of performance (but not all that much, Seagate drives really are garbage), and get some semblance of stability. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
