NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
briskik
Jul 07, 2019Aspirant
ReadyNas 104 Disk Errors
I have had a ReadyNas 104 for several years and it has worked really well. Last week I logged into it, and saw disk errors in the logs and have monitored it closesly over the past few days. My disk e...
briskik
Jul 07, 2019Aspirant
Thanks for the quick reply!
I have most of the important data backed up, but not all of it. I'm attempting to browse my share to back up everything and it times out. I try to log into the UI and it will sit on the Netgear ReadyNAS page for over 10 minutes, and now is sitting at the Connecting to the ReadNas Admin Page... page with the blue bar that is sliding accross looking like it is trying to load. Then once the bar is complete it says the ReadyNas Admin Page is offline
Last night I hit the power button twice and let it gracefully power down and powered it up this morning.
How do you recommend replacing drives in this condition? I'm unable to log into the UI at the moment. If I physically pull out the online drive, I don't think I'll have the ability to log in to manage the replacement drive and bring it into the RAID and start the raid rebuild process.
Sandshark
Jul 07, 2019Sensei - Experienced User
What is the status on the display and in RAIDar? Do you have SSH enabled so you can check status with that?
It sounds likely that drive 3 is making it hard to impossible for the NAS to properly boot. You could remove drive 3 and try booting in read-only mode to find out, but doing a bit more sleuthing before hand is a better approach. Definitely do not remove drive 3 and just boot normally. If you guess wrong, your volume likely gets destroyed.
- briskikJul 08, 2019Aspirant
I'm fortunate enough to occassionally and sporatically log back in. The status on the LCD Display is normal and no errors. When I log into the UI, it shows the status of the NAS as green and disks are all green. I can't use windows explorer to browse the share anymore. I checked the logs and over the past couple days its just Disk 3 having errors currently.
I'm sure I can enable SSH and putty in. I've never SSH'd into it before, what should I be looking for?
Current Summary: I have a 4 x 3TB Raid 5, with disk 3 throwing lots of errors, UI sporatically allowing me in (very slow response when I get in), I have a replacement drive ready in hand, I'm unable to browse the network shares.
- SandsharkJul 08, 2019Sensei - Experienced User
Probably not the best of time to learn Linux commands, but cat /proc/mdstat will show you the status of the arrays and top will show you what processes are running (and if any are taking a large chunk of CPU time). smartclt --all /dev/sda (followed by sdb, sdc, and sdd) will give detailed SMART data.
- briskikJul 09, 2019Aspirant
First I want to say to everyone in the community thanks for being so helpful and responsive!
The UI has became much more responsive, and I had the ability to backup the random things I had forgot. So I should have all the data on the NAS backed up.
Current Status: 2 of my 4 disks in a Raid-5 are throwing errors, but the system is not failing them out. UI is much more responsive. My system is "green", Raid data is online, all 4 of my disks are online. CIFS Share is intermittenlty responsive. I'm unable to stream content off the NAS as I normally do, because of its current status.
I'm just concerned that as time passes, both these drives are going to continue throwing errors and will fail at the same time. These errors started about 2 weeks ago, and i'm living on borrowed time. I'm hoping only 1 fails at a time, allowing me time to replace the drive and to let the Raid rebuild.
Any advice for my situation?
Here are my last ~15 log messages, the same error messages go back for weeks
Tue Jul 9 2019 6:59:07
Disk: Detected high command timeouts: [270] on disk 3 (Internal) [ST3000DM001-1CH166, W1F5QEWW]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 6:40:33
Disk: Detected high command timeouts: [269] on disk 3 (Internal) [ST3000DM001-1CH166, W1F5QEWW]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 6:34:10
Disk: Detected increasing ATA error count: [194] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 65 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 6:34:10
Disk: Detected increasing ATA error count: [194] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 65 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 6:34:10
Disk: Detected high uncorrectable error count: [4704] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 6:34:10
Disk: Detected increasing pending sector: count [4704] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 187 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 6:01:11
Disk: Detected high command timeouts: [268] on disk 3 (Internal) [ST3000DM001-1CH166, W1F5QEWW]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:52:22
Disk: Detected increasing ATA error count: [193] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 64 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:52:22
Disk: Detected increasing ATA error count: [193] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 64 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:52:22
Disk: Detected high uncorrectable error count: [4728] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:52:22
Disk: Detected increasing pending sector: count [4728] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 186 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:46:18
Disk: Detected increasing ATA error count: [192] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 63 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:46:18
Disk: Detected increasing ATA error count: [192] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 63 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:46:18
Disk: Detected high uncorrectable error count: [4736] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. Tue Jul 9 2019 5:46:18
Disk: Detected increasing pending sector: count [4736] on disk 1 (Internal) [ST3000DM001-1CH166, W1F5QFS2] 186 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!