4.6 Novell NetWare - When starting the NetWare operating system, the Adaptec Storage Manager agent may fail to start. A message "The Storage Manager agent failed to start" displays when starting the server. The server is unable to load the Storage Manager agent. This is usually caused by loading Java before the Storage Manager agent. In the file Autoexec.ncf, move the line "LOAD RAIDAGNT -BOOT" so that it is before any lines that reference Java. - A NetWare system can run only one instance of the Adaptec Storage Manager agent. - Under Novell NetWare 6.5, you cannot initialize a drive using Adaptec Storage Manager. You must use the BIOS Array Configuration Utility (ARC). -------------------------------------------------------------------- 5. RAID Level-Specific Notes 5.1 RAID 1 and RAID 5 Notes - During pool migration from a RAID 1 or RAID 5 to a RAID 0, if the original pool had a spare drive attached, the resulting RAID 0 retains the spare drive. 5.2 RAID 10 Notes - You cannot change the priority of a RAID-10 verify. Setting the priority at the start of a verify has no effect. The priority is still shown as high. Changing the priority of a running verify on a raid-10 changes the displayed priority until a rescan is done, then the priority shows as high again. - Performing a Verify and Verify/Fix on an RAID 10 displays the same message text in the event log, "Build/Verify started on second level pool of pool 'Pool_0.'" You may see the message three times for a Verify, but only once for a Verify/Fix. - During a migration from a RAID 0 to any redundant pool like RAID 5 or 10, Adaptec Storage Manager shows the status as "Degraded Reconfiguring" for a moment, then the status changes to "Reconfiguring." The "Degraded" status does not appear in the event log. 5.3 RAID x0 Notes - After building or verifying a leg of a second-level pool, the status of the second-level pool is displayed as a "Quick Initialized" pool. -------------------------------------------------------------------- 6. Other Issues and Notes 6.1 Internal RAID Storage Notes - If you initialize one or more drives in a snapshot source pool, the snapshot target cannot be deleted. To avoid creating a snapshot drive that cannot be deleted, you must delete the snapshot drive first, before you initialize the drives in the source pool. - With Linux kernel versions 2.4 and 2.6, the ARCCONF DELETE command may fail with a Kernel Oops error message. Even though the drives are removed from the Adaptec Storage Manager console, they may not really be deleted. Reboot the controller; then, issue the ARCCONF DELETE command again. 6.2 External RAID Storage Notes - If you create a pool, reboot your external RAID storage enclosure with an alternative image, then delete the pool, the pool appears with an offline status when you reboot with the original image. You cannot delete an offline pool. - Under rare conditions, configuration changes...

Ce manuel est également adapté pour les modèles :
Autres composants - Adaptec RAID 3405 (29.7 kb)
Autres composants - Adaptec RAID 31605 (29.7 kb)
Autres composants - Adaptec RAID 3085 (29.7 kb)
Autres composants - Adaptec RAID 3805 (29.7 kb)