Software⏱️ 4 min read📅 2026-06-19

How to Fix: RAID 0 (stripe) set can not be booted. `write same failed` error

Kernel issue with RAID 0 setup causing boot failure.

Quick Answer: Try disabling write_same in /etc/sysctl.conf or using a different kernel version.

📋 Table of Contents

  1. ⚠️ Common Causes
  2. 🛠️ Step-by-Step Verified Fixes
  3. 🎯 Final Words

The RAID 0 stripe set cannot be booted due to a 'write same failed' error, which is reported in various Linux forums. This issue affects users who have installedkernel version 3.9 or later on their Dell Precision T5400 workstations with a Dell hardware SAS raid controller and two SAS drives in striping.

This problem can be frustrating, especially when the only available machine to access the workstation is an Atom netbook. The goal of this troubleshooting guide is to help users resolve the issue by identifying the root cause and providing alternative fix methods.

⚠️ Common Causes

  • The primary reason for this error is that the kernel version 3.9 introduced changes that break compatibility with older systems. Specifically, the introduction of a new parameter called `max_write_same_blocks` in the `scsi_me command` to limit write same operations on striped devices. This change may not be compatible with all systems and can cause issues when booting RAID 0 stripe sets.
  • An alternative reason for this error could be related to the Dell hardware SAS raid controller firmware or driver issues, which may have been updated or changed after kernel version 3.9 was released. However, this is less likely to be the primary cause of the issue.

🛠️ Step-by-Step Verified Fixes

Disable write_same using sysfs

  1. Step 1: To disable write_same, first identify the correct device path for your RAID 0 stripe set by checking the `/sys/devices/pci0000:00` folder. This may involve searching through multiple subfolders and verifying that the ATA entries are correctly listed.
  2. Step 2: Next, create a temporary sysfs file to override the `max_write_same_blocks` parameter. Create a new file in `/etc/tmpfiles.d/`, for example, `scsi.conf`. Add the following line to this file: `max_write_same_blocks 0`. This will disable write same operations on your RAID 0 stripe set.
  3. Step 3: After creating the sysfs file, reboot the system and verify that it can be booted successfully. Note that this method may not provide a permanent solution and should only be used as a temporary workaround.

Upgrade to kernel version 4.x

  1. Step 1: To resolve the issue, consider upgrading to kernel version 4.x from the testing repository. This will likely address the compatibility issues introduced in kernel version 3.9.
  2. Step 2: Before upgrading, ensure that you have a valid backup of your system and that all necessary drivers are installed and compatible with the new kernel version.

🎯 Final Words

Resolving the RAID 0 stripe set boot issue can be challenging due to the introduction of new parameters in kernel version 3.9. However, by disabling write_same using sysfs or upgrading to kernel version 4.x, users should be able to resolve the issue and regain access to their workstation.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid