Xtore™ Professional Storage

RAID/Volume

When the user has written our program into a CF and then inserted it into the embedded system, the system will read the initial data from CF in the first installation. After that, any system updates will also update the CF content accordingly.
When the user has written our program into a CF and then inserted it into the embedded system, the system will read the initial data from CF in the first installation. After that, any system updates will also update the CF content accordingly.
When the user has written our program into a CF and then inserted it into the embedded system, the system will read the initial data from CF in the first installation. After that, any system updates will also update the CF content accordingly.
There are 2 reasons for this warning message:

1) Some HDDs do not support the Parity check required when you have RAID1 or RAID5. As a result, the system may not be able to detect those HDDs after the Volume building stage and a system warning could be triggered accordingly. Please try to rebuild the Volume as RAID 0 and see if the build is successful. If successful, please change the setting of the HDD and try again.

1) When the user builds the Volume as RAID0, RAID1, and RAID5; the system might take a particular HDD as defective if there is a bad sector or bad track. However, the user might be able to successfully format and install certain software/OS on this disk. Under these circumstances, please try to build up a full size Span volume and check the system log in order to locate the bad sector or track.
RAID 0 and Span both share the common features of zero redundancy and virtualizing the total disk space into one volume. The difference is that RAID 0 stores data randomly while Span stores data sequentially. System speed and capacity are increased from RAID 0 but not from Span.
The 1st 8Mb reserved space is for RAID/Image Writer Configuration (Disk version only). This reserved space is designed for the Disk Version only.

The 2nd reserved space is 32MB large and contains system configuration data, for example: IP, Server name…. Etc. (The OS will be stored here in the Disk version while others were stored in DOC/DOM)

The 3rd reserved space is known as the SWAP partition. The partition size will be the same as your RAM size and it contains the SWAP information.

The 4th reserved space contains all data required for Volume Management. The size varies depending on the actual disk size.

RAID 1 uses Mirroring to backup the data. If the system allowed an odd number of disk to be built as a RAID 1 system, a large amount of disk space would be wasted as the system would have to write the data several times. It would not only be a waste of storage space, but also a decrease of speed would be noticed due to the multiple copies being made by the system.
Please make sure all the hardware (including HDD, MB….etc) is OK. It's normally a Hot Swap Hardware spec and type problem that causes this problem.
The following reasons can cause a hard disk rebuilding operation to fail:

1) The replacement hard disk is also damaged. Try using a brand-new hard disk.
2) The hard disk used to rebuild is smaller than the original. Replace it with a disk of at least the same size as the other disks in the system.
3) The jumpers of the hard disks are set incorrectly. Since jumper settings depend on the model, refer to the instructions that came with the hard disk.
4) The replacement hard disk is of a different type. For example, if the original is an ATA 100 model, and you try to use an ATA 66 or a similar model from a different manufacturer, the data rebuild may fail. Always use models from the same manufacturer with similar specs.
5) It could also be that a second failure has occurred and another disk, apart from the one to be rebuilt, are also damaged.
Whenever a user notices a volume with a status of "crash", please try to re-create the Volume. If the re-creation fails, please check all HDDs and make sure there is no defective HDD. If all the HDDs are functioning normally, please call your system provider and ask for technical support.
Sometimes, due to the process priority being too low, the action was locked by another system process while the system was saving the vinum configuration. NAS has successfully raised the priority for the vinum configuration and as a result, the configuration will be saved right after the changes have been made.