Dennis HilkLinux diagnosticsDE

Storage controllers

JMicron JMB362 SATA function

This JMicron JMB36x SATA function is an AHCI driver match. JMicron multifunction controllers can also have a different PATA path, so controller family and individual PCI function must be kept distinct.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The PCI header names 197b:2362 as JMB362; ahci includes that exact function. This pair does not identify a disk brand or prove that a separate IDE/PATA function uses ahci.

Curated identifiers
pci 197b:2362

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The entry selects board_ahci_ign_iferr. This controller-specific error-handling selection is part of upstream ahci; it is not a recommendation to suppress unrelated errors manually.

  • ahci — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

Controller firmware, option ROM and drive firmware can be separate. The reviewed sources do not establish a host-loaded filename for this profile; firmware revision and update policy require the actual controller and OEM identity.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Check the PCI function and bound driver

lspci -nnk -s BDF

Replace BDF with the domain:bus:device.function address. Look for [197b:2362] and Kernel driver in use. ahci in Kernel modules is only a candidate, not proof of binding.

Inspect visible block-device identities

lsblk -d -o NAME,MODEL,TRAN,HCTL

MODEL describes a block device or a controller-presented logical volume; it is not a PCI-controller identity. HCTL helps distinguish SCSI targets. TRAN can be absent, and this list does not establish the complete physical disk topology.

Read controller and transport messages

sudo journalctl -k -b --no-pager

Elevated access may be needed. Root reads the current boot kernel journal. Associate ahci messages, port/host identifiers and timeout/reset timestamps with the actual controller. A reset message alone does not prove a bad disk or a firmware defect.

Limitations & related issues

Do not combine messages from adjacent SATA/PATA functions without checking their BDFs. A legacy BIOS RAID label does not establish how Linux exposes the attached disks or any array metadata.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.