Update alternative instructions for removing disk #240
Conversation
The script referenced no longer works and is unmaintained. Replaced references to the script with manual instructions compatible with Unraid 7.
WalkthroughThe documentation has been updated to clarify the process for removing drives from the Unraid array. The changes explain that while multiple drives can be removed simultaneously, sequential clearing is preferred due to performance issues with parallel operations. Additional commands for checking drive status, unmounting disks, and creating a mock disk to stop the array have been incorporated. The procedural steps have been reorganized for improved readability and clarity. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant CLI as Command Line
participant OS as Unraid OS
U->>CLI: Run command to check drive status
CLI->>OS: Query drive status
OS-->>CLI: Return current drive status
U->>CLI: Issue unmount command for drive
CLI->>OS: Process unmount request
OS-->>CLI: Confirm drive unmounted
U->>CLI: Create mock disk to stop the array
CLI->>OS: Initiate drive clearing procedure
OS-->>CLI: Acknowledge and process drive clear sequence
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/unraid-os/manual/storage-management.md (2)
927-932: Clarify and Emphasize Sequential Clearing Guidance
The added instructions now clearly spell out that the alternative method for removing disks requires the drive to be completely clear and warns against running multiple clear operations in parallel. This added detail helps users avoid the performance pitfalls caused by contention when updating the parity drive.
946-953: Reinforce the Rationale for Complete Data Removal
The newly inserted text effectively explains why the drive must be completely empty before running the clearing process. Emphasizing that removing all data prevents any accidental preservation or misunderstandings is a strong safety measure. You might consider slight rewording for maximum clarity; for example:- requiring the user to remove all data, there cannot be any - accidents or misunderstandings and data loss. + requiring the user to remove all data—thereby preventing any accidental data preservation or misunderstanding that might lead to data loss.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/unraid-os/manual/storage-management.md(3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: AWS Amplify Console Web Preview
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/unraid-os/manual/storage-management.md (2)
946-953: Refine the Explanatory Note for Data ErasureThe added explanatory note helps prevent misunderstandings about why a drive must be emptied before clearing. To further improve clarity and maintain a consistent tone, consider a slight language adjustment for a more formal style. For example:
"Since the clearing script will erase all existing data, please ensure that all files (including hidden ones) are removed beforehand to prevent accidental data loss."
996-1004: Fix Markdown List IndentationStatic analysis flagged several unordered list indentation issues (MD007). The current indentation (3 spaces) doesn’t meet the expected standard (0 spaces). Adjusting the indentation will enhance readability and consistency across the document. For example, change:
- - One quick way to clear a drive of files is to reformat it! To - format an array drive, you stop the array, and then on the Main - page click on the link for the drive and change the file system - type to something different than it currently is, then restart - the array. You will then be presented with an option to format - it.to:
- - One quick way to clear a drive of files is to reformat it! To - format an array drive, you stop the array, and then on the Main - page click on the link for the drive and change the file system - type to something different than it currently is, then restart - the array. You will then be presented with an option to format - it.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
996-996: Unordered list indentation
Expected: 0; Actual: 3(MD007, ul-indent)
1000-1000: Unordered list indentation
Expected: 0; Actual: 3(MD007, ul-indent)
1001-1001: Unordered list indentation
Expected: 0; Actual: 3(MD007, ul-indent)
1004-1004: Unordered list indentation
Expected: 0; Actual: 3(MD007, ul-indent)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/unraid-os/manual/storage-management.md(3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/unraid-os/manual/storage-management.md
996-996: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
1000-1000: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
1001-1001: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
1004-1004: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
🔇 Additional comments (1)
docs/unraid-os/manual/storage-management.md (1)
927-932: Clarify Sequential Disk-Clearing RequirementThe revised instructions clearly state that clearing multiple drives in parallel is discouraged due to contention issues with updating the parity drive. This change improves clarity and reinforces best practices.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/unraid-os/manual/storage-management.md (1)
927-932: Clarify Sequential vs. Parallel Clearing BehaviorThe revised instructions now explicitly emphasize that clearing multiple drives in parallel is slower due to contention on the parity drive. Consider adding a short explanation or example (or even a tip) to guide users on why sequential clearing is recommended versus a parallel operation for better performance. This will further help users make an informed choice regarding disk removal.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/unraid-os/manual/storage-management.md(3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: AWS Amplify Console Web Preview
🔇 Additional comments (1)
docs/unraid-os/manual/storage-management.md (1)
946-946: Strengthen the Data Removal WarningThe updated explanatory note now stresses that the drive must be completely empty—requiring users to remove all data before executing the clear operation—to prevent any accidental data loss. This added clarity is very helpful. Ensure that the phrasing remains friendly to all user levels, as it is vital they understand the irreversible impact on their data.
Also applies to: 952-953
The script referenced no longer works and is unmaintained.
Replaced references to the script with manual instructions compatible with Unraid 7.
Before Submitting This PR, Please Ensure You Have Completed The Following:
Summary by CodeRabbit