Data Recovery

External SCSI Disks; External Server Storage; Fibre Channel 40 Pin Disks; HARD TO FIND SCSI DRIVES; SAS TAPE STORAGE; SATA DISKS; SCSI Tape Storage.

We recover data from many types of Raid failure, Virtual Disks, Server Hard Drives, NAS drives.
This includes SCSI, iSCSI, VHD, VMDK, HDD, and raid array rebuild problems.
We also supply donor hard drives, repair USB memory sticks and dongles, and repair HDD SATA / IDE connectors.
We have recovered data for ...

  • BBC
  • Police
  • MOD
  • NHS
  • BAE Systems
  • HSBC
  • British Nuclear
  • The British Library
  • Royal Munitions Factory (Radway Green)
  • Essex County Council
  1. The company Buffalo We stand for competence and safety Find out more about us and our long-standing product development. In addition to pioneering developments in the wireless field, we have developed many patents that make our products unique.
  2. Part.1 Connecting iSCSI target with Windows iSCSI initiator 1. To launch the iSCSI initiator in Windows 7, please go to Control Panel Administrative Tools. On the iSCSI Initiator Properties page, click on Discovery, enter the IP address of.
  3. The iCSI configuration tool allows you to manage and configure the Buffalo TeraStation™ III iSCSI (TS-IXL). It also features automatic drive configuration and detection modules.
  4. BUFFALO HD-PCTU2 USB Device Drivers Download In our share libs contains the list of BUFFALO HD-PCTU2 USB Device drivers all versions and available for download. To download the proper driver by the version or Device ID.

and many others....

Our friendly team are here to help recover your data. Email or give us a call now!

Raid Data Recovery

Fast action!

We understand the time critical nature of central server and nas box failures. Countless times we have worked through 24 hours and weekends to return the data quickly, and some times for the next morning so that the organisation can continue to work on their files, documents databases and spreadsheets.

Data Recovery covers anything from modern Raid, Virtual Disks, iSCSI, all the way back to older SCSI Compaq servers.
We also write our own data recovery software, and bespoke recovery from optical disks or old proprietary unknown file systems.
We recover systems with a variety of operating system, e.g. Windows, Macintosh, Novell, Linux and Sun Solaris.

Recover Data from Virtual Disk VM machines and files

Virtual Disk Servers problems we have recovered data from ...

  • Buffalo Terastation Raid 5, Disk 2 in failed state and storing NTFS disks in VMFS filesystem
  • Iomega ix4-200d iSCSI VMWare Virtual Disks.
  • FibreCat SX80-i server ESX VM-ware VMFS Virtual Machines on 12 hard disk Raid 5 Raid Controller failed.
  • Thecus i5500 iSCSI with 2 disks missing from Raid5 array and partitions formatted in Windows NTFS file system.
  • Fujitsu Siemens Fibrecat SX80i VMFS Virtual File System disappeared after power outage, Raid 0 with ESX iSCSI VHDK files.
  • Buffalo Terastation Rack Mounted TS-RI4.0TGL/RR-EU iSCSI RAID 5 2x LUN's with NTFS and VMFS partitions holding VM's.
  • HP385 Server Raid 0,1 (ie Raid 10) with 4x 147GB SCSI drives. 3 out of 4 drives failed, data in VMFS virtual disks disks.
  • Synology DiskStation NAS 12 x 2TB HDDs , Citrix Virtual Machine Disks. Disk down from Raid 5 array, LVM vhd files.
  • Thecus i5500 iSCSI NAS 5x 1TB drives no data access as 2 disk missing from the RAID 5 and iSCSI partitions formatted in Windows NTFS file system.
  • HP StorageWorks MSA2324fc G2 - 3 drives failed in the Raid 6 ADG array, vdisk offline LEFTOVR (leftover) - vmdk file recovery from VMFS.
  • Citrix Server, VM-Ware (VMFS) / ESXi and VHD files created using Windows Server 2008 R2 and 2012 R2, Windows 10, Windows 8.1, Windows 8, Windows 7, Hyper-V VMWare server.

Recover Data from Raid 0 1 5 6 10 Servers

