Searching: firmware - 177 Results Found

SmartStor Hard Drive/Array Rebuild Times
Ken Chou posted this 14 July 2008

Having created ATA RAID back in 1997 we (Promise) know a lot about rebuilding arrays under various conditions. The RAID Engine is designed to set the rebuild speed at a low-medium priority in order maintain decent performance while the array or volume is being accessed during rebuild. Rebuilds can take anywhere from a few hours to 24 hours:

 

250GB Drive 6 hours*

 

500GB Drive 12 hours*

 

750GB 18 hours*

 

1TB Disk 24 hours*

 

*All Rebuild times are approx and can vary depending on system activity and disk performance.

 

 

If your rebuild is exceeding the times list above:

 

-Make sure the Disk is on our AVL (Approved Vendors List). We are very serious about the AVL when it comes to Drives as we must approve the Hardware and the Firmware of the Drive.

 

-The Disk (being rebuilt – the replacement Disk) could be “unhealthy” and suffering from numerous bad sectors which results in the Disk attempting to recover the bad sectors. If you are using Enterprise Class or RAID Edition Drives that feature Time Limited Error Recovery, this recovery process will be kept to a minimum of less than 10 seconds per bad sector. Non Enterprise Class Drives can take minutes during recovery and could slow the rebuild process significantly.

SmartStor NS4300N/NS2300N is unable to join Active Directory Domain under Windows 2003 or 2008 when using special characters in the Active Directory Domain Administrator Password
Ken Chou posted this 11 July 2008

The Active Directory support for the NS4300N/NS2300N has a small limitation with some special characters in the Domain Administrator Password that prevents the NN4300N/NS2300N from joining the Domain. The special characters are: #, $, % and &. ! and @ are acceptable special characters and work as expected. This issue will be resolved in SR5 Firmware which is scheduled for release in late July to early/mid August 2008. We apologize for the inconvenience this issue has caused.

In the meantime, you can work-around the issue by changing the AD Administrator Password to not use #, $, % and & special characters. Once you change the password, add the NS4300N/NS2300N to the domain, then change the password back (or create another).

Close