Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

NAS Reviews

Torture Test-more

Because some water came out of the drive enclosure, I decided to let the drives sit overnight again. I've submerged electronics accidentally before and usually if you let them dry out before turning them on you are fine. The image below shows the drives as they were pulled from the burned NAS.

ioSafe N2 drives after burn and soak

ioSafe N2 drives after burn and soak

While I waited for them to dry, I disassembled the rest of the NAS to get an idea of how it worked. The image below shows what I call the fireproof brick that the aluminum drive enclosure sits in.

What I call the ioSafe N2 firebrick

What I call the ioSafe N2 firebrick

As I mentioned before, the aluminum drive enclosure then sits inside the brick (with a plastic liner in between). The enclosed aluminum drive enclosure acts as a heatsink for the drives and you can see the many short cooling fins. You can see an image of the aluminum drive enclosure sitting inside the fireproof brick below.

ioSafe N2 drive enclosure after burn and soak

ioSafe N2 drive enclosure after burn and soak

As for the components of the NAS, they aren't designed to survive a fire. In the image below, you can see the wiring started to burn, as well as the charred remains of the motherboard. This sat on the bottom of the NAS enclosure with a thick galvanized steel plate separating it and the firebrick.

ioSafe N2 charred remains of component board

ioSafe N2 charred remains of component board

After a day had passed, I loaded the two recovered drives into the known-good NAS. I hit the power button on the NAS and after the N2 booted, I was able to check the contents of the volume and saw all of my data intact... amazing!

After a few minutes however, one drive started clicking badly and was automatically removed from the array, which you can see in the picture below.

Synology DSM showing degraded volume

Synology DSM showing degraded volume

Having two more good 1 TB drives, I started to disassemble the case to hot swap the clicking drive and repair the array, not knowing why the one drive was failing. When I got to the inner drive door there was already moisture accumulating on the door. In retrospect it appears that the water that got into the drive enclosure had not fully dried and the heat from running was sweating it out of the drive. Seeing water inside the drive enclosure I should have set the drives in rice for a few days to ensure they were fully dry.

The array repaired successfully and I left the inner and outer drive doors off in case the other recovered drive had moisture in it. The second drive continued to work after 2 days of sustained operation however. The lessons to be learned from this are two drives are better than one, make sure the recovered drives are completely dry and save the data somewhere else as quickly as you can just in case. If I were going to keep the NAS, I would have replaced the other original drive so that I removed any chance of latent failure from the torture test.

The gallery below has lots of images of the burning, the submerging, and the teardown.

Image Gallery

More NAS

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I run an OpenVPN client on my ASUS RT-AC86U with 384.10_2 firmware. Everything works fine except that whenever the VPN client disconnects (happens occ...
I just logged in and saw 1 core being maxed.Some rouge process has glitched and I have no idea how long it was pegged use a full cpu core.A script iss...
I can obviously ping the gateway from any device, but regardless of whether I turn on "guest" access to the share (or use username/pw), or try it with...
Hey guys; so obviously I can add my wifi printer to any particular SSID, but is there a way I can make it available to any device, regardless of which...
View attachment 17763why would a device be trying to access a private IP address from my network....View attachment 17764mysteriously here it is tryin...

Don't Miss These

  • 1
  • 2
  • 3