NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN214 file system read-only (again)
It seems I'm extremely unlucky with this device because this is not the first time a file system error appears (cf. https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/RN204-repeated-fil...
edkedk wrote:
Some weeks ago I replaced a disk that started to develop bad sectors.
Ok. And that resynced ok?
Perhaps enable ssh, and enter
# smartctl -x /dev/sda # smartctl -x /dev/sdb # smartctl -x /dev/sdc # smartctl -x /dev/sdd
and look for saved errors for the drives.
For example, something like this:
Error 12 [11] occurred at disk power-on lifetime: 36166 hours (1506 days + 22 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 0c 27 df 40 40 00 Error: UNC at LBA = 0x0c27df40 = 203939648 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 80 00 c8 00 00 0c 27 df 40 40 08 1d+08:15:46.204 READ FPDMA QUEUED 60 00 08 00 c0 00 01 06 34 36 98 40 08 1d+08:15:46.163 READ FPDMA QUEUED 60 00 80 00 b8 00 00 0c 27 e4 40 40 08 1d+08:15:46.146 READ FPDMA QUEUED 60 00 80 00 b0 00 00 0c 27 e9 40 40 08 1d+08:15:46.123 READ FPDMA QUEUED 60 00 80 00 a8 00 00 0c 27 ee 40 40 08 1d+08:15:46.094 READ FPDMA QUEUED
Yes, resync completed without any error.
Actually, the error I mentioned in the older thread I linked in the first post happened on the other RN214 device we have in the network...
The disk was replaced in the one this thread is about.
I have run the smartctl commands. On two disk there are 1 and 3 reallocated sectors. On sdd there is this error log:
Error 1 [0] occurred at disk power-on lifetime: 0 hours (0 days + 0 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 -- -- -- == -- == == == -- -- -- -- -- 84 -- 41 00 00 00 00 00 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 08 00 78 00 00 00 00 01 b8 40 08 00:00:32.826 READ FPDMA QUEUED 60 00 08 00 70 00 00 00 00 01 b0 40 08 00:00:32.826 READ FPDMA QUEUED 60 00 08 00 68 00 00 00 00 01 a8 40 08 00:00:32.825 READ FPDMA QUEUED 60 00 08 00 60 00 00 00 00 01 a0 40 08 00:00:32.825 READ FPDMA QUEUED 60 00 08 00 58 00 00 00 00 01 98 40 08 00:00:32.825 READ FPDMA QUEUED
edkedk wrote:
I have run the smartctl commands. On two disk there are 1 and 3 reallocated sectors. On sdd there is this error log:
Error 1 [0] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) Error: ICRC, ABRT at LBA = 0x00000000 = 0
It looks like that happened when the disk was initially powered up. Did you put it into the NAS right away, or did you connect it to a PC and test it first?
It's related to the communication between the NAS (or computer) and the drive, so it could simply be a poor connection when first plugged in. I don't think this error is concerning (and don't see how it would make your system read-only, since it happened before the drive was added to the array).
The other drives with the reallocated sectors might be part of the puzzle though, and probably should be tested.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
