[Probable Solution:] DiskWarrior error 2154

Question

I've been meaning to post this for awhile; ran into it again this week so thought I'd put it out there for, apparently, many others baffled by:
DiskWarrior ERROR (2154); not enough memory, restart from CD, etc.
So, there are times when a 2154 genuinely is a memory issue; the drive/volume you are attempting to rebuild (quite often a Time Machine drive) has such a large and complex directory that you really do need a substantial amount of free disk space on a known-good startup volume, especially when the CD gives you the same message. If your current boot volume won't do, you may need to install a fresh OS on an extra drive/volume with plenty of free space (40-50-100GB+) in order to allow DW room to breathe.
The probable underlying cause when you're certain you have plenty of free startup disk free space to go into VM as needed, is that the volume/drive you are attempting to repair has a case of bad blocks/sectors. For whatever reason, DW is unable to always properly fault to a read/write error, and instead goes nuts consuming memory trying to get past it, and throws a 2154, instead.
Use a utility like Drive Genius at this point to scan your entire troubled drive (including multiple volumes, if applicable) for bad blocks, and be sure to check 'Spare Bad Blocks' or you'll just have to scan it twice.
Chances are, not only will you find bad blocks, but it may also take a number of hours or even days to complete the scan. Even then, following up with DW to rebuild what must then surely be a corrupted directory, may still net you a 2154. Today, I got lucky; after a four day scan on a 3TB drive, finding 1571 bad blocks, DW still puked a 2154, whereas Drive Genius 3 was able to resurrect a mostly functional drive using its own version of the 'Rebuild Directory B-Tree' function. However, DG does not *optimize* the directory, nor give you a rescue and damaged file report/preview), so I still chose to follow up with DW. Sure enough, now DW got past the 2154 in Step 5, but immediately went into 'Speed reduced by lack of memory' mode, given the immense number of linking files on a Time Machine drive.
The good news is I got a list of bad files that was pretty reliable; the bad news is I lost a ton of data, despite less than 6MB of actual damaged blocks (<0.1% of the drive total), as too many files were linked inside those bad blocks.
The final lesson? Time Machine is never enough; local clones are never enough; you should also have offsite data backups. In this case I was well heeded and well-covered; but there was an amount of very fresh data that never made it to more then my TM before a FireWire device (original iSight camera) caused a massive hard crash, damaging blocks and destroying a total of four hard drives on a Mac Pro. Ouch. Sometimes, no matter how diligent you are, there's a window in which you'll be caught with your pants down.
HTH
Frederico

Answer 1

1300 is instrument specific error. This can be caused by a number of things. There could be an incompatability between some of your settings (i.e. exceeding current limit for a given voltage range) or in the case of a driver that supports multiple models of instruments, a value out of range for that particular instrument. Along with the error code, what is the text in the source box of the error indicator? A quick look at the driver says that there should be.