Volume suddenly read-only - Stripe Volumes

RE: Volume suddenly read-only

SoftRAID Support — Wed, 27 Jul 2022 18:15:38 +0000

I would "report to Apple", and look at the top line of the kernel panic. If it says "DART" in the top two lines, it is the bug that Apple is fixing in Ventura.

In which case, most all cases are resolved by creating the volume with 64k Stripe unit sizes.

It does appear that macOS 13, Ventura beta 3 fixes this issue permanently.

RE: Volume suddenly read-only

FdrBrian — Wed, 27 Jul 2022 16:46:59 +0000

@softraid-support I'm not sure how frequent the crashes would be because I've only transferred data a few times in large chunks, so I cannot know if something is being unreliable.

I will have to find a way to backup the data and re-format again.

What is the most reliable configuration for Thunderbay 8 64TB? I cannot continue to do this as my data keeps growing. ☹️

RE: Volume suddenly read-only

SoftRAID Support — Wed, 27 Jul 2022 05:47:03 +0000

@fdrbrian

You are correct, Disk Warrior is both HFS only and needs to run on intel and Big Sur or older. You could move a volume to an older computer to run it.

Yes you need to restore from backup. There are repair tools for exFat on windows, but I don't know if they would work on a macOS volume. So repairing the volume is difficult to perhaps impossible.

I wonder why you are getting frequent damage on your volume directories. Are you getting a lot of crashes?

RE: Volume suddenly read-only

FdrBrian — Tue, 26 Jul 2022 22:16:20 +0000

Hello,

I'm having this issue as well. It happened before with my HFS+ RAID, so I thought that switching to a different format would help, so I moved the data off and reformatted to exFAT RAID 5 before moving the data back and everything was fine until today.

Today, I moved some data onto ThunderBay and when I came back the MacBook had restarted due to a panic and ThunderBay is now in read-only mode. I am currently doing a manual verify on all disks to see if perhaps there are bad sectors. This surprises me because this ThunderBay 8 is relatively brand new and barely has had any use whatsoever. There shouldn't be any bad drives this early on.

I checked to see if DiskWarrior would help, but it looks like it's for HFS volumes and M1 Macs are not supported yet.

ThunderBay 8 64TB, RAID 5, exFAT

MacBook Pro 16 M1

Mac OS 12.4

Volume suddenly read-only

SoftRAID Support — Mon, 04 Feb 2019 05:36:24 +0000

yes, probably. email it to support at softraid

Volume suddenly read-only

Mark Alexander — Mon, 04 Feb 2019 03:20:36 +0000

Would it help to provide a SoftRAID support file? If yes how do I provide? Thanks

Volume suddenly read-only

SoftRAID Support — Mon, 04 Feb 2019 00:58:36 +0000

I usually have the advantage of looking at a SoftRAID support file before replying. If all the errors occurred during the Disk Warrior rebuild, then it could just have been the volume pointing to illegal locations for data, where the disks error and SoftRAID logs them. You can certainly erase the Time Machine volume (with SoftRAID) and the RAID will reset itself. Perhaps all you really need to do is pay attention for any additional problems. Disk Warrior is good to run monthly or so, or after any crash/power loss, etc.

Volume suddenly read-only

Mark Alexander — Sun, 03 Feb 2019 17:57:12 +0000

Thank you for reply. Ok, so as I understand it I would need to certify each disk? In doing so SoftRAID reads / writes to each disk, thus would lose all data. Let me see if I got this right that I should proceed simply to certify and then would have to rebuild all assuming disks are ok. However, The issue is that just one volumes shows the errors but each of 4 disks the shows I/O errors after the DiskWarrior rebuild. After all the running of DiskWarrior the SoftRAID log then last showed: Feb 2 18:59:16 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test. I see two alternative options for next course of action to perhaps isolate the long term problem: Option A) (1) Erase the degraded failed volume and re-run DiskWarrior to see if it was all started by the initial Read Only problem with Time Machine which I understand is a fairly common problem (2) Create new Time Machine Volume, Run DiskWarrior and start all over Time Machine process with OS X (3) With stability - take care to back up each volume with Carbon Copy Cloner and do 2 pass certify to ensure disks are ok and if so rebuild each volume (4) would you recommend I run DiskWarrior directory tests / rebuild before or after any of these steps? Option B) (1) I will first back up all the Volumes EXCEPT the Time Machine which I can rebuild once system is running. I’m not so worried about that. (2) Then I would do 2 pass certify. If disks are OK then I would start over again coping the data from backup to each new volume accordingly making fresh back up with Carbon Copy Cloner prior and then rebuilding with CCC back to the certified disks and volumes respectively. (3) would you recommend I run DiskWarrior directory tests / rebuild before or after any of these steps? Appreciate the assistance - I know just enough to be dangerous but not enough to be sure what is right path :-)

Volume suddenly read-only

SoftRAID Support — Sun, 03 Feb 2019 17:27:21 +0000

