I have a Pegasus2 R4 with 4 drives. Two of them are passthrough and they work fine. The other two drives were setup a RAID1 (mirroring) using the Promise utility. The volume has stopped showing up. Even more strangely, with the two drives in the enclosure, the Promise utility hangs (beach ball of death). If I remove the drives, the utility is able to see the enclosure and the other two drives.
In the old days with SCSI drives, I recall seeing this type of thing when errors from a disk on a shared bus would cause chaos with all devices on the chain. These are SATA drives, however.
I've read through a number of posts. Here's what I've tried:
- Made sure the latest firmware is installed on the array
- Installed the Promise driver for macOS
- Tried with just one of the two RAID1 drives installed (it's mirrored, so each drive has a complete copy)
The CLI shows the array (drives 1 and 4), even though it's marked 4 as dead.
PdId Model Type Capacity Location OpStatus ConfigStatus
1 WDC WD30EFRX SATA HDD 3TB Encl1 Slot1 OK Array1 No.0
2 ST31000528AS SATA HDD 1TB Encl1 Slot2 OK PassThru
3 ST1000DM003- SATA HDD 1TB Encl1 Slot3 OK PassThru
4 WDC WD30EFRX SATA HDD 3TB Encl1 Slot4 Dead Array1 No.1
Also odd is that the volume appears to have mounted (the name doesn't normally have a "2" appended), though any attempts to access that volume just hang. It shows in the CLI but not on the desktop.
% df -h|grep RAID
/dev/disk7s2 2.7Ti 2.6Ti 179Gi 94% 421796 4294545483 0% /Volumes/RAID Drive 2
Info "diskutil info" also shows up
% diskutil info /dev/disk7
Device Identifier: disk7
Device Node: /dev/disk7
Part of Whole: disk7
Device / Media Name: Pegasus2 R4
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Hardware AES Support: No
How do I get to the data?