Things you need to know about the Vantec NexStar MX and RAID
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
Edit: Users of the NST 360 MX with 2TB drives should read the great comments from JP
I just hooked up one of these NexStars to a Windows 2003 Server for a customer, and (with the help of the info above about the reset button) it’s humming right along and working perfectly. However, I can’t get the SteelVine Manager to recognize the device at all! When I tell it to “Scan Disks” it percolates for a while with the cursor turned into an hourglass, then comes back and says something about “daemon can’t find any disk” (this takes 10 – 15 minutes, and I wasn’t able to repeat it this last time to get the message – it just hourglassed for 15 minutes and then returned to an empty window – so I’m not sure at this point of the exact error message, and I’m out of time here … ).
Anyway, if anyone has any suggestions for how to get the device to show up in SteelVine, I would greatly appreciate it.
Thanks!
๐
@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).
Thanks for the heads up about the reset switch. I got the NextStar 3 MX drive and attempted to configure 2x2TB with RAID 0 for a total of 4TB. After much toil, I can confirm that it works with 4TB in 64bit Linux.
Initially, no matter what I did, less than 2TB of space showed up (despite the packaging claiming to support 4TB). Issues to be aware of:
* I had to email Vantec support to get a link to a firmware update: http://www.vantecusa.com/system/application/media/data_file/NST-400MX-SR_FW_11596.zip (only use this if you have the NST-360MX-SR!)
* Windows XP 32bit can’t support more than 2TB. AFAIK, Vista, Windows 7 and Ubuntu 64bit can support more than 2TB.
* The standard ‘basic’ old MBR partition can’t support more than 2TB. Instead, the GPT partition table is needed for drives larger than 2TB.
This was Vantecs instruction:
1. Update the firmware version to 1.1596 for support total 4TB of disk volume in JBOD or RAID 0 mode
2. Turn the power off and set the dip switch setting to JBOD or RAID 0
(configuration setting can be found at user guide)
3. Hold the reset button turn on the enclosure and continue holding the
reset button for approximately 10 more seconds after turning on the hard drive enclosure before letting the reset button go (this will reset the
NST-360MX-SR configuration to the dip switch setting)
4. Go to Disk Management partition and format disk volume (using GPT instead of MBR to initialize drive and GPT disk only ship with Windows 64bit’s OS)
Since I’m a Linux user, I used parted on the command line to create the GPT partion table and a 4TB partition. If your a Linux user, simply Google ‘Linux 2TB limit and GPT parted’.
Hi, thanks for sharing your experience!
I just received my NST-400MX-SR today, and doing some homework before inserting drives and starting backing up data.
I’ve got a couple of questions, maybe someone can advise:
1) I plugged in the box to eSATA, WITHOUT drives and it was recognized as 8.9Gb unpartitioned drive. The desktop is DELL Dimension 8400 and it has 2x250Gb SATA drives configured as RAID-1. It has 2 free SATA ports and I connected the box is to 1st that was free.
Can I partition/format this ghost drive, or just ignore it?
2) I downloaded the Silicon Image software from the link and inistalled it. The SteelVine manager sees the box, but does not show fan/temperature and shows the serial number as 12345678 and firmware version 1.1596. It asksme for a password to change anything. The version is 5.1.24, same as described.
What is the default password and is this manager still suitable for the box manufactured in the end of 2010 and shipped with Firmware 1.1596?
Follow up, one more thing.
I found the password (it is ‘admin’), but got puzzled with one more thing:
Why “SAFE33 / SAFE50” options are grayed out? Did anyone manage to enable it?
I recently purchased one of these devices and this blog post was invaluable in getting it setup using RAID1. Thank you so much for taking the time to post this, and thanks to everyone who has replied and added to the knowledge base here.
I have one thing to add that should have been obvious, but took me a few tries to figure out. Using the SteelVine utility, if you want to actually configure anything the default password is ‘admin’.
JP jy is n fokken yster ou!
Thanks JP. I wanted to do exactly the same as you did. I wanted a 4TB external backup device using the Vantec NST-360MX-SR and 2x2TB drives. I had exactly the same problem as you did. I spent a whole weekend trying to troubleshoot the issue – no luck. Read your comments on this post and fixed in 20 minutes.
Thanks!
Bookmarking this. Good job! Reset button trickery is what caught me.
Power on reset was the key for the jumper settings to “take”. The instructions were not clear on that. Thanks!
The firmware that is linked above (http://www.vantecusa.com/system/application/media/data_file/NST-400MX-SR_FW_11596.zip) Works with the Model NST-400MX-SR model. In fact the Upgrade Instructions designate:
Vantec Thermal Technologies.
-Firmware Upgrade Instructions-
Model: NST-400MX-SR ONLY
1. Install SteelVine Manager found within the file “57xxSteelVine_V5.1.24B.zip”.
2. Refer to page 78 of the “Sil57XX_Users_Guide_Rev_1.0.pdf” for how to upgrade the firmware.
3. For the step asking you to choose the firmware image file, choose “SiI5744_11596.bin”.
I just upgraded it myself and I now can see 4TB JBOD (2x 2TB). Vantec certainly does not make it easy. Why they don’t put these on their website is beyond me.
I’ve just bought myself the same unit and struggled my arse off to get the rebuilding done! The reseller couldn’t help me and the manual sure as hell did not help.
Thanks!
First I want to thank for the article and comments. I have set up my NST-360MX-SR about a year ago and it worked perfectly all this time. But now I have a problem with it and can’t find the correct solution. System can’t see the device and there are only two lights are on at the box: logo and raid 1. Both hdd indicators are off (lights once at power on and then goes off). As I understand I will lose all data if I press Reset. What should I do to restart it correctly without loseing data?
I’m not so lucky. I followed those instructions, flashed with the latest firmware, and now it seems bricked. The enclosure won’t be detected by the Steelvine manager, the blue lights don’t flash anymore, won’t detect anything either with USB or eSata. The 2 drives are detected instantly in my PC though.
Gone for good?
Thanks!
Hi Yanic
What enclosure model do you have and what firmware version did you use?
Hey there,
Not sure if anybody still is around, but I’m having a heck of a time trying to get my NST-400MX-SR to work in RAID 1.
I installed 2 drives (Seagate ST2000DL003) after setting the dip switches, pressed the reset all as instructed in the proper order. Win7 will only read them as separate drives. Windows let me format them individually, I disconnected the usb cable and it appeared that the raid was being built. However, after 48 hours of both LEDs being on and never blinking, I reattached the cable and windows still sees 2 drives.
Took the drives out and tried it again. Nothing. Installed the Steelvine software and it shows them as JBOD policy.
Any advice? Is my unit defective? Thanks for any input.
Hi Jim
I would double check the dip switches and make sure you are pressing it while the unit is powered on. Only other thought is that those drives have 4k sectors, might be that the RAID on the device doesn’t understand 4k sectors, but that’s a guess on my part. Perhaps Vantec can help you out?
I must have read this article a half-dozen times as well as the various comments here and at a couple of online retailers. I’ve finally realized that my problem was the phrase “powered on”. I took it to mean “with the power on”.
I originally turned the unit on, pressed the reset switch, held it for a while, then turned it off. I didn’t realize you meant to hold the switch WHILE TURNING THE UNIT ON. That isn’t what I understood from the various comments I read.
It now appears to be working. Steelvine is currently reporting it as Safe rebuilding (83%). Woohoo! Thanks so much.
I do have another somewhat dumb question however: If a drive fails, do you have to put the good drive in a specific slot? For instance, if I replaced one of the drives, would the unit know to mirror the drive with data and not the newly reformatted fresh one? Do you have to format the replacement drive outside the unit before you could install it?
Once again, thanks.
Hi Jim
You can press the switch while the unit has been running for a while, it doesn’t have to be while it’s powering on (but if it works, it works!).
If a drive fails best would be to not move drives around and replace the failed drive with a new drive in the same slot. With dedicated RAID controllers there is some information about the RAID stored on the disc, so in those scenarios it’s always best to wipe the disc with something like seatools or similar if you intend to try reinsert it. Again with the RAID implementation on the Nexstar, it’s hard to say what applies, so rather play it safe. A brand new unformatted drive you can just stick in as is.
DATA LOSS WARNING
I have a Nexstar 360MX SR and I had a drive failure on the “primary” drive, Drive 0 in Steelvine (CON2 on PCB and left hand drive as you look from front of unit).
Having removed the failed drive, I used Steelvine to examine the system setup and it correctly indicated that Drive 1 (right hand drive on CON3) was Normal and that the RAID array was broken because of failed disk.
I replaced the left hand drive (Steelvine showed as Drive 0) and 10 or so seconds after the drive was recognised, the rebuild started. MUCH to my consternation, the rebuild took place FROM Drive 0 to Drive 1, obliterating the data on the good drive!
So it appears that rebuilds are from Drive 0 to Drive 1 so if Drive 0 fails, you need to move the good drive to Drive 0 so rebuild copies data from good drive to new drive.
I cannot thank you enough for this article. I thought I was going to suffer the same fate as the 1-star reviewers on Amazon.
Sorry to have a poor question but…
I “think” everything is working fine set on raid 1 but how can I know?! I dont want to have to worry about precious photos etc etc.
I have the switches set correctly, Windows Diskmanagement shows just one drive so all good there BUT on the front of the unit there is 1 green light and 2 blue ones. Green is obviously power and blue for the drives I assume when they are working. My problem is that only one of the blue lights is going on and off when reading or writing to the unit… Is that correct for raid 1 or is it not accepting the second drive and I will have to do another reset!!
I do not want to take the drives out and test in my pc simply because if it is working now Im not sure if that would desterb the raid once I put it back in the unit.. help is muchhhh appreciated!!!
@David Millar best advice is to install SteelVine to see what the status of the RAID is.
All this has been very useful. I have used this drive without a problem for probably 3 years. I wanted to be able to rotate drives and put one in a safe so I would always have a remote backup. I have spent all day trying to replace a 1 TB drive with a 2 TB drive. Luckily I put the drive on the left side (the side opposite the switches (used to define the RAID type). I could not access the drive during the rebuild process. I assume I will be able to access it AFTER the rebuild. It is taking 4 to 5 hours (at least) to rebuild a 1 TB drive.
The “manual” indicates that you can access the drive during the rebuild process. Has anyone found this to be true???
@Eric Aderson It’s been a while since I did my testing, but if I read my article again it does look like I was able to access the drive while it was rebuilding. Have you checked in SteelVine that it is in fact rebuilding the existing 1TB onto the new 2TB and not the other way round?
I bought the NST-400MX-SR dual enclosure (used two 160gb drives) connected to a laptop and works fine. When I connect to a windows XP or 2003 server via USB the system asks for software FW 11596. I updated the FW to 1.1596. Does anyone have any suggestions
Im posting this because I am at my wits end here. About 1 month ago I bought the Vantex Nexstar 400MX S3R and put (2) 1TB Western Digital RED drives in. I then configured it in RAID 1 and it seemed to work great. I copied all my family videos and photos off of an older failing drive just before it crashed. Today I tried to access the RAID storage and it wasnt recognized in Windows, and when I looked at it through disk management it told me the volume was unallocated. Is there ANY way I can get my data back? Please, I need any help you can provide. Thanks.
@Tristan. If you’re tech savvy have a look at testdisk / photrec. These tools have a bit of a learning curve attached to them, but I have had success recovering data with them. On the other hand you can’t really put a price on family memories, so taking your disks to a professional data recovery business is probably the better call.
Thanks ek.is.befok. I actually found a program late last night which was able to restore the old partition. The software is called EaseUs Partition Master Pro. I have now made duplicate copies of the data just in case. Thanks for taking the time to respond, I appreciate the help. I will look into testdisk / photrec for future reference.
Hi Ek.is.befok. I currently own NEXStar 360-MX-SR and has been using it for a while as a “normal” enclosure. I end up reading your article when now that I am planning to finaly use the RAID1 feature of the drive. Do you have any recommendation on what HDD to use (looking for 2x2TB RAID1 setup). I read somewhere that WD Green is not recommended, any thought on that?
@Panda. For external enclosures I don’t believe it really matters. Go with the brand you like and/or what suits your wallet. The “surveillance” and “enterprise” drives often come with longer warranties and the promise of longer mean time before failure, but also cost a lot more. If you’re going to mirror 2 disks then the idea is that if a drive fails the data is safe on the 2nd, so the more expensive drive isn’t really required.
The secret for RAID-1 is indeed pressing the internal reset button while the device is already powered up. Took me a few days to figure it out. ๐ Vantec documentation is obviously lacking there.
Also, has anybody been able to get Steelvine Manager 5.124B to be able to detect the Nexstar MX NST-400MX-S3R to be detected under Windows 7 64-bit SP1? Thanks.
Using this post I have downloaded the firmware for the Vantec nexstar MX NST 400 MX SR and now when I power it on all I get is a green power light and Windows will not see it on USB and when I press the reset button I do not get a light flash like I did before the firmware update. I used the firmware above titled SiI5744_11596.bin. Since USB not detected Steelvine is no help. Please if you have an idea let me know.
Great tips from dedicated users here!
I just got my MX-400-SR3.
This unit comes with a different RAID controller {JMicron}.
The controller is available for download from VANTEC’s product page:
http://www.vantecusa.com/en/product/view_detail/497.
The JMicron RAID controller is nice for monitoring the status of the device.
It cannot repair or rebuild a broken RAID set, however.
Bro, I have been banging my head against the wall for an embarrassing amount of time trying everything and this worked for me. Thank you so much for posting this!! I was having trouble in JBOD trying to just span two 2tb drives, but this tip made all the difference.
This is very helpful…been trying to figure out to setup RAID 1. Thanks a lot for this post ๐
I have a unique error when I use the NexStar MX S3R in any mode. If I have everything plugged in and working, when I restart Windows 7, I cannot access my drive. It shows up but cannot be read. Furthermore, under Computer Management – Disk Manager, my drive shows up but right after that so does unallocated partition that is like 896979884 GB. If I turn the power switch on the NexStar off then on, it goes away. But when I restart, the problem shows itself again. Sometimes I get disk errors after doing this.
The thing is, I’ve purchased (2) different NexStars and used them on (2) different computers. Additionally, I had a spare hard drive with data on it that I tested. Lo and behold…same error.
Only thing left to test is firmware.
Can anyone offer insight? Ultimately what I want is (2) 4 TB drives in RAID 1 using Windows 7 as my OS. I haven’t had any problems with any of the other setup and functions thanks to this website.
Thx for all of the info…hugely useful. Does anyone know if there is a version of SteelVine that will run on an Intel-based Mac (MacPro, Lion Server). The link provided above is to software that will only run on PowerPC Macs. Thx
Hi
I had this unit for quite sometimes now.
The only problem I encountered was with the USB3 cable.
I bought a cable that is gold plated through Amazon and voilร !
The unit comes on without the hassel of reseating the cables every time.
I highly recommend this unit to recover and keep old disc drives once the OLD PC goes Kaput !
I do not use RAID and there is no SATA connector on my old model.
Regards