unraid / unraid/docs

Replacing Disks - Section is missing key details

Open
#402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
55
Forks
57
Avg merge
16h 25m
Merged PRs (30d)
5

Description

Source: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#preparing-for-drive-replacement

First:
Image

The "do not format"-warning seems important, but where/in what cases would i expect this message to show up? I was following the procedure as described, and i was never sure where i could do something wrong that would cause a reformat to appear. I think it would be helpful to make this warning more descriptive.

Second:

  1. Click Start to begin the rebuild. Unraid copies data from the emulated disk to the new disk. If the new disk is larger, Unraid manages the extra space.

After i started the array in maintenance mode, what do i need to expect?
On 7.1.4, the array successfully starts into maintenance with the new disk properly assigned.
However: It shows up as emulated in the Array-Devices-overview, and the "Array Operations"-Section now has a
"SYNC - Sync will start Data-Rebuild."-Button.

This forum post clears up that there is a distinction between maintenance-mode and normal-mode. An explanation on this distinction, and the expected outcome of the actions would be helpful.

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the “Preparing for drive replacement” section at the linked documentation page and compare its warning and step 8 with the linked forum post. Clarify when the “do not format” warning appears and explain the expected maintenance-mode, emulated-disk, and SYNC/Data-Rebuild states. Done means the procedure and outcomes are understandable without needing the forum discussion.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.