RAID Cards - Revision history

70.95.138.94: /* Rebuild speed */

2019-02-27T06:06:25Z

Rebuild speed

2019-02-24T18:04:46Z

CLI

← Older revision		Revision as of 11:04, 24 February 2019
Line 1,519:		Line 1,519:
	cli64 event info view error events		cli64 event info view error events
	cli64 disk identify drv=xx turn on lights on a disk		cli64 disk identify drv=xx turn on lights on a disk
	cli64 vsf check vol=1 ???		cli64 vsf check vol=1 careful (may start a long test)???
	</pre>		</pre>

2019-02-24T18:02:58Z

Updating F/W

2019-02-24T17:58:31Z

CLI

← Older revision		Revision as of 10:58, 24 February 2019
Line 1,528:		Line 1,528:
	cli64 disk info		cli64 disk info
	cli64 disk fail drv=XX only if disk is still in the array		cli64 disk fail drv=XX only if disk is still in the array
	------- replace the drive		------- physically replace the drive
	cli64 rsf createhs drv=XX		cli64 rsf createhs drv=XX start the rebuild

	</pre>		</pre>

2019-02-24T17:55:11Z

CLI

← Older revision		Revision as of 10:55, 24 February 2019
Line 1,527:		Line 1,527:
	<pre>		<pre>
	cli64 disk info		cli64 disk info
	cli64 disk fail drv=XX		cli64 disk fail drv=XX only if disk is still in the array
	replace the drive		------- replace the drive
	cli64 rsf createhs drv=XX		cli64 rsf createhs drv=XX

2019-02-24T17:53:20Z

← Older revision		Revision as of 10:53, 24 February 2019
Line 1,513:		Line 1,513:
	== CLI ==		== CLI ==

	<pre>cli64 vsf info		<pre>
	cli64 ~~rsf~~ info		cli64 rsf info view state of RAID
			cli64 vsf info view state of rebuild
			cli64 disk info view all disks
			cli64 event info view error events
			cli64 disk identify drv=xx turn on lights on a disk
			cli64 vsf check vol=1 ???
			</pre>

			To replace a drive and start a rebuild you must make sure the disk
			is removed from the RAID array and then insert the new disk and
			make it a hot spare.
			<pre>
	cli64 disk info		cli64 disk info
	cli64 ~~event info~~		cli64 disk fail drv=XX
	cli64 ~~vsf check vol~~=1		replace the drive
			cli64 rsf createhs drv=XX

	</pre>		</pre>

			View status of rebuild.
			<pre> cli64 vsf info </pre>

	== Updating F/W ==		== Updating F/W ==

2014-07-12T17:13:46Z

Replacing a failed drive

← Older revision		Revision as of 10:13, 12 July 2014
Line 1,306:		Line 1,306:
	<pre>		<pre>
	tw_cli maint deleteunit c0 u1		tw_cli maint deleteunit c0 u1
	tw_cli maint remove c0 u0 p1		tw_cli maint remove c0 u0 p1 (may not be needed)
	tw_cli maint rescan c0		tw_cli maint rescan c0
	tw_cli /c0 show all		tw_cli /c0 show all

2014-07-12T17:12:40Z

Replacing a failed drive

2014-07-12T02:57:37Z

Replacing a failed drive

← Older revision		Revision as of 19:57, 11 July 2014
Line 1,300:		Line 1,300:

	=== Replacing a failed drive ===		=== Replacing a failed drive ===

			If you don't remove the drive from a RAID-1 array before you replace it, the new drive comes up
			as a separate JBOD device. To fix this do

			<pre>
			tw_cli maint deleteunit c0 u1
			tw_cli maint rescan c0
			tw_cli /c0 show all
			tw_cli maint rebuild c0 u0 p1
			tw_cli /c0 show all
			</pre>

	After replacing the 2 dead drives, we see:		After replacing the 2 dead drives, we see:

2013-01-12T00:05:11Z

Rebuild speed

← Older revision		Revision as of 17:05, 11 January 2013
Line 1,284:		Line 1,284:

	== Rebuild speed ==		== Rebuild speed ==
	Do the following to slow down a rebuild speed sp as to improve performance		Do the following to slow down a rebuild speed so as to improve performance

	(1=fast, 5=slow)		(1=fast, 5=slow)
	tw_cli /c0 set rebuild=5		tw_cli /c0 set rebuild=5