SHR2 destabilized after DSM Upgrade

[Pomato]

Hi

I have an 1819+. Recently, I manually upgrade the OS to 7.3. Ever since then, everyday after 12:00 midnight, the NAS ran script (I think it’s a Synology maintainence script) which set my RAID to read only. It seems peculiar because the RAID always recoversan after a reboot, and Storage Manager has never complained of a bad hard disk. I am running Synology ECC Dram so it likely not an ecc corruption issue.

I am running on Ironwolf Pro hard drive but not Synology hard drive. To my understanding the newer DsM OS should accept non Synology disk.

At this stage I am thinking of rolling back DSM to an older release, or changing hard dos but I am not sure on the former how to do that, and on the later how to pin point a disk to replace or remove to fire the problem.

Help appreciated.

 

[Rusty]

Welcome!

Ever since then, everyday after 12:00 midnight, the NAS ran a script and set my EAID to read only

That does not seem right. What script are you talking about?

At this stage I am thinking of rolling back DSM to an older release

There is no official rollback of DSM. There was a an unofficial process but it is semi destructive, and should be used only as a last resort. There is no official support for this procedure as well.

 

[Pomato]

thanks for help.
I am not sure what the script is but I think it’s a Synology maintenance script running on cron, as it specifically activates at mid night, reports it runs into issue (but without specifics) and turn the RAID to read only mode. A reboot will repair the volume to read -write but the problem recurs again at the next 0:00

It would likely be a maintenance script to check the integrity of the volume. The problem is there is no indication of error from StorageManger and I had run SMART diagnostic on them without problem.

I tried running Scrubbing - but bec I have a large volume about 96 TB scrubbing always spans over 24 hours and stopped when mid night comes.