Apb r error code 9

apb r error code 9

Other requests shall be referred to APWAL / MLTN, WrightPatterson APB James N.; Hall, Eugena R.; MeDaniol, Dolorı Navy Training Feedback and. Test your connection fast with Xfinity's internet speed test tool and get tips on how to improve your internet performance. 101B will not appear in the Code of Explanation of Provisions Federal of a Registrant When Adopted in the term " error " as used in APB Opinion No.

Apb r error code 9 - idea necessary

1

I

A hard disk has been placed online.

Rebuild completed. Device was configured. Manual online was done.

None

2

I

A hard disk added as hot spare.

Device was configured. Manual hot spare was done. Automatic hot spare was done. `Raidbld' made it hot spare.

None

3

W

Hard disk error found.

A bad sector was found on the physical media. Mechanical failure on the device. Host SCSI device detected illegal instruction. Target device generated unknown phase sequence.

If problem occurs frequently, replace the device or contact service representative.

4

W

Hard disk PFA condition found, this disk may fail soon.

Physical device predicted some future failure. External RAID logical device may have become critical.

Follow device vendor's defined action.

5

I

An automatic rebuild has started.

A physical device failed and spare was available. A physical device failed and no spare was available. A spare was added.

None

6

I

A rebuild has started.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

7

I

Rebuild is over.

Rebuild completed successfully.

None

8

W

Rebuild is cancelled.

User cancelled the rebuild. Higher priority rebuild started.

Restart the rebuild if required.

9

E

Rebuild stopped with error.

Due to some unknown error on the controller, rebuild failed.

Try rebuild again.

10

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device may not be compatible with MDCA hardware/firmware.

Replace the physical device.

11

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array. Bad data table overflow.

It may not be possible to recover from this error. Contact your service representative.

12

S

A hard disk has failed.

A physical device failed. A user action caused the physical device to fail.

Replace the physical device.

13

I

A new hard disk has been found.

A physical device has been powered on. A new physical device has been added. Controller was powered on. Controller was added. System has rebooted.

None

14

I

A hard disk has been removed.

User removed an unconfigured physical device. An unconfigured physical device failed. A controller was removed. A controller powered off.

Replace the device if needed.

15

I

A previously configured disk is now available.

User set the physical device to unconfigured.

None

16

I

Expand Capacity started.

User started the RAID Expansion operation. A suspended RAID Expansion operation was started.

None

17

I

Expand Capacity completed.

RAID Expansion finished.

None

18

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

19

W

SCSI command time out on hard device.

Physical device has been removed. Physical device failed. Command timeout value is not correct.

None

20

C

SCSI command abort on hard disk.

User may have requested to abort the command. Firmware may have aborted the command to recover from error. The device may have aborted the command.

None

21

W

SCSI command retried on hard disk.

The command may have timed out. Bus reset may have occurred. Device reset may have occurred.

None

22

W

Parity error found.

A physical device did not generate proper parity. The controller failed, did not check parity properly. Cable failed. Improper cable length. Another physical device interfered. Some outside environment affected the data on the cable (for example, radio frequency signal). Terminator is not connected. Improper termination.

It may not be possible to recover from this error. Contact your service representative.

23

W

Soft error found.

An error was detected by physical device and data was recovered.

Run consistency check. If problem occurs frequently, replace the physical device.

24

W

Misc error found.

A physical device reported some error, which does not fit in any category. Read/Write command timeout. Data over run. Physical device was busy when host attempted to send command.

If problem occurs frequently, replace the physical device.

25

I

SCSI device reset.

Firmware has done reset to recover from error. User has done a reset.

None

26

I

Active spare found.

Device was configured. Manual active spare was done. Automatic active spare was done.

None

27

I

Warm spare found.

Device was configured. Manual warm spare was done. Automatic warm spare was done.

None

28

E

Request sense data available.

A physical device reported an error. Firmware reported an operational error.

Read the request sense data to understand the root cause.

29

I

Initialization started.

Host started the initialization.

Wait until the initialization is completed. If the system is shutdown prior to this process being completed, the physical device can be made useful only by reinitializing it.

30

I

Initialization completed.

Physical device initialization completed successfully.

None

31

W

Initialization failed.

Physical device could have problems supporting the SCSI format command.

Try to initialize again. Contact your service representative.

32

S

Initialization cancelled.

User cancelled the operation.

Hard disk must be initialized again or the hard disk cannot be used.

33

S

A hard disk failed because write recovery failed.

Write recovery process failed.

Replace hard disk and rebuild it.

34

S

A hard disk failed because SCSI bus reset failed.

SCSI bus reset failed.

Replace hard disk and rebuild it.

35

S

A hard disk failed because double check condition occurred.

Double check condition occurred.

Replace hard disk and rebuild it.

36

S

A hard disk failed because device is missing.

Access to the hard disk failed.

Replace hard disk and rebuild it.

37

S

A hard disk failed because of gross error on SCSI processor.

Gross error occurred to the on-board SCSI processor.

Replace hard disk and rebuild it.

38

S

A hard disk failed because of bad tag from the device.

The device responded with an invalid tag.

Replace hard disk and rebuild it.

39

S

A hard disk failed because command to the device timed out.

SCSI command timed out on the device.

Replace hard disk and rebuild it.

40

S

A hard disk failed because of the system reset.

System reset occurred.

Replace hard disk and rebuild it.

41

S

A hard disk failed because of busy status or parity error.

The device returned busy status. The SCSI transaction with the device met with parity error.

Replace hard disk and rebuild it.

42

S

A hard disk set to failed state by host.

Command from host set the hard disk to failed state.

Replace hard disk and rebuild it.

43

S

A hard disk failed because access to the device met with a selection time out.

Device disconnected or powered off. Bad device.

Replace hard disk and rebuild it. Check power and cabling.

44

S

A hard disk failed because of a sequence error in the SCSI bus phase handling.

Bad hard disk.

Replace hard disk and rebuild it.

45

S

A hard disk failed because returned an unknown status.

Bad hard disk or incompatible device.

Replace hard disk or the device and rebuild it.

46

S

A hard disk failed because device is not ready.

Device not spinning, just turned bad. Power to the device failed.

Replace hard disk and rebuild it. Check power and rebuild device.

47

S

A hard disk failed because device was not found on startup.

Device not connected. Device not responding. Clear configuration suspend mode command was invoked.

Check setup. Check the startup option parameters on the system.

48

S

A hard disk failed because write operation of the `Configuration On Disk' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

49

S

A hard disk failed because write operation of `Bad Data Table' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

50

W

Physical device status changed to offline.

None

51

I

Physical device status changed to Hot Spare.

None

52

W

Physical device status changed to rebuild.

None

53

W

Physical device ID did not match.

None

54

E

Physical device failed to start.

Reset the physical disk. Replace the disk.

55

W

Physical device negotiated different offset than configuration.

None

56

W

Physical device negotiated different bus width than configuration.

None

57

S

Physical drive missing on startup.

Physical drive missing.

Replace the physical drive or power on all enclosures.

58

E

Rebuild startup failed due to lower disk capacity.

Device capacity not sufficient for doing rebuild.

Replace with a disk having sufficient capacity.

59

W

Physical drive is switching from a channel to the other channel.

Physical drive removed or channel failed.

None

60

E

Temporary-Dead physical drive is automatically made online.

Temporary-Dead state caused because of transient errors.

Analyze event log to find out why the drive was marked DEAD.

61

I

A standby rebuild was started.

A physical device failed and spare was available.

None

62

I

Hot spare replaced with a smaller capacity physical disk.

The new hot spare may have a smaller physical capacity than the physical disk it replaced. The controller coercion setting may have reduced the configurable size of the new hot spare.

None

67

E

Physical disk found on only one disk channel.

Physical disk is connected on only one channel.

Inspect disk channel cables and related hardware for proper operation.

69

E

Physical disk has acquired an inappropriate loop ID. Enclosure disk-slot operations are disabled while this condition persists.

Enclosure selector switch conflict. Physical disk hardware failure. Enclosure disk slot hardware failure.

Ensure that each disk enclosure selector switch is set to a unique number per enclosure manufacturer specification. Inspect physical disk connector. Power-cycle entire system. Replace physical disk. Replace disk enclosure.

70

E

Physical disk port has failed or cannot operate at the configured channel speed.

Physical disk hardware failure. Physical disk is not compatible with system. Enclosure disk slot hardware failure.

Replace physical disk. Replace disk enclosure.

71

E

Mirror race recovery failed for logical drive.

A read or write operation to a physical disk failed while restoring redundancy.

Run consistency check and restore consistency.

72

E

Controller parameters checksum verification failed; restored default.

NVRAM battery low. NVRAM hardware failure. Improper shutdown of the controller during controller parameter update.

Restore correct controller parameter settings. If problem persists, replace controller.

73

I

Online controller firmware upgrade has started.

User has initiated an online firmware upgrade.

None

74

I

Online controller firmware upgrade has completed successfully.

Online controller firmware upgrade has completed without error. The partner controller will now be auto flashed.

None

75

E

Online controller firmware upgrade has failed.

Online controller firmware upgrade has failed. The original firmware will be reloaded.

Use the offline method to load the new firmware.

76

I

A COD with unsupported features has been detected.

Firmware does not support certain features in that COD. COD import is to wrong system COD data is sequestered.

Obtain compatible firmware then reimport the COD or import the COD to a different system

77

I

A new battery was found.

Battery present in the controller could be a new or a replaced unit.

None

78

S

Battery backup unit charger error.

Battery backup unit failure. Hardware problems in battery backup unit.

Replace the battery, or replace the battery backup unit hardware, or if the problem persists contact your service representative.

79

S

Battery will not hold a charge.

Battery failure.

Have your supplier replace the battery.

80

S

Firmware entered unexpected state at run-time.

Memory corruption. Hardware returned unexpected value.

If the controller stops responding reboot and try again. If problem persists contact your service representative.

81

I

Rebuild stopped on controller failure.

Rebuild moved to the surviving controller because the partner, which was running the rebuild, failed.

None

82

E

Check Consistency stopped on controller failure.

Check Consistency failed because the partner, which was running the Check Consistency, failed.

Restart the consistency check.

83

E

Foreground initialization stopped on controller failure.

Foreground initialization failed because the partner, which was running the foreground initialization, failed.

Restart the foreground initialization.

84

I

Background initialization stopped on controller failure.

Background initialization restarted on the surviving controller because the partner, which was running the background initialization, failed.

None

85

I

Configuration group not installed due to physical disk conflict.

Physical disk already configured in another group. Unable to map a physical device in this group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

86

I

Configuration group not installed due to logical drive conflict.

Logical drive already configured in another group. Unable to install all the logical drives in the group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

87

I

Configuration group not installed due to SAN Map conflict.

SAN Map conflicted with that of another installed group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

88

I

Foreign configuration group not installed.

Foreign COD Group found but not installed.

Move to another controller. Remove native configuration group and reboot with foreign group.

89

I

No configuration group installed.

All configuration groups are foreign and clash. Controllers may have changed.

Move to another controller. Re-insert original controllers or remove some groups and reboot with one group.

96

S

Device loop ID conflict (soft addressing) detected.

Device loop ID conflict detected on disk channel resulting in soft addressing; potential data corruption.

Change index selector to enable hard addressing per enclosure manufacturer's specification.

97

I

One or more transport Fibre channel CRC errors occurred during data transfer to/from the physical device in the last hour.

Physical devices were installed or removed causing momentary fibre channel loop disruption. Cabling or associated fibre channel hardware is faulty.

Unless the problem occurs frequently, action is not required.

98

I

The host fibre channel is down.

Host fibre channel device (cable, server, switch, hub, host adapter) has failed. Host fibre channel interface on the controller has failed.

Inspect host fibre channel cables and associated hardware.

99

I

The host fibre channel is up.

The host fibre channel loop initialized successfully.

None

100

I

Redundant access restored on physical disk.

Physical disk is now accessible on both disk channels.

Check I/O modules and back-end connections if disk frequently loses redundant accessibility.

101

I

Started to loop through each drive for predicted failure analysis.

Controller started a predicted failure analysis on disk drives.

None

102

I

Finished predicted failure analysis on each drive.

Controller finished predicted failure analysis.

None

103

I

Background patrol was started or resumed.

Background patrol started.

None

104

I

Background patrol has found no more drives or was commanded to stop.

Background patrol finished or stopped.

None

128

N

Consistency check is started.

User started a consistency check. `Raidbld' started consistency check.

None

129

I

Consistency check is finished.

Consistency check completed successfully without detecting any errors.

None

130

E

Consistency check is cancelled.

User cancelled the consistency check.

Restart consistency check, if required.

131

E

Consistency check on logical drive error.

Inconsistent data was found. Bad sectors were found. A physical device reliability problem.

See bad block and request sense table for more information.

132

E

Consistency check on logical drive failed.

A logical device became critical. A logical device failed.

See request sense data for more information.

133

S

Consistency check failed due to physical device failure.

A physical device failed.

See request sense data for more information.

134

S

Logical drive has been made offline.

One/multiple physical device(s) failed.

It may not be possible to recover from this error. Contact your service representative.

135

E

Logical device is critical.

One physical device failed.

Replace the physical device. Start the rebuild, if required.

136

I

Logical drive has been placed online.

Rebuild completed. User set the physical device online. New configuration was added.

None

137

I

An automatic rebuild has started on logical drive.

A physical device failed and a spare device was available. A spare physical device was found and replaced the failed device.

None

138

I

A manual rebuild has started on logical drive.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

139

I

Rebuild on logical drive is over.

Rebuild completed successfully only for this logical drive.

None

140

W

Rebuild on logical drive is cancelled.

User cancelled rebuild. Higher priority rebuild started.

Restart the rebuild if required.

141

E

Rebuild stopped with error.

Due to an unknown error on the controller rebuild failed.

Try rebuild again.

142

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device is not compatible with MDAC hardware/firmware.

Replace the new device.

143

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array.

It may not be possible to recover from this error. Contact your service representative.

144

I

Logical drive initialization started.

User started the initialization.

Any previous data is lost.

145

I

Logical drive initialization done.

Initialize operation completed successfully.

None

146

W

Logical drive initialization cancelled.

User cancelled the initialization.

Restart initialization if required.

147

E

Logical drive initialization failed.

One/multiple physical device(s) failed. Controller has been removed. Controller has been powered off.

Refer to the device failure event.

148

I

A logical drive has been found.

A new configuration has been added. MORE completed. A new controller has been plugged in. Controller has been powered on. System has rebooted.

None

149

I

A logical drive has been deleted.

A new configuration has been added. A new logical device has been deleted. Controller has been removed. Controller has been powered off.

None

150

I

Expand Capacity started.

User started the Online RAID Expansion operation.

None

151

I

Expand Capacity completed.

Online RAID Expansion completed.

None

152

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

153

C

Bad blocks found.

Bad sector was found on a physical device during consistency check/rebuild/RAID expansion operation.

Run a Consistency Check with the Restore option. Restore data from a backup.

154

I

System drive (LUN) size changed.

A new configuration has been added. RAID Expansion has added extra capacity.

None

155

I

System drive type changed.

A new configuration has been added. RAID Expansion completed on RAID 1.

None

156

S

Bad data blocks found. Possible data loss.

Bad blocks were found on multiple physical devices in same zone.

Restore data from a backup.

157

W

System drive LUN mapping has been written to config.

None

158

S

Attempt to read data from block that is marked in Bad Data Table.

Potential data loss.

Restore data from a backup.

159

E

Data for Disk Block has been lost due to Logical Drive problem.

Data retained in RAID Cache for a Write-back Logical Drive cannot be stored to the physical medium because of Logical Drive problem. The Logical Drive problem could be because of multiple physical devices offline or other reasons.

Insure that all the Physical Drives related to the Logical Drive, disk channel, enclosure, or cabling are functional and accessible. Repair or replace them if necessary.

160

E

Temporary-Offline RAID5/RAID3 array is available to the user again with the possibility of data loss in the array.

Temporary-Offline state caused because of transient errors in physical drives.

Verify data from backup.

161

E

Temporary-Offline RAID0+1/RAID1/RAID 0/JBOD array is available to the user again.

Temporary-Offline state caused because of transient errors in physical drives.

None

162

I

A standby rebuild has started on logical drive.

A physical drive failed and a spare device was available.

None

176

I

Logical drive background initialization started.

User may have started background initialization. Firmware may have automatically started background initialization.

None

177

I

Logical drive background initialization stopped.

User may have stopped background initialization. Firmware may have automatically stopped background initialization.

None

178

I

Logical drive background initialization paused.

Background initialization paused due to a higher priority operation.

None

179

I

Logical drive background initialization restarted.

Background initialization started after being paused.

None

180

I

Logical drive background initialization failed.

Background initialization failed.

None

181

I

Logical drive background initialization completed.

Background initialization completed successfully.

None

182

E

Low battery charge level. Logical drive may have lost data.

Controller was powered off for duration longer than battery capacity. User connected a new controller. User connected a new BBU battery.

Run consistency check to verify logical drive consistency. If needed, restore data from backup.

256

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

257

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

258

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

259

I

Storage cabinet fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

272

S

Power supply failure.

Cable connection is broken. Bad power supply.

Reconnect cable or replace the power supply as required.

273

I

Power supply has been restored.

Faulty power supply has been replaced.

None

274

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace power supply.

275

I

Storage cabinet power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

288

S

Over temperature. Temperature is above 70 degrees Celsius.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