Disk Read errors when they involve actual sectors (not just "sector 0, where the disk may be unavailable), are likely failure modes from the disk. I would take the time to do a 2 pass certify on this disk. the "read only" issue is a volume directory problem. That is most likely unrelated. Same with the Disk Warrior inability to rebuild, if you get that again, just restart and try again. Some disk errors are OS to volume communication errors, ie, the volume may point to non-existent locations. In this case, it is a point nearly 5TB into the disk. that would be a hardware issue with the disk and needs to be investigated.

Volume suddenly read-only

Mark Alexander — Sun, 03 Feb 2019 14:46:48 +0000

Further, here is log entries for past few days: Jan 28 04:12:09 - SoftRAID Monitor: Starting SMART test on all disks which support SMART. Jan 28 04:12:14 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test. Jan 29 13:52:36 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test. Jan 29 19:54:25 - SoftRAID Monitor: Finished uploading SMART disk statistics to server. Jan 29 19:54:26 - SoftRAID Monitor: Finished uploading anonymous usage statistics to server. Jan 30 14:27:25 - SoftRAID Monitor: Starting SMART test on all disks which support SMART. Jan 30 14:27:25 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test. Feb 1 08:00:14 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test. Feb 2 15:18:56 - SoftRAID Driver: The SoftRAID volume "MBP Backup" (disk14) encountered an error (E00002C1). A program attempted to read or write to a volume which was not open. Feb 2 15:18:57 - SoftRAID Driver: The SoftRAID volume "Misc" (disk11) encountered an error (E00002C1). A program attempted to read or write to a volume which was not open. Feb 2 15:18:57 - SoftRAID Driver: The SoftRAID volume "iTunes" (disk13) encountered an error (E00002C1). A program attempted to read or write to a volume which was not open. Feb 2 15:18:57 - SoftRAID Driver: The SoftRAID volume "Media" (disk15) encountered an error (E00002C1). A program attempted to read or write to a volume which was not open. Feb 2 15:18:57 - SoftRAID Driver: The SoftRAID volume "Images" (disk12) encountered an error (E00002C1). A program attempted to read or write to a volume which was not open. Feb 2 18:21:27 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a write error (E00002CD). The disk (disk2, SoftRAID ID: 07476EE9AF055E00) was unable to write sectors. The error occurred at volume offset 4847757901824 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:27 - SoftRAID Driver: A disk (disk2, SoftRAID ID: 07476EE9AF055E00) for the SoftRAID volume "Time Machine" (disk16) encountered multiple read or write errors. This disk has been marked "failed" and will no longer be used for when reading volume data. Feb 2 18:21:27 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a write error (E00002CD). The disk (disk2, SoftRAID ID: 07476EE9AF055E00) was unable to write sectors. The error occurred at volume offset 4847758426112 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:27 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a write error (E00002CD). The disk (disk3, SoftRAID ID: 07476EE9DEB106C0) was unable to write sectors. The error occurred at volume offset 4847758426112 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:27 - SoftRAID Driver: A disk (disk3, SoftRAID ID: 07476EE9DEB106C0) for the SoftRAID volume "Time Machine" (disk16) encountered multiple read or write errors. This disk has been marked "failed" and will no longer be used for when reading volume data. Feb 2 18:21:27 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) has encountered 2 or more read/write errors in the past 24 hours. SoftRAID will stop reporting read/write errors from this disk for the next 24 hours to prevent system log files from filling up. This disk (disk2, SoftRAID ID: 07476EE9AF055E00) should be replaced. Feb 2 18:21:27 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a read error (E00002CD). The disk (disk3, SoftRAID ID: 07476EE9DEB106C0) was unable to read sectors. The error occurred at volume offset 4847758426112 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:28 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) has encountered 2 or more read/write errors in the past 24 hours. SoftRAID will stop reporting read/write errors from this disk for the next 24 hours to prevent system log files from filling up. This disk (disk3, SoftRAID ID: 07476EE9DEB106C0) should be replaced. Feb 2 18:21:28 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a write error (E00002CD). The disk (disk4, SoftRAID ID: 07476EE9AEFD0D40) was unable to write sectors. The error occurred at volume offset 4847763406848 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:28 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a write error (E00002CD). The disk (disk1, SoftRAID ID: 07476EE9AEFBEC00) was unable to write sectors. The error occurred at volume offset 4847763406848 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:28 - SoftRAID Driver: A disk (disk4, SoftRAID ID: 07476EE9AEFD0D40) for the SoftRAID volume "Time Machine" (disk16) encountered multiple read or write errors. This disk has been marked "failed" and will no longer be used for when reading volume data. Feb 2 18:21:28 - SoftRAID Driver: A disk (disk1, SoftRAID ID: 07476EE9AEFBEC00) for the SoftRAID volume "Time Machine" (disk16) encountered multiple read or write errors. This disk has been marked "failed" and will no longer be used for when reading volume data. Feb 2 18:21:28 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a read error (E00002CD). The disk (disk4, SoftRAID ID: 07476EE9AEFD0D40) was unable to read sectors. The error occurred at volume offset 4847763406848 (i/o block size 262144). This disk should be replaced. Feb 2 18:21:28 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) encountered a read error (E00002CD). The disk (disk1, SoftRAID ID: 07476EE9AEFBEC00) was unable to read sectors. The error occurred at volume offset 4847763406848 (i/o block size 262144). This disk should be replaced. Feb 2 18:25:41 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) has encountered 2 or more read/write errors in the past 24 hours. SoftRAID will stop reporting read/write errors from this disk for the next 24 hours to prevent system log files from filling up. This disk (disk4, SoftRAID ID: 07476EE9AEFD0D40) should be replaced. Feb 2 18:25:41 - SoftRAID Driver: A disk for the volume "Time Machine" (disk16) has encountered 2 or more read/write errors in the past 24 hours. SoftRAID will stop reporting read/write errors from this disk for the next 24 hours to prevent system log files from filling up. This disk (disk1, SoftRAID ID: 07476EE9AEFBEC00) should be replaced. Feb 2 18:59:16 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test. Seems to have conflicting entries but not sure how best to read. Initial problems was the "Read Only" problem for "Time Machine" volume. Perhaps isolated to the volume or do all drives need to be replaced? Since last test showed all drives ok perhaps just a problem with the volume, if so how best to fix? Hope the readers of the support forum can make sense of this and I'm happy to provide additional data if helpful to resolution. Kind regards