djhead
Military Intelligence
went through the same problem. Wish I would have caught it sooner, and saved you some headache. The firepod's ports are a well documented problem.
pipelineaudio
Well-known member
I wouldnt dream of sticking an audio interface and a hard drive on the same firewire port
B
bluelonestar
New member
i have two ports on my firewire card. presonus recommends to daisy chain them...thats the only reason why i did. should i plug the external hard drive into the firewire card instead of the firepod? will that make any difference?
pipelineaudio
Well-known member
not sure...I would rather plug it in to another firewire card
B
bluelonestar
New member
ok, i fixed it.
right clicked on "my computer"
clicked "manage"
clicked "event viewer"
clicked "system"
found the errors and visited microsofts support with the 2 error codes and followed these instructions:
Message: Delayed Write Failed
To limit the maximum transfer size on a device
Click Start, Run, Type: regedit
Using Regedit, navigate to the following registry value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SBP2
A list of manufacturers and models is displayed.
Double-click the folder for the device.
You can determine the manufacturer, model identification number, and Logical Unit Number (LUN) by running the Disk Management tool or Device Management tool and then viewing the properties of the disk in question.
Double-click the folder for the NodeID for your device.
Right-click the Device Parameters folder, point to New, and then click DWORD Value.
In the right pane, type LegacyFlags, and then press ENTER.
Double-click LegacyFlags and then type 1 in the Value data box.
Caution: This bit flag key should only be set to 1.
The SBP2Port device driver must be unloaded and then loaded again. To unload and then load the driver, unplug the device. Wait 30 seconds, and then plug the device back in. Alternatively, you can restart the computer.
Then i had to repair the file system:
Message: The system failed to flush data to the transaction log. Corruption may occur
If this message appears frequently, run Chkdsk to repair the file system.
To repair the file system
Save any unsaved data and close any open programs.
Restart the computer.
The volume is automatically checked and repaired when you restart the computer.
Alternatively, you can run the Chckdsk tool from the command prompt without shutting down the computer first.
Click Start, click Run, and then type
cmd
At the command prompt, type chkdsk /R /X Drive:
Chkdsk runs and automatically repairs the volume.
right clicked on "my computer"
clicked "manage"
clicked "event viewer"
clicked "system"
found the errors and visited microsofts support with the 2 error codes and followed these instructions:
Message: Delayed Write Failed
To limit the maximum transfer size on a device
Click Start, Run, Type: regedit
Using Regedit, navigate to the following registry value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SBP2
A list of manufacturers and models is displayed.
Double-click the folder for the device.
You can determine the manufacturer, model identification number, and Logical Unit Number (LUN) by running the Disk Management tool or Device Management tool and then viewing the properties of the disk in question.
Double-click the folder for the NodeID for your device.
Right-click the Device Parameters folder, point to New, and then click DWORD Value.
In the right pane, type LegacyFlags, and then press ENTER.
Double-click LegacyFlags and then type 1 in the Value data box.
Caution: This bit flag key should only be set to 1.
The SBP2Port device driver must be unloaded and then loaded again. To unload and then load the driver, unplug the device. Wait 30 seconds, and then plug the device back in. Alternatively, you can restart the computer.
Then i had to repair the file system:
Message: The system failed to flush data to the transaction log. Corruption may occur
If this message appears frequently, run Chkdsk to repair the file system.
To repair the file system
Save any unsaved data and close any open programs.
Restart the computer.
The volume is automatically checked and repaired when you restart the computer.
Alternatively, you can run the Chckdsk tool from the command prompt without shutting down the computer first.
Click Start, click Run, and then type
cmd
At the command prompt, type chkdsk /R /X Drive:
Chkdsk runs and automatically repairs the volume.
dgatwood
is out. Leave a message.
Gross. Both of those look like what happens if you're getting massive data dropping between the computer and the device. This points to a bug in the FIREPOD hardware, unfortunately, or at the very least, a firmware bug.
If memory serves, a common cause for this problem is companies using a FW800 cell with a FW400 PHY and forgetting to program the FW800 cell to slow down to 400Mbit speed when talking to that PHY. Another possibility is that the FIREPOD simply isn't servicing interrupts fast enough and is dropping packets.
Either way, there's nothing Windows can do other than keep retrying, and apparently Windows is giving up. That said, in the presence of such massive FireWire bus corruption, I've seen Mac OS X and other OSes give up, too, so it's hard to be too critical of Windows (even though I would like to be
).
Here's my advice: do not under any circumstances chain any device through the FIREPOD unless it is another audio device. That way, you'll always be transferring data at a slow enough rate that the FIREPOD can keep up.
If memory serves, a common cause for this problem is companies using a FW800 cell with a FW400 PHY and forgetting to program the FW800 cell to slow down to 400Mbit speed when talking to that PHY. Another possibility is that the FIREPOD simply isn't servicing interrupts fast enough and is dropping packets.
Either way, there's nothing Windows can do other than keep retrying, and apparently Windows is giving up. That said, in the presence of such massive FireWire bus corruption, I've seen Mac OS X and other OSes give up, too, so it's hard to be too critical of Windows (even though I would like to be
).Here's my advice: do not under any circumstances chain any device through the FIREPOD unless it is another audio device. That way, you'll always be transferring data at a slow enough rate that the FIREPOD can keep up.