NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Raidar 6.5 drive ok, Frontview, reboot & volume scan needed, not rebooting. AFP sever shows no data
Hi
ReadyNAS Duo RND2000 with 1 x 2TB Seagate drive. Mac 10.11.6
I have a very old readynas duo that has 1 remaining 2TB drive running in it. All seems fine physically with unit, powered, LED's etc. I can access it via RAIDar and see the drive and I can open the frontview admin page and look at details. I'm just not getting any respose to actions taken in frontview and I can't see any of my data on the drive via AFP?
Recently I have been looking into upgrading all my storage options and trying to solve curent time machine backup messages and general storage on my iMac. I was using the readynas with time machine to backup my mac and also sperately to store larger files. I've been getting messages on time machine that I need to start a completely new back up on this drive. However I fear this will wipe the exisiting data and lose that which is not backed up (larger files). I'd like to be able to see what data is on the drive before attempting to backup the NAS (to external drive?) before possibly starting a new Time Machine back up?
RAIDar states:
Volume C: Raid level X, Not redundant. A disk Failure will render this volume dead. 1587 GB (85%) of 1853 GB used. - To me this seems that the drive is ok and has data on it?
I can't download the logs but I have copied them:
Severity Date Message
Sat Jan 11 19:59:59 WET 2020System is up.
Sat Jan 11 19:55:57 WET 2020Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Sat Jan 11 19:04:17 WET 2020System is up.
Sat Jan 11 18:58:26 WET 2020Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Wed Jul 17 15:31:46 WEST 2019System is up.
Wed Jul 17 15:19:47 WEST 2019System powering off...
Thu Apr 18 13:53:49 WEST 2019System is up.
Thu Apr 18 13:49:30 WEST 2019Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Fri Mar 22 22:57:33 WET 2019The default backup button job copies the contents of the [backup] share to the USB hard drive directly attached to the front of the NAS. Please attach a USB hard drive directly to the front USB port before pressing the backup button.
Tue Nov 20 14:02:09 WET 2018System is up.
Tue Nov 20 13:41:33 WET 2018System powering off...
Sat Sep 22 11:36:25 WEST 2018System is up.
Sat Sep 22 11:32:19 WEST 2018Rebooting device...
Sat Sep 22 11:32:17 WEST 2018Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Tue Sep 11 01:12:01 WEST 2018System is up.
Thu Aug 16 23:13:15 WEST 2018System powering off...
Thu Aug 16 19:23:06 WEST 2018System is up.
Thu Aug 16 19:18:59 WEST 2018Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Tue Jul 10 15:16:44 WEST 2018[media] The share and its subfolders have been configured to allow non-owner delete and rename.
Tue Jul 10 15:14:45 WEST 2018[media] Share contents ownership and permissions changed to match the share.
Wed Jun 27 23:02:46 WEST 2018System is up.
Wed Jun 27 22:56:30 WEST 2018Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Tue Apr 3 06:25:04 WEST 2018Volume C is approaching capacity: 100% used 18G available
Fri Mar 2 18:47:58 WET 2018RAID sync finished on volume C. The volume is now fully redundant.
Thu Mar 1 22:21:09 WET 2018System is up.
Thu Mar 1 22:16:02 WET 2018RAID sync started on volume C.
Thu Mar 1 22:15:49 WET 2018Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Sat Feb 24 05:30:05 WET 2018RAID sync finished on volume C. The volume is now fully redundant.
Fri Feb 23 10:48:53 WET 2018System is up.
Fri Feb 23 10:41:27 WET 2018RAID sync started on volume C.
Fri Feb 23 10:41:00 WET 2018Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Fri Feb 9 06:25:03 WET 2018Volume C is approaching capacity: 99% used 35G available
Thu Dec 14 06:25:04 WET 2017Volume C is approaching capacity: 98% used 55G available
Mon Dec 4 06:25:03 WET 2017Volume C is approaching capacity: 97% used 71G available
Fri Nov 3 04:32:44 WET 2017RAID sync finished on volume C. The volume is now fully redundant.
Thu Nov 2 09:29:25 WET 2017System is up.
Thu Nov 2 09:21:50 WET 2017RAID sync started on volume C.
Thu Nov 2 09:20:25 WET 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Sun Oct 22 05:21:42 WEST 2017RAID sync finished on volume C. The volume is now fully redundant.
Sat Oct 21 08:40:13 WEST 2017System is up.
Sat Oct 21 08:34:09 WEST 2017RAID sync started on volume C.
Sat Oct 21 08:33:50 WEST 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Fri Sep 29 06:25:04 WEST 2017Volume C is approaching capacity: 96% used 92G available
Thu Jul 13 22:02:32 WEST 2017System is up.
Thu Jul 13 21:57:43 WEST 2017System powering off...
Mon Jul 3 15:17:16 WEST 2017RAID sync finished on volume C. The volume is now fully redundant.
Sun Jul 2 23:01:50 WEST 2017System is up.
Sun Jul 2 22:56:11 WEST 2017RAID sync started on volume C.
Sun Jul 2 22:55:28 WEST 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Fri Jun 9 06:25:07 WEST 2017Volume C is approaching capacity: 90% used 204G available
Sun Apr 30 11:26:35 WEST 2017RAID sync finished on volume C. The volume is now fully redundant.
Sat Apr 29 15:27:27 WEST 2017System is up.
Sat Apr 29 15:22:40 WEST 2017RAID sync started on volume C.
Sat Apr 29 15:22:22 WEST 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Mon Apr 24 10:05:59 WEST 2017RAID sync finished on volume C. The volume is now fully redundant.
Sun Apr 23 13:15:09 WEST 2017System is up.
Sun Apr 23 13:07:52 WEST 2017RAID sync started on volume C.
Sun Apr 23 13:07:02 WEST 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Thu Jan 19 17:48:26 WET 2017RAID sync finished on volume C. The volume is now fully redundant.
Wed Jan 18 21:17:14 WET 2017System is up.
Wed Jan 18 21:11:03 WET 2017RAID sync started on volume C.
Wed Jan 18 21:08:08 WET 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Sun Jan 15 10:26:31 WET 2017RAID sync finished on volume C. The volume is now fully redundant.
Sat Jan 14 15:03:18 WET 2017System is up.
Sat Jan 14 14:57:14 WET 2017RAID sync started on volume C.
Sat Jan 14 13:49:29 WET 2017RAID sync started on volume C.
Sat Jan 14 13:49:09 WET 2017Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Mon Nov 7 16:11:59 WET 2016RAID sync finished on volume C. The volume is now fully redundant.
Sun Nov 6 19:59:01 WET 2016System is up.
Sun Nov 6 19:53:55 WET 2016RAID sync started on volume C.
Sun Nov 6 19:53:08 WET 2016Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Fri Sep 30 06:25:04 WEST 2016Volume C is approaching capacity: 80% used 388G available
Fri Aug 19 11:52:00 WEST 2016System clock has been updated.
Sat Jun 25 06:02:30 WEST 2016RAID sync finished on volume C. The volume is now fully redundant.
Fri Jun 24 09:43:04 WEST 2016System is up.
Fri Jun 24 09:38:17 WEST 2016RAID sync started on volume C.
Fri Jun 24 09:37:25 WEST 2016Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Sat Feb 20 11:22:39 WET 2016System is up.
Sat Feb 20 11:19:38 WET 2016Rebooting device...
Sat Feb 20 11:19:37 WET 2016Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Sat Feb 20 10:42:10 WET 2016System is up.
Sat Feb 20 10:35:20 WET 2016System powering off...
Tue Jan 19 02:47:05 WET 2016RAID sync finished on volume C. The volume is now fully redundant.
Mon Jan 18 08:07:04 WET 2016System is up.
Mon Jan 18 08:02:18 WET 2016RAID sync started on volume C.
Mon Jan 18 08:01:51 WET 2016Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled.
Fri Sep 18 21:00:08 WEST 2015System is up.
Fri Sep 18 20:41:21 WEST 2015Powering off device
Fri Sep 18 20:41:20 WEST 2015Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...
Thanks for any help.
Kieran
16 Replies
Replies have been turned off for this discussion
What firmware are you running on the NAS? If it is 4.1.x, then you have a v1; if it is 5.3.x you have a v2.
It does look like you have data on the NAS. Have you tried accessing it with finder using SMB? You could also try enabling FTP, and using that to offload your data (using an FTP client like FileZilla).
I suggest putting the full log zip file into cloud storage (google drive, icloud, etc), and asking the mods ( JohnCM_S or Marc_V ) to analyze them for you. Don't post the link to the logs publicly - send them a private message (PM) using the envelope icon in the upper right of the forum page.
Hi thanks for message.
Firstly I think it's 4.1 I can't remember how to check this info. How do I go about accessing the drive with SMB?
How do I go about zipping the log if I can't download it. I get this error message when I try to download all logs:
This XML file does not appear to have any style information associated with it. The document tree is shown below.<payload>Empty No Support</payload>Thanks
Kieran
Access via SMB:// gives this error.
The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.
Thanks
Kieran
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
