You can depress the power button on the front of the ioSafe R4 for about 5 secs until the disk LEDs start blinking, and then release. The shutdown process will take about 10 secs or so. Alternatively, you can shutodwn from FrontView from the System→Shutdown page.

No, you need to have at least one disk installed before you can update to the new firmware. You can do a factory default with all your disks after the firmware has been loaded.

Yes you can, however, please note that the smallest capacity disk will be used to determine the overall size of your data volume. Also, your performance may be limited by the slowest of the disks.

Yes, however, the ioSafe R4 will utilize the disks in SATA I (150MB/sec) mode.

After installation, delete the existing RAID volume and recreate it with one disk configured as a hot spare. Please be aware that X-RAID does not support hot spare.

Download the ioSafe R4 firmware to your PC and perform a local update from FrontView.

You can force a re-installation of the firmware from flash to the disk. This is helpful if you have lost your admin password and want to set it back to default, if errors in your network settings has made it impossible to connect to the ioSafe R4, or if you suspect that the operating system on your disk may somehow be corrupt. The firmware re-installation process will not touch your data volume.

Here are the steps:

1. Power down the ioSafe R4.
2. Locate a pinhole near the front panel power button.
3. Get a straightened paper clip and depress the hidden switch in the pinhole while the power is off, and then power on the ioSafe R4, keeping the switch depressed for about 5 secs.
4. You will see the drive LEDs in the front blink once. Release the switch immediately. Do not wait more than 10 seconds. Waiting 30 seconds (2nd blink of LED lights) will cause the unit to reformat all disks resulting in the loss of all data.

The firmware installation will begin from that point. You can monitor the progress with RAIDar. Your admin password will reset to 'iosafe1'.

Simply download the add-on and upload it from FrontView System→Update→Local tab. You will need to reboot before the add-on is installed.

Some of the Add-on packages will not be removable after they are installed. Add-on packages that install a service can be removed from the Services tab.

1. Make sure all software firewalls are turned off or disabled.
2. Make sure UDP ports on the routers are not blocked.
3. Make sure both the client PC and the ioSafe R4 are on same subnet.

You can reset your ioSafe R4 Admin password by accessing http://ip_address_of_r4/password_recovery . If you have forgotten the password recovery answer, you will need to perform a firmware re-installation to reset the admin password.

1. Assign a static IP address to the ioSafe R4, and set your PC with a static IP in the same subnet.
2. Connect the ioSafe R4 and PC NIC using a straight or crossover Ethernet cable.
3. Power on the ioSafe R4 and scan with RAIDar to locate the ioSafe R4.

Note: If the ioSafe R4 is set for DHCP (default mode), it will appear as IP 192.168.168.168.

The ioSafe R4 supports up to 4 data volumes, but each disk is limited to 2 data partitions.

X-RAID mode is designed as a single-volume system, so only one.

There are several things that factor into the usable capacity of your ioSafe R4 volume.

1. Disk manufacturers use 1GB = 1000^3, whereas most modern operating systems, including RAIDiator, use 1GB = 1024^3. This means a 500GB disk will show up as 465 GB in FrontView.
2. RAID requires one disk capacity to maintain redundancy. This means if you have 4 x 500GB disks, your end usable capacity will be 3 x 500GB.
3. RAIDiator operating system takes up roughly 2.25GB per disk.
4. The overhead of RAID and filesystem takes up roughly 2% of the total space.
5. Snapshot space takes up 5GB by default during installation. This is resizable.

For example, let's calculate the usable capacity of a 4 x 500GB system in RAID 5 or X-RAID mode. For simplicity, we'll calculate this based on

Raw capacity (GB = 1000^3)           = 2000
Conversion to (GB = 1024^3)          = 1862
Minus one disk for redundancy (-465) = 1397
Minus OS (10)                        = 1387
Minus RAID/Filesystem overhead (2%)  = 1359
Minus snapshot reserved space (5GB)  = 1354

Based on our calculation, the approximate usable capacity for a 4 x 500GB system is 1354GB.

