Get-ForensicFileRecord : Array dimensions exceeded supported range.

[AndresPae]

Get-ForensicFileRecord : Array dimensions exceeded supported range.

[AndresPae]

MFT Information

MFT size : 2205 MB (0% of drive)

PS C:> [int]::MaxValue
2147483647

Is this reason ?

[jaredcatkinson]

It doesn't appear to be an issue with the overall size of the MFT itself. Based on the StackTrace (thank you for providing that), the issue seems to be with the parsing of a Non Resident MFT Attribute. I'll try to get you a debug version tonight to identify where the issue is happening within the MFT itself. Then we can try to identify the specific attribute that is causing the issue.

Is this a production or test system? In either case, would you be able to provide me with an exported version of the MFT, or even a specific MFT Entry (once we narrow it down)?

[mgreen27]

im getting this same issue on a Windows10 machine over a winrm session running.
(Get-ForensicFileRecord -Path "C:\$Extend\$UsnJrnl").CopyFile($output + "\disk\$J","$J")
The Get-ForensicFileRecord component works but im hitting the same issue on the copy file.

$StackTrace
at PowerForensics.FileSystems.Ntfs.NonResident.GetBytes()
at PowerForensics.FileSystems.Ntfs.FileRecord.GetContent(String StreamName)
at PowerForensics.FileSystems.Ntfs.FileRecord.CopyFile(String Destination, String StreamName)
at CallSite.Target(Closure , CallSite , Object , Object , String )

[mgreen27]

testing this again across a few environments I believe this issue is caused when the file being copied is greater than the [int32]::MaxValue in bytes.
For example the $J above was above 3GB, I also tested on another file > 3GB and hit the same error.
The issue is consistent across Powershell and WinRM shell

Just to differentiate from the original issue. I can list the File details using Get-ForensicFilerecord but when copying hit the issue.

[mgreen27]

Hello,

I am reviewing source code to see how Powerforensics works about an issue I have been seeing where when running Powerforensics extractions over WinRM, Memory spikes on the target machine to larger than the copied file.

I can see Powerforensics seems to try to create an array of the full byte stream - why we hit the [int32]::MaxValue issue on large files.

I think even increasing to Int64 we will see memory issues, a better way would be to chunk the files up into smaller sizes and append to the destination file.

Matt