289

W

Temperature is above 50 degrees Celsius.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

290

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

291

S

Over temperature.

Room temperature is too high. Bad fan.

Turn off the system and allow it to cool down. Adjust the room temperature.

292

I

Storage cabinet temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

304

S

Enclosure reported failure state.

Power supply failed. Fan failed. Cabinet is too hot.

Follow enclosure management vendor's diagnostics and repair procedures.

305

W

Enclosure reported critical state.

Not available.

Not available.

306

I

Storage Works enclosure reported normal state.

Problem has been rectified.

None

307

I

Uninterruptible power supply disabled.

None

308

I

Uninterruptible power supply AC failed.

None

309

W

Uninterruptible power supply battery low.

None

310

S

Uninterruptible power supply failed.

None

311

I

Uninterruptible power supply normal.

None

320

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

321

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

322

I

Fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

323

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace the power supply.

324

I

Power supply has been restored.

Faulty power supply has been replaced.

None

325

I

Power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

326

S

Temperature is over safe limit. Failure imminent.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

327

W

Temperature is above working limit.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

328

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

329

I

Temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

330

W

Enclosure access critical.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

331

I

Enclosure access has been restored.

Enclosure has been fixed or replaced.

None

332

S

Enclosure access is offline.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

333

S

Enclosure Soft Addressing Detected.

Enclosure has duplicate loop ids (Soft Addressing). Potential data corruption.

Change index selector to enable hard addressing as per enclosure manufacturer's specification.

334

I

Enclosure services ready.

None

335

I

Access to temperature sensor has been lost.

Switch card or temperature sensor has been removed.

None

336

I

Access to power supply status information has been lost.

Switch card or connectivity has been removed.

None

337

I

Access to fan status information has been lost. Switch card or connectivity has been removed.

None

384

I

Array management server software started successfully.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

385

E

Write back error.

Data cache write failed.

The data may have been lost. Restore the data from a backup.

386

W

Internal log structures getting full; PLEASE SHUTDOWN AND RESET THE SYSTEM IN THE NEAR FUTURE.

Too many configuration changes occurred since the last boot.

Reboot the system by power cycling whenever convenient.

388

C

Controller is dead. System is disconnecting from this controller.

Contact your service representative.

389

W

Controller has been reset.

Controller failed. Controller was removed from the system. Controller has been powered off.

None

390

I

Controller is found.

Driver has reset the controller to recover from an error. Driver has reset the controller to activate new firmware.

None

391

C

Controller is gone. System is disconnecting from this controller.

New controller has been installed. Controller has been powered on. System has rebooted.

None

392

I

BBU Present.

Controller is dead. Controller has been removed. Controller has been powered off.

None

393

W

BBU Power Low.

A BBU unit was found on the controller.

If this message occurs without power failure, replace the BBU.

394

I

BBU Power OK.

BBU does not have enough power to enable the write data cache.

None

395

C

Controller is gone. System is disconnecting from this controller.

BBU has enough power to enable the write data cache.

None

396

I

Controller powered on.

Controller was removed from the system. Controller has been powered off.

None

397

I

Controller is online.

New controller has been installed.

None

398

C

Controller is gone. System is disconnecting from this controller.

Controller was set online.

None

399

W

Controller's partner is gone, controller is in failover mode now.

Controller was set offline.

If you did not expect this, investigate.

400

I

BBU reconditioning is started.

User started a BBU reconditioning.

None

401

I

BBU reconditioning is finished.

BBU reconditioning completed successfully.

None

402

I

BBU reconditioning is cancelled.

User cancelled the BBU reconditioning.

Restart the BBU reconditioning, if required.

403

S

Installation aborted.

Installation aborted.

404

S

Controller firmware mismatch.

Replacement controller with downlevel firmware installed.

Reload controller firmware.

405

W

BBU removed.

BBU physically removed.

Reinstall BBU.

406

S

WARM BOOT failed.

Memory error detected during WARM boot scan. Possible data loss.

Restore data from a backup.

407

I

BBU calibration cycle started.

New battery detected.

None

408

I

BBU calibration cycle finished.

BBU calibration completed successfully.

None

409

I

BBU calibration cycle is cancelled.

User cancelled the BBU calibration cycle.

None

410

I

BBU battery not present.

A BBU is present, but the battery is not detected.

Install or connect the battery.

411

W

Controller entered Conservative Cache Mode.

None

412

W

Controller entered normal cache mode.

None

413

W

Controller device start complete.

None

414

W

Soft ECC error corrected.

Faulty memory module.

Replace memory module.

415

W

Hard ECC error corrected.

Faulty memory module.

Replace memory module.

416

S

BBU recondition needed.

None

417

W

Controller's partner has been removed.

None

418

E

BBU out of service.

BBU will not be able to power the cache if AC power fails. Firmware will switch WriteBack logical drives to WriteThrough.

Replace BBU.

419

W

Updated partner's status.

None

420

W

Relinquished partner.

None

421

W

Inserted partner.

None

422

W

Dual controllers enabled.

None

423

W

Killed partner.

None

424

W

Dual controllers entered nexus.

None

425

S

Controller boot ROM image needs to be reloaded.

Wrong firmware image file downloaded. MAC address changed.

Contact your service representative to reload the boot ROM image.

426

C

Controller is using default non-unique world-wide name.

MAC address lost or not set.

Contact your service representative to set the controller MAC address.

427

E

Mirror Race recovery failed.

Some physical devices could have failed.

Run consistency check and restore consistency.

428

C

Mirror Race on critical drive.

Logical device is critical.

Replace dead drive and rebuild.

512

I

System started.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

513

I

Size table full.

Too much physical device size information is defined.

Remove unused device information for this system.

514

I

User logged in.

An array management utility user logged in on the server system.

Not available.

515

I

User logged out.

An array management utility user logged out of the server system.

Not available.

516

I

Server alive.

Reconnected to server. Server rebooted.

None

517

S

Lost connection to server, or server is down.

Lost network connection to server. Server shutdown.

None

518

I

Automatic reboot count has changed.

Controller has rebooted. Automatic reboot has rearmed itself or was reconfigured.

None

640

W

Channel failed.

Cable disconnected.

Plug in cable.

641

W

Channel online.

Cable reconnected.

None

642

S

Back end SCSI bus dead.

Lost access to data on SCSI bus.

LRC module may need replacing.

643

I

Back end SCSI bus alive.

Regained access to data on SCSI bus.

None

644

S

Back end fibre dead.

Lost access to data on fibre channel.

LRC module may need replacing.

645

I

Back end fibre alive.

Regained access to data on fibre channel.

None

700

W

Event log empty.

Tried to read past last entry.

None

701

W

Event log entries lost.

Tried to read an entry that does not exist in the event log.

None

702

W

Request sense.

A physical drive has generated an error.

Interpret the Key/ASC/ASCQ and take appropriate action.

703

W

Set real time clock.

Real time clock was set.

None

800

W

New configuration received.

A new configuration was downloaded to controller.

None

801

W

Configuration cleared.

Controller was told to clear the configuration.

None

802

W

Configuration invalid.

The controller found an invalid configuration.

None

803

W

Configuration on disk access error.

The controller could not read the configuration off of the disk.

None

804

W

Configuration on disk converted.

The controller converted a down level configuration on disk.

None

805

W

Configuration on disk import failed.

The controller could not import the configuration.

None

806

I

A debug dump exists on this system.

The controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

807

I

A debug dump exists on this system.

The partner controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

896

S

Internal controller is in the hung state.

Power controller off and on.

897

S

Introller controller has encountered a firmware breakpoint.

Power controller off and on.

912

S

Internal controller has encountered i960 processor specific error.

Power controller off and on.

928

S

Internal controller has encountered Strong-ARM processor specific error.

Power controller off and on.

929

S

Internal controller back end hardware error.

Timeout waiting for interrupt. Timeout waiting for command completion.

Power controller off and on.

Talk:APB: All Points Bulletin

removed[edit]

removed discussion about the game 80.192.61.220 00:47, 1 April 2007 (UTC)Reply[reply]

why? 216.234.58.18 15:20, 23 October 2007 (UTC)Reply[reply]

removed comment about original GTA not being 3D, removed speculation that APB was inspired by the earlier game from Atari with the same name. I work on the game and it wasn't.RobertAnderberg 00:49, 3 June 2007 (UTC)Reply[reply]

whole page is written like an advertisement.. somebody fix it, i can't be bothered. 222.153.154.182 (talk) 02:09, 22 January 2008 (UTC)Reply[reply]

Release Date[edit]

IGN say for the PC it is out in Japan on 31st december 2007 and 2007 in USA but unreleased in Europe. Xbox360 dates are all 2008, anyone know anything there is so many rumors going on about this game and this article is so small and it shouldnt be. —Preceding unsigned comment added by Andrew22k (talk • contribs) 13:10, 8 December 2007 (UTC)Reply[reply]

http://www.mcvuk.com/news/35129/APB-hits-retail-in-March Ne specific release date but it will be in March of 2010. And that article shps that it is being released for the 360 if any clarification was needed. UltimateSin01 (talk) 11:41, 23 July 2009 (UTC)Reply[reply]

concerned about copyvio[edit]

much of this article seems to have been lifted verbatim directly from http://www.apb-evolved.com. I'm also not sure if they are an appropriate reference site for information. Xenocidic (talk) 15:31, 22 January 2008 (UTC)Reply[reply]

I wrote the site's administrators about the content and received an email back from them "Thanks for the notice, as long as the information is given credit towards the site we are ok with it.". So I will work on ensuring the proper citations are given. I will also try to clean up the text to sound more encyclopaedic. Xenocidic (talk) 16:29, 22 January 2008 (UTC)Reply[reply]
This is why the whole article looks like an ad... it is just the PR text from the game's web page. I just saw the a talk on this game at GDC 2008, and the game looks lame. This whole article was probably made by someone who's working on it. YAWN. —Preceding unsigned comment added by Farktol (talk • contribs) 20:07, 22 February 2008 (UTC)Reply[reply]
actually it was lifted from a fan site. the article definately needs a lot of work. xenocidic (talk) 20:10, 22 February 2008 (UTC)Reply[reply]

Ext. Links[edit]

Do not remove link to the only APB forums, apb-evolved.com —Preceding unsigned comment added by 68.10.225.15 (talk • contribs)

I've removed the particular external link, until a concensus is reached. StaticGull Talk  11:12, 1 May 2008 (UTC)Reply[reply]
I'm typically against these types of links but in the case of apb-evolved.com, I'd be willing to let it stand for a few reasons: 1) it's not completely ad-laden and the ads that they have are unobtrusive. 2) there's not much info out there in the wild about this game, and this site is a pretty good resource for it, and 3) this article used to be a complete copy-vio cut and paste from apb-evolved and they let us keep it up as long as we linked to them (since it's no longer copy-vio, we're not bound to this, but it would be a courtesy). xenocidic (talk) 12:46, 1 May 2008 (UTC)Reply[reply]


All of your facts are true, but considering the very lack of community forums, and the news of this site providing constant indirect content towards the site. We should be able to give a link to this site, at least until the official forums open up. Many of the developers support, and are on this website and should be counted as semi-official. —Preceding unsigned comment added by 68.10.225.15 (talk) 11:00, 2 May 2008 (UTC)Reply[reply]

Please do not modify the external links section, APB-Evolved is added as a community forums until an official forums goes online. This is a rare exception, please fansites, guilds, and other unofficial sites please do not edit this area. —Preceding unsigned comment added by 68.10.225.15 (talk) 02:37, 18 August 2008 (UTC)Reply[reply]

-Agreed, ill keep a watch on this. - BlueFlamez

That site is no longer the only APB forum so it should no longer be listed. The newer site APBForums.com is also supported by the developers and not "ad-laden". In my opinion now that there is another forum exceptions should either be made for both or neither sites should be listed here. - nekon

Forums, official or not, are not appropriate external links for any article, (see WP:VG/EL). --MASEM 03:59, 18 August 2008 (UTC)Reply[reply]

Then like I said neither site should be listed, I've read the guidelines and they're clear. No forums in external links, no exceptions. Now lets take that link down. -nekon—Preceding unsigned comment added by Nekon (talk • contribs) 04:07, 18 August 2008 (UTC)Reply[reply]

That's fine, I was simply following a previously agreed terms discussed here. If we all agree since there are more than one forums neither should be allowed. - Blueflamez—Preceding unsigned comment added by 68.10.225.15 (talk) 12:32, 18 August 2008 (UTC)Reply[reply]

Not acceptable by whom? Wikapedia is a resource location allowing those who are interested in a topic to learn more about it. Apb-evolved.com has ALL of the current information released to the public on it, more than APB.com, Realtimeworlds website and APBforums.com combined. Not to mention the fact that its own Dev team including Chris Ulric community manager continue to use it to send out announcments. In fact, before the Register your interest page went up, APB-evolved.com was the only means of communication to the fans. I realise that APBforums.com doesnt want APB-evolved.com advertised as it lessens the likelyhood they will accrue members however we are supposed to be "supporting" the fans, not the Webmasters in need of members and so as it stands APB-evolved offers the most comprehensive database of information & collective fans in one place and until the APB official forums go up and innevitably change this it should stay. What is the negative impact on the Fan/User going to be if that link is there over what the postive will be? —Preceding unsigned comment added by 195.224.121.210 (talk) 12:15, 1 September 2008 (UTC)Reply[reply]

I think that one of the primary confusions here is that APB Evolved is being referred to solely as a forum, which it is not. It is a considerable news source which includes many updates not included through the developers' own website. And that's before you even get on the forum. So, the forum is simply one element of a larger site. Having a forum attached to a site does not qualify that site as a forum. Also, as has alreay been said, the website has a long standing relationship with the development team blurring the lines between fansite and official news source. As a closing point, it is utterly nonsensical and silly to refuse to include APB Evolved, which does have considerable info and has been publicly accepted by the developers while including the IGN page which has only one interview (which IGN did) and otherwise minimal and outdated info. We have to get this together and it least be sensible if we are going to follow rules somewhat arbitrarily. -CAWH —Preceding unsigned comment added by 98.218.174.19 (talk) 19:38, 15 August 2009 (UTC)Reply[reply]

Old APB[edit]

Er, wasn't there an APB video game in the 80s? I seem to remember seeing one for C64 (though I don't know enough about it to add anything useful to the article). --taras (talk) 13:41, 3 May 2008 (UTC)Reply[reply]

Fixed. They aren't related, so a dablink is enough. xenocidic (talk) 11:08, 5 May 2008 (UTC)Reply[reply]

Gameplay infomation[edit]

Hi, I thought I would post some stuff that could be possibly written in to one of the articles someday, all the things I put here are things that have come from RTW which they said would be in the game. I will update when more info is released each month in their newsletter.

This is an excerpt from Here: http://www.apb-evolved.com/news/53-apb-september-update

Idea already implemented: Arrest / Capture system

Enforcers have an arrest system available to them which serves to take out a criminal player until they are freed or the arrest timer expires and they must respawn as if killed. This can reduce the criminal force for longer periods of time than killing them would unless freed by their criminal group-mates.86.134.253.171 (talk) 19:41, 10 December 2008 (UTC)Reply[reply]

Please Read[edit]

Please stop putting Xbox 360 as a confirmed platform and putting out of date info on here, it has not been confirmed as a platform the game will be on yet, seriously I keep having to change it back. —Preceding unsigned comment added by Lilolirocksursocks (talk • contribs) 19:08, 25 May 2009 (UTC)Reply[reply]

Xbox 360?[edit]

On the official website they say, and I quote,

"Q: Will there be console ports? Or a Linux or Mac client?


A: We’re just starting to evaluate opportunities for a console port but do not have anything to announce yet."

This conflicts with the information wikipedia gives. —Preceding unsigned comment added by Jayrossss (talk • contribs) 19:47, 10 June 2009 (UTC)Reply[reply]

Indeed... But see the teamxbox article... I wish they would make up their mind. Anyhow, maybe this helps. –xenotalk 19:51, 10 June 2009 (UTC)Reply[reply]

It says they are developing it, not releasing it, they might just be starting to develop it to see if it is a good idea to release on the Xbox 360 then later if it goes well and works good then they will release it, the fact is is that they didn't say release they said develop. I don't know if any of that made sense but I hope I got my point across.Lilolirocksursocks (talk) 20:48, 14 June 2009 (UTC)Reply[reply]

payment[edit]

will have to pay a fee? thanks... —Preceding unsigned comment added by 69.110.69.39 (talk) 21:24, 13 July 2009 (UTC)Reply[reply]

It's unknown yet, hopefully not, because otherwise I'm not getting this game, I saw something that hinted that there wouldn't be any fees, but nothing official has been announced yet I don't think. —Preceding unsigned comment added by Lilolirocksursocks (talk • contribs) 09:33, 22 July 2009 (UTC)Reply[reply]

The official word is that there will not be a monthly fee. However, there is absolutely no info on the payment method. In fact, the most recent interview with David Jones says that they may not truly decide the payment method until the beta gets going. They want to feel out how people play it first. -CAWH

It has tough been confirmed that you need to buy game in stores before you can play it. Eibx (talk) 19:52, 17 August 2009 (UTC)Reply[reply]

History[edit]

I think the History section needs a clean up, or a new rewriting. I'll do my best. - Eibx 21:56, 17 September 2009 (UTC)Reply[reply]

MMO?[edit]

