RN314 read only file system

Question

I've been using a RN314 for backup purposes for a bunch of years now and all of a sudden the filesystem is read only. As this is a backup system and the primary storage is still intact as well as the copy I'm sending to the cloud, I reformated the drives and recreated the volume. After about a week the same thing happened again. I have no idea where to start. I tried to attach the logfiles to the post, but the file upload only allows images and pdfs. Sharing it from onedrive instead.

https://1drv.ms/u/s!Ao2ngGbMNQkGuwkbYnX_t-ILu-xu?e=L3qmXG

StephenB · Answer

You shouldn't post log files publicly, so please unshare your log zip.
&nbsp;
There are btrfs errors in the file system.
May 25 00:43:06 nasbackup kernel: BTRFS error (device md127): parent transid verify failed on 3710532419584 wanted 17240 found 17882
May 25 00:43:06 nasbackup kernel: BTRFS error (device md127): parent transid verify failed on 3710532419584 wanted 17240 found 17882
May 25 00:43:06 nasbackup kernel: BTRFS warning (device md127): Skipping commit of aborted transaction.
May 25 00:43:06 nasbackup kernel: BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure
May 25 00:43:06 nasbackup kernel: BTRFS info (device md127): forced readonly
May 25 00:43:06 nasbackup kernel: BTRFS: error (device md127) in btrfs_drop_snapshot:9412: errno=-5 IO failure
May 25 00:43:06 nasbackup kernel: BTRFS info (device md127): delayed_refs has NO entry
I don't know what is causing them though.
&nbsp;
I am a bit confused on the reformatting statement, as there are some much older dates in the log zip. For instance, smart_history.log begins with
2016-04-28 19:04:09  TOSHIBA DT01ACA200 ...
Did you do a factory default?&nbsp; Or just recreate the data volume?
&nbsp;

scarygary71 · Answer

I had no idea there was sensitive information in the log files. I unshared the file.

I only recreated the data volume. I might have factory reset the nas a long time ago though. Probably years ago.

I've replaced a few drives over the years.

Sandshark · Answer

Your NAS is having trouble communicating with one or more of the drives. Are you seeing ATA errors recorded on any of them? Note that the drive often will record an ATA error even if the problem is with the NAS, so don't jump to the conclusion a drive is bad. That takes some more testing.

Step one would be to (with power off) pull and re-seat all drives, checking the integrity and cleanliness of the connectors as you do so. If the log doesn't point to a specific drive, doing the built-in drive test might.

StephenB · Answer

scarygary71&nbsp;wrote:
I only recreated the data volume.
&nbsp;

Ok, that makes sense then.
&nbsp;
The puzzle is figuring out what might be corrupting the file system.&nbsp; Two disks are old (~7 years) but they all look healthy.&nbsp;
This bit from kernel.log doesn't look good:
Apr 06 00:59:36 nasbackup kernel: INFO: task btrfs:28575 blocked for more than 1000 seconds.
Apr 06 00:59:36 nasbackup kernel:       Tainted: P           O    4.4.190.x86_64.1 #1
But something else clearly happened on 17 May, starting here:
May 17 02:27:55 nasbackup systemd[1]: systemd-journald.service: Main process exited, code=killed, status=6/ABRT
May 17 02:27:55 nasbackup systemd[1]: systemd-journald.service: Unit entered failed state....May 17 02:27:55 nasbackup systemd[1]: Starting Reboot...
Was this a manual reboot?&nbsp; The first btrfs error happened about 40 minutes later:
May 17 03:11:12 nasbackup kernel: BTRFS error (device md127): parent transid verify failed on 393904128 wanted 622897 found 625113
That is when the volume was set to read-only.
&nbsp;
It looks like the NAS is using volume encryption, and also that it is not protected by a UPS.&nbsp; Is that correct?
&nbsp;
scarygary71&nbsp;wrote:
I had no idea there was sensitive information in the log files. I unshared the file.&nbsp;

That is best.&nbsp; I can see the email address you are using for alerts.&nbsp; There is also some username leakage in some logs.&nbsp; I don't know what is in db.dump (never looked), but there could be more stuff in there.
&nbsp;
I will delete the download when we're done with this discussion about the logs (and of course won't re-share anything).

scarygary71 · Answer

Not entirely sure what happened on the 17th. Maybe a patch was applied? I think the NAS hung after the upgrade and someone on site had to pull the plug.If volume encryption is enabled, it's not by choice. I don't even know where to enable that. There's no UPS connected to the NAS, that's correct.&nbsp;&nbsp;

Forum Discussion

RN314 read only file system

10 Replies

Related Content

Orbi Systems Manual Factory Reset Process

Hard Drive Upgrade RN314 NAS

Rn314 update to 6.10.1 made volume to read only

RN314 problems after Readynas 6.10.7

RN314 and high ATA error count on 2 disks

NETGEAR Academy

ProSupport for Business