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

# sk176952 - System reboot revert to snapshot fails for a Security Gateway - "The superblock could not be read..."

| Property | Value |
|----------|-------|
| Solution ID | sk176952 |
| Date Created | 2022-03-17 |
| Last Modified | 2022-12-08 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * System reboot revert to snapshot fails for a Security Gateway.
* These error messages appear:

  ```
  
  [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/mapper/vg_splat-lv_
  fsck.ext3: No such file or directory while trying to open /dev/mapper/vg_splat-lv_
  /dev/mapper/vg_splat-lv_
  The superblock could not be read or does not describe a correct ext3
  filesystem. If the device is valid and it really contains an ext3
  filesystem (and not swap or ufs or something else), then the superblock
  is corrupt, and you might try running e2fsck with an alternate superblock:
  
  e2fsck -b 8193 
  
  [FAILED]
  
  *** An error occurred during the file system check.
  *** Dropping you to a shell; the system will reboot
  *** when you leave the shell.
  (Repair filesystem) 1 # 
  ```

* The file system of the disk partition is *ext3*.

## Cause

The name of the snapshot partition was not changed correctly to *lv_current*.

## 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