The article seems to state you can interact with up to 25 players. I fail to see how a 26 player game is massive in any way, shape or form, when many other games, who do not bear the MMO genre, can support more players than this game will (BF2/2142 are 40 player capable I believe).

I wish developers would understand that having a monthly fee, being multiplayer only and having elements of persistance does not make their game MMOs. The main characteristic of MMOs is the word MASSIVE. No massive amount of players = not an MMO.

At the time massive multiplayer games came around, the phrase was used to describe games than contained a number of players way above the normal 4 players, which was very common at the time. APB is a MMO, since the description of what is Massive and what is not, is very unclear.- Eibx 01:24, 23 October 2009 (UTC)Reply[reply]

I believe this game needs to have it's article edited into the "MOG" genre. —Preceding unsigned comment added by 70.83.54.70 (talk) 22:40, 16 October 2009 (UTC)Reply[reply]

When you sign in, you will have to choose an instance of a world you want to play on. These worlds can contain about a 100 players. An unlimited number of instances can be made in theory. What is meant by interaction, is basically you will not be shooting at more than 25 people at a time. - Eibx 01:19, 23 October 2009 (UTC)Reply[reply]
This is true. Also, the closed beta date is very incorrect and I will not correct it. 91.105.133.73 (talk) 17:54, 14 March 2010 (UTC)Reply[reply]

Well the trailer says that the scale is much bigger than this. It states, "100 players to a city," and "100,000 players to a world." So I'm quite certain this means up to 100 players in an instance. 216.185.250.92 (talk) 00:59, 3 February 2010 (UTC)Reply[reply]

There were plans for servers where all 100 people could square off against each other, however, the ruleset was never implemented. There were also times in the game where you could kill any other player indiscriminantly. It was an MMO. Anyone of those 100 people could get in your way and mess up your mission even if they couldn't directly kill you. —Preceding unsigned comment added by 208.107.164.144 (talk) 22:59, 4 October 2010 (UTC)Reply[reply]

Development Costs[edit]

If someone can check the veracity of http://brokentoys.org/2010/08/20/apb-how-to-blow-100000000-00/, we might have something worth writing about here. --71.240.46.168 (talk) 03:48, 22 August 2010 (UTC)Reply[reply]

End[edit]

http://www.joystiq.com/2010/09/16/apb-comes-to-a-premature-end/—Preceding unsigned comment added by 173.168.239.69 (talk) 16:18, 16 September 2010 (UTC)Reply[reply]

Was vs Is[edit]

Games should be marked as was as the servers are shut down game is no longer playable. Games are not always marked as present tense see matrix online entry if they are no longer playable. —Preceding unsigned comment added by 81.131.103.156 (talk) 19:31, 5 October 2010 (UTC)Reply[reply]

I agree if the servers are shut then the game is no longer playable so should be referred to in past tense. —Preceding unsigned comment added by 90.196.77.229 (talk) 21:53, 8 October 2010 (UTC)Reply[reply]

The game has been created therefore it exists. Present tense is correct. Whether it is playable or not is a different argument. Only when every remnant of the game code has been deleted from existence can it be said that the game no longer exists and therefore becomes past tense. - X201 (talk) 09:53, 9 October 2010 (UTC)Reply[reply]

Why is matrix online marked as was then? also if a game is not playable it is no longer a game but just a mess of code lying somewhere. —Preceding unsigned comment added by 90.200.224.161 (talk) 19:12, 9 October 2010 (UTC)Reply[reply]

There are old films and TV programmes on archive shelves that aren't currently being broadcast. They don't stop existing just because they aren't being broadcast, likewise, games don't stop existing just because they aren't being played. - X201 (talk) 10:38, 10 October 2010 (UTC)Reply[reply]

but a game is something that can be played, if its not playable its not a game, so it does not exist as a game, especially as an mmo until the servers are turned back on. By definition it cannot be a mmo if no-one can play it. —Preceding unsigned comment added by 86.165.96.58 (talk) 12:34, 11 October 2010 (UTC)Reply[reply]

This IP is correct here, only due to this being an MMO. Half the game exists on a server you need to connect to. If that server is not there, it is unplayable - that is, it is no longer a game, simply a pile of executable code that will not do anything for the user. --MASEM (t) 14:00, 11 October 2010 (UTC)Reply[reply]
Seeing as how private servers will always keep popping up, APB one here, any MMO server will never truly be a "was", as there is always a chance of its fans keeping it alive. I think the best compromise would be for a form of wording such as "Game X is a 2010 something game, that had its online service terminated in 2011". I still think that for any hardware or software we should use "is", since the game code still exists.- X201 (talk) 14:26, 11 October 2010 (UTC)Reply[reply]

Article rewrite to accommodate re-release[edit]

Wondering if this article as a whole or specific sections might need to be rewritten so that newer readers won't become confused. For instance, the embargo controversy is no longer relevant since the game is being re-released and K2/Gamers First aren't responsible, but I am not saying that this section should be outright removed. —Preceding unsigned comment added by 198.85.208.101 (talk) 23:58, 27 January 2011 (UTC)Reply[reply]

Engine[edit]

the game runs on a modified Unreal Engine 2

Quote: Denn obwohl APB auf einer abgewandelten und arg angestaubten Unreal Engine 2 basiert, frisst das Actionspiel Hardware zum Frühstück.

Source: Gamestar.de (a well-known professional gaming related magazine in germany) -> http://www.gamestar.de/spiele/all-points-bulletin-reloaded/artikel/technik_check_apb,45066,2316165.html

APB from Spectrum[edit]

APB (All Points Bulletin) Its an old game from Spectrum Synclair computers.Main page dont tell anything about this.

APB reloaded its based on that videogame. — Preceding unsigned comment added by 84.122.250.171 (talk) 19:03, 13 September 2012 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on APB: All Points Bulletin. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

checkYAn editor has reviewed this edit and fixed any errors that were found.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 02:26, 16 January 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on APB: All Points Bulletin. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

☒NAn editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the to true

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 01:48, 1 March 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 07:27, 1 October 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 03:40, 24 June 2017 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 01:46, 19 September 2017 (UTC)Reply[reply]

Register Map and Descriptions

The registers are accessible through the APB target interface. The following table lists all the registers required to execute system services on PolarFire devices.

Address OffsetRegister NameTypeWidthReset ValueDescription
0x04SYS_SERV_CMDR/W320Request Command
0x08SYS_SERV_STATR/O320Response Status
0x0CSYS_SERV_REQR/W320Control Register
0x10MBX_ECCSTATUSR/O320Mailbox ECC Status
0x14MBX_WCNTR/W32‘d1Mailbox Write Count
0x18MBX_RCNTR/W32‘d1Mailbox Read Count
0x1CMBX_WADRDESCR/W320Mailbox Write Address Descriptor
0x20MBX_RADRDESCR/W320Mailbox Read Address Descriptor
0x28MBX_WDATAR/W320Mailbox Write Data
0x2CMBX_RDATAR/O320Mailbox Read Data
0x30SYS_SERV_USERR/O320System Service User

JTAG Status and Error Status - 2022.1 English

159:155RSVD_READS_0Reserved, returns 0154:148RESERVEDReserved147:136BOOTROM FIRST ERRORBootROM first error code (FEC) detected 135:124BOOTROM LAST ERRORBootROM last error code (LEC) detected 123:110PLM MAJOR ERRORPLM major error code109:94PLM MINOR ERRORPLM minor error code93:64GSW ERRORGeneral software error code for PLM63RESERVEDReserved62BOOTROM NCRBootROM non-correctable error

Set by RCU BootROM during boot

61PLM CRPlatform loader and manager boot correctable error

Set by PLM during boot

60PLM NCRPlatform loader and manager boot non-correctable error

Set by PLM during boot

59GSW CRGeneral software correctable error after boot58GSW NCRGeneral software non-correctable error after boot57CFU ERRORCFU error 56CFRAME ERRORCFRAME error55PSM CRPSM correctable error54PSM NCRPSM non-correctable error 53DDRMC MB CRDDRMC MicroBlaze correctable ECC error 52DDRMC MB NCRDDRMC MicroBlaze non-correctable ECC error51NOC CRNoC correctable error50NOC NCRNoC non-correctable error49NOC USER ERRORNoC user error48MMCM LOCK ERRORMMCM lock error47AIE CRAI Engine correctable error46AIE NCRAI Engine non-correctable error45DDRMC MC ECC CRDDRMC MC (memory controller) correctable ECC error 44DDRMC MC ECC NCRDDRMC MC (memory controller) non-correctable ECC error43GT CR GT correctable error42GT NCRGT non-correctable error41SYSMON CRSYSMON correctable error40SYSMON NCRSYSMON non-correctable error39USER PL0 ERRORUser-defined PL error38USER PL1 ERRORUser-defined PL error37USER PL2 ERRORUser-defined PL error36USER PL3 ERRORUser-defined PL error35NPI ROOT ERRORNPI root error34SSIT ERROR3SSI technology SLR error33SSIT ERROR4SSI technology SLR error32SSIT ERROR5SSI technology SLR error31PMC APB ERRORPMC APB error. Includes errors from registers: PMC_LOCAL, PMC_GLOBAL, CRP, PMC_IOP_SECURE_SLCR, PMC_IOP, BBRAM_CTRL, PMC_ANLG, RTC30PMC BOOTROM ERRORPMC BootROM validation error29RCU HARDWARE ERRORRCU hardware error 28PPU HARDWARE ERRORPPU hardware error27PMC PAR ERRORPMC switch and PMC IOP parity errors26PMC CRPMC correctable errors 25PMC NCRPMC non-correctable errors24PMC SYSMON0 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON23PMC SYSMON1 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON22PMC SYSMON2 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON21PMC SYSMON3 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON20PMC SYSMON4 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON19PMC SYSMON5 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON18PMC SYSMON6 ALARM PMC temperature shutdown alert and power supply failure detection errors from SYSMON17PMC SYSMON7 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON16PMC SYSMON8 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON15PMC SYSMON9 ALARM PMC temperature shutdown alert and power supply failure detection errors from SYSMON14CFI NCRCFI non-correctable error13SEU CRC ERRORSEU CRC error12SEU ECC ERRORSEU ECC error11:10RSVD_READS_0Reserved, returns 09RTC ALARM RTC alarm error8NPLL ERRORPMC NPLL lock error 7PPLL ERRORPMC PPLL lock error6CLOCK MONITOR ERRORClock monitor errors 5PMC TIMEOUT ERRORPMC interconnect timeout errors from interconnect mission interrupt status register, interconnect latent status register, and timeout interrupt status register4PMC XMPU ERRORPMC XMPU errors from register access error on APB. Includes read permission violation, write permission violation or security violation3PMC XPPU ERRORPMC XPPU errors from register access error on APB. Includes Master ID not found, read permission violation, Master ID access violation, Master ID parity error, TrustZone violation2SSIT ERROR0SSI technology SLR error1SSIT ERROR1SSI technology SLR error0SSIT ERROR2SSI technology SLR error

Apb r error code 9 - consider, what

JTAG Status and Error Status - 2022.1 English

159:155RSVD_READS_0Reserved, returns 0154:148RESERVEDReserved147:136BOOTROM FIRST ERRORBootROM first error code (FEC) detected 135:124BOOTROM LAST ERRORBootROM last error code (LEC) detected 123:110PLM MAJOR ERRORPLM major error code109:94PLM MINOR ERRORPLM minor error code93:64GSW ERRORGeneral software error code for PLM63RESERVEDReserved62BOOTROM NCRBootROM non-correctable error

Set by RCU BootROM during boot

61PLM CRPlatform loader and manager boot correctable error

Set by PLM during boot

60PLM NCRPlatform loader and manager boot non-correctable error

Set by PLM during boot

59GSW CRGeneral software correctable error after boot58GSW NCRGeneral software non-correctable error after boot57CFU ERRORCFU error 56CFRAME ERRORCFRAME error55PSM CRPSM correctable error54PSM NCRPSM non-correctable error 53DDRMC MB CRDDRMC MicroBlaze correctable ECC error 52DDRMC MB NCRDDRMC MicroBlaze non-correctable ECC error51NOC CRNoC correctable error50NOC NCRNoC non-correctable error49NOC USER ERRORNoC user error48MMCM LOCK ERRORMMCM lock error47AIE CRAI Engine correctable error46AIE NCRAI Engine non-correctable error45DDRMC MC ECC CRDDRMC MC (memory controller) correctable ECC error 44DDRMC MC ECC NCRDDRMC MC (memory controller) non-correctable ECC error43GT CR GT correctable error42GT NCRGT non-correctable error41SYSMON CRSYSMON correctable error40SYSMON NCRSYSMON non-correctable error39USER PL0 ERRORUser-defined PL error38USER PL1 ERRORUser-defined PL error37USER PL2 ERRORUser-defined PL error36USER PL3 ERRORUser-defined PL error35NPI ROOT ERRORNPI root error34SSIT ERROR3SSI technology SLR error33SSIT ERROR4SSI technology SLR error32SSIT ERROR5SSI technology SLR error31PMC APB ERRORPMC APB error. Includes errors from registers: PMC_LOCAL, PMC_GLOBAL, CRP, PMC_IOP_SECURE_SLCR, PMC_IOP, BBRAM_CTRL, PMC_ANLG, RTC30PMC BOOTROM ERRORPMC BootROM validation error29RCU HARDWARE ERRORRCU hardware error 28PPU HARDWARE ERRORPPU hardware error27PMC PAR ERRORPMC switch and PMC IOP parity errors26PMC CRPMC correctable errors 25PMC NCRPMC non-correctable errors24PMC SYSMON0 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON23PMC SYSMON1 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON22PMC SYSMON2 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON21PMC SYSMON3 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON20PMC SYSMON4 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON19PMC SYSMON5 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON18PMC SYSMON6 ALARM PMC temperature shutdown alert and power supply failure detection errors from SYSMON17PMC SYSMON7 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON16PMC SYSMON8 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON15PMC SYSMON9 ALARM PMC temperature shutdown alert and power supply failure detection errors from SYSMON14CFI NCRCFI non-correctable error13SEU CRC ERRORSEU CRC error12SEU ECC ERRORSEU ECC error11:10RSVD_READS_0Reserved, returns 09RTC ALARM RTC alarm error8NPLL ERRORPMC NPLL lock error 7PPLL ERRORPMC PPLL lock error6CLOCK MONITOR ERRORClock monitor errors 5PMC TIMEOUT ERRORPMC interconnect timeout errors from interconnect mission interrupt status register, interconnect latent status register, and timeout interrupt status register4PMC XMPU ERRORPMC XMPU errors from register access error on APB. Includes read permission violation, write permission violation or security violation3PMC XPPU ERRORPMC XPPU errors from register access error on APB. Includes Master ID not found, read permission violation, Master ID access violation, Master ID parity error, TrustZone violation2SSIT ERROR0SSI technology SLR error1SSIT ERROR1SSI technology SLR error0SSIT ERROR2SSI technology SLR error

Talk:APB: All Points Bulletin

removed[edit]

removed discussion about the game 80.192.61.220 00:47, 1 April 2007 (UTC)Reply[reply]

why? 216.234.58.18 15:20, 23 October 2007 (UTC)Reply[reply]

removed comment about original GTA not being 3D, removed speculation that APB was inspired by the earlier game from Atari with the same name. I work on the game and it wasn't.RobertAnderberg 00:49, 3 June 2007 (UTC)Reply[reply]

whole page is written like an advertisement.. somebody fix it, i can't be bothered. 222.153.154.182 (talk) 02:09, 22 January 2008 (UTC)Reply[reply]

Release Date[edit]

IGN say for the PC it is out in Japan on 31st december 2007 and 2007 in USA but unreleased in Europe. Xbox360 dates are all 2008, anyone know anything there is so many rumors going on about this game and this article is so small and it shouldnt be. —Preceding unsigned comment added by Andrew22k (talk • contribs) 13:10, 8 December 2007 (UTC)Reply[reply]

http://www.mcvuk.com/news/35129/APB-hits-retail-in-March Ne specific release date but it will be in March of 2010. And that article shps that it is being released for the 360 if any clarification was needed. UltimateSin01 (talk) 11:41, 23 July 2009 (UTC)Reply[reply]

concerned about copyvio[edit]

much of this article seems to have been lifted verbatim directly from http://www.apb-evolved.com. I'm also not sure if they are an appropriate reference site for information. Xenocidic (talk) 15:31, 22 January 2008 (UTC)Reply[reply]

I wrote the site's administrators about the content and received an email back from them "Thanks for the notice, as long as the information is given credit towards the site we are ok with it.". So I will work on ensuring the proper citations are given. I will also try to clean up the text to sound more encyclopaedic. Xenocidic (talk) 16:29, 22 January 2008 (UTC)Reply[reply]
This is why the whole article looks like an ad... it is just the PR text from the game's web page. I just saw the a talk on this game at GDC 2008, and the game looks lame. This whole article was probably made by someone who's working on it. YAWN. —Preceding unsigned comment added by Farktol (talk • contribs) 20:07, 22 February 2008 (UTC)Reply[reply]
actually it was lifted from a fan site. the article definately needs a lot of work. xenocidic (talk) 20:10, 22 February 2008 (UTC)Reply[reply]

Ext. Links[edit]

Do not remove link to the only APB forums, apb-evolved.com —Preceding unsigned comment added by 68.10.225.15 (talk • contribs)

