Pegasus 2R6 just powering down

  • 91 Views
  • Last Post 17 January 2023
John Doak posted this 17 January 2023

Well, this is going to be long and convoloted.  

The basics:

My R6 powers up, reads the drives, turns blue, 3 seconds later turns orange and shuts down.

If you remove all the drives and the thunderbolt cable, same deal.

It was working fine, but I just got a new mac studio and decided I'd migrate it from my old mac trashcan.

First thing was I did a copy over a local network connection using the finder. But my mac studio ended up rebooting.  No idea why, this is probably a separate issue that I will need to address.

I decided I'd rather rsync with both drive systems attached to the mac studio.

25 system reboots later, mutliple promise utiility updates, updating the firmware to the lastest, updating the userspace and kernel drives, + rebooting the promise raid and I got it to mount the pegasus.

Started to do a rsync from the pegasus to the drive storage, and it crashed again.  Now at this point, I suspect something is wrong with the studio, maybe the thunderbolt subsystem.  

However, after that, where before i could mount the promise on either machine, now it won't stay turned on.  The promise just shuts off after about 3 seconds after the light turns blue.  

What do I do?

Order By: Standard | Latest | Votes
R P posted this 17 January 2023

Hi John,

From the details posted, there is a good chance of a power supply issue.

A Thunderbolt 1 or 2 Pegasus should power on when the power cable is connected and it should stay on until directed to sleep by the MAC.

John Doak posted this 17 January 2023

 Hey RP,

The only thing that makes me suspect something else is that it goes orange/blue/orange off.  But it might be indeed what you say.  And it is suspicious that a misbehaving mac studio would short the power supply, but then again it could be all coincidence.

So if my power supply is bad, what are my choices here?  Buy a replacement power supply from you guys (if you have such a thing for pegasus 2 R6) or buy a newer version of R6 (that would support the drives from the pegasus 2 R6)?  

R P posted this 17 January 2023

Hi John,

It's difficult to do a root cause in this fashion. Lets dig deeper...

However, after that, where before i could mount the promise on either machine, now it won't stay turned on.  The promise just shuts off after about 3 seconds after the light turns blue. 

If you just plug in the Pegasus 2 (power cord only) does it boot and stay on? Or does it shut down shortly?

Or does it shut down only when plugged into the MAC?

Does it shut down when connected to the old MAC mentioned?

The Pegasus2 is long EOL and we have no parts available. But other posters have looked up the partnumber on the power supply and found a replacement somwhere.

Can you verify the driver used? Try these two commands...

promise@promises-Mac-mini ~ % kextstat | grep -i stex
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
promise@promises-Mac-mini ~ % systemextensionsctl list | grep -i promise
*       *       268CCUR4WN      com.promise.driverkit.pegasus (21.1.0/1)
                                           com.promise.driverkit.pegasus   [activated enabled]
promise@promises-Mac-mini ~ %

Only one command should return results. In the case above the kextstat command returned nothing, there is no kernel space driver (kext) loaded. The systemextensionsctl command tells us that the user space driver version 21.1.0/1 is loaded. If both return commands nothing, then there is no driver loaded.

John Doak posted this 17 January 2023

So the promise, no matter what, basically powers up, light turns blue and the yellow, then off.  It doesn't matter what its plugged into or not plugged into.  It doesn't matter if the drives are in or not.  

 

Different systems have different drivers:

Studio:

kextstat | grep -i stex

Executing: /usr/bin/kmutil showloaded

 

No variant specified, falling back to release

 

systemextensionsctl list | grep -i promise

 

* * 268CCUR4WN com.promise.driverkit.pegasus (21.1.0/1) com.promise.driverkit.pegasus [activated enabled]

 

System information shows PromiseSTEX 6.2.13 and 6.2.17.  Neither are loaded, but I also don't have the promise connected any longer to that one.

 

On the old mac, neighter of those show anything.  However, system information show PromiseSTEXT of 6.2.13 and 6.2.9

 

I can find a power supply if I need to.  Are the new crop of arrays compatible with the striping formats from my R6?  Could I just buy a new enclosure, throw in the drives and be back in business?

 

Btw, thanks for taking the time.  I know messing with older stuff is a pain.  My plan in the long run was to end up getting another one of these with newer thunderbolt that could store my slower moving data (but have a lot more capacity).  So if I need to jump on that, then it might be the way to go.

 

R P posted this 17 January 2023

Hi John,

So the promise, no matter what, basically powers up, light turns blue and the yellow, then off.  It doesn't matter what its plugged into or not plugged into.  It doesn't matter if the drives are in or not. 

This would seem to indicate a hardware issue, which are usually power supply issues.

Are the new crop of arrays compatible with the striping formats from my R6?  Could I just buy a new enclosure, throw in the drives and be back in business?

Yes, the newer systems should have no trouble reading drives from older Pegasus units. But Promise does not have Pegasus SKUs without drives.

My plan in the long run was to end up getting another one of these with newer thunderbolt that could store my slower moving data (but have a lot more capacity).  So if I need to jump on that, then it might be the way to go.

FYI, there is a Pegasus32 SKU with (8) 14TB drives for 112TB of raw storage (98TB in RAID5).

Search
Categories
Close