- [Show page]
- [Old revisions]
- [[unknown link type]]
- []
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
linux:raid [2016/03/16 23:26] admin |
linux:raid [2017/03/20 11:51] (current) tomsa [Setting up RAID10 with tw_cli] |
||
---|---|---|---|
Line 173: | Line 173: | ||
'' | '' | ||
+ | ====== Setting up RAID10 with tw_cli ====== | ||
+ | Generating the RAID10 field with disks in ports from 8 to 17: | ||
+ | ./tw_cli /c0 add type=raid10 disk=8-17 noautoverify | ||
+ | Software way of removing a disk from port 14: | ||
+ | ./tw_cli maint remove c0 p14 | ||
+ | Taking a look of what has it done: | ||
+ | ./tw_cli /c0/u0 show | ||
+ | "Adding" a disk back to the file system (more like identifying it): | ||
+ | ./tw_cli maint rescan c0 | ||
+ | Starting the verification process (if the unit was not previously initialized, it will be): | ||
+ | ./tw_cli /c0/u0 start verify | ||
+ | If you need to check which disk is connected to each port, you can use this command, it will light the external GUI light: | ||
+ | ./tw_cli /c0/p16 set identify=on | ||
+ | |||
+ | Add disk to raid: | ||
+ | tw-cli /c0/u0 start rebuild disk=16 | ||
+ | |||
+ | If the disk is in another unit (i.e. u1), just delete the unit | ||
+ | tw-cli /c0/u1 del | ||
+ | |||
+ | Problem: after physically removing a disk and installing it back, RAID started re-initializing by its own will without letting the master know. It's just bad. | ||
+ | |||
linux/raid.1458167196.txt.gz · Last modified: 2016/03/16 23:26 by admin