Forum Discussion
RN214 Drive Degraded After Restart
Hi all,
We had a breif power failure last night and luckily my UPS kept my NAS running long enough so that I could perform a proper shutdown. However after restarting it this morning, one of th...
Disks can and do fail at any time.
What do you see for the disk that was considered bad in the logs e.g. in smart_history.log. disk_info.log should indicate the disk letter (though that might have changed when adding the disk back) and you may see entries for the disk in dmesg.log, kernel.log and/or systemd-journal.log that may also give an indication as to why the disk was considered bad.
I went through the logs you suggested, didn't see anything bad in the logs ofr that drive. The only thing that stood out was in the kernel.log at the time the NAS weas being shut down:
Aug 29 20:55:03 ABC-Inc kernel: al_eth 0000:00:03.0 eth1: al_eth_down
Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: dma state didn't change to Disable
Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: failed to change state, error -110
Aug 29 20:55:03 ABC-Inc kernel: al_eth 0000:00:01.0 eth0: al_eth_down
Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: dma state didn't change to Disable
Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: failed to change state, error -110
Aug 29 20:55:05 ABC-Inc systemd-shutdown[1]: Sending SIGTERM to remaining processes...What stats did you see in disk_info.log?
I attached the log below.
After re-sync it's noting the drive as healthy however.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
