This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I upgraded to the current relase 6.10.1 and after reboot I recived the message:Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.
Has anyone else experienced this?
Is the only way to recitfy this issue is to default the box back to factory and rebuild the raid?
Can I rebuild the raid with out having to factory the unit?
So it looks like disk 3 is the problem, is it possible to just replace the disk and let the raid rebuilt itself? And when it's done will it become writeable once again?
Normally a failed disk won't result in a read-only volume - so I'm not sure if replacing the disk is enough. You could try booting up without disk 3, and see if volume still ends up read-only. If it doesn't, then hot-insert the replacement disk.
I upgraded to the current relase 6.10.1 and after reboot I recived the message:Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.
Begin by backing up your data. Don't try to figure it out until that's taken care of.
Re: Rn314 update to 6.10.1 made volume to read only
I am not so worried about the data as this box is a DR box and not our primary NAS so I can retrieve it from our off site facility and default it and rebuild it.
Thanks for the log info. I found this in the Kernel log.
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS error (device md127): parent transid verify failed on 304545792 wanted 749219 found 773951 May 29 10:12:17 matrix-nas-rmt kernel: BTRFS error (device md127): parent transid verify failed on 304545792 wanted 749219 found 773951 May 29 10:12:17 matrix-nas-rmt kernel: BTRFS warning (device md127): Skipping commit of aborted transaction. May 29 10:12:17 matrix-nas-rmt kernel: BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure May 29 10:12:17 matrix-nas-rmt kernel: BTRFS info (device md127): forced readonly May 29 10:12:17 matrix-nas-rmt kernel: BTRFS info (device md127): delayed_refs has NO entry May 29 10:12:17 matrix-nas-rmt kernel: VFS:Filesystem freeze failed May 29 10:12:19 matrix-nas-rmt kernel: BTRFS error (device md127): Remounting read-write after error is not allowed
Re: Rn314 update to 6.10.1 made volume to read only
One easy thing to do is look in disk_info.log in the log zip file. That will give you the SMART statistics for each disk.
You could also enable ssh, and look for disk errors by entering
# smartctl -x /dev/sda
(repeating for each disk you have).
That will give more information than is in disk_info.log. If there is a section for one of the disks that includes stuff like
Error XX [YY] occurred at disk power-on lifetime: ZZ hours (ZZ days + ZZ hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
then take a closer look - especially if the time is recent.
Re: Rn314 update to 6.10.1 made volume to read only
I accessed the disks through ssh and found disk 3 is having the issue, is it possible to just replace the disk and let the raid rebuilt itself?
Error 5 [4] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 bb 50 40 00 Error: UNC at LBA = 0x09e7bb50 = 16618 1712
Error 4 [3] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 bb 50 40 00 Error: UNC at LBA = 0x09e7bb50 = 16618 1712
Error 3 [2] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 a5 f0 40 00 Error: WP at LBA = 0x09e7a5f0 = 166176 240
Error 2 [1] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 a5 f0 40 00 Error: UNC at LBA = 0x09e7a5f0 = 16617 6240
Error 1 [0] occurred at disk power-on lifetime: 18710 hours (779 days + 14 hours ) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 07 c6 67 e0 40 00 Error: UNC at LBA = 0x07c667e0 = 13044 3232
Re: Rn314 update to 6.10.1 made volume to read only
So it looks like disk 3 is the problem, is it possible to just replace the disk and let the raid rebuilt itself? And when it's done will it become writeable once again?
Error 5 [4] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 bb 50 40 00 Error: UNC at LBA = 0x09e7bb50 = 16618 1712
Error 4 [3] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 bb 50 40 00 Error: UNC at LBA = 0x09e7bb50 = 16618 1712
Error 3 [2] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 a5 f0 40 00 Error: WP at LBA = 0x09e7a5f0 = 166176 240
Error 2 [1] occurred at disk power-on lifetime: 24251 hours (1010 days + 11 hour s) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 e7 a5 f0 40 00 Error: UNC at LBA = 0x09e7a5f0 = 16617 6240
Error 1 [0] occurred at disk power-on lifetime: 18710 hours (779 days + 14 hours ) When the command that caused the error occurred, the device was active or idle .
After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 07 c6 67 e0 40 00 Error: UNC at LBA = 0x07c667e0 = 13044 3232
So it looks like disk 3 is the problem, is it possible to just replace the disk and let the raid rebuilt itself? And when it's done will it become writeable once again?
Normally a failed disk won't result in a read-only volume - so I'm not sure if replacing the disk is enough. You could try booting up without disk 3, and see if volume still ends up read-only. If it doesn't, then hot-insert the replacement disk.
