Partially Corrupted External RAID Drive?

[lotzosushi]

Hey guys, the external RAID drive I've been using recently with my M1 Max MBP suddenly started stalling and hanging my computer when I try to transfer or read files from it. I set it up as brand new with this Mac and it's been working very well for a couple months since. I just ran First Aid in Disk Utility and it come back with this error, I'm not sure what it means. I've ran it a few times but it doesn't seem to have actually fixed anything. When I try to copy files onto the external it just gets stuck.

Can anyone help? I tried searching on Google but others that have talked about this problem seem to be relating to Time Machine snapshot errors but I don't use that...

For reference I'm on the latest version of Monterey.

 

[satcomer]

it told you what drive failed:

volume /dev/rdisk12s1

Just replace that failed drive!

 

[lotzosushi]

it told you what drive failed:

volume /dev/rdisk12s1

Just replace that failed drive!

It'll be difficult since I've got it set as a Raid 0 with 4 x 18TB drives. The thing is the files are still readable and I can open them, I just can't write to the drive anymore. That's why I'm not sure which one of the drives might be the culprit. I'm hoping it's still just a bug or drive error I can fix and not a complete drive failure.

 

[chabig]

The First Aid report you posted says the disk corruption was repaired successfully. But since you are still having problems, then something is probably wrong with the single disk drive or maybe your RAID controller. Chances are the disk is the culprit. I would expect your RAID box to identify the failing drive with an LED or something.

If one of your RAID drives fails, you'll lose all of the data on your RAID. Be prepared by making a backup!

 

[lotzosushi]

The First Aid report you posted says the disk corruption was repaired successfully. But since you are still having problems, then something is probably wrong with the single disk drive or maybe your RAID controller. Chances are the disk is the culprit. I would expect your RAID box to identify the failing drive with an LED or something.

If one of your RAID drives fails, you'll lose all of the data on your RAID. Be prepared by making a backup!

That's what confuses me, the RAID box doesn't show any signs of a failed drive. I can even read/open and copy files from the RAID onto my internal and other external drives. I only encounter the problem when trying to write to the RAID drive. I'll have to find another solution for backup as it's a 72TB raid and I don't have enough space anywhere to back up that much lol

I've even connected it to my older 16" Intel MBP and it still has the same problem, and exact same result when running First Aid in Disk Utility.

 

[jdb8167]

That's what confuses me, the RAID box doesn't show any signs of a failed drive. I can even read/open and copy files from the RAID onto my internal and other external drives. I only encounter the problem when trying to write to the RAID drive. I'll have to find another solution for backup as it's a 72TB raid and I don't have enough space anywhere to back up that much lol

I've even connected it to my older 16" Intel MBP and it still has the same problem, and exact same result when running First Aid in Disk Utility.

You shouldn’t ever use RAID0 on an array of that size. Especially without backup. You are likely about to lose whatever is stored on those drives.

 

[chabig]

I don't have enough space anywhere to back up that much lol

Yeah. That's a problem. But what is that data worth to you? Can you afford to lose 72GB?