Seagate BlackArmor NAS 220 - won't boot

[SBMongoos]

I have a Seagate BlackArmor NAS 220. Recently I spotted the NAS had hit it's 90% limit (logged into it to verify) I have set. So I removed old backup archives via Windows Explorer. I noticed the amber light remained on with the NAS so I reboot it. When it came back up all seemed fine. I went to login again and I noticed a HDD error message but it cleared fairly quickly. Shortly after I started hearing, whats sounds like, the drives spinning up and I lost network access. Could no long ping the NAS nor log into it. I disconnected the power and re-seated both drives. However I'm still hearing the same noise. Like they are trying to spin up but are stuck in a loop. Not sure if this is a HDD issue or maybe something on the NAS PCB board. There are two drives so if one goes I should be able to go about business as usual. I've lost a drive in the past and replaced it without issue. I'm doing mirroring on this NAS.

I'd really like to get it back up and running. I only do syncing of data backups but I do have software on this NAS that I cannot lose. Looking to get rid of old desktop (which has a second drive for redundancy and Synctoy copies backups to the NAS) and use laptop with a docking station. Even if it's just long enough to get the data moved to another resource.

 

[dosborne]

Try removing the drives and powering up to see if you get connectivity.

 

[SBMongoos]

Try removing the drives and powering up to see if you get connectivity.

Getting an orange light on the ethernet. Manual says that's the link activity but I'm not getting a green connection light. I'm not able to ping it, of course.

Any chance the battery I see (must be like a CMOS battery) needs to be replaced or is this the PCB board (ethernet, whatever else) issue you think?

Also, I tried connecting each drive to my Win10 PC. Both drives sound okay and spin up. Don't hear any weird sounds. Hmm

 

[dosborne]

Unfortunately, I'm not familiar with your specific NAS unit.

In most NAS units, removing the drives should at least allow basic access to the UI if the unit is functional. Is there a reset button (sometimes one of those pin hole types?).

Unlikely to be a battery issue. Typically it is just used to "remember" the system settings.

 

[SBMongoos]

Unfortunately, I'm not familiar with your specific NAS unit.

In most NAS units, removing the drives should at least allow basic access to the UI if the unit is functional. Is there a reset button (sometimes one of those pin hole types?).

Unlikely to be a battery issue. Typically it is just used to "remember" the system settings.

Just tried that but it doesn't appear to be responding. Still cannot ping the NAS.

 

[dosborne]

Still cannot ping the NAS.

Keep in mind of course that resetting, if you were able to, would clear any configured network settings so the NAS could potentially resurface with a different IP. Assuming you know that, run the software discovery client that came with it (or available download). I also assume you've tried the basics of using a different network cable, connected to a different port, etc.

I'm not familiar with it, but I see there is a reset to factory default utility (or possibly just instructions?)

Failing that, your last option is likely any firmware recovery tools that may or may not be available for your NAS. Checking with the manufacturer, or specific sites that specialise in that brand may provide more answers as these suggestions are just basic generic options.

And, sometimes, it truely is just a hardware failure. Looks like these units are 10 years old now.

Depending on the file system, worst case, you may be able to recover the data from the drives.

 

[SBMongoos]

Keep in mind of course that resetting, if you were able to, would clear any configured network settings so the NAS could potentially resurface with a different IP. Assuming you know that, run the software discovery client that came with it (or available download). I also assume you've tried the basics of using a different network cable, connected to a different port, etc.

I'm not familiar with it, but I see there is a reset to factory default utility (or possibly just instructions?)

Failing that, your last option is likely any firmware recovery tools that may or may not be available for your NAS. Checking with the manufacturer, or specific sites that specialise in that brand may provide more answers as these suggestions are just basic generic options.

And, sometimes, it truely is just a hardware failure. Looks like these units are 10 years old now.

Depending on the file system, worst case, you may be able to recover the data from the drives.

Yes, the manual does state (I'm not sure how long the reset button has to be held - it's not clear) but I held it for 10 seconds.

Here's what I'm seeing now (and was doing previously at one point). I can see the network connection from the NAS come on at the switch port. It's not getting assigned an IP (and should as all equipment is working okay and I've recently added a device without issue). I see the HDD light come and and the HDD spin up. But then after about 20 seconds it sounds like the HDD heads are parking or some sort of sound and the connection light on the switch goes out. Then it starts over again and this is the loop it's in. This is what happened shortly after I freed up space on the mirrored drives.

