Ubuntu启动/关机缓慢并报READ FPDMA QUEUED错误，同SSD下Windows正常如何解决？

Hey there, let's break down this disk error issue you're hitting with Ubuntu. Since Windows runs fine on the same SSD, we can rule out a full-on hardware failure—this is almost certainly a compatibility quirk between Linux and your drive's configuration. Here's how to diagnose and fix it:

Start with the simplest checks, since loose connections or misconfigured BIOS often cause these queued command errors:

• Power off your PC, unplug the power cord, then open the case and reseat both the SATA cable and power cable for your SSD. Sometimes a slightly loose interface can trigger intermittent FPDMA queue failures.
• Boot into your BIOS/UEFI and verify the SATA mode: If it’s set to RAID, switch it to AHCI (note: if Windows was installed in RAID mode, you’ll need to tweak its registry first to avoid boot issues—but since Windows works now, it’s probably already in AHCI). Also, disable any SATA power management or low-power modes, as these can interfere with Linux’s disk handling.

Even though Windows works, let’s confirm your SSD doesn’t have underlying health issues. Boot from your Live USB, open a terminal, and run:

# First, identify your SSD with lsblk (look for the drive with your Ubuntu partitions)
lsblk
# Then run smartctl (replace /dev/sda with your SSD's device name)
sudo smartctl -a /dev/sda

Look for the line SMART overall-health self-assessment test result: If it says PASSED, your drive is physically healthy. If there are warnings (like high reallocated sector counts), that might indicate a failing drive—but since Windows works, this is unlikely.

The READ FPDMA QUEUED error points to problems with Native Command Queuing (NCQ), a feature that lets the disk handle multiple commands at once. Some SSDs don’t play nice with Linux’s NCQ implementation, and this is the most common fix:

• Test the fix temporarily: When booting from your Live USB, at the GRUB menu press e to edit the boot command. Find the line starting with linux, add libata.force=noncq to the end of that line, then press Ctrl+X to boot. If the errors disappear and boot speeds up, we’ve found the culprit.
• Make the fix permanent: Once you’re in a working Ubuntu system, edit the GRUB config:

  sudo nano /etc/default/grub
  

  Find the line GRUB_CMDLINE_LINUX_DEFAULT and add libata.force=noncq inside the quotes, like:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq"
  

  Save the file (Ctrl+O, then Enter) and exit (Ctrl+X), then update GRUB:

  sudo update-grub
  

Many SSD manufacturers release firmware updates that fix Linux-specific compatibility bugs. Since Windows boots fine, use it to download and install the latest firmware from your SSD’s official website. After updating, reboot into Ubuntu to see if the issue is resolved.

While you’ve already reinstalled Ubuntu, it’s worth checking for file system corruption in case the initial install had issues. From the Live USB, run:

# Replace /dev/sdaX with your Ubuntu root partition (use lsblk to find it)
sudo fsck /dev/sdaX

Follow any prompts to repair errors if they’re found.

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