• left-quotesOur server that ran a SQL database for one of our large clients crashed, and two of the five SAS drives were not reading and reported ‘Off-line’...”

  • left-quotesOur main backup server for a large financial institution crashed, and we were unable to get the RAID back up and running...”

  • left-quotesOne of our primary databases that contained critical financial data crashed, and we could not get it up and running again - the server had more than 24 drives in it containing thousands of gigabytes of mission-critical data…”

Server And Raid Data Recovery And Digital Forensic Investigations

Advanced server data recovery, forensic data recovery and digital forensic investigations from ransomware affected, crashed, broken, noisy, clicking, corrupt, formatted, deleted, re-loaded, burnt, fire damaged, power and lightning surge damaged, water damaged, virus damaged Windows, Linux, Apple Mac, Unix and Netware server drives and volumes irrespective of the configuration (RAID, NAS, SAN, mirror, stripe-set, JBOD etc.) or the condition of the media or the potential data loss situation.

Typical Potential Data Loss Scenarios Would Include:

  • All types of ransomware-affected storage devices
  • Multiple servers and/or RAID drive failure
  • RAID controller failure or failed controller no longer available
  • Failed RAID controller firmware upgrades
  • RAID not ready
  • RAID metadata failure
  • Un-mountable volume, i.e. after a power failure or where More than one drive failed in a RAID set
  • Partially rebuilt RAID volume
  • An automatic or forced RAID rebuild
  • Damage caused by system repair utilities, e.g. check-disk (chkdsk) and fsck
  • Primary hard disk failure
  • Server not ready
  • Inaccessible boot device
  • Unable to access drive "X"
  • The device not ready; reading drive "X"
  • NTLDR is missing
  • Operating system not found/missing operating system
  • The BIOS recognizes the drive but with garbage parameters
  • The BIOS recognizes the drive, but the data is inaccessible
  • Improper drive or media replacement
  • Fire/Water Damage
  • The drive reports bad sectors
  • Corrupt data
  • Formatted, Fdisked, partially re-loaded hard disk drives
  • The server or RAID device won't boot
  • Corrupted parity/data drive
  • Accidental/Intentional deleted partition
  • Incomplete and/or partial server rebuilds
  • Grinding or clicking noises, normally associated with electro-mechanical failure
  • The drive is no longer recognized by the BIOS after rebooting, despite the platters spinning

We Recover and Investigate All Server and Raid Configurations and Volume Types, Including -

  • All types of hardware and software RAID configurations, including:
    • RAID array levels - RAID 0, RAID 1, RAID3, RAID 4, RAID 5, RAID 5E/EE, RAID6;
    • Striped, Spanned, Simple, Mirrored, JBOD volumes and array sets;
    • HP ADG, RAID 1E/1EE, Nested RAID (10, 50, 60, 50E, etc)
  • NAS and SAN devices
  • Multi-disk Btrfs configured using mdadm or hardware RAID
  • Storage systems like NetApp, EMC and HP use atypical block sizes - 520 bytes, 524 bytes, 528 bytes, etc.
  • Volumes encrypted with LUKS, BitLocker and FileVault 2, APFS volumes encrypted with Fscrypt and eCryptfs etc.
  • Digital video storage (DVR/CCTV) systems using proprietor (vendor-specific) storage configurations
  • All Linux server (and desktop) distributions and versions, including Ubuntu, CentOS, Debian, Fedora, Red Hat Linux (RHEL), SUSE Linux, Oracle Linux, AlmaLinux, Rocky Linux, SLES, Arch Linux, Slackware, VzLinux, True NAS, AlmaLinux, Photon OS etc.
  • Windows NT3.5, Windows NT4, Windows Server 2000, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022 and all MS SQL file server versions.
  • SCSI hard disk drives
  • SSD (Solid State), IDE, PATA, SATA, SAS server hard disk drives
  • Virtual machines and virtual volumes
  • Logical Volume Management (LVM)
  • File, Application, Mail, and Web Server
  • Fiber Channel
  • Basic disk & dynamic disk configurations
  • SUN/Oracle with ZFS stripe - RAID-Z
  • SUN/Oracle ZFS hardware RAID

We Recover and Investigate All Partitions, File Type And File Systems, Including: -

  • All versions of MS-DOS
  • 12-bit FAT (FAT12)
  • 16-Bit FAT (FAT 16)
  • 32 Bit FAT (FAT 32)
  • Extensible File Allocation Table (exFAT)
  • New Technology File System (NTFS)
  • New Technology File System version 5 (NTFS 5)
  • Windows NT3.5, Windows NT4, Windows Server 2000, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022
  • Windows 3.0, Windows 3.1, Windows 95, Windows 98, Windows ME, Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10 and Windows 11
  • Microsoft Live File System - Universal Disk Format (UDF) - CD/DVD media
  • Resilient File System (ReFS) - Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
  • Second, third and fourth extended file system (EXT2, EXT3 and EXT4) - Linux
  • Reiser File System (ReiserFS) - Linux
  • Linux distributions and versions, including Ubuntu, CentOS, Debian, Fedora, Red Hat Linux (RHEL), SUSE Linux, Oracle Linux, AlmaLinux, Rocky Linux, SLES, Arch Linux, Slackware, VzLinux, True NAS, AlmaLinux, Photon OS etc.
  • B-tree file system (Btrfs) - Linux
  • Macintosh File System (MFS), Hierarchical File System (HFS), Mac OS Extended (HFS+), HPFS, Apple file system (APFS), ISO9660
  • UNIX File System (UFS1 and UFS2) - Mac, Unix
  • Journaled File System (legacy JFS) and Enhanced Journaled File System (JFS2) - IBM AIX and Linux
  • Virtual drives - VMware (VMFS), DD, IMG, BIN, VHD, VHDX, E01, ESX(i) volumes
  • Novell Storage Services (NSS) and NetWare File System (NWFS)
  • HP-UX VxFS version 6 and below
  • Symantec Storage Foundation
  • SUN/Oracle ZFS
  • OpenVMS
  • ISO 9660 - CD-ROM
  • LYNX OS (LynxFS)
  • High-Performance File System (HPFS) - OS2
  • Yet Another Flash File System - Yaffs2

Our experienced technicians are here to help; please do not hesitate to contact us.