I'm trying to get clear on what type of OS is running on this thing. I'm wondering if installing Oracle VMBox and a form of Linux would work and then trying to access one of the drives via USB to get the data would work.

 

[dosborne]

My *guess*, and one of the most common failure points, would be a power supply issue based on the description. That is partly the reason for trying to recover the device without installing the drives.

I'm trying to get clear on what type of OS is running on this thing. I'm wondering if installing Oracle VMBox and a form of Linux would work and then trying to access one of the drives via USB to get the data would work.

The FS used should be documented *somewhere*, but most often linux-based (however due to the age it could be proprietary too). There are a number of Linux distros that boot from an image (CD, USB, ISO), so installation is not required. http://www.system-rescue-cd.org/ may be an option too. Just can't think of the one commonly used right now.....

In some cases you can also load the Linux FS extension (ext2fsd or similar) that allows read-only access as that is all you would need to offload the data, so your usb enclosure/dock/adapter idea would work. I keep a dock and usb-sata and usb-ide adapter cables in my closet for this very reason. Very handy to have at times.

Edit: here are some options, a search for "Live cd" will turn up more. https://www.linux.com/tutorials/five-best-linux-live-cds/

 

[SBMongoos]

Be nice to find a way to test with another power supply. That''s a good idea.

As for Linux options those are also good ideas and I think I have some things laying around Probably need to update first though.

 

[SBMongoos]

I decided to buy a AC Adapter Universal Regulated Multi Voltage Switching Power Supply. I can use it as a regular replacement or multi purpose needs. FIgured if I'mg going to spend the money and this isn't the fix I'll have a tool that may come in handy.

https://www.amazon.com/gp/product/B07YCJZ2CZ/?tag=snbforums-20

At the manufacturer web site I believe they said it was UL listed. Nice features.

 

[SBMongoos]

My *guess*, and one of the most common failure points, would be a power supply issue based on the description. That is partly the reason for trying to recover the device without installing the drives.

The FS used should be documented *somewhere*, but most often linux-based (however due to the age it could be proprietary too). There are a number of Linux distros that boot from an image (CD, USB, ISO), so installation is not required. http://www.system-rescue-cd.org/ may be an option too. Just can't think of the one commonly used right now.....

In some cases you can also load the Linux FS extension (ext2fsd or similar) that allows read-only access as that is all you would need to offload the data, so your usb enclosure/dock/adapter idea would work. I keep a dock and usb-sata and usb-ide adapter cables in my closet for this very reason. Very handy to have at times.

Edit: here are some options, a search for "Live cd" will turn up more. https://www.linux.com/tutorials/five-best-linux-live-cds/

So I'm know using the AC adapter from the link I provided above. I'm getting power and blinking amber ethernet light. I am getting a steady green light on the ethernet but it looks like the unit is rebooting. Windows is not connecting to it. If it reset last time (from my trying to do so before the AC adapter was replaced) I would think I could at least ping it now as I have MAC filtering setup and to assign the MAC address of this device a specific IP. But no go.

From the manual of the NAS after doing a reset:
Resetting Your BlackArmor Server
Follow these steps to reset the BlackArmor server’s name, DHCP setting (network mode)
and log in password.
Note: You will need a paperclip or other narrow device to perform this task.
1. Carefully access the back of the server.
2. Ensure that the server is powered on and connected to the LAN.
3. On the back of the server, find a single small opening. The reset button is inside the
opening.
4. Insert the end of the paperclip into the opening, then press and hold the reset button. Do
not release the button yet.
5. Hold the reset button until the System Status LED on the front of the server blinks. This
takes several seconds.
6. Release the reset button.
The server reboots itself. Once the server has restarted and the front LEDs are lit up, the reset
is complete. The server is renamed to “BA-MAC address”, where MAC address is the last six
characters of the server’s MAC address.

So DHCP should be enabled on the NAS if the reset took and the the original IP should be assigned again based on the manual assigning via MAC address. But again I cannot even ping it. Plus I tried the idea of BA-(last six characters of MAC address) via a browser but nothing. My security software can scan the network and see devices but not the NAS.

Plus, the NAS is rebooting. Maybe solved one problem but have others.

According the my security software history this NAS is running on Linux.

Also, as a last minute thought. I reconnected the original AC adapter and the NAS is acting just like above with the new one. LOL. No access to NAS here either.

 

[dosborne]

What *I* would do:

