@@ -990,21 +990,21 @@ The procedure is as follows:
990
990
umount /mnt/diskX
991
991
```
992
992
10 . Clear the drive (replace ` X ` with the drive number)
993
- ``` shell
994
- dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress
995
- ```
996
- - On Unraid 7 and later, the parity protected drives are mounted
997
- at the path ` /dev/mdXp1 ` but on older versions, they are mounted
998
- at the path ` /dev/mdX ` . Double check that you're using the
999
- correct path.
1000
- - Clearing takes a loooong time! Progress info will be displayed.
1001
- - For best performance, make sure there are no reads/writes
1002
- happening to the array. It is recommended that you stop the
1003
- Docker and VM Manager services, and temporarily disable the mover
1004
- prior to clearing.
1005
- - While the script is running, the Main screen may show invalid
1006
- numbers for the drive, ignore them. Important! Do not try to
1007
- access the drive, at all!
993
+ ``` shell
994
+ dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress
995
+ ```
996
+ - On Unraid 7 and later, the parity protected drives are mounted
997
+ at the path ` /dev/mdXp1` but on older versions, they are mounted
998
+ at the path ` /dev/mdX` . Double check that you' re using the
999
+ correct path.
1000
+ - Clearing takes a loooong time! Progress info will be displayed.
1001
+ - For best performance, make sure there are no reads/writes
1002
+ happening to the array. It is recommended that you stop the
1003
+ Docker and VM Manager services, and temporarily disable the mover
1004
+ prior to clearing.
1005
+ - While the script is running, the Main screen may show invalid
1006
+ numbers for the drive, ignore them. Important! Do not try to
1007
+ access the drive, at all!
1008
1008
11. When the clearing is complete, stop the array
1009
1009
12. On Unraid 7 and later, stopping the array may get stuck with the
1010
1010
message `Retry unmounting disk share(s)...`. That' s because we
0 commit comments