基于Debian 9的NAS启动时出现SMBus/IPMI写入错误求助

Hey there, let's unpack this issue for you—first off, that red SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 error isn't a signal that your RAID drives are failing. Let's tackle each of your questions one by one:

1. Is this a sign of a failing disk? #

Almost certainly not. This error comes from your motherboard's SMBus/IPMI subsystem—think of this as the hardware monitoring/management bus on your board, not the SATA/SAS links that connect your RAID drives. To be 100% sure, run a SMART check on each drive:

smartctl -a /dev/sda
smartctl -a /dev/sdb
smartctl -a /dev/sdc
smartctl -a /dev/sdd

Keep an eye on metrics like Reallocated_Sector_Ct and Current_Pending_Sector—if these are 0 or haven't increased over time, your drives are healthy. You can also verify your RAID status with:

mdadm --detail /dev/md0  # Replace md0 with your first RAID device
mdadm --detail /dev/md1  # Replace md1 with your second RAID device

If the output shows all drives as "active sync", your arrays are in good shape.

2. Should I be worried? #

Not really—if your NAS boots fine, your RAID arrays work normally, and drive SMART data checks out, this is just a minor driver compatibility quirk. It won't threaten your data or core NAS functionality. That said, keep an eye out for other odd behavior (like RAID sync issues, drive errors, or system crashes) just in case, but this error alone isn't a red flag.

3. What causes this error? #

The root cause is a mismatch between the Linux kernel's SMBus/IPMI driver and your motherboard's hardware monitoring chip. Common triggers include:

• Debian 9's default kernel is pretty old, and it has known compatibility bugs with some IPMI/SMBus implementations.
• Conflicting settings in your motherboard's BIOS/UEFI (like misconfigured IPMI options).
• While not a direct cause, forced shutdowns might leave the motherboard's monitoring subsystem in a wonky state that triggers the driver bug, but this is an indirect link at best.

4. How do I fix it? #

Try these solutions in order:

• Quick fix: Hide the error
  If you just want to get rid of the red error message, add a kernel parameter to disable the problematic IPMI driver path. Edit /etc/default/grub, find the line starting with GRUB_CMDLINE_LINUX_DEFAULT, and add ipmi_si.force_kipmi=0:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipmi_si.force_kipmi=0"
  

  Then run update-grub and reboot—this should suppress the error.
• Better fix: Update your kernel
  Debian 9 has backports with newer kernels that fix many driver bugs. Enable backports and upgrade your kernel:

  echo "deb http://deb.debian.org/debian stretch-backports main" >> /etc/apt/sources.list
  apt update
  apt -t stretch-backports install linux-image-amd64
  

  Reboot after installation, and the error should be gone for good.
• Check BIOS settings
  Boot into your NAS's BIOS/UEFI, look for options related to IPMI, SMBus, or Hardware Monitor. Try disabling IPMI (if you don't use remote server management) or resetting BIOS to default settings, then reboot to see if the error disappears.

5. Does this relate to my forced shutdowns? #

Forced shutdowns don't directly cause this SMBus/IPMI error, but they could temporarily mess up your motherboard's monitoring subsystem, which might trigger the existing driver compatibility bug. That said, the core issue is the driver/hardware mismatch, not the shutdowns themselves. That being said—stop forcing shutdowns! They can corrupt file systems or mess up RAID sync states, which are way bigger risks than this error. Always use shutdown -h now or your NAS's web UI to power down properly.

内容的提问来源于stack exchange，提问作者user3450548