NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NV+ 4.1.9 constantly re-syncing
I've got two 1tb drives in X-Raid - newly installed and constantly seem to be re-syncing.
Date Message
Sun Aug 19 15:14:13 WEST 2012 System is up.
Sun Aug 19 15:13:18 WEST 2012 RAID sync started on volume C.
Sun Aug 19 15:13:00 WEST 2012 Volume scan found and corrected errors.
Sun Aug 19 13:44:54 WEST 2012 RAID sync finished on volume C. The volume is now fully redundant.
Sun Aug 19 05:06:06 WEST 2012 System is up.
Sun Aug 19 05:05:10 WEST 2012 RAID sync started on volume C.
Sun Aug 19 05:04:55 WEST 2012 Volume scan found and corrected errors.
Sun Aug 19 03:45:41 WEST 2012 RAID sync finished on volume C. The volume is now fully redundant.
There is _no_ data on these drives yet. It is juist sitting there idle.
If i look at the health of the drives, SMART says no errors or anything unusual. I can send a zip of the logs if anyone is able to analyse them.
One thing which caught my eye was:
Aug 19 05:05:11 nas-01-3B-D2 kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 19 05:05:11 nas-01-3B-D2 kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Aug 19 05:05:11 nas-01-3B-D2 kernel: ide: failed opcode was: 0xef
I'm not entirely sure if this was during boot or what - but i've not rebooted this device. Is there any way to see the uptime, or to SSH into the device?
Thanks!\
Date Message
Sun Aug 19 15:14:13 WEST 2012 System is up.
Sun Aug 19 15:13:18 WEST 2012 RAID sync started on volume C.
Sun Aug 19 15:13:00 WEST 2012 Volume scan found and corrected errors.
Sun Aug 19 13:44:54 WEST 2012 RAID sync finished on volume C. The volume is now fully redundant.
Sun Aug 19 05:06:06 WEST 2012 System is up.
Sun Aug 19 05:05:10 WEST 2012 RAID sync started on volume C.
Sun Aug 19 05:04:55 WEST 2012 Volume scan found and corrected errors.
Sun Aug 19 03:45:41 WEST 2012 RAID sync finished on volume C. The volume is now fully redundant.
There is _no_ data on these drives yet. It is juist sitting there idle.
If i look at the health of the drives, SMART says no errors or anything unusual. I can send a zip of the logs if anyone is able to analyse them.
One thing which caught my eye was:
Aug 19 05:05:11 nas-01-3B-D2 kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 19 05:05:11 nas-01-3B-D2 kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Aug 19 05:05:11 nas-01-3B-D2 kernel: ide: failed opcode was: 0xef
I'm not entirely sure if this was during boot or what - but i've not rebooted this device. Is there any way to see the uptime, or to SSH into the device?
Thanks!\
4 Replies
- ok, I installed SSH - looks like maybe my box is rebooting - uptime is :
nas-01-3B-D2:~# uptime
21:24:49 up 6:25, 1 user, load average: 0.04, 0.05, 0.06
nas-01-3B-D2:~# date
Sun Aug 19 21:25:00 WEST 2012
I think i'm rebooting for some reason - and this is triggering a sync due to improper shutdown maybe? - Aug 19 15:13:19 nas-01-3B-D2 /usr/sbin/cron[886]: (CRON) INFO (pidfile fd = 3)
Aug 19 15:13:19 nas-01-3B-D2 /usr/sbin/cron[890]: (CRON) STARTUP (fork ok)
Aug 19 15:13:19 nas-01-3B-D2 /usr/sbin/cron[890]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
***** File system check performed at Sun Aug 19 14:59:42 WEST 2012 *****
fsck 1.40.11 (17-June-2008)
e2fsck 1.40.11 (17-June-2008)
c was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
c: 24/30474240 files (4.2% non-contiguous), 512763/60889088 blocks
Aug 19 13:44:51 nas-01-3B-D2 kernel: VERSION/ID : SB=(V:0.1.0) ID=<a2013bd2.00000000.00000000.00000000> CT:502d2ae5
Aug 19 13:44:51 nas-01-3B-D2 kernel: RAID_INFO : DISKS(TOTAL:2 RAID:2 PARITY:1 ONL:2 WRK:2 FAILED:0 SPARE:0 BASE:0)
Aug 19 13:44:51 nas-01-3B-D2 kernel: SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Aug 19 13:44:51 nas-01-3B-D2 kernel: LOGICAL_DRIVE : 0: B:0000000032 E:0004096000 R:1 O:1 I:1:000000000 DM:3
Aug 19 13:44:51 nas-01-3B-D2 kernel: LOGICAL_DRIVE : 1: B:0004096032 E:1949012614 R:1 O:1 I:1:000000000 DM:3
Aug 19 13:44:51 nas-01-3B-D2 kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Aug 19 13:44:51 nas-01-3B-D2 kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Aug 19 13:44:51 nas-01-3B-D2 kernel: CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Aug 19 13:44:51 nas-01-3B-D2 kernel: Total=2; raid=2; ready=0; work=2; failed=0
Aug 19 13:44:51 nas-01-3B-D2 kernel: sata_hotplug: /sbin/hotplug xraid_sync_finished hdeUser mode helper start.
Aug 19 13:44:51 nas-01-3B-D2 kernel: done do_sata_hotplug
Aug 19 15:13:18 nas-01-3B-D2 syslogd 1.4.1#10: restart.
Aug 19 15:13:18 nas-01-3B-D2 kernel: klogd 1.4.1#10, log source = /proc/kmsg started.
Aug 19 15:13:18 nas-01-3B-D2 kernel: Linux version 2.6.17.14ReadyNAS (root@calzone) (gcc version 3.3.5 (Infrant 3.3.5-1)) #1 Wed Jun 20 20:08:20 PDT 2012
Aug 19 15:13:18 nas-01-3B-D2 kernel: You system is PZERO.
Aug 19 15:13:18 nas-01-3B-D2 kernel: ASIC=IT3107
Aug 19 15:13:18 nas-01-3B-D2 kernel: zlist 0 802f115c
Aug 19 15:13:18 nas-01-3B-D2 kernel: zone 802f0f14, name Normal
So something happened at 15h13 - a reboot -but why? Do these look like spontaneous reboots?
Thanks, - I tested the ram twice - shows as OK. I have 256Mb - should I consider upgrading this?
I removed a drive - so I only have one drive installed now - and did a factory reset still using XRaid - so lets see how stable it is. If it is stable today, i'll add the second disk in, let it sync, and see. - Ok, after doing the above, it seems more stable now. Will monitor for the next few days. I hope this helps someone in the future.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
