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.
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.
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.
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.