I've removed the particular external link, until a concensus is reached. StaticGull Talk  11:12, 1 May 2008 (UTC)Reply[reply]
I'm typically against these types of links but in the case of apb-evolved.com, I'd be willing to let it stand for a few reasons: 1) it's not completely ad-laden and the ads that they have are unobtrusive. 2) there's not much info out there in the wild about this game, and this site is a pretty good resource for it, and 3) this article used to be a complete copy-vio cut and paste from apb-evolved and they let us keep it up as long as we linked to them (since it's no longer copy-vio, we're not bound to this, but it would be a courtesy). xenocidic (talk) 12:46, 1 May 2008 (UTC)Reply[reply]


All of your facts are true, but considering the very lack of community forums, and the news of this site providing constant indirect content towards the site. We should be able to give a link to this site, at least until the official forums open up. Many of the developers support, and are on this website and should be counted as semi-official. —Preceding unsigned comment added by 68.10.225.15 (talk) 11:00, 2 May 2008 (UTC)Reply[reply]

Please do not modify the external links section, APB-Evolved is added as a community forums until an official forums goes online. This is a rare exception, please fansites, guilds, and other unofficial sites please do not edit this area. —Preceding unsigned comment added by 68.10.225.15 (talk) 02:37, 18 August 2008 (UTC)Reply[reply]

-Agreed, ill keep a watch on this. - BlueFlamez

That site is no longer the only APB forum so it should no longer be listed. The newer site APBForums.com is also supported by the developers and not "ad-laden". In my opinion now that there is another forum exceptions should either be made for both or neither sites should be listed here. - nekon

Forums, official or not, are not appropriate external links for any article, (see WP:VG/EL). --MASEM 03:59, 18 August 2008 (UTC)Reply[reply]

Then like I said neither site should be listed, I've read the guidelines and they're clear. No forums in external links, no exceptions. Now lets take that link down. -nekon—Preceding unsigned comment added by Nekon (talk • contribs) 04:07, 18 August 2008 (UTC)Reply[reply]

That's fine, I was simply following a previously agreed terms discussed here. If we all agree since there are more than one forums neither should be allowed. - Blueflamez—Preceding unsigned comment added by 68.10.225.15 (talk) 12:32, 18 August 2008 (UTC)Reply[reply]

Not acceptable by whom? Wikapedia is a resource location allowing those who are interested in a topic to learn more about it. Apb-evolved.com has ALL of the current information released to the public on it, more than APB.com, Realtimeworlds website and APBforums.com combined. Not to mention the fact that its own Dev team including Chris Ulric community manager continue to use it to send out announcments. In fact, before the Register your interest page went up, APB-evolved.com was the only means of communication to the fans. I realise that APBforums.com doesnt want APB-evolved.com advertised as it lessens the likelyhood they will accrue members however we are supposed to be "supporting" the fans, not the Webmasters in need of members and so as it stands APB-evolved offers the most comprehensive database of information & collective fans in one place and until the APB official forums go up and innevitably change this it should stay. What is the negative impact on the Fan/User going to be if that link is there over what the postive will be? —Preceding unsigned comment added by 195.224.121.210 (talk) 12:15, 1 September 2008 (UTC)Reply[reply]

I think that one of the primary confusions here is that APB Evolved is being referred to solely as a forum, which it is not. It is a considerable news source which includes many updates not included through the developers' own website. And that's before you even get on the forum. So, the forum is simply one element of a larger site. Having a forum attached to a site does not qualify that site as a forum. Also, as has alreay been said, the website has a long standing relationship with the development team blurring the lines between fansite and official news source. As a closing point, it is utterly nonsensical and silly to refuse to include APB Evolved, which does have considerable info and has been publicly accepted by the developers while including the IGN page which has only one interview (which IGN did) and otherwise minimal and outdated info. We have to get this together and it least be sensible if we are going to follow rules somewhat arbitrarily. -CAWH —Preceding unsigned comment added by 98.218.174.19 (talk) 19:38, 15 August 2009 (UTC)Reply[reply]

Old APB[edit]

Er, wasn't there an APB video game in the 80s? I seem to remember seeing one for C64 (though I don't know enough about it to add anything useful to the article). --taras (talk) 13:41, 3 May 2008 (UTC)Reply[reply]

Fixed. They aren't related, so a dablink is enough. xenocidic (talk) 11:08, 5 May 2008 (UTC)Reply[reply]

Gameplay infomation[edit]

Hi, I thought I would post some stuff that could be possibly written in to one of the articles someday, all the things I put here are things that have come from RTW which they said would be in the game. I will update when more info is released each month in their newsletter.

This is an excerpt from Here: http://www.apb-evolved.com/news/53-apb-september-update

Idea already implemented: Arrest / Capture system

Enforcers have an arrest system available to them which serves to take out a criminal player until they are freed or the arrest timer expires and they must respawn as if killed. This can reduce the criminal force for longer periods of time than killing them would unless freed by their criminal group-mates.86.134.253.171 (talk) 19:41, 10 December 2008 (UTC)Reply[reply]

Please Read[edit]

Please stop putting Xbox 360 as a confirmed platform and putting out of date info on here, it has not been confirmed as a platform the game will be on yet, seriously I keep having to change it back. —Preceding unsigned comment added by Lilolirocksursocks (talk • contribs) 19:08, 25 May 2009 (UTC)Reply[reply]

Xbox 360?[edit]

On the official website they say, and I quote,

"Q: Will there be console ports? Or a Linux or Mac client?


A: We’re just starting to evaluate opportunities for a console port but do not have anything to announce yet."

This conflicts with the information wikipedia gives. —Preceding unsigned comment added by Jayrossss (talk • contribs) 19:47, 10 June 2009 (UTC)Reply[reply]

Indeed... But see the teamxbox article... I wish they would make up their mind. Anyhow, maybe this helps. –xenotalk 19:51, 10 June 2009 (UTC)Reply[reply]

It says they are developing it, not releasing it, they might just be starting to develop it to see if it is a good idea to release on the Xbox 360 then later if it goes well and works good then they will release it, the fact is is that they didn't say release they said develop. I don't know if any of that made sense but I hope I got my point across.Lilolirocksursocks (talk) 20:48, 14 June 2009 (UTC)Reply[reply]

payment[edit]

will have to pay a fee? thanks... —Preceding unsigned comment added by 69.110.69.39 (talk) 21:24, 13 July 2009 (UTC)Reply[reply]

It's unknown yet, hopefully not, because otherwise I'm not getting this game, I saw something that hinted that there wouldn't be any fees, but nothing official has been announced yet I don't think. —Preceding unsigned comment added by Lilolirocksursocks (talk • contribs) 09:33, 22 July 2009 (UTC)Reply[reply]

The official word is that there will not be a monthly fee. However, there is absolutely no info on the payment method. In fact, the most recent interview with David Jones says that they may not truly decide the payment method until the beta gets going. They want to feel out how people play it first. -CAWH

It has tough been confirmed that you need to buy game in stores before you can play it. Eibx (talk) 19:52, 17 August 2009 (UTC)Reply[reply]

History[edit]

I think the History section needs a clean up, or a new rewriting. I'll do my best. - Eibx 21:56, 17 September 2009 (UTC)Reply[reply]

MMO?[edit]

The article seems to state you can interact with up to 25 players. I fail to see how a 26 player game is massive in any way, shape or form, when many other games, who do not bear the MMO genre, can support more players than this game will (BF2/2142 are 40 player capable I believe).

I wish developers would understand that having a monthly fee, being multiplayer only and having elements of persistance does not make their game MMOs. The main characteristic of MMOs is the word MASSIVE. No massive amount of players = not an MMO.

At the time massive multiplayer games came around, the phrase was used to describe games than contained a number of players way above the normal 4 players, which was very common at the time. APB is a MMO, since the description of what is Massive and what is not, is very unclear.- Eibx 01:24, 23 October 2009 (UTC)Reply[reply]

I believe this game needs to have it's article edited into the "MOG" genre. —Preceding unsigned comment added by 70.83.54.70 (talk) 22:40, 16 October 2009 (UTC)Reply[reply]

When you sign in, you will have to choose an instance of a world you want to play on. These worlds can contain about a 100 players. An unlimited number of instances can be made in theory. What is meant by interaction, is basically you will not be shooting at more than 25 people at a time. - Eibx 01:19, 23 October 2009 (UTC)Reply[reply]
This is true. Also, the closed beta date is very incorrect and I will not correct it. 91.105.133.73 (talk) 17:54, 14 March 2010 (UTC)Reply[reply]

Well the trailer says that the scale is much bigger than this. It states, "100 players to a city," and "100,000 players to a world." So I'm quite certain this means up to 100 players in an instance. 216.185.250.92 (talk) 00:59, 3 February 2010 (UTC)Reply[reply]

There were plans for servers where all 100 people could square off against each other, however, the ruleset was never implemented. There were also times in the game where you could kill any other player indiscriminantly. It was an MMO. Anyone of those 100 people could get in your way and mess up your mission even if they couldn't directly kill you. —Preceding unsigned comment added by 208.107.164.144 (talk) 22:59, 4 October 2010 (UTC)Reply[reply]

Development Costs[edit]

If someone can check the veracity of http://brokentoys.org/2010/08/20/apb-how-to-blow-100000000-00/, we might have something worth writing about here. --71.240.46.168 (talk) 03:48, 22 August 2010 (UTC)Reply[reply]

End[edit]

http://www.joystiq.com/2010/09/16/apb-comes-to-a-premature-end/—Preceding unsigned comment added by 173.168.239.69 (talk) 16:18, 16 September 2010 (UTC)Reply[reply]

Was vs Is[edit]

Games should be marked as was as the servers are shut down game is no longer playable. Games are not always marked as present tense see matrix online entry if they are no longer playable. —Preceding unsigned comment added by 81.131.103.156 (talk) 19:31, 5 October 2010 (UTC)Reply[reply]

I agree if the servers are shut then the game is no longer playable so should be referred to in past tense. —Preceding unsigned comment added by 90.196.77.229 (talk) 21:53, 8 October 2010 (UTC)Reply[reply]

The game has been created therefore it exists. Present tense is correct. Whether it is playable or not is a different argument. Only when every remnant of the game code has been deleted from existence can it be said that the game no longer exists and therefore becomes past tense. - X201 (talk) 09:53, 9 October 2010 (UTC)Reply[reply]

Why is matrix online marked as was then? also if a game is not playable it is no longer a game but just a mess of code lying somewhere. —Preceding unsigned comment added by 90.200.224.161 (talk) 19:12, 9 October 2010 (UTC)Reply[reply]

There are old films and TV programmes on archive shelves that aren't currently being broadcast. They don't stop existing just because they aren't being broadcast, likewise, games don't stop existing just because they aren't being played. - X201 (talk) 10:38, 10 October 2010 (UTC)Reply[reply]

but a game is something that can be played, if its not playable its not a game, so it does not exist as a game, especially as an mmo until the servers are turned back on. By definition it cannot be a mmo if no-one can play it. —Preceding unsigned comment added by 86.165.96.58 (talk) 12:34, 11 October 2010 (UTC)Reply[reply]

This IP is correct here, only due to this being an MMO. Half the game exists on a server you need to connect to. If that server is not there, it is unplayable - that is, it is no longer a game, simply a pile of executable code that will not do anything for the user. --MASEM (t) 14:00, 11 October 2010 (UTC)Reply[reply]
Seeing as how private servers will always keep popping up, APB one here, any MMO server will never truly be a "was", as there is always a chance of its fans keeping it alive. I think the best compromise would be for a form of wording such as "Game X is a 2010 something game, that had its online service terminated in 2011". I still think that for any hardware or software we should use "is", since the game code still exists.- X201 (talk) 14:26, 11 October 2010 (UTC)Reply[reply]

Article rewrite to accommodate re-release[edit]

Wondering if this article as a whole or specific sections might need to be rewritten so that newer readers won't become confused. For instance, the embargo controversy is no longer relevant since the game is being re-released and K2/Gamers First aren't responsible, but I am not saying that this section should be outright removed. —Preceding unsigned comment added by 198.85.208.101 (talk) 23:58, 27 January 2011 (UTC)Reply[reply]

Engine[edit]

the game runs on a modified Unreal Engine 2

Quote: Denn obwohl APB auf einer abgewandelten und arg angestaubten Unreal Engine 2 basiert, frisst das Actionspiel Hardware zum Frühstück.

Source: Gamestar.de (a well-known professional gaming related magazine in germany) -> http://www.gamestar.de/spiele/all-points-bulletin-reloaded/artikel/technik_check_apb,45066,2316165.html

APB from Spectrum[edit]

APB (All Points Bulletin) Its an old game from Spectrum Synclair computers.Main page dont tell anything about this.

APB reloaded its based on that videogame. — Preceding unsigned comment added by 84.122.250.171 (talk) 19:03, 13 September 2012 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on APB: All Points Bulletin. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

checkYAn editor has reviewed this edit and fixed any errors that were found.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 02:26, 16 January 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on APB: All Points Bulletin. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

☒NAn editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the to true

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 01:48, 1 March 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 07:27, 1 October 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 03:40, 24 June 2017 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 01:46, 19 September 2017 (UTC)Reply[reply]

1

I

A hard disk has been placed online.

Rebuild completed. Device was configured. Manual online was done.

None

2

I

A hard disk added as hot spare.

Device was configured. Manual hot spare was done. Automatic hot spare was done. `Raidbld' made it hot spare.

None

3

W

Hard disk error found.

A bad sector was found on the physical media. Mechanical failure on the device. Host SCSI device detected illegal instruction. Target device generated unknown phase sequence.

If problem occurs frequently, replace the device or contact service representative.

4

W

Hard disk PFA condition found, this disk may fail soon.

Physical device predicted some future failure. External RAID logical device may have become critical.

Follow device vendor's defined action.

5

I

An automatic rebuild has started.

A physical device failed and spare was available. A physical device failed and no spare was available. A spare was added.

None

6

I

A rebuild has started.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

7

I

Rebuild is over.

Rebuild completed successfully.

None

8

W

Rebuild is cancelled.

User cancelled the rebuild. Higher priority rebuild started.

Restart the rebuild if required.

9

E

Rebuild stopped with error.

Due to some unknown error on the controller, rebuild failed.

Try rebuild again.

10

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device may not be compatible with MDCA hardware/firmware.

Replace the physical device.

11

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array. Bad data table overflow.

It may not be possible to recover from this error. Contact your service representative.

12

S

A hard disk has failed.

A physical device failed. A user action caused the physical device to fail.

Replace the physical device.

13

I

A new hard disk has been found.

A physical device has been powered on. A new physical device has been added. Controller was powered on. Controller was added. System has rebooted.

None

14

I

A hard disk has been removed.

User removed an unconfigured physical device. An unconfigured physical device failed. A controller was removed. A controller powered off.

Replace the device if needed.

15

I

A previously configured disk is now available.

User set the physical device to unconfigured.

None

16

I

Expand Capacity started.

User started the RAID Expansion operation. A suspended RAID Expansion operation was started.

None

17

I

Expand Capacity completed.

RAID Expansion finished.

None

18

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

19

W

SCSI command time out on hard device.

Physical device has been removed. Physical device failed. Command timeout value is not correct.

None

20

C

SCSI command abort on hard disk.

User may have requested to abort the command. Firmware may have aborted the command to recover from error. The device may have aborted the command.

None

21

W

SCSI command retried on hard disk.

The command may have timed out. Bus reset may have occurred. Device reset may have occurred.

None

22

W

Parity error found.

A physical device did not generate proper parity. The controller failed, did not check parity properly. Cable failed. Improper cable length. Another physical device interfered. Some outside environment affected the data on the cable (for example, radio frequency signal). Terminator is not connected. Improper termination.

It may not be possible to recover from this error. Contact your service representative.

23

W

Soft error found.

An error was detected by physical device and data was recovered.

Run consistency check. If problem occurs frequently, replace the physical device.

24

W

Misc error found.

A physical device reported some error, which does not fit in any category. Read/Write command timeout. Data over run. Physical device was busy when host attempted to send command.

If problem occurs frequently, replace the physical device.

25

I

SCSI device reset.

Firmware has done reset to recover from error. User has done a reset.

None

26

I

Active spare found.

Device was configured. Manual active spare was done. Automatic active spare was done.

None

27

I

Warm spare found.

Device was configured. Manual warm spare was done. Automatic warm spare was done.

None

28

E

Request sense data available.

A physical device reported an error. Firmware reported an operational error.

Read the request sense data to understand the root cause.

29

I

Initialization started.

Host started the initialization.

Wait until the initialization is completed. If the system is shutdown prior to this process being completed, the physical device can be made useful only by reinitializing it.

30

I

Initialization completed.

Physical device initialization completed successfully.

None

31

W

Initialization failed.

Physical device could have problems supporting the SCSI format command.

Try to initialize again. Contact your service representative.

32

S

Initialization cancelled.

User cancelled the operation.

Hard disk must be initialized again or the hard disk cannot be used.

33

S

A hard disk failed because write recovery failed.

Write recovery process failed.

Replace hard disk and rebuild it.

34

S

A hard disk failed because SCSI bus reset failed.

SCSI bus reset failed.

Replace hard disk and rebuild it.

35

S

A hard disk failed because double check condition occurred.

Double check condition occurred.

Replace hard disk and rebuild it.

36

S

A hard disk failed because device is missing.

Access to the hard disk failed.

Replace hard disk and rebuild it.

37

S

A hard disk failed because of gross error on SCSI processor.

Gross error occurred to the on-board SCSI processor.

Replace hard disk and rebuild it.

38

S

A hard disk failed because of bad tag from the device.

The device responded with an invalid tag.

Replace hard disk and rebuild it.

39

S

A hard disk failed because command to the device timed out.

SCSI command timed out on the device.

Replace hard disk and rebuild it.

40

S

A hard disk failed because of the system reset.

System reset occurred.

Replace hard disk and rebuild it.

41

S

A hard disk failed because of busy status or parity error.

The device returned busy status. The SCSI transaction with the device met with parity error.

Replace hard disk and rebuild it.

42

S

A hard disk set to failed state by host.

Command from host set the hard disk to failed state.

Replace hard disk and rebuild it.

43

S

A hard disk failed because access to the device met with a selection time out.

Device disconnected or powered off. Bad device.

Replace hard disk and rebuild it. Check power and cabling.

44

S

A hard disk failed because of a sequence error in the SCSI bus phase handling.

Bad hard disk.

Replace hard disk and rebuild it.

45

S

A hard disk failed because returned an unknown status.

Bad hard disk or incompatible device.

Replace hard disk or the device and rebuild it.

46

S

A hard disk failed because device is not ready.

Device not spinning, just turned bad. Power to the device failed.

Replace hard disk and rebuild it. Check power and rebuild device.

47

S

A hard disk failed because device was not found on startup.

Device not connected. Device not responding. Clear configuration suspend mode command was invoked.

Check setup. Check the startup option parameters on the system.

48

S

A hard disk failed because write operation of the `Configuration On Disk' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