On ioSafe R4 systems, you can take out the failed disk and replace it with a new disk while the ioSafe R4 is online (there's no need to shutdown the ioSafe R4). Make sure after taking out the failed disk, you wait about 10 secs before inserting the replacement. Once the replacement disk is in-place, the disk will be initialized and sync'd into the RAID volume.

This depends on the size of the disk. Typically it'll take anywhere from an hour to several hours. You can monitor the progress in RAIDar or FrontView RAID Settings tab.

RAID 0, 1, and 5 are part of the Flex-RAID RAID levels. If you want to switch from this mode to X-RAID (expandable RAID), you will need to backup your data first, and then perform a factory default. During the factory default process, there will be a 10-minute window during the boot where you can use RAIDar to click the Setup and set the box to the desired RAID mode (Flex-RAID or X-RAID). RAIDar will prompt with "Click Setup" during this 10-minute period.

Never migrate disks if your volume is in degraded mode. Make sure the volume is redundant first. Then follow the steps below:

1. Power down both systems, and move the disks over to the target ioSafe R4. Although not required, it's always a good idea to keep the ordering the same.
2. Perform an update to the latest RAIDiator release. This will sync up the firmware on disk with what's on flash.
3. After reboot, go to the Status/Health tab, and recalibrate the fan.

First, make sure the disk is at least as large as the smallest disk in the existing X-RAID volume. Then simply add the disk into the ioSafe R4. The ioSafe R4 supports drive hot-swapping; you can hot-add it while the ioSafe R4 is online.

The newly added disk will go through an initialization and sync phase. This can take several hours (e.g. 750GB disk can take about 7 hours). You will be notified by email after this is done, and you will need to reboot the ioSafe R4. Upon boot, your existing volume will either be made redundant if this is the 2nd disk, or your volume capacity will expand if this is your 3rd disk or higher. This is an offline process that can take several hours. You can monitor this with RAIDar, and you will receive an email when the process is complete (Note: email alerts must be configured to receive status/completion emails).

Replace one disk at a time with a larger disk, letting it finish initializing and syncing after each replacement (this process can take several hours depending on disk capacity, but you can continue access to the ioSafe R4), and after the last disk has been replaced, reboot the ioSafe R4. The expansion will occur at boot time. The expansion time will depend on your existing volume size, the ending volume size, and the number of files in your volume. Typically, it'll take anywhere from an hour to several hours. You will be notified by email at each step of the process.

Keep in mind that when you replace your disks, the ioSafe R4 supports drive hot-swapping; you do not need to shutdown the box before replacing the disks. Simply pull out the disk, wait at least 10 secs, and then add the replacement disk.

Yes

Contact ioSafe Customer Service.

Contact ioSafe Customer Service.

Contact ioSafe Customer Service.

You'll need to allow the ioSafe R4 to automatically power-down for the auto power-on to work. Manually powering off the ioSafe R4 overrides the automatic Power-On feature.

1. Check the Volume tab and see if the volume usage information is as expected.
2. Make sure you did not encounter multiple disk failures. Check your logs.
3. Do a Download All Logs, file a support request with ioSafe Customer Service, and attach your system logs with the request.

Resetting the ioSafe R4 back to factory default settings will wipe out all configuration and data. Please understand this before continuing. If you choose to continue, here are the steps:

1. Power down the ioSafe R4.
2. Locate the pinhole on the front of the ioSafe R4.
3. Get a straightened paper clip and depress the hidden switch in the pinhole while the power is off, and then power on the ioSafe R4, keeping the switch depressed for about 30 secs.
4. You will see the drive LEDs in the front blink once at about 5 secs and again at about 30 secs. Release the switch at the 2nd blink.

There will be a 10-minute window where you can use RAIDar to change the RAID mode and/or select the snapshot reserved space. RAIDar will prompt with "Click Setup". If you do not click Setup, the installation will begin with the default settings. Otherwise, it will begin when you've confirmed your option selection in RAIDar. You can monitor the installation progress with RAIDar.

Yes, the frame size will be negotiated down to the non-jumbo size with clients not supporting jumbo frames.

This may happen when the ioSafe R4 is configured to obtain IP address from a DHCP server, but the DHCP server does not provide an IP address when ioSafe R4 requests it. When this happens, correct the DHCP server problem, then wait until the ioSafe R4 obtains a correct IP address from the server. You can also unplug and then plug in the ethernet cable to force the network to re-initialize.

This may happen in these situations.

• After a power outage, the DHCP server's boot process takes longer than the ioSafe R4's.
• The DHCP lease period expired while the DHCP server was unavailable.
• The "renew" button in the "Ethernet" tab under the "Network" menu of FrontView was pressed while the DHCP server was unavailable.

ioSafe R4 uses a self-signed certificate. IE7 or Windows Vista will not trust this certificate unless you explicitly import this certificate by yourself. Below is brief procedure to import the certificate.

1. First, examine the certificate. (Left click on "Certificate Error" in address bar, and click "View Certificate".) If certificate's "Issued to:" and current IP are different, navigate to FrontView/Services/Standard_FIle_protocol. Under "HTTPS" service, there is a "Generate new key" button. Specify "SSL key host," match with your R4's IP, and click "Generate." Exit IE7 (to flush cache) and connect to FrontView again.
2. Then install the certificate into IE7. Left click on "Certificate Error" in the address bar of IE7 and click "View Certificate." There is an "Install Certificate" button. Click this button to start the "Certificate Import Wizard," and follow the wizard to install the certificate.
3. Once the certificate is installed properly, the warning will disappear.

Please note that Vista works different than XP. When you using Vista, you need to specify the ioSafe R4 as a "Trusted Zone"; otherwise you won't see the "Install Certificate" button when viewing the certificate. And during the "Certificate Import Wizard," you need to click "Place all certificates in the following store" radio button, and specify "Trusted Root Certification Authorities." (If you place certificates in your personal store, IE will not trust them.)

If you have less than 4 disks, simply add your disk(s) to the box. Your ioSafe R4 supports drive hot-swapping. The newly added disk(s) must be at least the same size as the smallest existing disk. Note that you can add one or more disks at a time. You will be notified by email and through FrontView that the disks will be initialized (this can take several hours depending on the disk capacity). During the initialization phase, you can use the ioSafe R4 normally. Once the initialization is done, you will be notified to reboot the ioSafe R4. Upon reboot, the expansion process will occur (this can take several hours depending on your drive capacity and the number of files in your data volume). You can monitor the status via RAIDar. Upon completion, you will be notified that the volume has been expanded.

You will need to replace each of your disks, one at a time, with a larger one. Each time the disk is replaced, you will need to allow the disk to initialize and sync before continuing with the next disk. The initialization and sync process will take several hours to complete depending on the capacity of your disk. The ioSafe R4 supports drive hot-swapping; you can replace the disk online. Once all the disks have been replaced, reboot the ioSafe R4 to start the expansion process. This will take several hours to complete depending on the volume capacity and the number of files in your volume. Do not interrupt the process during this time. Once completed, you will be notified of the new volume size.

The expansion will still occur, but the expansion size will be limited by the smallest disk in the system. When you replace each of the smaller disks to the larger disk capacity, X-RAID will expand itself, utilizing all the space from these larger disks.

If a failure occurs, please contact ioSafe Customer Service immediately. Provide the system logs and steps you took to expand your X-RAID volume. Do not try to fix the problem yourself at this point as you may create a 2-disk failure condition that might make data recovery impossible.

Using IOMeter in sequential read/write test with the ioSafe R4, you can achieve 30 MB/sec reads and 24 MB/sec writes. This was tested using a Dell 2.8GHz PC running Windows XP Pro.

The transfer rate should be similar to what you would get with the above IOMeter test. The read/write speed from your PC hard disk may limit these results.

You can enable the Fast USB Write option in the Performance tab. You will need to properly unmount the USB disk if you select this option; otherwise, you should run a file system check on the disk before accessing it next time. You can use the front Backup button to unmount and mount a USB disk. Depressing the Backup button for 5 seconds until the disk LEDs blink will unmount a mounted disk or mount an unmounted disk.

Try setting TCP delay_ack to 0. Default is 3, which causes handshake problems with the ioSafe R4, causing a severe performance penalty. You can set the delay_ack with the following command from the OS X terminal:

sysctl -w net.inet.tcp.delayed_ack=0

If you want the setting to stick when you reboot, add the line to /etc/sysctl.conf. For reference, see:

http://julipedia.blogspot.com/2006/02/samba-performance-under-mac-os-x.html
http://mail-index.netbsd.org/tech-net/2003/01/28/0004.html
http://systemsboy.blogspot.com/2006/02/delayed-a

The optimization performed on the ioSafe R4 may adversely affect compatibility with some routers. To turn off this optimization and thus provide better compatibility, change the MTU setting on the ioSafe R4 FrontView Network tab to 1492 (from the default 1500).

If you need to restart a service such as NFS, simply go to the Services tab, uncheck the box next to the service name, press "Apply," recheck the box and press "Apply" again. Disabling and re-enabling the service has the same effect as restarting a service, and no share access restrictions are affected during the process.

The private user home shares are available over CIFS or AFP.

Users are restricted from accessing each other's home share. Only Admin has access to other user home shares. If you want users to have mutual access privilege, create a public share, and put access restrictions so only these users have access to the share.

The home shares are created the first time users access the ioSafe R4. If a user has not logged in yet, the home share will not have been created yet.

The option is available in the Accounts → Preferences tab.

In order to delete files under the current share in User mode, the following conditions must be met:

1. The user is able to write to the share.
2. The user is able to write to the file. This can be for two reasons -- the file is writeable by everyone, or the user is a member of a group with write permissions for the file.
3. "Grant rename and delete privileges to non-owner of files" must be turned on in the Advanced Options tab.

In Windows, right click on the file. Then select Properties, and Security. Verify that the user has the proper permissions to delete the file. If not, connect to the share as user admin and delete the files and folders using admin privilege.

Sweeping changes to the ownership and permissions of the contents of a share can be made with the Advanced Options tab.

Try appending the pound (#) sign to the end of the URL like this: http://$mynas/$myshare/#

You can setup a backup job between two shares.

In Windows, right click on the file, then select Properties, and Security. Verify that the user has the proper permissions to read from or write to the file.

You can create a batch file with the following contents:

net use e: \\$hostname\$sharename $password /u:$username /persistent:no

and place it in your Startup menu.

Alternatively, you can use "Map Network drive" under the "Tools" menu in File Explorer, and check the "Reconnect at login" option.

The Advanced Options tab can be used to change the ownership and permissions of the contents of the share. Keep in mind that these options are meant for advanced users and can cause access problems if used improperly.

Since NTFS support is Read-only, you can use either Ext3 or FAT32. Ext3 allows for better retention of file ownership and permission and may be more appropriate in a mult-user backup environment.

You can download an Ext3 driver for Windows at: http://www.fs-driver.org/ .

Ext3 driver for OS X can be downloaded at: http://sourceforge.net/projects/ext2fsx/

From the command line, run

net use /delete \\nas_name\share_name

Port-forwarding is a way of selectively allowing access from a WAN (Internet) to your LAN through your existing router firewall. Only the network protocol "ports" that you forward will be allowed access to a particular box on your LAN. For instance, if you want to enable only FTP access to your ioSafe R4, simply forward ports 20 and 21 on your router to the ioSafe R4 IP. You can do the same for HTTP or HTTPS by forwarding ports 80 and 443.

Each router will have a slightly different method to allow this option. Here's a link that explains how you would do this with many of the routers on the market. This link is courtesy of MrCyberdude.

http://www.portforward.com/english/routers/port_forwarding/routerindex.htm

First configure your router for port forwarding. Ports 21 and the passive port range, which can be configured in the Services tab, must be forwarded to the ioSafe R4 IP address. Also set the "Masquerade as" setting to your external IP address or domain name.

In the Services page, select Anonymous for FTP mode. Note that Anonymous FTP is the only mode available in Share mode.

Try changing the MTU on your router to 1492. This is often needed when the ioSafe R4 is connected to the Internet through a Cable-based broadband service.

You will need to setup the ioSafe R4 for passive (PASV) FTP. To do this, go to the Services page and setup the options under FTP. In this case, you will need to select a passive port range (in most cases, a small range of 10 to 20 ports will do) and forward them from your router to the NAS. You will also need to enter your public domain name or IP address in the Masquerade field.

For more information on passive FTP, go here:

http://slacksite.com/other/ftp.html 

Try forcing your FTP client to use active (PORT) or standard passive (PASV) mode. Extended passive (EPSV) is only needed to IPv6 networks, and is not supported by the ioSafe R4.

Depending on the security mode and FTP mode, you may need to adjust the permissions on these files and folders to permit access through FTP. In Share mode or Anonymous FTP mode, the NAS will see an FTP user as a user named "ftp". Therefore, files and folders will need to be accessible by this user for them to be accessible via FTP. The easiest way to allow access to a file or folder is to go into Windows, right click on the file and select Properties, then select the Security tab, and add the required permissions to the "Everyone" setting.

In User-based FTP mode (available in User and Domain security modes), the NAS will see the ftp user as whichever user's credentials you used to login. Therefore, if you logged in as user "ewok", the NAS will see you as "ewok" and will allow you to access files and folders that are accessible by "ewok" when mounting the share in Windows.

Try putting your internal or external IP address (depending on whether you will be accessing the NAS from a server on your local network or through the Internet) in the Masquerade As field in the Services page.

Timestamp backup uses the file timestamp to determine if incremental backup should include the source file or not. The source file will be copied only if the timestamp on the file is later than that on the destination.

Archive Bit backup is similar to how Windows perform its backups and is the preferred method for backing up Windows. It uses an archive bit for each file to determine if the file has been backed up already or not. Once the file has been backed up, the archive bit gets cleared, so the file will not be included in future backups.

While the Archive bit backup type is the preferred type for Windows backups, the need to modify the archive bit on the source leads to three requirements. If they cannot be met, the Timestamp method should be used instead.

1. That ioSafe R4 has both read and write capability for the destination location. For example, this excludes all NTFS volumes connected via USB (NTFS on USB is supported only in read-only mode), but not FAT32 volumes connected via USB.

2. That ioSafe R4 has write access for the source location, specifically the type that allows it to modify the Archive bit.

3. That ioSafe R4 is the sole backup solution using the Archive bit method for the source location. Failure to meet this requirement will lead to incomplete backups for one or both backup systems.

Verify that you are able to access the backup source share over the selected protocol and using the credentials you entered when configuring the backup job.

1. Make sure that the USB device is listed in Frontview.
2. Verify that you can successfully access the USB drive share over the network when it is connected to the ioSafe R4.
3. Check that the USB drive is formatted with Ext2/3 or FAT32 file system.

Enable rsync access for the shares to be mirrored on both ioSafe R4 devices. Then, on each ioSafe R4, create a backup job using the remote share as the source, and the local share as the destination. Schedule these jobs so that they do not run at the same time.

Select Home Share as the backup protocol, and then enter the name of the user in the field under the protocol dropdown list.

The backup manager will timeout on attempts to access an FTP server after 270 seconds. If the connection is still timing out, try accessing the remote server at a less busy time. Also, try connecting to the remote FTP with an FTP client to verify that it is available.

Use the Windows (Archive Bit) backup protocol which will handle foreign characters without a problem.

By default, backup path names can contain only English ascii characters. In order to allow other characters in this feild, you need to enable "Allow Unicode for user, group and share names" option in FrontView's System/Language tab. This option is available only when Language is set to Unicode. Once this option is enabled, all Unicode characters can be used, including Germanic Umlaut, Cyrillic characters, Chinese characters, etc.

Use the rsync protocol in the backup manager to transfer the files from one ioSafe R4 to another. Rsync can also handle incremental backups efficiently. If several shares need to be backed up, create a separate backup job for each share.

Put a dollar sign ($) at the end of the share name. For example, if the D: drive is being shared on the Windows machine, the source path would be: //$machine/D$

Try searching the backup logs for lines starting with the word "cp:". The error message in these lines will give you some clues.

Use the Download All Logs link or use the Send All Logs button and send the logs to your personal email address.

rsync can use a lot of memory and the default 512MB memory may not be enough. Contact ioSafe Customer Service if you think you are having this problem.

Make sure that SMB signing is disabled on the Windows 2003 Server machine.

In most cases, this comes down to a DNS problem. You'll need to make sure that the ioSafe R4 is configured to resolve DNS from a properly configured DNS server. The easiest way is to run the DNS service on the domain controller. For NT4-style domains, make sure you are joining using an account with proper credentials for joining the domain.

The ioSafe R4 can handle up to 30,000 user + computer accounts, and up to 30,000 group accounts. Please do note however that the web-based FrontView management utility will behave slowly when there are more than a couple thousand domain users. We are hoping to have a firmware update in the future to resolve this problem.

1. Make sure the ioSafe R4 has successfully joined the domain.
2. Make sure the login credential is correct.
3. Make sure the user is logged into the domain on the client PC.

You can use Windows ACLs to do this -- right-click on a file, select Properties, then the Security tab. From there, you can set the permissions as desired. Most Windows operating systems will have this feature. Some, such as Windows XP Home, do not. To get the Security option to show under properties, you may need to uncheck the "simple file sharing" option in the Folder Options/View menu.

You can access the user home shares over CIFS or AFP.

Yes, but you will need to rejoin the domain.

Windows does not preserve ACLs when dragging files over the network, regardless of whether the target is an ioSafe R4 or a Windows server. To preserve ACLs, you can use xcopy /o from the command prompt.

All account management is handled on the domain controller.

It's likely the system clocks on the ioSafe R4 and the domain controller are not sync'd. It is recommended that a common NTP server be used to keep the clocks in sync.

Make sure your DNS and the ADS realm address settings are correct.

Macs are well-supported via AFP, CIFS and NFS protocols.

Check if your Mac is blocking UDP traffic. Go to System Preferences → Sharing → Firewall → Advanced. If you are, uncheck it and press OK and you should now be able to use RAIDar to find your NAS.

Our Mac users typically prefer AFP over CIFS due to better support for extended character set and better resource fork handling. Some prefer CIFS due to better forced compatibility with Windows users. Performance-wise, AFP and CIFS provide excellect throughput, with AFP providing faster searches via the Finder.

If you will be using AFP, from the Finder, select Go → Network → My Network → AFP on Hostname. If you will be using CIFS/SMB, from the Finder, select Go → Network → Workgroup → Hostname. Another option is Go → Connect to Server → Enter server address. This can be used to connect using SMB, AFP or NFS by entering the protocol then the IP of the NAS (e.g. smb://192.168.168.168, afp://192.168.168.168, nfs://192.168.168.168/sharename).

Try setting TCP delay_ack to 0. Default is 3, which causes handshake problems with the ioSafe R4, causing severe performance penalty. You can set the delay_ack with the following command from the OS X terminal:

sudo sysctl -w net.inet.tcp.delayed_ack=0

If you want the setting to stick when you reboot, add the line to /etc/sysctl.conf. For reference, see:

http://julipedia.blogspot.com/2006/02/samba-performance-under-mac-os-x.html
http://mail-index.netbsd.org/tech-net/2003/01/28/0004.html
http://systemsboy.blogspot.com/2006/02/delayed-a

For ioSafe R4

ioSafe R4 supports up to 750GB disks.

Contact ioSafe Customer Service for the latest details.

Starting with RAIDiator 3.01, there is comprehensive memory test that you can run on the ioSafe R4. To invoke it, power-down the ioSafe R4 and depress the front power button, until you see all disk LEDs blink together for the 5th time (ignore the quick flash at the beginning). Disks will blink for about a second at about the 5-, 10-, 15-, 20-, and 25-sec mark. Release at that point. The first disk LED will come on to signify the first of an 8-stage memory test. The LED sequence for the 8 stages will be in binary format going from left to right. When all disk LEDs are lit, the memory is good. If the first and second LED blink, followed by the 3rd and 4th LEDs, in an alternating pattern, the memory is bad.

Please keep in mind that the success rate for flagging an actual bad memory is about 85%, so we do recommend that you run this test twice.

Yes, however please use a hub that is powered by an AC adapter.

Currently multi-readers are not supported.

Yes, you can attach multiple USB printers to the ioSafe R4.

Ever since Windows XP SP2, some printer drivers really slowed down with Windows Printing. If you have have one of those printers/drivers, a nice workaround is to use IPP instead of Windows Printing. An easy way to setup IPP Printing is by downloading Bonjour for Windows from Apple's website, and just follow the wizard as it discovers and sets up IPP.

You don't actually need Bonjour for Windows to use IPP, since Bonjour is nothing more than a discovery service. To use IPP Printing without Bonjour, try: Control Panel -> Printers -> Add Printer -> Network Printer. Then click on the button that says something about connecting to a printer on the internet. For URL, use "http://[nas]:631/printers/[printer_share_name]". As an added benefit, it should be *much* faster than Windows printing.

You can attach printers, external hard disks, flash devices, UPS' and USB hubs. Please see the ioSafe Hardware Compatibility List for the complete list of devices.

Please check if your drive is listed in the ioSafe Hardware Compatibility List. It may be using a chipset that may be currently incompatible with the ioSafe R4. If your drive is 2.5" disk, please use an AC adaptor instead of getting power from USB bus.

The ioSafe R4 will not work as a target USB device.

Simply refer to the Hardware Compatibility List for a compatible UPS and plug the USB monitoring cable to the ioSafe R4. FrontView will show that your UPS is detected, and any UPS alerts will be automatically sent to the Alert contact list. Upon battery-low condition, the ioSafe R4 will power down gracefully.

First, make sure the ioSafe R4 has been updated to the latest RAIDiator 3 or later release. Earlier RAIDiator releases do not support disk spindown. Next, disable services that you don't need -- UPnP is one such service that might prevent your disks from spinning down.

The ioSafe R4 itself does not sleep in disk-spindown mode, hence the power supply and main board can overheat if the fan is not running.

Seagate uses these SMART fields for internal counts, so this is a known issue with Seagate disks. Look for abnormal counts in other fields, especially Reallocated Sector Ct and ATA Error Count.

After powering down and removing the front door of the R4, the fan module involves loosening the captive screw located on the fan door. After loosening, simply slide the original fan module out and replace with a new fan module.

Only ioSafe approved fan modules can be used. Please contact ioSafe Customer Service for assistance.

Can I use the regular standard ATX power supply unit to power the ioSafe R4?

Can I use a serial-to-USB converter from a serial port-only UPS to the ioSafe R4?

How can I release a stuck ioSafe R4 tray?

Miscellaneous

What port does RAIDar use?

How do I install the rack mount kit?

ioSafe Remote Access Policy

I hereby authorize ioSafe Inc. (ioSafe) support
personnel or ioSafe's authorized representatives to gain 
remote access of my ioSafe equipment to help diagnose and 
repair operational problems. I understand that such support
action cannot be guaranteed of its success and may yield
partial or total data loss. By allowing the remote access,
I agree to hold ioSafe and its representatives harmless of
wrongdoing or negligence of any kind.

How do I send all logs?

1. Go to Status/Logs tab.
2. Click on the Download All Logs link at the upper right corner.
3. Forward the zipped logs to customerservice@iosafe.com.