> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/dedicated-servers/other/requesting-a-part-swap/disk-swap.md). # Disk Swap How to request a disk swap on a dedicated server on Synteq ## Collecting the required information/logs ### 1. smartctl Start by collecting the smartctl information about the disk. You can do this with the following command: ``` smartctl -a /dev/sdX > smart.txt ``` Don't forget to replace `/dev/sdx` with the appropriate disk letter ### 2. lsblk Then, you'll need to collect the list of your block devices, which you can do with this command: ``` lsblk > lsblk.txt ``` ### 3. Firmware version Afterward, check the firmware version of your LSI controller with: ``` dmesg | grep LSI ``` If it shows up empty, then on the ticket please mention that ### 4. Server logs Another useful log that we always take a look at is the server logs, which can be obtained with: ``` dmesg > dmesg.txt ``` ### 5. RAID information If the device is in a RAID array, please share with us the status of the raid array with:
mdadmZFS
cat /proc/mdstat > mdstat.txt

zpool status > zpool.txt
## Reporting a broken disk: ### 1. Open a ticket Start by going to our client area, and then on the left navigation bar, please select `Support` \[1] > `Open Ticket` \[2]
### 2. Fill out the body of the ticket Then, select the `Technical Support` department
Afterward, please select the appropriate server in the `Realted Service` \[1] field, and fill out the `Subject`, and the `Message` part as per the table below:
Subject [2]
Disk swap request - dedicated server
Message [3]
Hello, 

I'd like to request a disk swap on my server \[42-XX-XX].
The S/N of the disk is: \[SERIAL NUMBER].
The LSI FW version is: \[FW Version].
I'm also attaching the following files to this ticket:
smartctl.txt
lsblk.txt
dmesg.txt
\[mdstat.txt] / \[zpool.txt]

\[Addicional Concerns]

Thank you!
Attachments \[4]smartctl.txt, lsblk.txt, dmesg.txt, \[mdstat.txt] / \[zpool.txt]
Please make sure to change the variables that are in square brackets to the appropriate values. In case you aren't running RAID, then please delete the mdstat, and the zpool variables from the ticket. If you'd like to point something out to us, or have some concerns, please put them into the `Addicional Concerns` variable.
Then, after filling everything out, please click the `Submit` button:
Then wait for us to get back to you with the next steps! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://legacy.docs.synteq.com/dedicated-servers/other/requesting-a-part-swap/disk-swap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.