SAT3540U3ER - 4 Bay 3.5in SATA HDD RAID Enclosure - Power Issue?

Hello,

I have a StarTech 4xHDD RAID Enclosure (SAT3540U3ER),

I plugged in four Hitachi 4GB Sata3 HDDs (HDS724040ALE640) and configured them for RAID-5, giving a volume capacity of 11GB.

I have noticed recently that the unit has the REBUILD light on and two red RAID lights: +1 and +5. There is no drive warning light.

There is no rebuild going on, the unit goes into sleep mode after some time.

I’m therefore attempting to reset the unit, by following these instructions:

  1. Turn off the enclosure and remove the drives.
  2. Power the enclosure back up and set it to RAID 0 by pressing the “Mode” button Press and hold the “Confirm” button on the back of the enclosure next to the ESATA port behind the plastic cover, until it powers off.
  3. Install the drives.
  4. Turn the power back on.

Step 1: OK

Step 2: Not OK

  1. I press the power button. Nothing.
  2. I press the Mode button and the unit turns itself on, the fan starts to spin up, then, after ~5 seconds, the unit turns itself off again.
  3. Pressing the Mode button a second time does nothing.
  4. It’s as if there was some residual power in the unit (the unit is plugged into its PSU and turned on), just enough for a 5-second power-up before it was drained.

Has anyone seen this happen before? The power button doesn’t turn the unit on but the “mode” button does, and only for a few seconds.

Kind regards,

Paul

Hello @PaulF,

Thank you for taking the time to ask your question here on the StarTech.com Community.

The SAT3540U3ER is a discontinued product but I have taken a few moments to review your details here and the symptoms. When checking our product information I found there is a firmware update that may be worth trying.

You can find the firmware update on the Drivers & Downloads section of the StarTech.com product page

SAT3540U3ER Drivers & Downloads

If this updates was not already applied, I would be curious if it is possible to apply it and test further.

Please let us know if this is helpful and we can certainly look into this further with you if the firmware does not resolve the issue.

Sincerely,

@DavidF