For my model of Maxtor hard drive there were three different numbers I needed to identify a replacement controller board: Drive Code Number: YAR41BW0 First 7-digits of the drive Model Number: 6Y080L0 9-Digit Code number on the largest IC on the controller: 040111500 Edit: Also I found that not all models of Maxtor hard drives have bios chips (refer to picture). Yes, I am well acquainted with the Disk Management tool. Unfortunately there are no paths starting with Device Harddisk# visible here. The harddisk5 dr5 appears like a logical drive and partition on one of the non-system disks. The system disk will be disk 0. It appears as Disk 1 on my machine. Drivers › Hard Disk Controller. Hard Disk Controller. Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0. HARD DISK CONTROLLER IS MARVELL 91XX CONFIG ATA DEVICE DRIVER DOWNLOAD - Athlon 64 Motherboard: New 04 Aug 3. The matching Intel Core i7 Ivy Bridge also has many new features. Brings up a nice report on the controller.

If your RAID disks are not recognized by the Lazesoft WinPE boot disk, you need to load the proper RAID driver files for your RAID controller.

Here are the steps to load RAID controller driver files from Lazesoft WinPE boot disk:

There might be an instance, wherein the drive gets corrupt or format while enabling the disk controller in BIOS. Therefore, to resolve all such issues, one can use Computer Data Recovery Software. It is a simple and reliable solution, which helps to recover all deleted files from the HDD.

Sysnucleus Hard Disk Controller Driver

1. Find RAID controller driver of your computer for Windows Server 2008 R2. (If you do not know how to or cannot find Windows Server 2008 R2 driver for your RAID controller, please feel free to contact us at support@lazesoft.com.
2. Download the driver files package or setup file. And then extract the driver files.
3. Install the new, downloaded version of the Lazesoft Recovery Suite.
4. Launch the Lazesoft Recovery Suite.
5. Click <Burn CD/USB Disk> on the home page of Lazesoft Recovery Suite
6. Click <Options> on the welcome page of the Lazesoft Media Builder.
7. Enable the option <Specify WinPE Version> and select <Windows 7 64 bit PE> (Windows 7 64 bit has same core with Windows 2008 R2).
8. Click <OK> to save the options.
9. Follow the Lazesoft Media Builder ‘wizard’ to create a WinPE boot disk.
10. Copy the extracted the RAID controller driver files folder to a USB disk.
11. Insert the USB Disk into your locked/target computer.
12. Reboot your locked/target computer from the new burned Lazesoft WinPE boot disk
13. On the home page of Lazesoft Recovery Suite boot disk, click <Load Drivers>, after boot disk is loaded.
14. Load the driver file, *.inf, from the the extracted the RAID controller driver files folder.

If you do not know how to find and load your RAID drivers, please contact our technical staff with your computer brand name/model number and RAID controller brand name/model number. We will help you find the proper driver files, then reply with detailed steps to download and load RAID drivers.

Sysnucleus Hard Disk Controller Drivers

Download and try USBTrace evaluation version:

• Ease of use

  USBTrace is an easy-to-use USB protocol analyzer. To start analyzing a USB device, just select the device to be analyzed and click the 'capture' button.

• Ease of viewing captured data

  USBTrace decodes each and every captured USB protocol request, and displays it in an easily readable format. Data buffer, if any, associated with the request is also displayed.

• Monitors USB requests at all levels

  With USBTrace you can analyze USB requests at USB Host Controllers, USB Hubs or USB devices.

• USBTrace does not use any filter drivers

  Unlike other software-based USB analyzers, USBTrace does not use any filter driver to capture the USB protocol. So USBTrace will not disturb the PnP system due to its presence.

• Captures all USB protocol data during device enumeration

  USBTrace is capable of capturing all USB requests exchanged between the host controller/hub and the device during device enumeration. See USB Enumeration Explained to know how USBTrace is different from other USB analyzer software.

• Displays valuable information for device driver developers

  The IRP, URB and IO_STACK_LOCATION structures associated with each captured request is decoded and displayed by USBTrace. Also, in addition to capturing URBs, USBTrace captures Internal USB IOCTLs, User mode USB IOCTLs, PnP and Power IRPs.

  See Complete list of USB requests captured, decoded and displayed by USBTrace USB Analyzer.

  USBTrace also allows device driver developers to capture USB requests made/received by any device object in the USB device stack.

• USBTrace can be setup to automatically capture hot plugged devices

  With this option enabled, USBTrace will capture USB requests from all newly plugged devices. This option can be used to monitor USB requests during device enumeration. Read about capturing hot plugged devices.

• Search and Filter captured requests

  Advanced search feature allows you to search the capture log for request types and/or buffer contents of requests.

  The filtering feature allows you to exclude requests which you are not interested in while capturing. You can also apply filters based on endpoint addresses.

• Comments and Bookmarks

  Comment and Bookmark features help you to document the captured USB protocol data by adding notes and highlights.

• View & export detailed device information

  View USB Device, Hub, Configuration, Interface, Endpoint descriptors & Windows specific USB enumeration information. Device information can be exported as an HTML or text file.

• Supports device class decoding
  USBTrace can decode class specific usb descriptors/requests and display detailed information regarding them. Read more about USB device class decoding

• Fully compatible with ACPI features

  You can shutdown, hibernate or standby your system while running USBTrace.

• Saving captured data

  The captured USB protocol data can be saved for storage and for viewing later.

• Export log as HTML, XML, Text or CSV reports

  The Export Utility allows you to export the captured USB transactions as an HTML, XML, text or CSV file, in addition to the native USBTrace binary file format.

• Background capturing for improved performance

  Background capturing facilitates high performance capture sessions. The GUI is not updated while capturing. The logged transactions are displayed only when capture operation is stopped.

• Continuous capturing for non stop analysis.

  For a normal capture session, USBTrace will stop capture operation when the internal log data buffer is full. With continuous capturing, this will not happen. When the buffer is full, instead of stopping capture, USBTrace will wrap around the buffer and start writing data again from the beginning.Continuous capturing simulates an infinite buffer.
  Read more about Background and Continuous Capture.

• Capture device traffic directly to file.

  Using this feature you can route the data captured from devices directly to a file on your hard disk (or any other storage device). The user interface will not be updated during capture operation. This results in high performance capture sessions which can capture large amount of data. This feature also helps to debug unstable or faulty systems by ensuring that the captured data is not lost even if the system crashes/restarts during capturing. Read more about capturing data direclty to file.

• Trigger

  Trigger facility allows you to define a condition and capture operation will stop automatically when that condition is satisfied.

• Performance Statistics

  Performance Statistics feature allows you to extract a lot of valuable performance related information from the captured data. The values of various performance counters and Read/Write data transfer rate graph are displayed. Performance statistics can be exported as an HTML or text file.

• Set any captured request as 'time 0' request

  Any request in capture log view can be set as the timing reference request using this feature. The timestamp of the selected request will be set to zero and those of others will be marked relative to this reference request. This feature is helpful to find the timing of various USB transactions in reference to a selected transaction.

• Send support requests and check for updates directly from the application

  In case you need support you can contact USBTrace Support Team directly from the application (See the program's help menu). Your support request along with the internal error log file will be emailed to us. Once we receive your error report, our support engineer will contact you at the earliest. You can also check for availability of new updates from the application help menu.

• Decode captured data using user defined structure templates

  You may define your own structure templates using which the captured data can be decoded. Structure definitions are specified via a template XML file which can be edited from within USBTrace.