49

S

A hard disk failed because write operation of `Bad Data Table' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

50

W

Physical device status changed to offline.

None

51

I

Physical device status changed to Hot Spare.

None

52

W

Physical device status changed to rebuild.

None

53

W

Physical device ID did not match.

None

54

E

Physical device failed to start.

Reset the physical disk. Replace the disk.

55

W

Physical device negotiated different offset than configuration.

None

56

W

Physical device negotiated different bus width than configuration.

None

57

S

Physical drive missing on startup.

Physical drive missing.

Replace the physical drive or power on all enclosures.

58

E

Rebuild startup failed due to lower disk capacity.

Device capacity not sufficient for doing rebuild.

Replace with a disk having sufficient capacity.

59

W

Physical drive is switching from a channel to the other channel.

Physical drive removed or channel failed.

None

60

E

Temporary-Dead physical drive is automatically made online.

Temporary-Dead state caused because of transient errors.

Analyze event log to find out why the drive was marked DEAD.

61

I

A standby rebuild was started.

A physical device failed and spare was available.

None

62

I

Hot spare replaced with a smaller capacity physical disk.

The new hot spare may have a smaller physical capacity than the physical disk it replaced. The controller coercion setting may have reduced the configurable size of the new hot spare.

None

67

E

Physical disk found on only one disk channel.

Physical disk is connected on only one channel.

Inspect disk channel cables and related hardware for proper operation.

69

E

Physical disk has acquired an inappropriate loop ID. Enclosure disk-slot operations are disabled while this condition persists.

Enclosure selector switch conflict. Physical disk hardware failure. Enclosure disk slot hardware failure.

Ensure that each disk enclosure selector switch is set to a unique number per enclosure manufacturer specification. Inspect physical disk connector. Power-cycle entire system. Replace physical disk. Replace disk enclosure.

70

E

Physical disk port has failed or cannot operate at the configured channel speed.

Physical disk hardware failure. Physical disk is not compatible with system. Enclosure disk slot hardware failure.

Replace physical disk. Replace disk enclosure.

71

E

Mirror race recovery failed for logical drive.

A read or write operation to a physical disk failed while restoring redundancy.

Run consistency check and restore consistency.

72

E

Controller parameters checksum verification failed; restored default.

NVRAM battery low. NVRAM hardware failure. Improper shutdown of the controller during controller parameter update.

Restore correct controller parameter settings. If problem persists, replace controller.

73

I

Online controller firmware upgrade has started.

User has initiated an online firmware upgrade.

None

74

I

Online controller firmware upgrade has completed successfully.

Online controller firmware upgrade has completed without error. The partner controller will now be auto flashed.

None

75

E

Online controller firmware upgrade has failed.

Online controller firmware upgrade has failed. The original firmware will be reloaded.

Use the offline method to load the new firmware.

76

I

A COD with unsupported features has been detected.

Firmware does not support certain features in that COD. COD import is to wrong system COD data is sequestered.

Obtain compatible firmware then reimport the COD or import the COD to a different system

77

I

A new battery was found.

Battery present in the controller could be a new or a replaced unit.

None

78

S

Battery backup unit charger error.

Battery backup unit failure. Hardware problems in battery backup unit.

Replace the battery, or replace the battery backup unit hardware, or if the problem persists contact your service representative.

79

S

Battery will not hold a charge.

Battery failure.

Have your supplier replace the battery.

80

S

Firmware entered unexpected state at run-time.

Memory corruption. Hardware returned unexpected value.

If the controller stops responding reboot and try again. If problem persists contact your service representative.

81

I

Rebuild stopped on controller failure.

Rebuild moved to the surviving controller because the partner, which was running the rebuild, failed.

None

82

E

Check Consistency stopped on controller failure.

Check Consistency failed because the partner, which was running the Check Consistency, failed.

Restart the consistency check.

83

E

Foreground initialization stopped on controller failure.

Foreground initialization failed because the partner, which was running the foreground initialization, failed.

Restart the foreground initialization.

84

I

Background initialization stopped on controller failure.

Background initialization restarted on the surviving controller because the partner, which was running the background initialization, failed.

None

85

I

Configuration group not installed due to physical disk conflict.

Physical disk already configured in another group. Unable to map a physical device in this group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

86

I

Configuration group not installed due to logical drive conflict.

Logical drive already configured in another group. Unable to install all the logical drives in the group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

87

I

Configuration group not installed due to SAN Map conflict.

SAN Map conflicted with that of another installed group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

88

I

Foreign configuration group not installed.

Foreign COD Group found but not installed.

Move to another controller. Remove native configuration group and reboot with foreign group.

89

I

No configuration group installed.

All configuration groups are foreign and clash. Controllers may have changed.

Move to another controller. Re-insert original controllers or remove some groups and reboot with one group.

96

S

Device loop ID conflict (soft addressing) detected.

Device loop ID conflict detected on disk channel resulting in soft addressing; potential data corruption.

Change index selector to enable hard addressing per enclosure manufacturer's specification.

97

I

One or more transport Fibre channel CRC errors occurred during data transfer to/from the physical device in the last hour.

Physical devices were installed or removed causing momentary fibre channel loop disruption. Cabling or associated fibre channel hardware is faulty.

Unless the problem occurs frequently, action is not required.

98

I

The host fibre channel is down.

Host fibre channel device (cable, server, switch, hub, host adapter) has failed. Host fibre channel interface on the controller has failed.

Inspect host fibre channel cables and associated hardware.

99

I

The host fibre channel is up.

The host fibre channel loop initialized successfully.

None

100

I

Redundant access restored on physical disk.

Physical disk is now accessible on both disk channels.

Check I/O modules and back-end connections if disk frequently loses redundant accessibility.

101

I

Started to loop through each drive for predicted failure analysis.

Controller started a predicted failure analysis on disk drives.

None

102

I

Finished predicted failure analysis on each drive.

Controller finished predicted failure analysis.

None

103

I

Background patrol was started or resumed.

Background patrol started.

None

104

I

Background patrol has found no more drives or was commanded to stop.

Background patrol finished or stopped.

None

128

N

Consistency check is started.

User started a consistency check. `Raidbld' started consistency check.

None

129

I

Consistency check is finished.

Consistency check completed successfully without detecting any errors.

None

130

E

Consistency check is cancelled.

User cancelled the consistency check.

Restart consistency check, if required.

131

E

Consistency check on logical drive error.

Inconsistent data was found. Bad sectors were found. A physical device reliability problem.

See bad block and request sense table for more information.

132

E

Consistency check on logical drive failed.

A logical device became critical. A logical device failed.

See request sense data for more information.

133

S

Consistency check failed due to physical device failure.

A physical device failed.

See request sense data for more information.

134

S

Logical drive has been made offline.

One/multiple physical device(s) failed.

It may not be possible to recover from this error. Contact your service representative.

135

E

Logical device is critical.

One physical device failed.

Replace the physical device. Start the rebuild, if required.

136

I

Logical drive has been placed online.

Rebuild completed. User set the physical device online. New configuration was added.

None

137

I

An automatic rebuild has started on logical drive.

A physical device failed and a spare device was available. A spare physical device was found and replaced the failed device.

None

138

I

A manual rebuild has started on logical drive.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

139

I

Rebuild on logical drive is over.

Rebuild completed successfully only for this logical drive.

None

140

W

Rebuild on logical drive is cancelled.

User cancelled rebuild. Higher priority rebuild started.

Restart the rebuild if required.

141

E

Rebuild stopped with error.

Due to an unknown error on the controller rebuild failed.

Try rebuild again.

142

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device is not compatible with MDAC hardware/firmware.

Replace the new device.

143

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array.

It may not be possible to recover from this error. Contact your service representative.

144

I

Logical drive initialization started.

User started the initialization.

Any previous data is lost.

145

I

Logical drive initialization done.

Initialize operation completed successfully.

None

146

W

Logical drive initialization cancelled.

User cancelled the initialization.

Restart initialization if required.

147

E

Logical drive initialization failed.

One/multiple physical device(s) failed. Controller has been removed. Controller has been powered off.

Refer to the device failure event.

148

I

A logical drive has been found.

A new configuration has been added. MORE completed. A new controller has been plugged in. Controller has been powered on. System has rebooted.

None

149

I

A logical drive has been deleted.

A new configuration has been added. A new logical device has been deleted. Controller has been removed. Controller has been powered off.

None

150

I

Expand Capacity started.

User started the Online RAID Expansion operation.

None

151

I

Expand Capacity completed.

Online RAID Expansion completed.

None

152

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

153

C

Bad blocks found.

Bad sector was found on a physical device during consistency check/rebuild/RAID expansion operation.

Run a Consistency Check with the Restore option. Restore data from a backup.

154

I

System drive (LUN) size changed.

A new configuration has been added. RAID Expansion has added extra capacity.

None

155

I

System drive type changed.

A new configuration has been added. RAID Expansion completed on RAID 1.

None

156

S

Bad data blocks found. Possible data loss.

Bad blocks were found on multiple physical devices in same zone.

Restore data from a backup.

157

W

System drive LUN mapping has been written to config.

None

158

S

Attempt to read data from block that is marked in Bad Data Table.

Potential data loss.

Restore data from a backup.

159

E

Data for Disk Block has been lost due to Logical Drive problem.

Data retained in RAID Cache for a Write-back Logical Drive cannot be stored to the physical medium because of Logical Drive problem. The Logical Drive problem could be because of multiple physical devices offline or other reasons.

Insure that all the Physical Drives related to the Logical Drive, disk channel, enclosure, or cabling are functional and accessible. Repair or replace them if necessary.

160

E

Temporary-Offline RAID5/RAID3 array is available to the user again with the possibility of data loss in the array.

Temporary-Offline state caused because of transient errors in physical drives.

Verify data from backup.

161

E

Temporary-Offline RAID0+1/RAID1/RAID 0/JBOD array is available to the user again.

Temporary-Offline state caused because of transient errors in physical drives.

None

162

I

A standby rebuild has started on logical drive.

A physical drive failed and a spare device was available.

None

176

I

Logical drive background initialization started.

User may have started background initialization. Firmware may have automatically started background initialization.

None

177

I

Logical drive background initialization stopped.

User may have stopped background initialization. Firmware may have automatically stopped background initialization.

None

178

I

Logical drive background initialization paused.

Background initialization paused due to a higher priority operation.

None

179

I

Logical drive background initialization restarted.

Background initialization started after being paused.

None

180

I

Logical drive background initialization failed.

Background initialization failed.

None

181

I

Logical drive background initialization completed.

Background initialization completed successfully.

None

182

E

Low battery charge level. Logical drive may have lost data.

Controller was powered off for duration longer than battery capacity. User connected a new controller. User connected a new BBU battery.

Run consistency check to verify logical drive consistency. If needed, restore data from backup.

256

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

257

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

258

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

259

I

Storage cabinet fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

272

S

Power supply failure.

Cable connection is broken. Bad power supply.

Reconnect cable or replace the power supply as required.

273

I

Power supply has been restored.

Faulty power supply has been replaced.

None

274

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace power supply.

275

I

Storage cabinet power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

288

S

Over temperature. Temperature is above 70 degrees Celsius.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

289

W

Temperature is above 50 degrees Celsius.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

290

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

291

S

Over temperature.

Room temperature is too high. Bad fan.

Turn off the system and allow it to cool down. Adjust the room temperature.

292

I

Storage cabinet temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

304

S

Enclosure reported failure state.

Power supply failed. Fan failed. Cabinet is too hot.

Follow enclosure management vendor's diagnostics and repair procedures.

305

W

Enclosure reported critical state.

Not available.

Not available.

306

I

Storage Works enclosure reported normal state.

Problem has been rectified.

None

307

I

Uninterruptible power supply disabled.

None

308

I

Uninterruptible power supply AC failed.

None

309

W

Uninterruptible power supply battery low.

None

310

S

Uninterruptible power supply failed.

None

311

I

Uninterruptible power supply normal.

None

320

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

321

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

322

I

Fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

323

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace the power supply.

324

I

Power supply has been restored.

Faulty power supply has been replaced.

None

325

I

Power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

326

S

Temperature is over safe limit. Failure imminent.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

327

W

Temperature is above working limit.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

328

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

329

I

Temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

330

W

Enclosure access critical.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

331

I

Enclosure access has been restored.

Enclosure has been fixed or replaced.

None

332

S

Enclosure access is offline.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

333

S

Enclosure Soft Addressing Detected.

Enclosure has duplicate loop ids (Soft Addressing). Potential data corruption.

Change index selector to enable hard addressing as per enclosure manufacturer's specification.

334

I

Enclosure services ready.

None

335

I

Access to temperature sensor has been lost.

Switch card or temperature sensor has been removed.

None

336

I

Access to power supply status information has been lost.

Switch card or connectivity has been removed.

None

337

I

Access to fan status information has been lost. Switch card or connectivity has been removed.

None

384

I

Array management server software started successfully.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

385

E

Write back error.

Data cache write failed.

The data may have been lost. Restore the data from a backup.

386

W

Internal log structures getting full; PLEASE SHUTDOWN AND RESET THE SYSTEM IN THE NEAR FUTURE.

Too many configuration changes occurred since the last boot.

Reboot the system by power cycling whenever convenient.

388

C

Controller is dead. System is disconnecting from this controller.

Contact your service representative.

389

W

Controller has been reset.

Controller failed. Controller was removed from the system. Controller has been powered off.

None

390

I

Controller is found.

Driver has reset the controller to recover from an error. Driver has reset the controller to activate new firmware.

None

391

C

Controller is gone. System is disconnecting from this controller.

New controller has been installed. Controller has been powered on. System has rebooted.

None

392

I

BBU Present.

Controller is dead. Controller has been removed. Controller has been powered off.

None

393

W

BBU Power Low.

A BBU unit was found on the controller.

If this message occurs without power failure, replace the BBU.

394

I

BBU Power OK.

BBU does not have enough power to enable the write data cache.

None

395

C

Controller is gone. System is disconnecting from this controller.

BBU has enough power to enable the write data cache.

None

396

I

Controller powered on.

Controller was removed from the system. Controller has been powered off.

None

397

I

Controller is online.

New controller has been installed.

None

398

C

Controller is gone. System is disconnecting from this controller.

Controller was set online.

None

399

W

Controller's partner is gone, controller is in failover mode now.

Controller was set offline.

If you did not expect this, investigate.

400

I

BBU reconditioning is started.

User started a BBU reconditioning.

None

401

I

BBU reconditioning is finished.

BBU reconditioning completed successfully.

None

402

I

BBU reconditioning is cancelled.

User cancelled the BBU reconditioning.

Restart the BBU reconditioning, if required.

403

S

Installation aborted.

Installation aborted.

404

S

Controller firmware mismatch.

Replacement controller with downlevel firmware installed.

Reload controller firmware.

405

W

BBU removed.

BBU physically removed.

Reinstall BBU.

406

S

WARM BOOT failed.

Memory error detected during WARM boot scan. Possible data loss.

Restore data from a backup.

407

I

BBU calibration cycle started.

New battery detected.

None

408

I

BBU calibration cycle finished.

BBU calibration completed successfully.

None

409

I

BBU calibration cycle is cancelled.

User cancelled the BBU calibration cycle.

None

410

I

BBU battery not present.

A BBU is present, but the battery is not detected.

Install or connect the battery.

411

W

Controller entered Conservative Cache Mode.

None

412

W

Controller entered normal cache mode.

None

413

W

Controller device start complete.

None

414

W

Soft ECC error corrected.

Faulty memory module.

Replace memory module.

415

W

Hard ECC error corrected.

Faulty memory module.

Replace memory module.

416

S

BBU recondition needed.

None

417

W

Controller's partner has been removed.

None

418

E

BBU out of service.

BBU will not be able to power the cache if AC power fails. Firmware will switch WriteBack logical drives to WriteThrough.

Replace BBU.

419

W

Updated partner's status.

