Pegasus 2 R8 - Need Help

  • 164 Views
  • Last Post 4 weeks ago
Ryan Iltis posted this 4 weeks ago

I have a Pegasus 2 R8 that I am trying to get data from.  It disconnects consistently and has very slow copying that eventually bombs out - randomly reboots the whole machine. 

 

  • Started with a Mac Mini M1 - had Sonoma as the OS - I was able to copy from it and write data to it without any problem.  I updated the OS to Sequoia and that is when the problems started. 
  • I updated the firmware to the most current. 
  • I installed the Mac Silicon driver
  • I uninstalled the Mac Silicon driver and installed the standard Dext Driver.  
  • I have gone back to the previous OS Sonoma and used the Promise Utility to make sure that the device or raid array didn't have any issues.  (unit passes all tests)
  • I bought an old mac mini (intel chip) with monterey on it thinking I can use the old driver - but no luck.  

Here is my question - what am I missing.  Is there a utility that can tell me what is wrong.  Can anybody advise?

 

Is the firmware causing the problem? Is there a firmware I should use for Monterey.  Or is there a specific version of Mac Os and firmware combo that is the perfect set.

 

 

Order By: Standard | Latest | Votes
R P posted this 4 weeks ago

Hi Ryan,

I updated the OS to Sequoia and that is when the problems started.

Actually Apple Silicon Sequoia worked great up till 15.4 and 15.4.1 when some few customer reported unusual issues. Intel Sequoia has had no issues. We have not been able to reproduce any of these issues in the lab.

It should work fine from the Intel Mac, even with old firmware. If it does not, then there may be a chassis or power supply issue.

If it is a chassis issue, you can find a used chassis and move the drives over (make sure both devices are powered off) and the Volume should mount. You don't have to get a Pegasus2 chassis, a Pegasus3 or Pegasus32 chassis will also work.

You can often find a used chassis at EBay, amazon, or even Google Shopping. Some have found one at their local computer store.

Ryan Iltis posted this 4 weeks ago

Can you share with me the recommended driver and firmware for the drive.  I also haven't rulled out the cable as well?  Currently using the apple usbc to thunderbolt 2 conversion.  

R P posted this 4 weeks ago

Hi Ryan,

Intel Macs have a Pegasus driver builtin, Apple Silicon (M1/M2/M3/M4) Macs need a driver to be installed.

This Utiltity can update the firmware on a Pegasus1 or Pegasus2.

This is the fimware file for the latest Pegasus2 firmware.

Be aware that the firmware file is not a mac executable, you need to use the Promise Utility to do a firmware update on a Pegasus.

 

 

 

Ryan Iltis posted this 4 weeks ago

Are there any specific testing methods to rule out the chassis to see if the problem sits there vs. a compatibility of drivers?  I moved it back to sequia on my m1 mac mini.  Every few files I access I get the disconnection beep and then after a bit it reconnects.  I have considerable amount of data on this raid, and I don't see an easy way to get the data off with it in the current state.  So the only option is to isolate the chassis vs. the software.  

Ryan

R P posted this 4 weeks ago

Hi Ryan,

Are there any specific testing methods to rule out the chassis to see if the problem sits there vs. a compatibility of drivers? 

There is no driver compatibility issue.

I have considerable amount of data on this raid, and I don't see an easy way to get the data off with it in the current state.

The RAID set can be moved to another Pegasus chassis and the Volume will mount.

So the only option is to isolate the chassis vs. the software.  

The only software you need is to have the driver correctly installed.

We have a basic troubleshooting guide if that would help.

Ryan Iltis posted this 4 weeks ago

Ok I will gro through the basic trouble shooting you listed -- THANK YOU! .  In poking around I have noticed that I have a drive going bad (screen shot attached).  Could this be causing the lock ups or do you think this is still a chassis issue.  Meanwhile in the promise utility the system isn't reporting any errors (besides the bad sectors on drive 1)

 

R P posted this 4 weeks ago

Hi Ryan,

A bad disk can definately cause lockups, the entire RAID has to wait till that disk responds.

You might want to unseat that drive (if you have a RAID 5), pull it out an inch or so but leave it in the slot till you can get a replacement drive.

There's a documentary in here somewhere, "When good disks go bad". :-)

Ryan Iltis posted this 4 weeks ago

The second I pulled that drive out - it appears to have solved the problem.  Seriously - the amount of hours I have spent working on this.  :). 

 

Thank you for your patience. 

Ryan 

Search
Categories
Close