Raid disks problems we have recovered data from ...

  • Lacie INNS04-4200-LAC NAS device that has stopped working. The Lacie chassis had a Raid-5 configuration, 4 drives, 1TB each.
  • Buffalo Terastation Raid Array E13 E23 error.
  • Dell PowerEdge SCSI raid array with 2 disks missing from raid 5 array.
  • Buffalo Terastation Pro. disappeared off the network.
  • HP Server SCSI hard disks missing 3 out of 4 disks from Raid 5.
  • Buffalo TeraStation Live just showing JBOD / disk spanning - raid array lost.
  • Buffalo Linkstation RAID 5 NAS a disk had failed then raid array rebuild failed.
  • Dell PowerEdge R610 server with Power Vault MD1000 and 15 SAS drives Dell PERC 6/E controller in degraded mode
  • Acer Easystore disk change notification and raid array will have disappeared.
  • Dell Poweredge 1850 and Dell PowerVault 220S SCSI disks PERC RAID card configuration no arrays or logical disks present.
  • Buffalo Terastation PRO raid error during the rebuild, another drive failed.
  • Buffalo Terastation Live EMERGENCY MODE NO ARRAY INFO.
  • Terastation TS3400R can see the shares but access is blocked.
  • Thecus N4100+ NAS, supplied by Evesham RAID 5 device was not detected on the network.
  • Lacie SS4000e RAID drive lost data after power outage.
  • Terastation System error E04 can’t load kernel.
  • Iomega Storcenter NAS failed while reconstructing RAID disk.
  • Intel SS4000E Nas box after power failure requested the disks to be initialized status is now New instead of RAID5 array.
  • Buffalo Terastation Error meassages Raid Array 1 E14 RAID can't mount, Raid5 Broken, and HD2 broken E30 Replace the disk.
  • Terastation Emergency Mode Error EM963. After a power outage it was showing “degraded” rebooted to get the “Emergency Mode No RAID Info Found” error.
  • Intell SS4000e , HDD3 failed, Raid5 degraded - shows share folders but no data after rebuild.
  • Lacie 2BIG network drive Mirrored Raid drives power failure.
  • Acer Altos EasyStore after power failure showing shared folders as NOT READY.
  • Buffalo Terastation with E06 Raid issue.
  • Netgear SC101 Recovery - oh yes the toaster of the network drive world
  • Evesham Silverstor NAS lost array after power failure
  • Readynas by Infrant and Netgear with their infamous X-RAID system.
  • Intel Server SR1450 RAID CONTROLLER Intel SRCU42X.
  • SCSI Raid Data Recovery
  • Apple Mac HFS Server Raid Recovery
  • G-Raid Recovery
  • Linux Raid Data Recovery

On-Site Data Recovery

On-Site (mobile) recovery services we have undertaken ...

  • Buffalo Terastation Lost Raid Array for MOD.
  • Document Scanner (DIP work-station) conversion to pdf files.
  • MIRRA 2 DVD RAM disks square Cartridge / case, Data is in NICE proprietary format, unknown file system.
  • 5.2GB MO disks Plasmon P5200E from a NICE telephone recording system - physical errors not allow files to be copied off the disks.
  • OpenText Integrated Document Management (IDM). Convert to TIFF with doc ifnid and disk set ifnds numbers and move to Unix.
  • FileNet Data recovery from HP SureStore Optical MO disks which FileNet system could not read the files due to errors
  • HP WORM optical disks from OpenText which could not be read.
  • Soft-Co PCDOC Enterprise EDMS system transfer scanned documents written to Magneto optical disks to TIF/PDF.

Data Recovery News and Reviews

Click for Data Recovery News.

Click for Data Recovery Reviews.

Data Recovery

Data Recovery problems that we recover data from are listed below.
Raid Array Rebuild, Raid Rebuild, On-Site Data Recovery, File Conversions, Disk Conversions.
We recover data from many types of Raid failure, Virtual Disks, Server Hard Drives, NAS drives. This includes SCSI, iSCSI, VHD, VMDK, HDD, raid array rebuilds..

For further information on Data Recovery see this info

Search by either entering keywords or by selecting a product.

Configuration and Usage of iSCSI Volumes on a Buffalo TeraStation

Buffalo Scsi & Raid Devices Driver Download For Windows 7

iSCSI, which stands for Internet Small Computer System Interface, works on top of the Transport Control Protocol (TCP) and allows SCSI command to be sent end-to-end over local area networks. iSCSI works by transporting block-level data between an iSCSI initiator on a server and an iSCSI target on a storage device. The iSCSI protocol encapsulates SCSI commands and assembles the data in packets for the TCP/IP layer. Packets are sent over the network using a point-to-point connection. Upon arrival, the iSCSI protocol disassembles the packets, separating the SCSI commands so the operating system (OS) will see the storage as a local SCSI device that can be formatted as usual.

Examples iSCSI Usage


Here are some instances where iSCSI can be used to provide a useful storage alternative:

1. Adding storage to an existing server.

In this case, you may be running short of space on an existing server and don't want to have to reconfigure your network or have users change what path they use to access the existing server. Connecting a RAID backed iSCSI volume will allow you to add terabytes of storage to an existing server without shutting it down or adding physical drives. This is especially useful if the server lacks bays to add additional drives.

2. Providing storage with domain-level file and folder permissions.

If you have a need for volumes with NTFS permissions at the file or folder level, a standard TeraStation cannot provide this. By using iSCSI volumes attached to a Windows server, the volume can be formatted with an NTFS file system and administered the same as any other Windows volume.

