kern service manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:kern service manual.pdf
Size: 4688 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 17 May 2019, 12:32 PM
Rating: 4.6/5 from 678 votes.
Status: AVAILABLE
Last checked: 18 Minutes ago!
In order to read or download kern service manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
kern service manualThe service manual is obligatory for repair work. After repair, original conditions of the device have to be restored. Only original spare parts should be used. Note all rights are reserved. Copying any part of this manual is prohibited without our permission. The switch for this step is located at the bottom of the housing between the two turning feet. The display appears the first linearity point, e.g. Display suddenly 1. Built-in battery (option) has been consumed.Adjust the level. Remove fixing screw on AJDP board and unplug connector with CN4 on AJDP board. When linearity adjustment is done. Use weights of higher accuracy than the scale. Remove the pan and pan base. Remove case fixing screw with a screwdriver. Locate two hooks beneath the scale near front. Pull those two hooks toward you to lift the case up, then shift the case to rear to release it from hooks. Remove the pan and pan base. (2) Remove case fixing screw with screwdriver. (3) Locate two hooks toward you to lift the case up, then shift the case to rear to release it from hooks. Insert the rear hooks first, then press the upper case gently until two front hooks are set securely. Mechanism unit fixing screws 5.3.1.2 EW 2200-12K (1) Remove the case referring to 5-1. (2) Remove wires to the Tuning-fork sensor, by welding solders at AJDP circuit board. Cover the mechanism unite with the sensor cover. Fit it with four fixing screw. (EW 120-1200). Fix the Tuning-fork sensor wire to hexagon pillar with cord band. (EW2200-12K) (4) Cover the scale referring to 5-2. CN1: AJLF cord CN3: Calibration cord CN4: AJIF cord CN5: Battery cord (3) Place the AJDP board on the chassis. Fix it with a fixing screw. (4) Cover the scale referring to 5-2. Discover everything Scribd has to offer, including books and audiobooks from major publishers. Start Free Trial Cancel anytime.http://gemwares.com/userfiles/latch-manual-2014.xml
- Tags:
- kern service manual, kern 572 service manual, kern pfb service manual, kern mpe service manual, kern 770 service manual, kern abj service manual, kern cfs service manual, kern service manuals.
Report this Document Download now Save Save Kern 440 Precision Balance - Service Manual For Later 100 (2) 100 found this document useful (2 votes) 252 views 11 pages Kern 440 Precision Balance - Service Manual Uploaded by Scott Tyler Description: KERN Calibration Manual Full description Save Save Kern 440 Precision Balance - Service Manual For Later 100 100 found this document useful, Mark this document as useful 0 0 found this document not useful, Mark this document as not useful Embed Share Print Download now Jump to Page You are on page 1 of 11 Search inside document Browse Books Site Directory Site Language: English Change Language English Change Language Quick navigation Home Books Audiobooks Documents, active. Full Tare. Memory function with indicator. Stable indicator. Negative value indication. Two types of Digital Auto Calibration. Solder pads to prevent end-user internal calibration. Low battery indicator. Auto off function (battery mode only). AC adaptable. Display segment test function. Overload protectionIt is collected for only two reasons: Administrative purposes, should a need to contact you arise. To inform you of new comments, should you subscribe to receive notifications. A cookie may be set on your computer. This is used to remember your inputs. It will expire by itself. This policy is subject to change at any time and without notice.By submitting a comment, you are declaring that you agree with these rules: Although the administrator will attempt to moderate comments, it is impossible for every comment to have been moderated at any given time. You acknowledge that all comments express the views and opinions of the original author and not those of the administrator. You agree not to post any material which is knowingly false, obscene, hateful, threatening, harassing or invasive of a person's privacy. The administrator has the right to edit, move or remove any comment for any reason and without notice.http://belniig.by/public/latent-gold-choice-manual.xml Failure to comply with these rules may result in being banned from submitting further comments. By submitting a comment, you are declaring that you agree with these rules: Although the administrator will attempt to moderate comments, it is impossible for every comment to have been moderated at any given time. You acknowledge that all comments express the views and opinions of the original author and not those of the administrator. You agree not to post any material which is knowingly false, obscene, hateful, threatening, harassing or invasive of a person's privacy. The administrator has the right to edit, move or remove any comment for any reason and without notice. Failure to comply with these rules may result in being banned from further commenting. Full Tare. Memory function with indicator. Stable indicator. Negative value indication. Two types of Digital Auto Calibration. Solder pads to prevent end-user internal calibration. Low battery indicator. Auto off function (battery mode only). AC adaptable. Display segment test function. Overload protectionBy submitting a comment, you are declaring that you agree with these rules: Although the administrator will attempt to moderate comments, it is impossible for every comment to have been moderated at any given time. You acknowledge that all comments express the views and opinions of the original author and not those of the administrator. You agree not to post any material which is knowingly false, obscene, hateful, threatening, harassing or invasive of a person's privacy. The administrator has the right to edit, move or remove any comment for any reason and without notice. Failure to comply with these rules may result in being banned from further commenting.http://www.statcardsports.com/node/905719:12:03 freebsd kernel: GEOM: da6: the primary GPT table is corruptSep 22 19:12:03 freebsd kernel: GEOM: da6: using the secondary instead --Sep 22 19:12:03 freebsd kernel: GEOM: da7: the primary GPT table is corruptSep 22 19:12:03 freebsd kernel: GEOM: da7: using the secondary instead --Sep 22 19:12:03 freebsd kernel: GEOM: da8: the primary GPT table is corruptSep 22 19:12:03 freebsd kernel: GEOM: da8: using the secondary instead --Sep 22 19:12:03 freebsd kernel: GEOM: da9: the primary GPT table is corruptSep 22 19:12:03 freebsd kernel: GEOM: da9: using the secondary instead --Sep 22 19:12:03 freebsd kernel: GEOM: da10: the primary GPT table isSep 22 19:12:03 freebsd kernel: GEOM: da10: using the secondary instead --Sep 22 19:12:04 freebsd kernel: GEOM: da11: the primary GPT table isSep 22 19:12:04 freebsd kernel: GEOM: da11: using the secondary instead --Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:Sep 22 19:12:04 freebsd kernel: GEOM:There's a lot of this noise when an initiator is online and trying toOn the initiator which is running debian-based proxmox there is a lot ofSense: Logical unit not ready, manual intervention requiredNo idea why it's saying illegal option here.https://kinetictr.com/images/compaq-wf1907-service-manual.pdf It's listed in the commandUsage. Primary commands:Any assistance greatly appreciated! Thanks! Sense: Logical unit no. Sense: Logical unit not ready Sense: Logical unit not readySense: Logical unit not readyIs that an EMC Symmetrix storage system. If you don't have SAN admin access, find someone who has.Sense: Logical unit not readyBy using this site, you accept the Terms of Use and Rules of Participation. Please refer the belwo outputs. Please correct me if i wrong. It is very wellTo answer your questions. You can not send IOs on passive paths. Please correct me if i wrong. Get your array details, that would be able to help out. It is very wellTo answer your questions. Get your array details, that would be able to help out. Let us know so we can fix it. In many environments it is not possible to completely eliminate these messages, but they can be substantially reduced by removing the HBA driver from the initrd, and loading the module at a later stage in the boot process. Monitor the output of this command to ensure the HBA driver is not being added to the kernel for some other reason. - Reboot NOTE - If the server is booting from a SAN, this solution should not be used. However, if the server is not using devices on the SAN for system partitions, there should be no issues implementing this change. Using this configuration, server boot times should be substantially faster. In one extreme case, the server startup time was reduced from over 45 minutes, to just a few minutes. If it is Linux Related and doesn't seem to fit in any other forum then this is the place. You are currently viewing LQ as a guest. 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. Registration is quick, simple and absolutely free. Join our community today. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.If you need to reset your password, click here. Having a problem logging in. Please visit this page to clear all LQ-related cookies. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.We are using Powerpath for multipathing and have disabled native multipathing. Sense: Logical unit not ready, manual intervention required Can anyone please suggest how to get rid of these errors. Any Help wud be much appreciated. Thanks Is the LUN accessible. Does this errors only show up during reboot. What HBA is used? What parameters are passed in modprobe.conf to the HBA? Array failover mode: 1 The LUN is accessible. Appreciate your help. Thanks, Ramya It is created during first time access to the passive storage path. Powerpoath should suppress the message. Did you check EMC knowlaedge base ID: emc187631. Do you use the last version of powerpath and naviagent? Editorials, Articles, Reviews, and more. If you'd like to contribute. When I access the filesystem on the raid while the disks are in standby mode I sometimes (but not always) get these messages in dmesg:Could this have to do with Staggered Spin up. What do I need to do to fix this? Several problems at a time are rare, so to keep the options down, we'll work on the idea that its a single problem.HDD controller? PSU?This feature does not have to be used and I'm unsure if it got into the SATA spec. The makes for slow spin up times of a group of drives but almost eliminates the start up current spike caused by, in your case, 7 drives trying to spin up at the same time.Additionally there is a SSD for the system but it's not inside one of the cages), 5 disks in the first, 3 in the second one. They use the same PSU (the system has only one), but different cables if I remember correctly.It's a 500W PSU, when in idle the system uses around 40-50W and when disks are spinning up it's 150-200W for a few seconds, then 90-100W while they are running.MGA G200eW WPCM450 (rev 0a) Note that he has the same controller (they have different names but are the same hardware), and is also using SATA disks. The only difference is that I don't get errors by mdraid. Later in that thread someone posted a patch which was included in the kernel (I'm using 3.9.9-gentoo, and the patch is included there, I checked). It's this patch here. But it doesn't seem to be the same problem I have (my disks do spin up and there are no errors beside those posted above).Or a configuration problem. What to do next?I have this controller only couple of weeks and I have experienced it fewer than 10 times. Drives are going to standby and waking up couple of times a day. I did not yet test reconnecting drives to other ports. What is your setup? Which exact controller do you have, on which drive does it happen and how often? No raid controller involved though, all onboard. So I assume this is an issue with your controller(s).? I am hitting a very similar situation and can add some data. I have output below from dmesg when this case is hit. There are a few extra lines of debugging that I inserted. The sense data logs are from executing:Same mpt2sas driver with both tests:It's as if the change being made by the sdparm call from the B controller is locking access to the drive long enough that IO on the A side times out (errors out). Just guessing at that right now.Also running 3.17.7 now (before 3.16.5 for the last few months).In the normal setup, that is on the enclosure (which I became suspicious of, because I bought it used); but for debugging I have moved some onto the 8-slot cage with the 9211 and the same problem arises.I verified several backups and they are perfect. mdraid etc. does not show any problem.I'll keep on running smartctl and keep an eye open, but I think it's harmless really.I simply (almost) disabled power management.A value of 255 tells hdparm to disable Advanced Power Management altogether on the drive (not all drives support disabling it, but most do)But as I understand a minimal level of drive APM remains with 254, so I have chosen that setting. Rather stupid not to check that before.Be aware though, that your disks will be running almost constantly. I guess I'll find out (that's what backups are for).For now i am testing some sysctl tuning:Let me test it longer till i can say it helped. Raid is stable. For now it looks promising. For now it looks promising. Thus sg is used for scanners, cd writers and reading audio cds digitallyThese are notes on the Linux SCSI generic packet device driver (sg)Foard and remained in place with minimal changes since circa 1992. Version 2 of this driver remains backward compatible (binary and. It adds scatter gather, command queuing,A shorter (abridged) form of this document can be found atThe interface and usage of the original sg driver have been documentedIt can found at. A copy of this document can be found at:The author is not aware of any usefulIt may indeed be useful to distinguish between the original and theArchitecture. The SCSI generic packet device driver (sg) is a character based device. It is one of the four high level device driver in the SCSI sub-system;The other three devices are block devices. The unifying layer of the SCSI sub-system is the so-called mid-level.Also at this level are pseudoATAPI (which are similar to one another) for use by IDE devices. Since sg is a character device it supports the traditional UnixAn SG device is accessed by write()ing SCSI commands plus any associatedThe device may be. The buffer given to the write() call is madeThe buffer received from the corresponding read() call contains:The given SCSI command has its LUN field overwritten by the LUN value ofSCSI commands are only attempted once (i.e. there are no internalThis is the name of the control structure that conveys informationIn its original form it looked like this:Even though it looks like anThe 'result' is also bizarre, turning certain types of host codes to 0 (noWith better error reporting now available, theThe command length detection algorithm is as follows. Group: 0 1 2 3 4 5 6 7. Length: 6 10 10 12 12 12 10 10Firstly the new header is binary compatible with the original. This isOnly those elements (or fields) that are new or in some way differentIn all casesThe allowableA copy of these. A copy of theseIt is not used. Memory issues. This driver uses a double-handling technique to move data from a SCSIIO involves DMAing data from SCSI device to kernel buffers then using the. CPU to move it from these kernel buffers to the user space (or vice versaObtaining memory for the kernel buffers for this indirect IO technique isThese kernel buffers are needed duringThe size of the reserved buffer. This reserved buffer becomes the kernel buffer for a given write()-read()If either of these condition is not met then the write() will attempt toThe reserved buffer is freed when the file descriptorIts value can beLinux 2.2 does not put aside any memory for drivers; they just compete forGiven the above constraintsYet more and moreThe safest strategy for limiting memory problems is:Alternatively, applications can be written in such a way to do somethingSystem Calls. What follows are descriptions of the characteristics of the standard. Unix operating system calls when applied to a SCSI generic deviceThe combination of. Calls that would otherwise blockBy default, sequencing is per file descriptor in this version of sg. ThisThis may or may not make sense depending onThe reserved buffer will be used if:Error codes (value in 'errno' after -1 returned). EACCES Either the user doesn't have appropriate permissions onENODEV sg not compiled into kernel or the kernel cannot find theENOENT given filename not found. ENOMEM An attempt to get memory to store this open's context. ENXIO either there is no attached device corresponding to givenWrite() is used to send aThe mandatoryThe optional part is:These should appear as one contiguous string in the buffer given toIf a write() accepts this packet then at some later time the user shouldThe previous sgHowever, for backward compatibility, command queuing is turned off. In this sg driver a write() should return more or less immediately. Error codes (value in 'errno' after -1 returned). EAGAIN SCSI mid-level out of command blocks (rare), try again.EDOM a) command queuing off: a packet is already queuedEFAULT 'buffer' for 'count' bytes is an invalid memory range. EIO a) incoming buffer too short. It should be at least. ENOMEM can't get memory for DMA. Take evasive action.ENXIO either scsi sub-system is currently processing some errorThe optional part is:The buffer given to a read() and its corresponding count should beTruncation occursUnfortunately the return value in the non-error case is simply theIt is not the actual number of bytes. DMA-ed by the SCSI device. This driver is currently unable to provideIf the SCSI device reports an error then a REQUEST SENSE is automatically. EAGAIN either no waiting packet or requested packet is not. EFAULT 'buffer' for 'count' bytes is an invalid memory range. EINTR while waiting for a packet, a signal is received, justLinux supplies. Assumes 3rd argument points to an int containing the new timeout valuePackets that are. The default value is setAssumes 3rd argument points to an int and outputs a flag indicatingA value of 1 means emulatedThe third argument is interpreted as an integer. When it is non-zero thenWhen zero is passed as the 3rd argument toBeware, this state will affectThird argument is ignored.Returns 1 when it is transforming them. Assumes 3rd argument points to an int containing 0 or 1. 0 (default)PCI SCSI adapters will indicate they can DMA to the whole 32 bit addressIf 1 is given then the host adapter is overridden and only memory belowA requirement for this should beOnly the current file descriptor is affected. Assumes 3rd argument points to an int and places 0 or 1 in it. 0Assumes 3rd argument is pointing to an int. 0 (default) instructs read()Only the current file descriptor is affected by this command.If no packet is waiting to be read thenAssumes 3rd argument points to an int and places the number of packetsAssumes 3rd argument points to an int and places the maximum number ofAssumes 3rd argument is pointing to an int. That value will be used toThe previous reserved bufferA new reserved buffer is then allocated and its actual size can be found by. The reserved buffer is then usedLarge buffers can be requested (eg 1 MB). Assumes 3rd argument points to an int and places the size in bytes ofThe result can be 0 if memory is very tight. InAssumes 3rd argument is pointing to an int. 0 (the default) causes allIf this command tries to change the currentPer device sequencing was the originalThis commandPer file descriptor. Assumes 3rd argument points to an int and places 0 or 1 in it. 0 impliesAssumes 3rd argument is pointing to an int. 0 (current default, set by. Attempts to write()Changing the queuing state only affects write()s done after the change. Only the current file descriptor is affected by this command. Only the current file descriptor is affected by this command (unless. Assumes 3rd argument points to an int and places 0 or 1 in it. 0 impliesAssumes 3rd argument is pointing to an int.After that write() the SCSI command length logic isIf the current SCSI command length maximum ofGiving this ioctl() a value of 0 will set automatic length detection forAssumes 3rd argument points to an int. The version number is then placed. Assumes 3rd argument points to an int. Unfortunately doesn't currentlyEBUSY error if the SCSI bus or the associated device is being resetAssumes 3rd argument is pointing to an int. 0 (default) turns debuggingAccess permissions may differ a little fromIt gets populated with scsi channel, device id and lun data for the given. This probably indicates that this ioctl commandGiven a choice poll() should probably beOnly if something drastically is wrong (eg file handle gone stale) will. POLLERR ever be set. POLLPRI, POLLHUP and POLLNVAL are never set. POLLIN is set when there is one or more packets waiting to be read. When POLLIN is set it implies that a read() will not block (nor yield. EAGAIN in non-blocking mode) but return a packet immediately. POLLOUT (aka POLLWRNORM) is set when write() is able to accept a packet. The setting of POLLOUT is affectedNote that a packet can be queued after write()ing but not available to beA working example of this logic. Some work has to be done in Linux to set up for asynchronous notification. This is a non-blocking mode of operation in which, when the driver receivesA working example of this logic. Utility and Test ProgramsBriefly, that tarball contains the following utilities. It uses POSIXIt also contains the following test programs. SCSI 2 errors and warnings. This code is used by most of the aboveHeader filesSeveral distributions have taken their own copies of these files and placed. It was is Redhat 5.1 and 5.2 but it isRedhat where it is a symbolic link) so it is hard to understand why. The fact theDistinguishing the original from the new driver. People writing applications have to cope with the existing Linux codeSo the problem arises:This can be addressed at 2 levels: run time and compile time. EvenRun time selection is more flexible and can be based on whether aThis is best demonstrated byIt has that value for backwardIf anything its valueIf you have plenty of memory on yourThis could beAs can be seen above. This can be changedHowever changing its value may wellChanging its value to beIn this case the reservedIt can be accessed with:It only remains for backwardShortcomings. Most real world programs need to make compromises to be implementableTaking the last point first, the mid level layer is the unifying layer. It defines most of the interfaces for both the high level driversGiven that investment, especially in those lowIt is planned that the next major changes toThe following shortcomings are listed in point form:SCSI 2 requires a minimum of 18 bytes andThis transferA Unix close() can occur at any timeSome people would prefer a unified space for SCSI device handles inThere are arguments both ways, but from a device driver writer'sRemember also that Linux. The downside of the separate space is that each SCSI device potentiallyUltimately the introduction of theFuture DirectionsRecent experiments indicateThis is more than sufficient for most currentSome people are interested in significantlyThis could be distinguished by having a negative. Investigate CAM (in FreeBSD 3.2). ReferencesEric is primarilyConclusion. The SCSI generic packet device driver attempts to make as few assumptionsSome of these aims areFor example: shouldThere is noIf you have any suggestion about sg (or improving (the accuracy of) thisAppendix. The following ASCII art is obtained from draft copies (and copies ofHopefully they are accurate. Summary of SCSI commandsGiven a 512 byte block size it can accessThat should satisfy most requirements.The 'Control' byte and other 'Reserved' fields should be set to 0 inThe 'Logical Unit Number' is set internally byExample of a SCSI command: INQUIRYUnless EVPD is set 'Page Code' should be 0.SCSI Status ByteIt is related to but not exactly theThe difference is that the. SCSI status byte has its reserved bits masked off and it is shifted onceGOOD. This status indicates that the target has successfully completed theCHECK CONDITION. This status indicates that a contingent allegiance. CONDITION MET. This status or INTERMEDIATE-CONDITION MET is returned wheneverBUSY. This status indicates that the target is busy. This status shall beThe recommendedINTERMEDIATE. This status or INTERMEDIATE-CONDITION MET shall be returned forRESERVATION CONFLICT, or COMMAND TERMINATED status. If INTERMEDIATE or. INTERMEDIATE-CONDITION MET status is not returned, the series of linkedMET and INTERMEDIATE statuses.RESERVE and RESERVE UNIT commands). The recommended initiator recovery actionCOMMAND TERMINATED. This status shall be returned whenever the targetQUEUE FULL. This status shall be implemented if tagged queuing isTAG, or HEAD OF QUEUE TAG message is received and the command queue is full. CHECK CONDITION and COMMAND TERMINATED. The latter case occurs in Linux since low level drivers that emulate a. Also CHECK CONDITION does not necessarily imply an error. For example,SCSI Sense bufferWhat actually happens is that when a SCSI target (device) returns a SCSISCSI mid level automatically issues a follow up SCSI REQUEST SENSE commandThe sense buffer returned by the REQUEST SENSE command looks like this. This is a complicated beast and the reader is referred to the SCSI 2A brief summary of the importantThe 'Valid' but is rather deceptively named and just indicates whetherThe important fields are the Sense Key, the. Additional Sense Code (ASC) and the Additional Sense Code Qualifier (ASCQ)Sense Key DescriptionWhen multiple recovered errors occurThis sense key may alsoIf the target detects an invalid parameter inThis sense key may also indicateSense Code Qualifiers (ASCQ) follow. The same information is presented in 2ASC and ASCQ in numerical order. ASC and ASCQ in alphabetical order by description. Douglas Gilbert. READ CAPACITY failure looks like a very generic, target side,Are you sure FreeNAS support devices that large. On Sun, 2017-10-22 at 02:13 -0200, Elias Pereira wrote. Note that the return code can sometimes appear truncated, that is has less than 4 parts, as leading zeros are sometimes suppressed when output. In this case the scsi status byte will be the default value of 00 but that doesn't mean a successful scsi command status in this case. The following information is a synopsis of what these status mean: CHECK CONDITION 02 Indicates a contingent allegiance condition has occurred (see sense buffer for more details) CONDITION MET 04 Requested operation is satisfied. BUSY 08 Indicates the target is busy. Returned whenever a target is unable to accept a command from an otherwise acceptable initiator. INTERMEDIATE 10 Shall be returned for every successfully completed command in a series of linked commands (except the last command) INTERMEDIATE-CONDITION MET 14 Combination of CONDITION MET and INTERMEDIATE status's. RESERVATION CONFLICT 18 Logical unit or an extent (portion) within the logical unit is reserved for another device. This also indicates that a contingent allegiance condition has occurred. QUEUE FULL ( TASK SET FULL ) 28 Shall be implemented if tagged command queuing is supported. Indicated that the target command queue is full. ACA ACTIVE 30 Indicates an auto contingent allegiance condition exists. All other codes Reserved. The Blue ones are rarely seen. The Red ones are very uncommon and almost never are seen.