NAS Codex › QNAP › QNAP "Stopped converting volume" (thick to thin): volume Unmounted, what to do
QNAP "Stopped converting volume" (thick to thin): volume Unmounted, what to do
You started converting a thick volume to a thin one, often because QTS recommended it so you could use snapshots, and it stopped partway. The volume now shows Unmounted and its data cannot be reached, even though every disk shows Good and the storage pool shows Ready. QNAP published an FAQ for exactly this case. This page gives its steps in order, starting with what not to do.
Written against: QTS (QNAP FAQs last modified 2025-06-17, 2025-07-01 and 2026-11-16). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Stop and change nothing. QNAP says not to remove or recreate the volume or pool, not to re-initialize the NAS or reconfigure RAID, not to pull disks or change their order, and not to retry the conversion. Avoid writing to the pool. Note the event-log errors and statuses. If the volume still offers Check File System, run it and wait. If the option is greyed out or the check fails, open a QNAP Helpdesk ticket. QNAP says the data is usually still intact on disk.
The message
[Storage & Snapshots] Stopped converting volume "DataVol1". Old type: Thick volume, New type: Thin volume, Storage pool: 1. The volume's storage pool is abnormal.QNAP gives this as the error users report, with your own volume name and pool number in place of "DataVol1" and "1". After it, the volume shows as Unmounted and its data is temporarily inaccessible. The disks still show Good and the storage pool still shows Ready. QNAP notes that "Disks Good / Pool Ready" in the interface does not guarantee that the underlying LVM thin-pool metadata is healthy.
Why QTS suggested the conversion
QNAP explains the two volume types this way. A thick volume takes its full size from the storage pool when it is created, and that space is reserved for it. A thin volume takes pool space only as data is written, and space freed by deleting data can go back to the pool. QNAP recommends thin volumes for snapshots, because on a thick volume new writes to empty space grow snapshot use by the same amount. Both are "flexible volumes" inside a storage pool and can be converted between thin and thick. A static volume has no storage pool and cannot be converted.
Step 0: stop. Do not make it worse
QNAP's list of what not to do once the conversion has failed and the volume is unmounted:
- Do not remove or recreate the volume or the storage pool.
- Do not re-initialize the NAS or reconfigure RAID.
- Do not pull disks or change the disk order.
- Do not retry the conversion again and again.
QNAP also says to avoid any further write operations to the pool. Its reasoning: the data is usually still intact on disk, the failure is typically in the volume/LVM layer, and careless actions at this point are what cause real data loss.
Step 1: collect information
- System Event Logs: note every storage-related error around the time of the conversion.
- Storage & Snapshots: record the pool status, the volume status and any error badge on the pool.
- Diagnostic log: download one if you can, from Support > Help Center > Diagnostic Tool. Otherwise keep the NAS as it is for remote support.
Step 2: Check File System, only if the volume offers it
If the volume is unmounted but still listed:
- Go to Storage & Snapshots > Storage > Storage/Snapshots.
- Select the volume and click Manage.
- Click Actions > Check File System and confirm.
- Wait for it to finish, then see whether the volume remounts. QNAP says this can take many hours on large volumes.
QNAP's general file-system-check FAQ adds that all services stop during a check, so the system can unmount the volume for repair. If the option is greyed out, or the check fails or aborts, QNAP says not to force anything further from the interface. Go to step 3.
Step 3: open a QNAP support ticket
QNAP calls this the recommended path. A failed thick-to-thin conversion with "storage pool is abnormal" usually means the LVM thin-pool metadata needs manual inspection or repair by QNAP support engineers over a remote session.
- Create a ticket at the QNAP Helpdesk.
- Give the NAS model, the QTS version, the exact event-log error, the fact that the conversion was started from the snapshot recommendation, and the current pool and volume status.
- Enable remote support access when asked (Helpdesk app > Remote Support).
- Until support has checked the system, avoid any other operation on the volume or storage pool.
Before you try a conversion again
QNAP's precautions for the conversion itself:
- Have a current backup first (QNAP mentions the 3-2-1 rule and HBS 3), especially if this is the only volume on the NAS.
- Check that every disk is Good with no S.M.A.R.T. warnings, and that the pool and volume are Ready: not degraded, rebuilding, resyncing or scrubbing. After power loss, unclean shutdowns or file system warnings, run Check File System first and let it finish.
- Leave free space in the pool. QNAP says QTS warns at the pool space threshold, typically 80%.
- Convert off-peak. Pause HBS 3 jobs, Qsync, virtual machines, containers, downloads and heavy iSCSI or file-server use, and do not reboot or shut down while it runs.
- Use a UPS, since QNAP says a power loss mid-conversion can corrupt thin-pool metadata, and update QTS to the latest build for your model.
- Decide the target type first. QTS supports both directions, but QNAP says not to convert back and forth.
After converting to thin, watch pool use: QNAP says a thin volume switches to read-only or read-delete mode if the pool runs out of free space.
When to stop and get help
If there is no backup, QNAP says to tell the support engineer immediately, because that changes which operations are considered safe. If advised, consider imaging the disks or consulting a professional data-recovery service before any repair is attempted. QNAP also reminds you that snapshots are not a backup: they live in the same storage pool, so a pool-level failure affects both. See also RAID group degraded, read-only.
Questions
Is my data gone after a failed thick-to-thin conversion?
QNAP says the data is usually still intact on disk and that the failure is typically in the volume/LVM layer. It warns that careless actions after the failure, such as removing the volume or pool, re-initializing or changing disk order, are what cause real data loss.
Can I just retry the conversion?
No. QNAP's first step after the failure is to stop, and its list of what not to do includes retrying the conversion repeatedly. Run Check File System if the volume offers it, otherwise open a QNAP Helpdesk ticket.
Why does the pool show Ready if the volume is unmounted?
QNAP notes that Disks Good and Pool Ready in the interface do not guarantee that the underlying LVM thin-pool metadata is healthy. A failed conversion with the storage-pool-abnormal message usually needs that metadata inspected by QNAP support.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-16.