ZAPISZ JAKO PDF
Seagate NAS Pro 2-Bay | 4-Bay | 6-Bay Seagate NAS Pro 2-Bay | 4-Bay | 6-Bay
Seagate NAS Pro 2-Bay | 4-Bay | 6-Bay 

Czy ta treść była pomocna?

Operation

Powering on the product 

 Caution: Do not operate the product until the ambient temperature is within the specified operating range (see System Overview). Confirm that newly installed hard drives are acclimatized before operating them. 

Use the front power button to power on or power off the Seagate NAS Pro 2-Bay | 4-Bay | 6-Bay. You can also shut down the device or place it into deep sleep using NAS OS. Follow the directions below if the device is connected to a power source and turned off or in deep sleep.

  1. Before powering on the product, make sure that all the modules are firmly seated in their bays. Note that all drive slots must be filled by drives or empty disk trays in order for the product to receive sufficient cooling.
  2. Confirm that the NAS Pro power supply is connected to a compatible power outlet.
  3. Press the product's power button.

 

The status and hard drive LEDs blink white as the NAS boots. 

Powering off the product 

  1. Make certain that users on the network are not accessing the NAS Pro.
  2. Use NAS OS to turn the NAS Pro off or apply a short push to the power button. See the note below regarding a short push and a long push.

The LEDs will turn off once the system has shut down. 

Short push 

 Important info: Always eject the volume from your computer before applying a short push. 

A short push is a manual depression on the power button that lasts no longer than two seconds. When the product is operating, a short push on the power button will:

  • Turn the NAS Pro off
  • Place the NAS Pro into deep sleep

Deep sleep must be configured in NAS OS. 

Long push

A long push is a manual depression on the power button that lasts more than four seconds. When the product is operating, a long push will cut the power from the NAS Pro, forcing it to shut down immediately. A long push is not recommended as it may result in data loss. Therefore, it should only be used when troubleshooting a problem.