Pull the drives
Connect it directly to your PC or laptop via ethernet
Reset NAS
Run discovery client
(Ensure pc has static IP on same default subnet as the NAS)
Run DHCP server on your PC or next best option, disable mac filters and remove IP reservations associated with this device (keep it as simple as possible)

Forget about the IP that used to be on the NAS as there are many reasons it may no longer work, just look in the DHCP assignment list and/or run the discovery app

 

[SBMongoos]

What *I* would do:

Pull the drives
Connect it directly to your PC or laptop via ethernet
Reset NAS
Run discovery client
(Ensure pc has static IP on same default subnet as the NAS)
Run DHCP server on your PC or next best option, disable mac filters and remove IP reservations associated with this device (keep it as simple as possible)

Forget about the IP that used to be on the NAS as there are many reasons it may no longer work, just look in the DHCP assignment list and/or run the discovery app

I'll look into these options. Thing keeps rebooting so not sure I can connect to it. Comes on, I hear the drives spin up, I hear a click..continued spinning of the HDDs and then a louder click sound an it looks it shuts down and then starts the process again. A loop.

I tried the reset (pin hole on back) again but it just kept doing it's loop.

Edit: ugh, you did say pull the drives. Will try again.

Edit II: so I pulled the drives and it stopped rebooting. I can see I'm getting a connect at the ethernet port on the back and at the switch. But, I'm getting an amber colored light on the front. I tried resetting it by hold the button down for over a half minute but nothing.

 

[SBMongoos]

Okay, I forgot how finicky this NAS can be. Funny I've been thinking about getting a new one for a while now. But this box always chugs along.

Seems after being powered off for a while helped. Cleared system memory apparently. I did finally get connected without the drives. Finicky getting up and connected. Determined that HDD1 (how the drives are labeled in the box - HDD1/HDD2) must have failed. When it's installed it just reboots. With HDD2 it boots up and I can login and access data via Windows Explorer. I let it sit on with HDD2 installed so will see if it's still up when I get home today. I'll copy everything off to another backup USB drive. Need to decide if I want to simply replace HDD1 and let the mirror rebuild or get a new NAS. I had to replace HDD2 two or three years ago. I like the idea of having local backups that I don't have to disconnect/connect. Although I am moving to a laptop with a dock.

 

[SBMongoos]

Well the new hard drive came quickly. Was able to buy an identical with a 3 year warranty for a great price. I'm fine with that for what I'm going to use this for.

So, you can power the unit off, swap out the bad drive with the new, pop it in place and then power up the NAS. You go into the OS (or use the Seagate tool) and choose the option to reclaim the new drive via the software, as it's a mirrored system. BUT now I can't gain access back to the NAS again, I can't login or ping it. I was able to do so with only the one good drive in earlier. The amber light as on which would denote a bad or missing drive (or other issue). I can confirm that the drive that I took out was bad. I have equipment to test and I could tell as it spins up at clicks loudly and then it shuts off and it's in that cycle. With the replacement drive installed the amber light went out. Blue light is on!

Edit:

Okay, take a step back. I did mention this thing can be a bit finicky and always has been. Here's notes I put together on what I did in case someone else may need them. Granted I need to confirm the RAID 1 is rebuilt but it is in process.

****************

BlackArmor NAS 220 Drive Replacement Tutorial

Follow the steps below to replace a drive from a BlackArmor NAS 220:

• Power off the unit and unplug the AC power cable from the power supply
• Position the unit so you can access the rear panel, and turn it on its side
• Remove the three screws from the back of the unit that holds the top cover to the chassis
• Take the cover off sliding approximately 2 inches within the tracks on the bottom of the chassis
• Gently pull the hard drive bracket assembly white pull strap forward to release the hard drive from the bay.

Note: When replacing a drive, it's important to identify the drive first. After removing the top cover you will notice that the drive on the top is the drive 1 and the one on the bottom is the drive 2, both will have their labels facing up. Don't replace the wrong drive!

• Pull the hard drive out of the drive bay while pulling forward on the bracket assembly strap.
• Remove the brackets by carefully pulling the bracket away from the side of the hard drive.
• Carefully position the replacement hard drive in the bracket assembly.
• Re-install the brackets onto the sides of the hard drive.
• Two metal quick release pins hold the brackets to the side of the drive.
• Align the bracket pins with the corresponding holes in the side of the hard drive. Push on the bracket face until the pins have completely and firmly seated.
• After attaching the brackets, carefully slide the hard drive and bracket assembly back into the drive bay. The bracket will lock the hard drive into its system connector.
• Reinsert the top cover and replace the screws back in place.

