Data Scrubbing Issue

[3ManIT]

My DS1621 has DSM 7.2.2-72806. Not long after updating, I got an alert that my volume1 (only one I have) was Read Only. I had to force the nas to restart. After it booted, the drives are healthy and the volume is fine. A few hours later it was back to read only. Tried running the data scrubbing manually but it does not complete. I found some corrupted data in a MS365 backup location. Deleted that. Ran scrubbing again but it still won't complete. The system tells me to check the drives and volume but they're all good. Running Raid 5. Anyone have an idea of what might be happening or where I can look next?

 

[Coop777]

Did you check log center for any further details? My next steps would be that and then to power down the NAS and test each hard drive by connecting it to a MAC or PC and run vendor drive diagnostics as a secondary check for possible failure(s).

 

[3ManIT]

Fascinatingly enough, I pull one of the four drives out of its bay. Waited about a minute, then plugged it back into the bay. The nas went nuts! I had to pull the power cord to get it to shut down. Definitely not normal behavior. It booted just fine but complained that I was missing a drive. It saw that the drive was available but didn't automatically add it to the array. So, I added it manually and the nas told me this drive was from a different volume. I replied that I did not care and yes, please delete the data on that drive and add it to the array. It's in the process of doing that now. I'll follow up to see what happens afterward.

I like your idea, and if I have trouble after the resync, that will be my next step.

 

[fredbert]

Just noticed your thread. I posted this in thread 'Version: 7.2.2-72806 UP1'…
DSM Update - Version: 7.2.2-72806 UP1

There sounds to be some similarities.

 

[3ManIT]

Followed the link. Thanks. All of these troubles did start after updating.

 

[3ManIT]

Synology support helped look through my logs. Apparently I had a bad drive and also unrecoverable corrupted data. Had to remove and recreate the volume. Seems to be fine now.

 

[DSfuchs]

I had the same for myself, but we have to ask ourselves: Why do we even have a Synology NAS?
The hardware and support cannot handle it. Perhaps it’s due to the outdated kernel or Btrfs versions Synology provides. Otherwise, it’s a design flaw.
To rule all this out, I’m now running ZFS on DSM or DSM on ZFS so I don’t lose everything again.

 

[DSfuchs]

Did you check log center for any further details? My next steps would be that and then to power down the NAS and test each hard drive by connecting it to a MAC or PC and run vendor drive diagnostics as a secondary check for possible failure(s).

In my case, it was Btrfs checksum errors in a few files that could be deleted. Even so, it turned into a total disaster.

 

[Coop777]

Fascinatingly enough, I pull one of the four drives out of its bay. Waited about a minute, then plugged it back into the bay. The nas went nuts! I had to pull the power cord to get it to shut down. Definitely not normal behavior. It booted just fine but complained that I was missing a drive. It saw that the drive was available but didn't automatically add it to the array. So, I added it manually and the nas told me this drive was from a different volume. I replied that I did not care and yes, please delete the data on that drive and add it to the array. It's in the process of doing that now. I'll follow up to see what happens afterward.

I like your idea, and if I have trouble after the resync, that will be my next step.

If you pulled the drive while the NAS was powered on, removal of it immediately put the array into degraded status and that's why "it went nuts!" powering it down before drive removal would have prevented that....