3. Providing storage for a cluster.

Depending on the OS used on the clustered hosts, you can use iSCSI volumes on a TeraStation or another WSS NAS to provide storage for a high availability cluster. For VMware (ESXi) hosts, any TeraStation that supports iSCSI can provide storage to a cluster. If you need to run a Windows cluster (for applications like Hyper-V, SQL, or Exchange) you will need host the iSCSI target on a WSS based unit.

Rules for iSCSI

While iSCSI can provide a useful and efficient supplement to straight NAS functionality, there are some hard and fast rules that must be followed as well as some recommendations to increase performance and manageability.

1. Do not connect multiple Windows hosts to a single iSCSI volume.

This is the biggest mistake many users make with iSCSI devices. Windows uses the NTFS file system, which is not designed to be shared between hosts. Remember that iSCSI provides a block-level storage device to the host. To the OS it appears as a physical drive installed in the system. The only time that multiple Windows hosts should be connected to the same iSCSI volume is when the volume is providing storage for a failover cluster. For Buffalo devices this is only possible with a WSS-based NAS.

If you connect multiple Windows hosts to the same iSCSI volume without the benefit of MS Cluster Services to arbitrate disk access, it will result in data corruption because none of the hosts will notify each other of open files, reads, writes, or changes to the master file table. It's not a matter of if data corruption will occur - it's a matter of when.

One way to ensure that only one host is allowed to connect to the volume is to configure CHAP authentication, either one way or mutual. A link to an article explaining how to set this up is included at the end of this document.

2. Always use the correct startup and shutdown sequence.

Buffalo Scsi Vs

Buffalo scsi vs

Try to avoid having the iSCSI target (storage device) shut down while the server is still accessing it. Imagine disconnecting a hard drive from a computer in the middle of a write operation. The result will often be data loss or data corruption. When shutting down, always shut down the server(s) first, then the storage device and the switch(es) last. When starting up go in the reverse order: switch, storage, server. Make sure that each device is fully booted before moving on the next one. It is strongly recommended that all components are connected to a UPS to prevent connection loss due to a power outage. If the storage device has multiple power connections, such as the TS7120, it is recommended to connect each power supply to a different power source if possible.

NOTE: In the event that an iSCSI volume gets disconnected/reconnected from a Windows server that has shared folders on the iSCSI volume, restarting the 'server' service in the services.msc snapin should re-activate the shares.

3. Do not team or trunk ports used for iSCSI.

Because of the way that iSCSI sessions are created and managed, NIC teaming or trunking will reduce the performance of iSCSI. Instead of teaming set up multiple NICs and use MPIO settings in the host's iSCSI initiator to configure multipath options. This will result in overall better performance and better utilization of multiple network paths.

4. Segregate iSCSI traffic from the rest of the LAN.

While not required, it is recommended to segregate iSCSI to a separate LAN segment, either by creating a separate VLAN or by using physically separate switches. The nature of iSCSI generates a tremendous amount of network traffic and keeping the iSCSI traffic separate will increase the performance of both the iSCSI LAN and the regular LAN.

5. Optimize switch configuration

It is recommended to have flow control and RSTP enabled on all switch ports used for iSCSI.

6. Jumbo frames

Enabling jumbo frames can increase performance in iSCSI environments but is not a panacea. If you are seeing very poor performance in your iSCSI environment, enabling jumbo frames will not be likely to improve performance and may degrade performance even further. The use of jumbo frames can increase performance in environments where performance is already good and all other parameters are optimal, but in some rare cases it can actually degrade performance in an otherwise well-performing environment.

Rules for using iSCSI volumes as shared storage in a clustered environment

While iSCSI can be extremely useful as shared storage for a cluster, there are some rules you need to keep in mind when planning/configuring the cluster.

1. Windows clusters can't use iSCSI volumes on a standard TeraStation for cluster storage.

Standard TeraStation devices do not support the use of SCSI-3 persistent reservations on iSCSI volumes. This is a requirement to pass the validation tests on a Windows cluster. If you need to create shared storage for a Windows cluster you will need to use a TeraStation running WSS (Windows Storage Server) instead of a standard TeraStation.

2. VMware (ESXi) clusters can use iSCSI volumes on a standard TeraStation.

If you are planning an ESXi cluster for a virtualized environment, you should have no problem using iSCSI volumes on any TeraStation products to provide the storage. Because ESXi uses VMFS (VMware File System) for datastores there is no need for persistent reservations. VMFS is a shareable file system and all attached hosts can lock the parts they are currently accessing to prevent other hosts from making changes and causing data corruption.

For more information, please see these articles:

Join The Herd

Buffalo Scsi Adapter

Stay up to date on the latest product information

Buffalo Scsi Gun

Join Now
Coments are closed

Most Viewed Posts

Scroll to top