NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
fearless_fool
Feb 03, 2014Aspirant
"Disk fail event" during RAID sync following initialization
Environment: ReadyNAS NV running 4.1.13 Four SAMSUNG HD103UJ (1TB) drives UPS After running the HD103UJ drives for just over five years, the drive in slot 3 started to show increased Ra...
fearless_fool
Feb 03, 2014Aspirant
Stranger and stranger.
The third attempt at reinsert - reinitialize - resync succeeded.
It wasn't until I tried to access the volume (to do a TimeMachine backup) that it failed. What I got on my MacBook console:
...etc. Shortly after that, my ReadyNAS log declared the drive dead:
It seems suspicious that the RAID sync completed without trouble, but problems show up only after trying to access the disk over the net.
Any insights?
The third attempt at reinsert - reinitialize - resync succeeded.
It wasn't until I tried to access the volume (to do a TimeMachine backup) that it failed. What I got on my MacBook console:
2/3/14 6:07:23.000 AM kernel[0]: AFP_VFS afpfs_mount: /Volumes/ReadyNAS-1, pid 96482
2/3/14 6:07:23.000 AM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80d927c008 /Volumes/ReadyNAS-1 (error = 0, retval = 0)
2/3/14 6:07:31.000 AM kernel[0]: jnl: disk5s2: replay_journal: from: 210067456 to: 212340736 (joffset 0x2ace000)
2/3/14 6:07:39.000 AM kernel[0]: disk5s2: 0xc005 (UNDEFINED).
2/3/14 6:07:39.000 AM kernel[0]: jnl: disk5s2: update_fs_block: error reading fs block # 44500856! (ret 5)
2/3/14 6:07:39.000 AM kernel[0]: disk5s2: 0xc005 (UNDEFINED).
2/3/14 6:07:39.000 AM kernel[0]: jnl: disk5s2: update_fs_block: error reading fs block # 44500858! (ret 5)
2/3/14 6:07:39.000 AM kernel[0]: disk5s2: 0xc005 (UNDEFINED).
2/3/14 6:07:39.000 AM kernel[0]: jnl: disk5s2: update_fs_block: error reading fs block # 44500860! (ret 5)
2/3/14 6:07:39.000 AM kernel[0]: disk5s2: 0xc005 (UNDEFINED).
...etc. Shortly after that, my ReadyNAS log declared the drive dead:
Mon Feb 3 06:11:11 PST 2014 Disk fail event occurred on SATA channel 4. If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead.
Mon Feb 3 03:00:01 PST 2014 RAID sync finished on volume C. The volume is now fully redundant.
Sun Feb 2 22:46:49 PST 2014 RAID sync started on volume C.
It seems suspicious that the RAID sync completed without trouble, but problems show up only after trying to access the disk over the net.
Any insights?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!