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

Information Menu

The Status menu displays a useful summary of the status of the NAS along with links back to the appropriate menus such as networking, volume and burning.

The Log menu has tabs for system, Samba and FTP logs.  The number of entries appears to be fairly limited in each category, and the log messages are fairly cryptic - what you'd expect coming out of a Linux-based system, but not particularly the user-friendly messages you might expect from a device targeted at the home user.  Figure 11 shows a sample from the FTP log.

FTP log

Figure 11: FTP log

Drive Pull Test

No review of a multi-drive NAS would be complete without testing the fault tolerance of the RAID 1 configuration.  For this test, I started copying a number of .MP3 files and then, with the file copy running, pulled one of the hard drives. 

The N2B1 continued to write files to the remaining drive, and the LCD Panel indicated drive removal.  The drive status light on the front panel also turned from the normal status blue to failed status red.  When I logged into the admin page, however, there wasn't an alert on the home page, or on the main status page for that matter, showing that the NAS was running in a degraded condition.  However, when I clicked on the Volume tab in the Status page, I finally found an error indication as shown in Figure 12.

Status showing unexpected removal of a hard drive

Figure 12: Status showing unexpected removal of a hard drive

I continued to copy files with the NAS running in a degraded condition and then reinserted the drive.  The LCD display noted the drive insertion, but RAID rebuild didn't begin automatically.  The drive just appeared as "Inactive" and I had to select it as shown in Figure 13 and add it to the existing RAID1 volume. 

Adding hard drive

Figure 13: Adding hard drive

After finishing that step, the replaced drive was added to the RAID and synchronization began (Figure 14).  The entire synchronization process took a little over 5 hours during which the NAS was still online and available to service client file requests.  No data was lost in this process.

RAID resynchronization

Figure 14: RAID resynchronization

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

For reasons not important here, I have both Xfinity and FiOS connetions active at my house. (The FiOS will be the only permanent one, Xfinity goes awa...
Whenever I try to update/upgrade opkg I'm getting the following response:Code: admin@RT-AC68U-08B0:/usr/lib# opkg updateDownloading http://bin.entwar...
My post relates to an issue with ASUS AiMesh and 2.4GHz clients.I have configured a Blue Cave as the AiMesh router and 2x RT-AC68U's as AiMesh nodes. ...
Several times per day my AC-58U refuses to work on the 5GHz band.Looking at the system log I can see the following repeating 50-100 times:Jul 14 12:59...
Hi,Got the mesh system setup and tweaked the settings and wanted to test the masternode connection speed.I tried to ssh but there's no iPerf on neithe...

Don't Miss These

  • 1
  • 2
  • 3