12-02-2007 06:23 PM
12-04-2007 12:36 PM
12-08-2007 08:18 PM
12-09-2007 06:23 AM - edited 12-09-2007 06:24 AM
12-16-2007 09:14 AM
02-27-2008 02:11 AM
03-20-2008 05:17 PM - edited 03-20-2008 05:27 PM
03-21-2008 02:11 AM
04-07-2008 01:41 PM - edited 04-07-2008 02:46 PM
I think I figured it out for myself but you need to be familiar with Linux to get into this since it involves VI and familiarizing yourself on how to use MDADM. For those planning to go this route because, 1) you don't have your data backed up because RAID 1 is supposed to be failsafe and 2) you'd rather not lose all your data by sending it in to Seagate without paying a nice chunk of change to their data recovery division, let me warn you that going beyond step 2 will invalidate your warranty. Given that caveat, here goes how I did my rebuild:
First, I initially thought that the the web server was not loading since I wasn't able to talk to the the IP address and the computer name that I previously used to access my MSS II. After checking my DHCP tables, I saw that it had picked up a dynamic IP on my network and reset it's name to a generic name like MSS-XXXXXX. I had totally forgot that I had performed a reset when I was talking to the Seagate/Maxtor tech which couldn't offer me any more that that and to send it in for warranty service and lose all my data. So you gotta' find out the IP address of your MSS II and log into the advanced settings screen with your web browser.
Second, after getting into the web interface, you can start by upgrading to the most recent firmware to reduce any problems if you are still on older firmware. The latest firmware is 3.1.28 at:
Third, load the open-source version of the firmware that has SSH included at:
Fourth, SSH into your MSS II and follow the installation instructions included with the readme on the open source firmware to change the root password.
Fifth, fix the "can't access tty: job control turned off" error during login:
Sixth, start the rebuild using MDADM:
I used "mdadm --detail /dev/md0" to view my array information. Make sure that you have one active device and that it's working. If you have a failed device, you'll need to check whether you need to actually replace it rather than attempt a rebuild.
The drive that was still active for me was /dev/sdb6. Thus, /dev/sda6 is my drive that is probably out of sync. If the other drive failed on yours, you'll obviously use the other drive in these commands (/dev/sdb6 rather than /dev/sda6). To double-check that the problem is a sync problem, I did a "mdadm --query /dev/sda6" and it reported that this drive is not in the array because of a "mismatch". Then, I did a "mdadm --examine /dev/sda6" to see that the state is "clean".
To rebuild the array, I did a "mdadm --manage --add /dev/md0 /dev/sda6". This will put the drive back in the array and start rebuiding.
I did a "mdadm --detail md0" at this point, to see that the drive is added back into the array as a spare, the state of the array is "clean, degraded, recovering" and gives the rebuild status.
Seventh, after the rebuild was completed, I then checked the MSS II RAID settings status in the web interface says "healthy" before closing SSH and configuring my network settings back to the way I had it before. Voila, good as before without sending it to Seagate and losing all my data!
To clear the error light on the front panel, just reboot. If you want to fix everything, you can also fix this typo:
07-17-2008 10:29 AM - edited 07-17-2008 10:31 AM