NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Lost access to ReadyNAS 214
Hi everyone, I have a grave problem with my ReadyNAS 214. I'm working with this device several years now. I have the latest firmware on it (6.10.3) and everything seemed to be working fine up until ...
Wolf54-2 wrote:
Disk 1, the oldest and smallest (Hitachi, 2TB)
Error 1150 [1] occurred at disk power-on lifetime: 17934 hours (747 days + 6 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 -- 51 00 71 00 00 00 a0 7f cf 00 00 Error: ICRC, ABRT 113 sectors at LBA = 0x00a07fcf = 10518479That's the only disk that reports any sectors and errors.
Could that one disk inhibit the network access to the device?
A followup here - you should check the current power-on hours, and see how long ago this error occured.
Are you seeing other issues with this drive (reallocated sectors, etc)?
If the error happened before the problem began, then it's probably not the cause. I'd also expect to see more than one occurance.
But generally - disk problems can create problems with access, because retries and error processing can load down the system.
Maybe try journalctl -r
If you want to search it, you could use something like
# journalctl -r --no-pager | grep -i error
-k might also be useful (only showing kernel entries).
Wolf54-2 wrote:
I have a spare, new 8TB disk on the shelf. Would it be wise to swap out that small, old Hitachi disk.
Replacing one disk should trigger a data recovery, right? Would that also restore network access?I wouldn't do that yet. If the problem isn't the disk, it won't help (and could complicate things).
One option is to go with brute-force - doing a factory reset, reconfiguring the NAS, and restoring data from backup. While that might end up the only way to resolve it, it'd be best to figure out what is going on.
This is what I get:
/dev/sda: Pending Defects log (GP Log 0x0c) not supported
/dev/sdb:
# smartctl -l defects /dev/sda
Pending Defects log (GP Log 0x0c) not supported
# smartctl -l defects /dev/sdb
Pending Defects log (GP Log 0x0c)
No Defects Logged
# smartctl -l defects /dev/sdc
Pending Defects log (GP Log 0x0c)
No Defects Logged
But from the comprehensive log (smartctl -x) I get this output:
Disk 1, the oldest and smallest (Hitachi, 2TB)
Error 1150 [1] occurred at disk power-on lifetime: 17934 hours (747 days + 6 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 -- 51 00 71 00 00 00 a0 7f cf 00 00 Error: ICRC, ABRT 113 sectors at LBA = 0x00a07fcf = 10518479
That's the only disk that reports any sectors and errors.
I searched the output of all disks (smartctl -x) for 'timeout', but did not find anything about timeouts.
Could that one disk inhibit the network access to the device?
I have a spare, new 8TB disk on the shelf. Would it be wise to swap out that small, old Hitachi disk.
Replacing one disk should trigger a data recovery, right? Would that also restore network access?
I could also zip up the output and attach it here, if that helps.
Oh, btw, thanks for all your help. Very much appreciated.
Wolf54-2 wrote:
Disk 1, the oldest and smallest (Hitachi, 2TB)
Error 1150 [1] occurred at disk power-on lifetime: 17934 hours (747 days + 6 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 -- 51 00 71 00 00 00 a0 7f cf 00 00 Error: ICRC, ABRT 113 sectors at LBA = 0x00a07fcf = 10518479
That's the only disk that reports any sectors and errors.
Could that one disk inhibit the network access to the device?
A followup here - you should check the current power-on hours, and see how long ago this error occured.
Are you seeing other issues with this drive (reallocated sectors, etc)?
If the error happened before the problem began, then it's probably not the cause. I'd also expect to see more than one occurance.
But generally - disk problems can create problems with access, because retries and error processing can load down the system.
Maybe try journalctl -r
If you want to search it, you could use something like
# journalctl -r --no-pager | grep -i error
-k might also be useful (only showing kernel entries).
Wolf54-2 wrote:
I have a spare, new 8TB disk on the shelf. Would it be wise to swap out that small, old Hitachi disk.
Replacing one disk should trigger a data recovery, right? Would that also restore network access?
I wouldn't do that yet. If the problem isn't the disk, it won't help (and could complicate things).
One option is to go with brute-force - doing a factory reset, reconfiguring the NAS, and restoring data from backup. While that might end up the only way to resolve it, it'd be best to figure out what is going on.
I was able to safe all the information off that device. Will try to run a factory reset and see if it recovers.
Thanks for all your help.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