None

420

W

Relinquished partner.

None

421

W

Inserted partner.

None

422

W

Dual controllers enabled.

None

423

W

Killed partner.

None

424

W

Dual controllers entered nexus.

None

425

S

Controller boot ROM image needs to be reloaded.

Wrong firmware image file downloaded. MAC address changed.

Contact your service representative to reload the boot ROM image.

426

C

Controller is using default non-unique world-wide name.

MAC address lost or not set.

Contact your service representative to set the controller MAC address.

427

E

Mirror Race recovery failed.

Some physical devices could have failed.

Run consistency check and restore consistency.

428

C

Mirror Race on critical drive.

Logical device is critical.

Replace dead drive and rebuild.

512

I

System started.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

513

I

Size table full.

Too much physical device size information is defined.

Remove unused device information for this system.

514

I

User logged in.

An array management utility user logged in on the server system.

Not available.

515

I

User logged out.

An array management utility user logged out of the server system.

Not available.

516

I

Server alive.

Reconnected to server. Server rebooted.

None

517

S

Lost connection to server, or server is down.

Lost network connection to server. Server shutdown.

None

518

I

Automatic reboot count has changed.

Controller has rebooted. Automatic reboot has rearmed itself or was reconfigured.

None

640

W

Channel failed.

Cable disconnected.

Plug in cable.

641

W

Channel online.

Cable reconnected.

None

642

S

Back end SCSI bus dead.

Lost access to data on SCSI bus.

LRC module may need replacing.

643

I

Back end SCSI bus alive.

Regained access to data on SCSI bus.

None

644

S

Back end fibre dead.

Lost access to data on fibre channel.

LRC module may need replacing.

645

I

Back end fibre alive.

Regained access to data on fibre channel.

None

700

W

Event log empty.

Tried to read past last entry.

None

701

W

Event log entries lost.

Tried to read an entry that does not exist in the event log.

None

702

W

Request sense.

A physical drive has generated an error.

Interpret the Key/ASC/ASCQ and take appropriate action.

703

W

Set real time clock.

Real time clock was set.

None

800

W

New configuration received.

A new configuration was downloaded to controller.

None

801

W

Configuration cleared.

Controller was told to clear the configuration.

None

802

W

Configuration invalid.

The controller found an invalid configuration.

None

803

W

Configuration on disk access error.

The controller could not read the configuration off of the disk.

None

804

W

Configuration on disk converted.

The controller converted a down level configuration on disk.

None

805

W

Configuration on disk import failed.

The controller could not import the configuration.

None

806

I

A debug dump exists on this system.

The controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

807

I

A debug dump exists on this system.

The partner controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

896

S

Internal controller is in the hung state.

Power controller off and on.

897

S

Introller controller has encountered a firmware breakpoint.

Power controller off and on.

912

S

Internal controller has encountered i960 processor specific error.

Power controller off and on.

928

S

Internal controller has encountered Strong-ARM processor specific error.

Power controller off and on.

929

S

Internal controller back end hardware error.

Timeout waiting for interrupt. Timeout waiting for command completion.

Power controller off and on.

Register Map and Descriptions

The registers are accessible through the APB target interface. The following table lists all the registers required to execute system services on PolarFire devices.

Address OffsetRegister NameTypeWidthReset ValueDescription
0x04SYS_SERV_CMDR/W320Request Command
0x08SYS_SERV_STATR/O320Response Status
0x0CSYS_SERV_REQR/W320Control Register
0x10MBX_ECCSTATUSR/O320Mailbox ECC Status
0x14MBX_WCNTR/W32‘d1Mailbox Write Count
0x18MBX_RCNTR/W32‘d1Mailbox Read Count
0x1CMBX_WADRDESCR/W320Mailbox Write Address Descriptor
0x20MBX_RADRDESCR/W320Mailbox Read Address Descriptor
0x28MBX_WDATAR/W320Mailbox Write Data
0x2CMBX_RDATAR/O320Mailbox Read Data
0x30SYS_SERV_USERR/O320System Service User

youtube video

APB problem how to fix (error code 9)

1

I

A hard disk has been placed online.

Rebuild completed. Device was configured. Manual online was done.

None

2

I

A hard disk added as hot spare.

Device was configured. Manual hot spare was done. Automatic hot spare was done. `Raidbld' made it hot spare.

None

3

W

Hard disk error found.

A bad sector was found on the physical media. Mechanical failure on the device. Host SCSI device detected illegal instruction. Apb r error code 9 device generated unknown phase sequence.

If problem occurs frequently, replace the device or contact service representative.

4

W

Hard disk PFA condition found, this disk may fail soon.

Physical device predicted some future failure. External RAID logical device may have become critical.

Follow device vendor's defined action.

5

I

An automatic rebuild has started.

A physical device failed and spare was available. A physical device failed and no spare was available. A spare was added.

None

6

I

A rebuild has started.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

7

I

Rebuild is over.

Rebuild completed successfully.

None

8

W

Rebuild is cancelled.

User cancelled the rebuild. Higher priority rebuild started.

Restart the rebuild if required.

9

E

Rebuild stopped with apb r error code 9 to some unknown error on the controller, rebuild failed.

Try rebuild again.

10

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device may not be compatible with MDCA hardware/firmware.

Replace the physical device.

11

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array. Bad data table overflow.

It may not be possible to apb r error code 9 from this error. Contact your service representative.

12

S

A hard disk has failed.

A physical device failed. A user action caused the physical device to fail.

Replace the physical device.

13

I

A new hard disk has been found.

A physical device has been powered on. A new physical device has been added. Controller was powered on. Controller was added. System has rebooted.

None

14

I

A hard disk has been removed.

User removed an unconfigured physical device. An unconfigured physical device failed. A controller was removed, apb r error code 9. A controller powered off.

Replace the device if needed.

15

I

A previously configured disk is now a disk read error occurred windows xp set the physical device to unconfigured.

None

16

I

Expand Capacity started.

User started the RAID Expansion operation. A suspended RAID Expansion operation was started.

None

17

I

Expand Capacity compile error byref argument type mismatch vba completed.

RAID Expansion finished.

None

18

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact essbase error 1019002 service representative.

19

W

SCSI command time out on hard device.

Physical device has apb r error code 9 removed, apb r error code 9. Physical device failed. Command timeout value is not correct.

None

20

C

SCSI command abort on hard disk.

User may have requested to abort the command. Firmware may have aborted the command to recover from error. The device may have aborted the command.

None

21

W

SCSI command retried on hard disk.

The command may have timed out, apb r error code 9. Bus reset may have error 017 undefined symbol removeplayervariables. Device reset may have occurred.

None

22

W

Parity error found.

A physical device did not generate proper parity. The controller failed, did not check parity properly. Cable failed. Improper cable length. Another physical device interfered. Some outside environment affected the data on the cable (for example, radio frequency signal). Terminator is not connected. Improper termination.

It may not be possible to recover from this error, apb r error code 9. Contact your service representative.

23

W

Soft error found.

An error was detected by physical device and data was recovered.

Run consistency check. If problem occurs frequently, replace the physical device.

24

W

Misc error found.

A physical device reported some error, which does not fit in any category. Read/Write command timeout. Data over run. Physical device was busy when host attempted to send command.

If problem occurs frequently, replace the physical device.

25

I

SCSI device reset.

Firmware has done reset to recover from error. User has done a reset.

None

26

I

Active spare found.

Device was configured. Manual active spare was done. Automatic active spare was done.

None

27

I

Warm spare found.

Device was configured. Manual warm spare was done. Automatic warm spare was done.

None

28

E

Request sense data available.

A physical device reported an error. Firmware reported an operational error.

Read the request sense data to understand the root cause.

29

I

Initialization started.

Host started the initialization.

Wait until the initialization is completed. If the system is shutdown prior to this process being completed, the physical device can be made useful only by reinitializing it.

30

I

Initialization completed.

Physical device initialization completed successfully.

None

31

W

Initialization failed.

Physical device could have problems supporting the SCSI format command.

Try to initialize again. Contact your service representative.

32

S

Initialization cancelled.

User cancelled the operation.

Hard disk must be initialized again or the hard disk cannot be used.

33

S

A hard disk failed because write recovery failed.

Write recovery process failed.

Replace hard disk and rebuild it.

34

S

A hard disk failed because SCSI bus reset failed.

SCSI bus reset failed.

Replace hard disk and rebuild it.

35

S

A hard disk failed because double check condition occurred.

Double check condition occurred.

Replace hard disk and rebuild it.

36

S

A hard disk failed because device is missing.

Access to the hard disk failed.

Replace hard disk and rebuild it.

37

S

A hard disk failed because of gross error on SCSI processor.

Gross error occurred to the on-board SCSI processor.

Replace hard disk and rebuild it.

38

S

A hard disk failed because of bad tag from the device.

The device responded with apb r error code 9 invalid tag.

Replace hard disk and rebuild it.

39

S

A hard disk failed because command to the device timed out.

SCSI command timed out on the device.

Replace hard disk and rebuild it.

40

S

A hard disk failed because of the system reset.

System reset occurred.

Replace hard disk and rebuild it.

41

S

A hard disk failed because of busy status or parity error.

The device returned busy status. The SCSI transaction with the device met with parity error.

Replace hard disk and rebuild it.

42

S

A hard disk set to failed state by host.

Command from host set the hard disk to failed state.

Replace hard disk and rebuild it.

43

S

A hard disk failed because access to the device met with a selection time out.

Device disconnected or powered off. Bad device.

Replace hard disk and rebuild it. Check power and cabling.

44

S

A hard disk failed because of a sequence error in the Access violation error.log updated bus phase handling.

Bad hard disk.

Replace hard disk and rebuild it.

45

S

A hard disk failed because returned an unknown status.

Bad hard disk or incompatible device.

Replace hard disk or the device and rebuild it.

46

S

A hard disk failed because device is not ready.

Device not spinning, just turned bad. Power to the device failed.

Replace hard disk and rebuild it. Check power and rebuild device.

47

S

A hard disk failed because device was not found on startup.

Device not connected. Device not responding. Clear configuration suspend mode command was invoked.

Check setup. Check the startup option parameters on the system.

48

S

A hard disk failed because write operation of the `Configuration On Disk' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

49

S

A hard disk failed because write operation of `Bad Data Table' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

50

W

Physical device status changed to offline.

None

51

I

Physical device status changed to Hot Spare.

None

52

W

Physical device status changed to rebuild.

None

53

W

Physical device ID did not match.

None

54

E

Physical device failed to start.

Reset the physical disk. Replace the disk.

55

W

Physical device negotiated different offset than configuration.

None

56

W

Physical device negotiated different bus width than configuration.

None

57

S

Physical drive missing on startup.

Physical drive missing.

Replace the physical drive or power on all enclosures.

58

E

Rebuild startup failed due to lower disk capacity.

Device capacity not sufficient for doing rebuild.

Replace with a disk having sufficient capacity.

59

W

Physical drive is switching from a channel to the other channel.

Physical drive removed or channel failed.

None

60

E

Temporary-Dead physical drive is automatically made online.

Temporary-Dead state caused because of transient errors.

Analyze event log to find out why the drive was marked DEAD.

61

I

A standby rebuild was started.

A physical device failed and spare was available.

None

62

I

Hot spare replaced with a smaller capacity physical disk.

The new hot spare may have a smaller physical capacity than the physical disk it replaced. The controller coercion setting may have reduced the configurable size of the new hot spare.

None

67

E

Physical disk found on only one disk channel.

Physical disk is connected on only one channel.

Inspect disk channel cables and related hardware for proper operation.

69

E

Physical disk has acquired an inappropriate loop ID. Enclosure disk-slot operations are disabled while this condition persists.

Enclosure selector switch conflict. Physical disk hardware failure. Enclosure disk slot hardware failure.

Ensure that each disk enclosure selector switch is set to a unique number per enclosure manufacturer specification, apb r error code 9. Inspect physical disk connector. Power-cycle entire system. Replace physical disk. Replace disk enclosure.

70

E

Physical disk port has failed or cannot operate at apb r error code 9 configured channel speed.

Physical disk hardware failure. Physical disk is not compatible with system. Enclosure disk slot hardware failure.

Replace physical disk. Replace disk enclosure.

71

E

Mirror race recovery failed for ariston 501 error drive.

A read or write operation to a physical disk failed while restoring redundancy.

Run consistency check and restore consistency.

72

E

Controller parameters checksum verification failed; restored default.

NVRAM battery low. NVRAM hardware failure. Improper shutdown of the controller during controller parameter update.

Restore correct controller parameter settings. If problem persists, replace controller.

73

I

Online controller firmware upgrade has started.

User has initiated an online firmware upgrade.

None

74

I

Online controller firmware upgrade has completed successfully.

Online controller firmware upgrade has completed without error. The partner controller will now be auto flashed.

None

75

E

Online controller firmware upgrade has failed.

Online controller firmware upgrade has failed. The original firmware will be reloaded.

Use the offline method to load the new firmware.

76

I

A COD with unsupported features has been detected.

Firmware does not support certain features error - 1270006 that COD. COD import is to wrong system COD data is sequestered.

Obtain compatible firmware then reimport the COD or import the COD to a different system

77

I

A new battery was found.

Battery present in the controller could be a new or a replaced unit.

None

78

S

Battery backup unit charger error.

Battery backup unit failure. Hardware problems in battery backup unit.

Replace the battery, or replace the battery backup unit hardware, or if the problem persists contact your service representative.

79

S

Battery will not hold a charge.

Battery failure.

Have your supplier replace the battery.

80

S

Firmware entered unexpected state at run-time.

Memory corruption. Hardware returned unexpected value.

If the controller stops responding reboot and try apb r error code 9 again. If problem persists contact your service representative.

81

I

Rebuild stopped on controller failure.

Rebuild moved to the surviving controller because the partner, which was running the rebuild, failed.

None

82

E

Check Consistency stopped on controller failure.

Check Consistency failed because the partner, which was running the Check Consistency, failed.

Restart the consistency check.

83

E

Foreground initialization stopped on controller failure.

Foreground initialization failed because the partner, which was running the foreground initialization, failed.

Restart the foreground initialization.

84

I

Background initialization stopped on controller failure.

Background initialization restarted on the surviving controller because the partner, which was running the background asus p5ql pro cpu fan error, failed.

None

85

I

Configuration group not installed due to physical disk conflict.

Physical disk already configured in another group. Unable to map a physical device in this group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

86

I

Configuration group not installed due to logical drive conflict.

Logical drive already configured in another group. Unable to install all the logical drives in the group.

Move to another controller, apb r error code 9. Remove one or more existing configuration groups and reboot with this group.

87

I

Configuration group not installed due to SAN Map conflict.

SAN Map conflicted with that of another installed group.

Move to another controller, apb r error code 9. Remove one or more existing configuration groups and error #1054 eleanor cms rc5 reboot with this group.

88

I

Foreign configuration group not installed.

Foreign COD Group found but not installed.

Move to another controller. Remove native configuration apb r error code 9 group and reboot with foreign group.

89

I

No configuration group installed.

All configuration groups are foreign and clash. Controllers may have changed.

Move to another controller. Re-insert original controllers or remove some groups and reboot with one group.

96

S

Device loop ID conflict apb r error code 9 addressing) detected.

Device loop ID conflict detected on disk channel resulting in soft addressing; potential data corruption.

Change index selector to apb r error code 9 hard addressing per enclosure manufacturer's specification.

97

I

One or more transport Fibre channel CRC errors occurred during data transfer to/from the physical device in the last hour.

Physical devices were installed or removed causing momentary fibre channel loop disruption. Cabling or associated fibre channel hardware is faulty.

Unless the problem occurs frequently, action is not required.

98

I

The host fibre channel is down.

Host fibre channel device (cable, server, switch, apb r error code 9, hub, host adapter) has failed. Host fibre channel interface on the controller has failed.

Inspect host fibre channel cables and associated hardware, apb r error code 9.

99

I

The host fibre channel is up.

The host fibre channel loop initialized successfully.

None

100

I

Redundant access restored on physical disk.

Physical disk is now accessible on both disk channels.

Check I/O modules and back-end connections if disk frequently loses redundant accessibility.

101

I

Started to loop through each drive for predicted failure analysis.

Controller started a predicted failure analysis on disk drives.

None

102

I

Finished predicted failure analysis on each drive.

Controller finished predicted failure analysis.

None

103

I

Background patrol was started or resumed.

Background patrol started.

None

104

I

Background patrol has found no more drives or was commanded to stop.

Background patrol finished or stopped.

None

128

N

Consistency check is started.

User started a consistency check. `Raidbld' started consistency check.

None

129

I

Consistency check is finished.

Consistency check completed successfully without detecting any errors.

None

130

E

Consistency check is cancelled.

User cancelled the consistency check.

Restart consistency check, if required.

131

E

Consistency check on logical drive error.

Inconsistent data was found. Bad sectors were found. A physical device reliability problem.

See bad block and request sense table for more information.

132

E

Consistency check on logical drive failed.

A logical device became critical. A logical device failed.

See request sense data for more information.

133

S

Consistency check failed due to physical device failure.

A physical device failed.

See request sense data for more information.

134

S

Logical drive has been made offline.

One/multiple physical device(s) failed.

It may not be possible eoserror code 5 2008 recover from this error. Contact your service representative.

135

E

Logical device is critical.

One physical device failed.

Replace the physical device. Start the rebuild, if required.

136

I

Logical drive has been placed online.

