When the Vantec NexStar MX (NST-400MX-S2) first came out I was quite excited. A dual drive housing, “how great will that not be for backups?” Then I discovered that it did not have RAID 1 support. I then looked at some of the entry level NAS devices, but they were more than I needed and cost quite a bit more. Fortunately not too long after the S2 they released a new version the SR (NST-400MX-SR) which supported RAID 0 and RAID 1. I sent Vantec USA a few technical questions specifically around RAID rebuild times and what happens in the event of a disk failing. They were pretty quick to respond. The disk light would go off in the event of a disk failing and the rebuild time was about 1GB/m. I also asked if the drive would rebuild without being attached to a machine and they said it would.
So I recently purchased the SR version and proceeded to setup 2 x 250GB SATA disks in RAID 1 (mirroring). I initially flipped through the instructions and then installed the drives in the housing. Everything was easy to install and the manual was reasonably clear and I set the jumpers to RAID 1. When I first attached the housing to my machine and started up disk management in Windows I was presented with 2 drives. I suspected I had not set the jumpers correctly but proceeded to create partitions and format the disks anyway to test it out. I then shut the housing down and opened it up and checked the jumpers and found that I had in fact not set them correctly, so I set them and pressed the little reset switch as per the documentation, but was still presented with two drives in Windows. After going through all the jumper options I could still only get two single drives. I even went as far as wiping the disks with the Seagate tools and starting again, no joy. I mailed Vantec twice, but their speedy support was now something of the past and I received no replies whatsoever. I then sent the housing back to the supplier and asked them to make it work. Two days later the housing was back and declared working. So I started it up and sure enough it was now in RAID 1. I then queried the technician who had worked on it and the trick was to press the reset button while the unit was powered on! Something that was not stated in the documentation (they suggest you press it before installing the drives). So I tested it for myself and sure enough it worked. It was actually quite cool starting up disk manager, setting the jumpers, pressing the reset switch and watching the disk config change suddenly. Obviously doing this destroys any data you had on the drives!
So the next thing to do was to simulate a drive failure and the subsequent rebuild with RAID 1. What you will notice immediately when coping data to the housing is that both drive lights will burn solid, once the copy is complete they will turn off. I then shut the housing down, removed one of the drives and started it back up again. Contrary to what Vantec support claimed, the drive light did not go off, instead it would flash on/off. Thus I would suggest each time you start your housing up let it flash through the initiation sequence and wait for both lights to stop flashing. If one continues to flash on/off at steady intervals, you have a failed drive. If you copy data to the housing while a disk is in a failed state the good drive will burn solid and the failed disk will continue to flash. I then shut the housing down reattached the drive and started it up again. It probably took about a minute or two before the rebuild started. Both lights will burn solid similar to when coping data. I did also test ejecting the housing while a rebuild was in progress (I used USB) and as soon as I did that the lights would stop flashing, so I had no idea if the rebuild was still running or not. I suspect that once again Vantec were incorrect and it’s best you leave the drive attached while the rebuild runs. I would also advise against copying data to the housing during the rebuild as this will only slow the rebuild down and potentially cause other unforeseen problems.
After all that struggling I am however very happy with the unit. The only minus (and most of the reviews mentions this) is that the fan is quite loud. I don’t leave the housing on for long (it’s just there for backups) so I don’t have to bare it for long 
I hope this post helps someone else in the future!
Edit:
After some futher digging on the internet I found some posts on Newegg suggesting that Silicon Image SteelVine Manager is able to show you the RAID status of the NexStar MX. To find this go to:
Silicon Image Support Page
- Select SiI5723 Storage Processor
- Then Configuration Manager
- Then your desired OS (I selected Vista)
- I then downloaded SiI57xx SteelVine Manager for Windows 5.1.24B
For convenience a direct link can be found here
@TekServer, I suspect it may be an OS compatibility issue. Have you tried attaching the housing to a desktop OS and run SteelVine on there to see if it is detected?
I wondered about that myself, though I didn’t get a chance to test it on a workstation before I left. It kind of needs to be on the server anyway, because it’s going to be a central data repository for archived pdf files.
The Silicon Image download page does include 2003 Server in the list of supported OSes, though …
I’ll try to connect the drive enclosure to a workstation next time I’m out there (which should be next week some time), and I’ll let you know what I find.
Thanks!
@TekServer. It’s more a process of elimination. If SteelVine picks up the drive correctly on a desktop OS, then you know the issue is software related. If it does not work on the desktop either you probably have a defective unit.
I’m running NexStar-400MX in Raid 1 mode. I recently began noticing a problem that it would do a Raid rebuild every time I powered it up. After several emails/conversations with Vantec, and a firmware upgrade, it appears that the problem only happens when I power up the device while it’s plugged into my eSATA port. If I power it on before plugging it into the computer, no problem.
Since the symptom is recent, I’m wondering if it may be tied in with my recent upgrade from XP to Win7. Anyway, thought I’d share FWIW.
@Duffy. Thanks for sharing!
Great work! Thanks for this blog, saved me lots of grief.
I agree that the manual is no good, I was also concerned that the model I purchased was the older version (nst-360mx-sr) as Vantec’s website only shows info on the 400 series? Are you sure 360 is newer?
Anyway, the firmware on this unit was 1.1593 out-of-the-box, so newer than on Silicon Images website (thanks for the config manager also, great work!)
Also have it with esata, works great went through the same stress of connecting a single HDD, then adding second, not seeing anything in OS (Windows 7 x64) then finding this blog and doing a reset, seeing the drive and using config manager to confirm in rebuild mode (again thank you!).
I like how the manual tells you to install disk 2 first then disk 1 using pictures, but when you come to read the works for RAID1 it says plug HDD into drive slot behind esata/usb ports - ended up looking at sata port labels on circuit board and went with lower number
Cheers for making the late night end before 11:30pm!
oh yeah, that fan is a bit loud, any suggestions as it sits behind my TV?
Thanks again!
Thanks! Combination of the article, comments and the silicon image software really saved the day.
The re-building process takes a lot longer than I would have ever imagined.
Heh. My RSS feed just alerted me that there were new comments here, and I realized I never came back to update my previous comments.
It turns out the software works just fine on Server 2003. I don’t remember exactly what got it working, but I think it was something simple (like rebooting the server).