# Ln: failed to create symbolic link Operation not supported
**URL:** https://community.seqera.io/t/ln-failed-to-create-symbolic-link-operation-not-supported/1144
**Category:** Ask for help
**Tags:** nextflow
**Created:** [August 28, 2024, 7:53am UTC](https://community.seqera.io/t/ln-failed-to-create-symbolic-link-operation-not-supported/1144 "2024-08-28T07:53:07Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Hanjiewu](https://community.seqera.io/u/Hanjiewu)
#### Post date: [August 28, 2024, 7:53am UTC](https://community.seqera.io/t/ln-failed-to-create-symbolic-link-operation-not-supported/1144/1 "2024-08-28T07:53:07Z")
I have a server with a SATA hard disk mounted on it. I created a directory on the SATA hard disk and ran a Nextflow script that is located on the server, but it failed. There was no `.command.err` file, but I found the following message in the `.command.log` : `ln: failed to create symbolic link 'FAX37527_pass_barcode25_d51b1ed1_89554596_17.fastq.gz': Operation not supported` . The workflow runs successfully when the project directory is on the server’s local storage. What should I do to run the workflow on a mounted hard disk?
---
### Author:  [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)
#### Post date: [September 2, 2024, 12:27pm UTC](https://community.seqera.io/t/ln-failed-to-create-symbolic-link-operation-not-supported/1144/2 "2024-09-02T12:27:30Z")
Is your attached disk formatted with FAT32? Does it support symbolic links? This is a requirement for Nextflow and is supported by most POSIX filesystems.
Generally, I wouldn’t run a Nextflow pipeline on an attached disk, I would run it on some fast, locally available storage. You can still read the data from the remote disk, but use the faster local storage to analyse the data. Set the working directory to the local disk and/or use [process.scratch](https://www.nextflow.io/docs/latest/process.html#scratch) to work from your internal drives.