Rebuild completed. User set the physical device online. New configuration was added.

None

137

I

An automatic rebuild has started on logical drive.

A physical device failed and a spare device was available. A spare physical device was found and replaced the failed device.

None

138

I

A manual runtime error 6 at has started on logical drive.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

139

I

Rebuild on logical drive is over.

Rebuild completed successfully only for this logical drive.

None

140

W

Rebuild on logical drive is cancelled.

User cancelled rebuild. Higher priority rebuild started.

Restart the rebuild if required.

141

E

Rebuild stopped with error.

Due to an unknown error on the apb r error code 9 rebuild failed.

Try rebuild again.

142

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device is not compatible with MDAC hardware/firmware.

Replace the new device.

143

E

Rebuild stopped because logical drive failed.

At least one more physical device failed apb r error code 9 the array.

It may not be possible to recover from this error. Contact your service representative.

144

I

Logical drive initialization started.

User started the initialization.

Any previous data is lost.

145

I

Logical drive initialization done.

Initialize operation completed successfully.

None

146

W

Logical drive initialization cancelled.

User cancelled the initialization.

Restart initialization if required.

147

E

Logical drive initialization failed.

One/multiple physical device(s) failed. Controller has been removed. Controller has been powered off.

Refer to the device failure event.

148

I

A logical drive has been found.

A new configuration has been added. MORE completed. A new controller has been plugged in. Controller has been powered on. System has rebooted.

None

149

I

A logical drive has been deleted.

A new configuration has been added. A new logical device has been deleted. Controller has been removed. Controller has been powered off.

None

150

I

Expand Capacity started.

User started the Online RAID Expansion operation.

None

151

I

Expand Capacity completed.

Online RAID Expansion completed.

None

152

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

153

C

Bad blocks found.

Bad sector was found on a physical device during consistency check/rebuild/RAID expansion operation.

Run a Consistency Check with the Restore option. Restore data from a backup.

154

I

System drive (LUN) size changed.

A new configuration has been added. RAID Expansion has added extra capacity.

None

155

I

System drive type changed.

A new configuration has been added. RAID Expansion completed on RAID 1.

None

156

S

Bad data blocks found. Possible data loss.

Bad blocks were found on multiple physical devices in apb r error code 9 zone.

Restore data from a backup.

157

W

System drive LUN mapping has been written to config.

None

158

S

Attempt to read data from block that is marked in Bad Data Table.

Potential data loss.

Restore data from a backup.

159

E

Data for Disk Block has been lost due to Logical Drive problem.

Data retained in RAID Cache for a Write-back Logical Drive cannot be stored to the physical medium because of Logical Drive problem. The Logical Drive problem could be because of multiple physical devices offline or other reasons.

Insure that all the Physical Drives related to the Logical Drive, disk channel, enclosure, or cabling are functional and accessible. Repair or replace them if necessary.

160

E

Temporary-Offline RAID5/RAID3 array is available to the user again with the possibility of data loss in the array.

Temporary-Offline state caused because of transient errors in physical drives.

Verify data from backup.

161

E

Temporary-Offline RAID0+1/RAID1/RAID 0/JBOD array is available to the user again.

Temporary-Offline state caused because of transient errors in physical drives.

None

162

I

A standby rebuild has started on logical drive.

A physical drive failed and a spare device was available.

None

176

I

Logical drive background initialization started.

User may have started background initialization. Firmware may have automatically started background initialization.

None

177

I

Logical drive background initialization stopped.

User may have stopped background initialization. Firmware may have automatically stopped background initialization.

None

178

I

Logical drive background initialization paused.

Background initialization paused due to a higher priority operation.

None

179

I

Logical drive background initialization restarted.

Background initialization started after being paused.

None

180

I

Logical drive background initialization failed.

Background initialization failed.

None

181

I

Logical drive background initialization completed.

Background initialization completed successfully.

None

182

E

Low battery charge level. Logical drive may have lost data.

Controller was powered off for duration longer than battery capacity. User connected a new controller. User connected a new BBU battery.

Run consistency check to verify logical drive consistency. If needed, restore data from backup.

256

S

Fan failure.

Cable connection broken, apb r error code 9. Bad fan.

Replace fan.

257

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

258

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

259

I

Storage cabinet fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

272

S

Power supply failure.

Cable connection is broken. Bad power supply.

Reconnect cable or replace the power supply as required.

273

I

Power supply has been restored.

Faulty power supply has been replaced.

None

274

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace power supply.

275

I

Storage cabinet power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

288

S

Over temperature. Temperature is above 70 degrees Celsius.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

289

W

Temperature is above 50 degrees Celsius.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

290

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

291

S

Over temperature.

Room temperature is too high. Bad fan.

Turn apb r error code 9 the system and allow it to cool down. Adjust the room temperature.

292

I

Storage cabinet temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad, apb r error code 9. Sensor is apb r error code 9 present.

Follow enclosure management vendor's diagnostics and repair procedures.

304

S

Enclosure reported failure state.

Power supply failed. Fan failed. Cabinet is too hot.

Follow enclosure management vendor's diagnostics and repair procedures.

305

W

Enclosure reported critical state.

Not available.

Not available.

306

I

Storage Works enclosure reported warning hash data error state.

Problem has been rectified.

None

307

I

Uninterruptible power supply disabled.

None

308

I

Uninterruptible power supply AC failed.

None

309

W

Uninterruptible power supply battery low.

None

310

S

Uninterruptible power supply failed.

None

311

I

Uninterruptible power supply normal.

None

320

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

321

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

322

I

Fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

323

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace the power supply.

324

I

Power supply has been restored.

Faulty power supply has been replaced.

None

325

I

Power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

326

S

Temperature is over safe limit. Failure imminent.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

327

W

Temperature is above working limit.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

328

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

329

I

Temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

330

W

Enclosure access critical.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

331

I

Enclosure access has been restored.

Enclosure has been fixed or replaced.

None

332

S

Enclosure access is offline.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

333

S

Enclosure Soft Addressing Detected.

Enclosure has duplicate loop ids (Soft Addressing). Potential data corruption.

Change index selector to enable hard addressing as per enclosure manufacturer's specification.

334

I

Enclosure services ready.

None

335

I

Access to temperature sensor has been lost.

Switch card or temperature sensor has been removed.

None

336

I

Access to power supply status information has been lost.

Switch card or connectivity has been removed.

None

337

I

Access to fan status information has been lost. Switch card or connectivity has been removed.

None

384

I

Array management server software started successfully.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

385

E

Write back error.

Data cache write failed.

The data may have been lost. Restore the data from a backup.

386

W

Internal log structures getting full; PLEASE SHUTDOWN AND RESET THE SYSTEM IN THE NEAR FUTURE.

Too many configuration changes occurred since the last boot.

Reboot the system by power cycling whenever convenient.

388

C

Controller is dead. System is disconnecting from this controller.

Contact your service representative.

389

W

Controller has been reset.

Controller failed. Controller was removed from the system. Controller has been powered off.

None

390

I

Controller is found.

Driver has reset the controller to recover from an error. Driver has reset the controller to activate new firmware.

None

391

C

Controller is gone. System is disconnecting from this controller.

New controller has been installed. Controller has been powered on. System has rebooted.

None

392

I

BBU Present.

Controller is dead. Controller has been removed. Controller has been powered off.

None

393

W

BBU Power Low.

A BBU unit was found on the controller.

If this message occurs apb r error code 9 power failure, replace the BBU.

394

I

BBU Power OK.

BBU does not have enough power to enable the write data cache.

None

395

C

Controller is gone. System is disconnecting from this controller.

BBU has enough power to enable the write data cache.

None

396

I

Controller powered on.

Controller was removed from the system. Controller has been powered off.

None

397

I

Controller is online.

New controller has been installed.

None

398

C

Controller is gone. System is disconnecting from this controller.

Controller was set online.

None

399

W

Controller's partner is gone, controller is in failover mode now.

Controller was set offline.

If you did not expect this, investigate.

400

I

BBU reconditioning is started.

User started a BBU reconditioning.

None

401

I

BBU reconditioning is finished.

BBU reconditioning completed successfully.

None

402

I

BBU reconditioning is cancelled.

User cancelled the BBU reconditioning.

Restart the BBU reconditioning, if required.

403

S

Installation aborted.

Installation aborted.

404

S

Controller firmware mismatch.

Replacement controller with downlevel firmware installed.

Reload controller firmware.

405

W

BBU removed.

BBU physically removed.

Reinstall BBU.

406

S

WARM BOOT failed.

Memory error detected during WARM boot scan, apb r error code 9. Possible data loss.

Restore data from a backup.

407

I

BBU calibration cycle started.

New battery detected.

None

408

I

BBU calibration cycle finished.

BBU calibration completed successfully.

None

409

I

BBU calibration cycle is adsl crc errors cancelled the BBU calibration cycle.

None

410

I

BBU battery not present.

A BBU is present, but the battery is not detected.

Install or connect the battery.

411

W

Controller entered Conservative Cache Mode.

None

412

W

Controller entered normal cache mode.

None

413

W

Controller device apb r error code 9 complete.

None

414

W

Soft ECC error corrected.

Faulty memory module.

Replace memory module.

415

W

Hard ECC error corrected.

Faulty memory module.

Replace memory module.

416

S

BBU recondition needed.

None

417

W

Controller's partner has been removed.

None

418

E

BBU out of service.

BBU will not be able to power the cache if AC power fails. Firmware will switch WriteBack logical drives to WriteThrough.

Replace BBU.

419

W

Updated partner's status.

None

420

W

Relinquished partner.

None

421

W

Inserted partner.

None

422

W

Dual controllers enabled.

None

423

W

Killed partner.

None

424

W

Dual controllers entered nexus.

None

425

S

Controller boot ROM image needs to be reloaded.

Wrong firmware image file downloaded. MAC address changed.

Contact your service representative to apb r error code 9 the boot ROM image.

426

C

Controller is using default non-unique world-wide name.

MAC address lost or not set.

Contact your service representative to set the controller MAC address.

427

E

Mirror Race recovery failed.

Some physical devices could have failed.

Run consistency check and restore consistency.

428

C

Mirror Race on critical drive.

Logical device is critical.

Replace dead drive and rebuild.

512

I

System started.

The apb r error code 9 system (or array management utility server) started.

If you did not expect a system reboot, investigate.

513

I

Size table full.

Too much physical device size information is defined.

Remove unused device information for this system.

514

I

User logged in.

An array management utility user logged in on the server system.

Not available.

515

I

User logged out.

An array management utility user logged out of the server system.

Not available.

516

I

Server alive.

Reconnected to server. Server rebooted.

None

517

S

Lost connection to server, or server is down.

Lost network connection to server. Server shutdown.

None

518

I

Automatic reboot count has changed.

Controller has rebooted. Automatic reboot has rearmed itself or was apb r error code 9 reconfigured.

None

640

W

Channel failed.

Cable disconnected.

Plug in cable.

641

W

Channel online.

Cable reconnected.

None

642

S

Back end SCSI bus dead.

Lost access to data on SCSI bus.

LRC module may need replacing.

643

I

Back end SCSI bus alive.

Regained apb r error code 9 to data on SCSI bus.

None

644

S

Back end fibre dead.

Lost access to data on fibre channel.

LRC module may need replacing.

645

I

Back end fibre alive.

Regained access to data on fibre channel.

None

700

W

Event log empty.

Tried to read past last entry.

None

701

W

Event log entries lost.

Tried to read an entry that does not exist in the event log.

None

702

W

Request sense.

A physical drive has generated an error.

Interpret the Key/ASC/ASCQ and take appropriate sccm client installation error 1305 real time clock.

Real time clock was set.

None

800

W

New configuration received.

A new configuration was downloaded to controller.

None

801

W

Configuration cleared.

Controller was told to clear the configuration.

None

802

W

Configuration invalid.

The controller found an invalid configuration.

None

803

W

Configuration on disk access canon imagerunner system error e197 controller could not read the configuration off of the disk.

None

804

W

Configuration on disk converted.

The controller converted a down level configuration on disk.

None

805

W

Configuration on disk import failed.

The controller could not import the configuration.

None

806

I

A debug dump exists on this system.

The controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

807

I

A debug dump exists on this system.

The partner controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

896

S

Internal controller is in the hung state.

Power controller off and on.

897

S

Introller controller has encountered a firmware breakpoint.

Power controller off and on.

912

S

Internal controller has encountered i960 processor specific error.

Power controller off and on.

928

S

Internal controller has encountered Strong-ARM processor specific error.

Power controller off and on.

929

S

Internal controller back end hardware error.

Timeout waiting for interrupt. Timeout waiting for command completion.

Power controller off and on.

Talk:APB: All Points Bulletin

removed[edit]

removed discussion about the game 80.192.61.220 00:47, 1 April 2007 (UTC)Reply[reply]

why? 216.234.58.18 15:20, 23 October 2007 (UTC)Reply[reply]

removed comment about original GTA not being 3D, removed speculation that APB was inspired by the earlier game from Atari with the same name. I work on the game and it wasn't.RobertAnderberg 00:49, 3 June 2007 (UTC)Reply[reply]

whole page is written like an advertisement. somebody fix it, i can't be bothered. 222.153.154.182 (talk) 02:09, 22 January 2008 (UTC)Reply[reply]

Release Date[edit]

IGN say apb r error code 9 the PC it is out in Japan on 31st december 2007 and 2007 in USA but unreleased in Europe. Xbox360 dates are all 2008, anyone know anything there is so many rumors going on about this game and this article is so small and it shouldnt be. —Preceding unsigned comment added by Andrew22k (talk • contribs) 13:10, 8 December 2007 (UTC)Reply[reply]

http://www.mcvuk.com/news/35129/APB-hits-retail-in-March Ne specific release date but it will be in March of 2010. And that article shps that it is being released for the 360 if any clarification was needed. UltimateSin01 (talk) 11:41, 23 July 2009 (UTC)Reply[reply]

concerned about copyvio[edit]

much of this article seems to have been lifted verbatim directly from http://www.apb-evolved.com. I'm also not sure if they are an appropriate reference site for information. Xenocidic (talk) 15:31, 22 January 2008 (UTC)Reply[reply]

I wrote the site's administrators about the content and received an email back from them "Thanks for the notice, as long as the information is given credit towards the site we are ok with it.". So I will work on ensuring the proper citations are given. I will also apb r error code 9 to clean up the text to sound more encyclopaedic. Xenocidic (talk) 16:29, 22 January 2008 (UTC)Reply[reply]
This is why the whole article looks like an ad. it is just the PR text from the game's web page. I just saw the a talk on this game at GDC 2008, and the game looks lame. This whole article was probably made by someone who's working on it. YAWN. —Preceding unsigned comment added by Farktol (talk • contribs) 20:07, apb r error code 9, 22 February 2008 (UTC)Reply[reply]
actually it was lifted from a fan site. the article definately needs a apb r error code 9 of work. xenocidic (talk) 20:10, 22 February 2008 (UTC)Reply[reply]

Ext. Links[edit]

Do not remove link to the only APB forums, apb-evolved.com —Preceding unsigned comment added by 68.10.225.15 (talk • contribs)

I've removed the particular external link, apb r error code 9, until a concensus is reached. StaticGull Talk  11:12, apb r error code 9, 1 May 2008 (UTC)Reply[reply]
I'm typically against these types of links but in the case of apb-evolved.com, I'd be willing to let it stand for a few reasons: 1) it's not completely ad-laden and the ads that they have are unobtrusive. 2) there's not much info out there in the wild about this game, and this site is a pretty good resource for it, and 3) this article used to be a complete copy-vio cut and paste from apb-evolved and they let us keep it up as long as we linked to them (since it's no longer copy-vio, we're not bound to this, but it would be a courtesy). xenocidic (talk) 12:46, 1 May apb r error code 9 (UTC)Reply[reply]


All of your facts are true, but considering the very lack of community forums, and the news of this site providing constant indirect content towards the site. We should be able to give a link to this site, at least until the official forums open up. Many of the developers support, and are on this website and should be counted as semi-official. —Preceding unsigned comment added by 68.10.225.15 (talk) 11:00, apb r error code 9, 2 May 2008 (UTC)Reply[reply]

Please do not modify the external links section, APB-Evolved is added as a community forums until an official spb shell 3d chelpus error goes online. This is a rare exception, please fansites, guilds, and islom terror emas unofficial sites please do not edit this area. —Preceding unsigned comment added by 68.10.225.15 (talk) 02:37, 18 August 2008 (UTC)Reply[reply]

-Agreed, ill keep a watch on this. - BlueFlamez

That site is no longer the only APB forum so it should no longer be listed. The newer site APBForums.com is also supported by the developers and not "ad-laden". In my opinion now that there is another forum exceptions should either be made for both or neither sites should be service error 5100 canon pixma printer here. - nekon

Forums, official or not, are not appropriate external links for any article, (see WP:VG/EL). --MASEM 03:59, 18 August 2008 (UTC)Reply[reply]

Then like I said neither site should be listed, I've read the guidelines and they're clear. No forums in external links, no exceptions. Now lets take that link down. -nekon—Preceding unsigned comment added by Nekon (talk • contribs) 04:07, 18 August 2008 (UTC)Reply[reply]

That's fine, I was simply following a previously agreed terms discussed here. If we all agree since there are more than one forums neither should be allowed. - Blueflamez—Preceding unsigned comment added by 68.10.225.15 (talk) 12:32, 18 August 2008 (UTC)Reply[reply]

