How to resolve “failed to map pci bar” error in dmesg
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
- Tutorial Videos & Installation Guides
FnL Product Line Determining PCIe lane assignment for your SSD7000 Controller MacOS Windows Linux SSD6200 Series Controller SSD7000 Series Controller RocketStor Series RocketRAID Series RocketU Series Motherboard Compatible Report Other Questions Standard Responses for Known Issues or Subjects WebGUI eStore
- Compatibility Reports
- Performance Report
- Workaround Issue
Title: How to resolve “failed to map pci bar” error in dmesg.
Applicable Products: SSD7000 series
1. Problem Description & Analysis:
a. “Failed to Assign” and “Failed to Map PCI Bar” errors are displayed when using the dmesg terminal command in a Linux environment. These errors are also present in the NVMe driver log. The NVMe PCIe Bar MEM application failed, which resulted in a failure of the Map PCIe Bar. This in turn resulted in the NVMe Device failing once the driver was loaded.
b. If the above errors are reported by your Linux system, the problem is most likely related to one of the following (both of which are related to the motherboard platform):
- The motherboard is not compatible with the NVMe storage and/or Linux Operating system. These errors are most commonly associated with motherboards based on an Intel Madison/Tylersburg or similar Chipset, (most of which are no longer in production).
- Insufficient system resources – the motherboard chipset is unable to provide the required PCIe resources to support the configuration. As with #1, this is associated with older chipsets.
2. Recommended Solutions & Workaround:
a. Solution: Use a known compatible motherboard. The compatibility lists are available from the SSD7000 controller’s Resources webpage, and include tested motherboards and NVMe SSD’s.
b. One Possible Work-around: Try disabling the “Realloc” feature.
- Open a terminal and add "pci=realloc=off" to the kernel command line. Then, restart the system to see if the errors are still reported.
- If the errors are still reported, we recommend checking the following link: