Pegasus2 R6 forced in "Read Only Mode"

  • 17 Views
  • Last Post yesterday
Florian Singer posted this 2 days ago

I recently had an external SSD (Samsung T7) failure that caused several kernel panics on my MacBook Pro. During that time, macOS set my Pegasus RAID volume to read-only.

 

I’m using a Pegasus2 R6 connected via Thunderbolt to an Apple Silicon MacBook Pro (macOS 15.x). I checked the SMART logs for all drives and found that the disk in Slot 4 was still online but showed reallocated/unstable sectors, so I treated it as failing.

 

What I did:

 

  • Made a full backup of the Pegasus volume to an external HDD

  • Hot-swapped the drive in Slot 4 (without powering down the Pegasus)

  • Inserted a new identical drive, set it to Unconfigured and manually rebuilt the disk array

  • Rebuild finished successfully, redundancy check and currently running media patrol

  • In Promise Utility everything is green and all drives report as healthy

 

 

However, the RAID is still read-only in macOS, and on every boot I get a message that macOS tried to repair the volume, failed, and therefore mounted it read-only. Disk Utility First Aid on the Pegasus volume also still fails.

 

My questions:

 

  • Is there any Pegasus-side flag or state I need to clear to get out of read-only, or is this purely a filesystem issue on the macOS side now?

  • Given that I have a full backup: is the recommended / safest solution to delete the logical drive, recreate and reformat the array, then restore from backup?

 

 

 

Any guidance on the proper next step would be very much appreciated.

Order By: Standard | Latest | Votes
R P posted this 2 days ago

Hi Florian,

Is there any Pegasus-side flag or state I need to clear to get out of read-only, or is this purely a filesystem issue on the macOS side now?

This is correct, at this point it's a filesystem issue and not a RAID issue.

Given that I have a full backup: is the recommended / safest solution to delete the logical drive, recreate and reformat the array, then restore from backup?

If you have already rebuilt the LD, there is no added benefit to deleting and recreating the array, you can just put a new filesystem on the RAID.

I'm not sure disk utility will put a new filesystem on a readonly volume, so you might want to do a quick init on the LUN from the background activities in the upper right hand corner of the Promise Utility then use the Disk Utility erase option to put a new HFS+ filesystem on the LUN. Do not use the APFS filesystem as it is not designed for spinning disks.

 

Florian Singer posted this yesterday

Can I just put a new file system on the RAID without deleting all the files? In theory I have an backup, but I made that after the "Kernel Panic" Event, so in best case szenario I would love to not having to rely on that Backup drive. 

R P posted this yesterday

Hi Florian,

Can I just put a new file system on the RAID without deleting all the files?

There is a reason Apple calls the option to put a new filesystem on a storage device Erase, it will erase any and all files. 

If you want to repair the filesystem try the Disk Utility First Aid option. If that does not work, and it probably won't work, your best bet is a program called DiskWarrior. This is not a free utility but it's your best bet to repair the filesystem.

Search
Categories
Close