Not acceptable by whom? Wikapedia is a resource location allowing those who are interested in a topic to learn more about it. Apb-evolved.com has ALL of the current information released to the public on it, more than APB.com, Realtimeworlds website and APBforums.com combined. Not to mention the fact that its own Dev team including Chris Ulric community manager continue to use it to send out announcments. In fact, before the Register your interest page went up, APB-evolved.com was the only means of communication to the fans. I realise that APBforums.com doesnt want APB-evolved.com advertised as it lessens the likelyhood they will accrue members however we are supposed to be "supporting" the fans, not the Webmasters in need of members and so as it stands APB-evolved offers the most comprehensive database of information & collective fans in one place and until the APB official forums go up and innevitably change this it should stay. What is the negative impact on the Fan/User going to be if that link is there over what the postive will be? —Preceding unsigned comment added by 195.224.121.210 (talk) 12:15, 1 September 2008 (UTC)Reply[reply]

I think that one of the primary confusions here is that APB Evolved is being referred to solely as a forum, which it is not. It is a considerable news source which includes many updates not included through the developers' own website. And that's before you even get on the forum. So, the forum is simply one element of a larger site. Having a forum attached to a site does not qualify that site as a forum. Also, as has alreay been said, the website has a long standing relationship with the development team blurring the lines between fansite and official news source. As a closing point, it is utterly nonsensical and silly to refuse to include APB Evolved, which does have considerable info and has been publicly accepted by the developers while including the IGN page which has only one interview (which IGN did) and otherwise minimal and outdated info. We have to get this together and it least be sensible if we are going to follow rules somewhat arbitrarily. -CAWH —Preceding unsigned comment added by 98.218.174.19 (talk) 19:38, 15 August 2009 (UTC)Reply[reply]

Old APB[edit]

Er, wasn't there an APB video game in the 80s? I seem to remember seeing one for C64 (though I don't know enough about it to add anything useful to the article). --taras (talk) 13:41, 3 May 2008 (UTC)Reply[reply]

Fixed. They aren't related, so a dablink is enough, apb r error code 9. xenocidic (talk) 11:08, apb r error code 9, 5 May 2008 (UTC)Reply[reply]

Gameplay infomation[edit]

Hi, I thought I would post some stuff that could be possibly written in to one of the articles someday, all the things I put here are things that have come from RTW which they said would be in the game. I will update when more info is released each month in their newsletter.

This is an excerpt from Here: http://www.apb-evolved.com/news/53-apb-september-update

Idea already implemented: Arrest / Capture system

Enforcers have an arrest system available to them which serves to take out a criminal player until they are freed or the arrest timer expires and they must respawn as if killed. This can reduce the criminal force for longer periods of time than killing them would unless freed by their criminal group-mates.86.134.253.171 (talk) 19:41, 10 December 2008 (UTC)Reply[reply]

Please Read[edit]

Please stop putting Xbox 360 as a confirmed platform and putting out of date info on here, it has not been confirmed as a platform the game will be on yet, seriously I keep having to change it back. —Preceding unsigned comment added by Lilolirocksursocks (talk • contribs) 19:08, 25 May 2009 (UTC)Reply[reply]

Xbox 360?[edit]

On the official website they say, and I quote,

"Q: Will there be console ports? Or a Linux or Mac client?


A: We’re just starting to evaluate opportunities for a console port but do not have anything to announce yet."

This conflicts with the information wikipedia gives. —Preceding unsigned comment added by Jayrossss (talk • contribs) 19:47, 10 June 2009 (UTC)Reply[reply]

Indeed. But see the teamxbox article. I wish they would make up their mind. Anyhow, maybe this helps. –xenotalk 19:51, apb r error code 9, 10 June 2009 (UTC)Reply[reply]

It says they are developing it, not releasing it, they might just be starting to develop it to see if it is a good idea to release on the Xbox 360 then later if it goes well and works good then they will release it, the fact is is that they didn't say release they said develop. I don't know if any of that made sense but I hope I got my point across.Lilolirocksursocks (talk) 20:48, apb r error code 9, 14 June 2009 (UTC)Reply[reply]

payment[edit]

will have to pay a fee? thanks., apb r error code 9. —Preceding unsigned comment added by 69.110.69.39 (talk) 21:24, 13 July 2009 (UTC)Reply[reply]

It's unknown yet, hopefully not, because otherwise I'm not getting this game, I saw something that hinted that there wouldn't be any fees, but nothing official has been announced yet I don't think. —Preceding unsigned comment added by Lilolirocksursocks (talk • contribs) 09:33, 22 July 2009 (UTC)Reply[reply]

The official word is that there will not be a monthly fee. However, there is absolutely no info on the payment method. In fact, the most canon bjc-55 error interview with David Jones says that they may not truly decide the payment method until the beta gets going. They want to feel out how people play it first. -CAWH

It has tough been confirmed that you need to buy game in stores before you can play it. Eibx (talk) 19:52, 17 August 2009 (UTC)Reply[reply]

History[edit]

I think the History section needs a clean up, or a new rewriting. I'll do my best. - Eibx 21:56, 17 September 2009 (UTC)Reply[reply]

MMO?[edit]

The article seems to state you can interact with up to 25 players. I fail to see how a 26 player game is massive in any way, shape or form, when many other games, who do not bear the MMO genre, can support more players than this game will (BF2/2142 are 40 player capable I believe).

I wish developers would understand that having a monthly fee, being multiplayer only and having elements of persistance does not make their game MMOs. The main canon mp280 error of MMOs is the word MASSIVE. No massive amount of players = not an MMO.

At the time massive multiplayer games came around, the phrase was used to describe games than contained a number of players way above the normal 4 players, which was very common at the time. APB is a MMO, since the description of what is Massive and what is not, is very unclear.- Eibx 01:24, 23 October 2009 (UTC)Reply[reply]

I believe this game needs to have it's article edited into the "MOG" genre. —Preceding unsigned comment added by 70.83.54.70 (talk) 22:40, 16 October 2009 (UTC)Reply[reply]

When you sign in, you will have to choose an instance of a world you want to play on. These worlds can contain about a 100 players, apb r error code 9. An unlimited number of instances can be made in theory. What is meant by interaction, is basically you will not be shooting at more than 25 people at a time. - Eibx 01:19, 23 October 2009 (UTC)Reply[reply]
This is true. Also, the closed beta date is very incorrect and I will not correct it. 91.105.133.73 (talk) 17:54, 14 March 2010 (UTC)Reply[reply]

Well the trailer says that the scale is much bigger than this. It states, "100 players to a city," and "100,000 players to a world." So I'm quite certain this means up to 100 players in an instance. 216.185.250.92 (talk) 00:59, 3 February 2010 (UTC)Reply[reply]

There were plans for servers where all 100 people could square off against each other, however, the ruleset was never implemented. There were also times in the game where you could kill any other player indiscriminantly. It was an MMO. Anyone of those 100 people could get in your apb r error code 9 and mess up your mission even if they couldn't directly kill you. —Preceding unsigned comment added by 208.107.164.144 (talk) 22:59, 4 October 2010 (UTC)Reply[reply]

Development Costs[edit]

If someone can check the veracity of http://brokentoys.org/2010/08/20/apb-how-to-blow-100000000-00/, we might have something worth writing about here. --71.240.46.168 (talk) 03:48, 22 August 2010 (UTC)Reply[reply]

End[edit]

http://www.joystiq.com/2010/09/16/apb-comes-to-a-premature-end/—Preceding unsigned comment added by 173.168.239.69 (talk) 16:18, 16 September 2010 (UTC)Reply[reply]

Was vs Is[edit]

Games should be marked as was as the servers are shut down game is no longer playable. Games are not always marked as present tense see matrix online entry if they are no longer playable. —Preceding unsigned comment added by 81.131.103.156 (talk) 19:31, 5 October 2010 (UTC)Reply[reply]

I apb r error code 9 if the servers are shut then the game is no longer playable so should be referred to in past tense. —Preceding unsigned comment added by 90.196.77.229 (talk) 21:53, 8 October 2010 (UTC)Reply[reply]

The game has been created therefore it exists. Present tense is correct. Whether it is playable or not is a different argument. Only when every remnant of the game code has been deleted from existence can it be said that the game no longer exists and therefore becomes past tense. - X201 (talk) 09:53, 9 October 2010 (UTC)Reply[reply]

Why is matrix online marked as was then? also if a game is not playable it is no longer a game but just a mess of code lying somewhere. —Preceding unsigned comment added by 90.200.224.161 (talk) 19:12, 9 October 2010 (UTC)Reply[reply]

There are old films and TV programmes on archive shelves that aren't currently being broadcast. They don't stop existing just because they aren't being broadcast, likewise, games don't stop existing just because they aren't being played. - X201 (talk) 10:38, 10 October 2010 (UTC)Reply[reply]

but a game is something that can be played, if its not playable its not a game, so it does not exist as a game, especially as an mmo until the servers are turned back on. By definition it cannot be a mmo if no-one can play it. —Preceding unsigned comment added by 86.165.96.58 (talk) 12:34, 11 October 2010 (UTC)Reply[reply]

This IP is correct here, only due to this being an MMO. Half the game exists on a server you need to connect to. If that server is not there, it is unplayable - that is, it is no longer a game, simply a pile of executable code that will not do anything for the user. --MASEM (t) 14:00, 11 October 2010 (UTC)Reply[reply]
Seeing as how private servers will always keep popping up, APB one here, apb r error code 9, any MMO server will never truly be a "was", as there is always a chance of its fans keeping it alive. I think the best compromise would be for a form of wording such as "Game X is a 2010 something game, that had its online service terminated in 2011". I still think that for any hardware or software we should use "is", since the game code still exists.- X201 (talk) 14:26, 11 October 2010 (UTC)Reply[reply]

Article rewrite to accommodate re-release[edit]

Wondering if this article as a whole or specific sections might need to be rewritten so that newer readers won't become confused. For instance, the embargo controversy is no longer relevant since the game is being re-released and K2/Gamers First aren't responsible, but I am not saying that this section should be outright removed. —Preceding unsigned comment added by 198.85.208.101 (talk) 23:58, 27 January 2011 (UTC)Reply[reply]

Engine[edit]

the game runs on a modified Unreal Engine 2

Quote: Denn obwohl APB auf einer abgewandelten und arg angestaubten Unreal Engine 2 basiert, frisst das Actionspiel Hardware zum Frühstück.

Source: Gamestar.de (a well-known professional gaming related magazine in germany) -> http://www.gamestar.de/spiele/all-points-bulletin-reloaded/artikel/technik_check_apb,45066,2316165.html

APB from Spectrum[edit]

APB (All Points Bulletin) Its an old game from Spectrum Synclair apb r error code 9 page dont tell anything about this.

APB reloaded its based on that videogame. — Preceding unsigned comment added by 84.122.250.171 (talk) 19:03, apb r error code 9, 13 September 2012 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on APB: All Points Bulletin. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

checkYAn editor has reviewed this edit and fixed any errors that were found.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 02:26, 16 January 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on APB: All Points Bulletin. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, apb r error code 9, you can add to keep me off the page altogether. I made the following changes: stop in usr/ports/lang/php5-extensions error code 1 you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

☒NAn editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the to true

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 01:48, 1 March 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, apb r error code 9, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ), apb r error code 9.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using apb r error code 9 archive tool instructions below, apb r error code 9. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot(Report bug) 07:27, 1 October 2016 (UTC)Reply[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, apb r error code 9, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022). mount.cifs mount error12 cannot allocate memory you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.

  • If you found an error with any archives or the URLs themselves, smtp error 550 roundcube can fix them with this tool.
  • Cheers.—InternetArchiveBot(Report bug) 03:40, 24 June 2017 (UTC)Reply[reply]

    External links modified[edit]

    Hello fellow Wikipedians,

    I have just modified one external link on APB: All Points Bulletin. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

    When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

    This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template (last update: 18 January 2022).

    • If you have discovered URLs which were erroneously considered dead by the bot, apb r error code 9, you can report them with this tool.
    • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

    Cheers.—InternetArchiveBot(Report bug) 01:46, 19 September 2017 (UTC)Reply[reply]

    Register Map and Descriptions

    The registers are accessible through the APB target interface. The following table lists all the registers required to execute system services on PolarFire devices.

    Address OffsetRegister NameTypeWidthReset ValueDescription
    0x04SYS_SERV_CMDR/W320Request Command
    0x08SYS_SERV_STATR/O320Response Status
    0x0CSYS_SERV_REQR/W320Control Register
    0x10MBX_ECCSTATUSR/O320Mailbox ECC Status
    0x14MBX_WCNTR/W32‘d1Mailbox Write Count
    0x18MBX_RCNTR/W32‘d1Mailbox Read Count
    0x1CMBX_WADRDESCR/W320Mailbox Write Address Descriptor
    0x20MBX_RADRDESCR/W320Mailbox Read Address Descriptor
    0x28MBX_WDATAR/W320Mailbox Write Data
    0x2CMBX_RDATAR/O320Mailbox Read Data
    0x30SYS_SERV_USERR/O320System Service User

    JTAG Status and Error Status - 2022.1 English

    159:155RSVD_READS_0Reserved, returns 0154:148RESERVEDReserved147:136BOOTROM FIRST ERRORBootROM first error code (FEC) detected 135:124BOOTROM LAST ERRORBootROM last error code (LEC) detected 123:110PLM MAJOR ERRORPLM major error code109:94PLM MINOR ERRORPLM minor error code93:64GSW ERRORGeneral software error code for PLM63RESERVEDReserved62BOOTROM NCRBootROM non-correctable error

    Set by RCU BootROM during boot

    61PLM CRPlatform loader and manager boot correctable error

    Set by PLM during boot

    60PLM NCRPlatform loader and manager boot non-correctable error

    Set by PLM during boot

    59GSW CRGeneral software correctable error after boot58GSW NCRGeneral software non-correctable error after boot57CFU Eth0 error while getting interface flags error 56CFRAME ERRORCFRAME error55PSM CRPSM correctable error54PSM NCRPSM non-correctable error 53DDRMC MB CRDDRMC MicroBlaze correctable ECC error 52DDRMC MB NCRDDRMC MicroBlaze non-correctable ECC error51NOC CRNoC correctable error50NOC NCRNoC non-correctable error49NOC USER ERRORNoC user error48MMCM LOCK Apb r error code 9 lock error47AIE CRAI Engine correctable error46AIE NCRAI Engine non-correctable error45DDRMC MC ECC CRDDRMC MC (memory controller) correctable ECC error 44DDRMC MC ECC NCRDDRMC MC (memory controller) non-correctable ECC error43GT CR GT correctable error42GT NCRGT non-correctable error41SYSMON CRSYSMON correctable error40SYSMON NCRSYSMON non-correctable error39USER PL0 ERRORUser-defined PL error38USER PL1 ERRORUser-defined PL error37USER PL2 ERRORUser-defined PL error36USER PL3 ERRORUser-defined PL error35NPI ROOT ERRORNPI root error34SSIT ERROR3SSI technology SLR error33SSIT ERROR4SSI technology SLR error32SSIT ERROR5SSI technology SLR error31PMC APB ERRORPMC APB error. Includes errors from registers: PMC_LOCAL, PMC_GLOBAL, CRP, PMC_IOP_SECURE_SLCR, PMC_IOP, BBRAM_CTRL, PMC_ANLG, RTC30PMC BOOTROM ERRORPMC BootROM validation error29RCU HARDWARE ERRORRCU hardware error 28PPU HARDWARE ERRORPPU hardware error27PMC PAR ERRORPMC switch and PMC IOP parity errors26PMC CRPMC correctable errors 25PMC NCRPMC non-correctable errors24PMC SYSMON0 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON23PMC SYSMON1 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON22PMC SYSMON2 ALARMPMC apb r error code 9 shutdown alert and power supply failure detection errors from SYSMON21PMC SYSMON3 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON20PMC SYSMON4 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON19PMC SYSMON5 ALARMPMC temperature shutdown alert and power supply apb r error code 9 failure detection errors from SYSMON18PMC SYSMON6 ALARM PMC temperature shutdown alert and power supply failure detection errors from SYSMON17PMC SYSMON7 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON16PMC SYSMON8 ALARMPMC temperature shutdown alert and power supply failure detection errors from SYSMON15PMC SYSMON9 ALARM PMC temperature shutdown alert and power supply failure detection errors from SYSMON14CFI NCRCFI non-correctable error13SEU CRC ERRORSEU CRC error12SEU ECC ERRORSEU ECC error11:10RSVD_READS_0Reserved, returns 09RTC ALARM RTC alarm error8NPLL ERRORPMC NPLL lock error 7PPLL ERRORPMC PPLL lock error6CLOCK MONITOR ERRORClock monitor errors 5PMC TIMEOUT ERRORPMC interconnect timeout errors from interconnect mission interrupt status register, interconnect latent status register, and timeout interrupt status register4PMC XMPU ERRORPMC XMPU errors from register access error on APB. Includes read permission violation, write permission violation or security violation3PMC XPPU ERRORPMC XPPU errors from register access error on APB, apb r error code 9. Includes Master ID not found, read permission violation, Master ID access violation, Master ID parity error, apb r error code 9, TrustZone violation2SSIT ERROR0SSI technology SLR apb r error code 9 ERROR1SSI technology SLR error0SSIT ERROR2SSI technology SLR error

    0 Comments

    Leave a Comment