What's next?

Drive Removal/Replacement:

The following provides the steps necessary for using Seagate’s BlackArmor Manager to claim a replacement drive and recover a RAID 1 volume. It is assumed that you are logged into the BlackArmor Manager as an admin user before proceeding.

Claiming the New HDD:

• Mouseover Storage and click the Disk Manager link. The Disk Manager page opens.
• Locate the replacement hard drive from the list provided (it should be listed as Foreign) and click on the Claim Disk icon.
• A window opens, asking you to confirm this request. Click the OK button. The drive reclamation starts processing.
• When finished, the Disk Manager displays a text message stating that, "HDD (hard disk drive)…claimed successfully". The disk is ready to be recovered into a volume.
• Now, mouseover Storage and select Volume, the screen refreshes.
• You may have a few choices here and the one you want is to recover/reclaim. Choose this option and it should recreate the mirror by copying the data from the good existing disk back to the new disk to recreate the RAID 1 mirror.

 

[dosborne]

After removing the top cover you will notice that the drive on the top is the drive 1 and the one on the bottom is the drive 2, both will have their labels facing up. Don't replace the wrong drive

As part of my SOP, I always put labels on the drives when I install them in my NAS (or really any device, PC, etc). If the bays themselves are not well marked, I label them too Doing this at initial install time saves many headaches down the road when scrambling to get things running under pressure.

I usually go way overboard and put the date of purchase on the drives as well. I can't forget to mention that all the documentation either gets scanned or downloaded, same for all receipts. Screen captures showing manufacturer, brand, model and serial numbers get converted to PDF for future reference. Typically, I even scan the box the stuff came in even though I keep EVERY original box lol If the device has firmware versions, every one, past and present gets archived and of course every saved configuration file gets renamed to include date and firmware version.

 

[System Error Message]

sounds like the armour is not bullet proof

 

[SBMongoos]

Yes, I had to label these drives as well. The NAS wasn't it terribly will marked on the inside.

I get it. I'm big on documentation. I think that's why people like to have me do it because I like to do screenshots and try to be concise.

As part of my SOP, I always put labels on the drives when I install them in my NAS (or really any device, PC, etc). If the bays themselves are not well marked, I label them too Doing this at initial install time saves many headaches down the road when scrambling to get things running under pressure.

I usually go way overboard and put the date of purchase on the drives as well. I can't forget to mention that all the documentation either gets scanned or downloaded, same for all receipts. Screen captures showing manufacturer, brand, model and serial numbers get converted to PDF for future reference. Typically, I even scan the box the stuff came in even though I keep EVERY original box lol If the device has firmware versions, every one, past and present gets archived and of course every saved configuration file gets renamed to include date and firmware version.

Yep, I find doing these things really help when it hits the fan. Then you have resources.

Thanks for your feedback earlier.

 

[Igor Katsman]

I have a Seagate BlackArmor NAS 220. Recently I spotted the NAS had hit it's 90% limit (logged into it to verify) I have set. So I removed old backup archives via Windows Explorer. I noticed the amber light remained on with the NAS so I reboot it. When it came back up all seemed fine. I went to login again and I noticed a HDD error message but it cleared fairly quickly. Shortly after I started hearing, whats sounds like, the drives spinning up and I lost network access. Could no long ping the NAS nor log into it. I disconnected the power and re-seated both drives. However I'm still hearing the same noise. Like they are trying to spin up but are stuck in a loop. Not sure if this is a HDD issue or maybe something on the NAS PCB board. There are two drives so if one goes I should be able to go about business as usual. I've lost a drive in the past and replaced it without issue. I'm doing mirroring on this NAS.

I'd really like to get it back up and running. I only do syncing of data backups but I do have software on this NAS that I cannot lose. Looking to get rid of old desktop (which has a second drive for redundancy and Synctoy copies backups to the NAS) and use laptop with a docking station. Even if it's just long enough to get the data moved to another resource.

Hi, did you ever manage to revive this NAS? I got a diskless 220 and though there's Ethernet activity, NAS does not register with LAN/DHCP- with or without blank Drives. I wanted to check if anyone knows: does blackarmor 220 normally boot without drives to where it starts its webserver? Or does it need NAS OS installed to new 1st disk manually? I see mention of NAS OS installer for 4-bay NAS, as well as rescue ISO, but I cannot find any docs on what and how.
Thanks.

 

[SBMongoos]

Igor Katsman - read post #15 above. Just scroll up. Step by step instructions.