> Source: [sk149412](https://support.checkpoint.com/results/sk/sk149412)

# sk149412 - Long boot process due to errors in /etc/rc3.d/S09fw1boot

| Property | Value |
|----------|-------|
| Solution ID | sk149412 |
| Date Created | 2019-03-18 |
| Last Modified | 2020-11-03 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Longer boot process following an upgrade, for example from 3 minutes on R80.10 to 10 minutes on R80.20.
* Similar errors appear during boot:  
  ` 
  /etc/rc3.d/S09fw1boot: line 720: [: simlinux_excluded_ifs_list: unary operator expected`  
  `
  /etc/rc3.d/S09fw1boot: line 720: [: simi_reorder_max_packets: unary operator expected`

## Cause

Unsupported configuration of *$FWDIR/boot/modules/fwkern.conf* file, i.e. spaces around the "=" sign.

The file *$FWDIR/boot/modules/fwkern.conf*is used to configure a permanent change in kernel parameters and assign values during boot process.

**Pay attention** (as per [sk26202](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk26202)), the *$FWDIR/boot/modules/fwkern.conf* should:  

* *Not* contain spaces around the "=" sign
* Each parameter should be on a different line
* There should be no empty lines
* There should be no commented out lines with "#"
* There should be no duplicated lines

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content