NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PRO4 Gone Read Only - BTRFS Errors
Pro4 running FW 6.10.7. Was stable for a number of years with 4 x 3TB RAID5. Free space dwindled to extremely low (think <1% but can't remember exactly). So a couple of months ago roughly I replaced 2x 3TB drives with 2x 6TB drives (system now 2x 3TB + 2x 6TB). Volumes synced all ok (I thought) and freespace 2.71TB of 10.9TB total (8.19TB data). No errors / alerts and all data accessible. Web GUI shows Healthy and volumes green. PDF and JPG files are accessible but Word / Excel files won't load.
I backup to another Readynas RN104 over rsync and backup jobs have been running - I've checked files accessible and appears "safe", ie. legitimate backup. To be safe I am now backing up the Shares to a brand new Seagate 8TB USB HDD.
However, have had a number of power cuts of recent months and not running a UPS. So there have been a number of reboots. Over last couple weeks, system becomes Read Only. I've downloaded logs and see the following respectively:
dmesg:
[Sun Apr 24 00:25:41 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 00:25:42 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 00:30:43 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 01:07:32 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 01:16:23 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 01:16:25 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 01:25:15 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 02:07:28 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 02:17:19 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 02:17:21 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 02:22:21 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 03:07:31 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 03:14:11 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 03:14:13 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 03:28:44 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 04:07:30 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 04:14:51 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 04:14:53 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 04:25:23 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:07:30 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:15:11 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:15:13 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:28:13 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:51:27 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:54:37 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:55:25 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 05:56:35 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 06:04:16 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 06:05:17 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 06:06:49 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 06:23:40 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 07:07:32 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 07:23:23 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 07:23:25 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 07:28:25 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 07:58:47 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:47 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:47 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:48 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:49 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:55 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:55 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:55 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:58:56 2022] TCP: out of memory -- consider tuning tcp_mem
[Sun Apr 24 07:59:01 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:04:02 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:07:30 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:15:21 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:15:23 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:23:33 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:44:40 2022] BTRFS error (device md126): Remounting read-write after error is not allowed
[Sun Apr 24 08:45:11 2022] BTRFS error (device md126): bdev /dev/md126 errs: wr 88, rd 100, flush 0, corrupt 0, gen 0system-mdjournal:
Apr 24 08:13:44 NAS-PRO connmand[2869]: ntp: adjust (slew): -0.000084 sec
Apr 24 08:15:21 NAS-PRO noflushd[2881]: Spinning down disk 4 (/dev/sdd).
Apr 24 08:15:21 NAS-PRO noflushd[2881]: Error: Unable to remount /dev/md126: Invalid argument
Apr 24 08:15:21 NAS-PRO kernel: BTRFS error (device md126): Remounting read-write after error is not allowed
Apr 24 08:15:23 NAS-PRO noflushd[2881]: Spindown of disk 4 (/dev/sdd) cancelled.
Apr 24 08:15:23 NAS-PRO noflushd[2881]: Error: Unable to remount /dev/md126: Invalid argument
Apr 24 08:15:23 NAS-PRO kernel: BTRFS error (device md126): Remounting read-write after error is not allowed
Apr 24 08:17:01 NAS-PRO CRON[24315]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 24 08:17:01 NAS-PRO CRON[24316]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 24 08:17:01 NAS-PRO CRON[24315]: pam_unix(cron:session): session closed for user root
Apr 24 08:21:12 NAS-PRO msmtpq[24388]: mail [ 1 ] [ 2022-04-17-18.01.01 ] from queue ; send failed ; msmtp rc = 77
Apr 24 08:21:19 NAS-PRO msmtpq[24679]: 14 more mails from queue failed to send with rc = 77
Apr 24 08:23:33 NAS-PRO noflushd[2881]: Spinning down disk 2 (/dev/sdb).
Apr 24 08:23:34 NAS-PRO noflushd[2881]: Error: Unable to remount /dev/md126: Invalid argument
Apr 24 08:23:34 NAS-PRO kernel: BTRFS error (device md126): Remounting read-write after error is not allowed
Apr 24 08:23:36 NAS-PRO noflushd[2881]: Spinning down disk 3 (/dev/sdc).
Apr 24 08:30:48 NAS-PRO connmand[2869]: ntp: adjust (slew): -0.000015 sec
Apr 24 08:35:19 NAS-PRO noflushd[2881]: Spinning down disk 1 (/dev/sda).
Apr 24 08:35:22 NAS-PRO noflushd[2881]: Spinning down disk 4 (/dev/sdd).
Apr 24 08:38:29 NAS-PRO noflushd[2881]: Spinning up disk 1 (/dev/sda) after 0:03:07.
Apr 24 08:42:30 NAS-PRO noflushd[2881]: Spinning up disk 4 (/dev/sdd) after 0:07:06.
Separately I see that notification emails have been failing to send but this is secondary issue to resolve vs main drive issue.
Is this scenario, just get backups confirmed and then factory reset?
5 Replies
No sure exactly what you mean by Volume Read only mode but yes I have previously re-booted it a number of times from when it was in read only mode and it came back with read/write access. This was before I realised the seriousness of the situation. Focused on ensuring backups before doing anything else right now.
Typically, the NAS is doing you a favor going into read-only mode so that no more damage can be done to an already damaged but still accessible volume before you complete a backup. And also typically, deleting and re-creating the volume (or a factory default, if you prefer) is the only assured way that the problem is 100% fixed. Been there, done that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
