Hi there,

I did a successful preclear of a 3tb WD red drive (md14) afterwards I started the data rebuild which now stopped because the drive is shown as a red dot. The preclear completed without issues. I have included the preclear results (which was done in another machine) and from my main unraid box. The drive is sitting in a SS500 5in 3 cage. Any help is greatly appreciated.

rebuilt_issues.zip

Hi there,

I did a successful preclear of a 3tb WD red drive (md14) afterwards I started the data rebuild which now stopped because the drive is shown as a red dot. The preclear completed without issues. I have included the preclear results (which was done in another machine) and from my main unraid box. The drive is sitting in a SS500 5in 3 cage. Any help is greatly appreciated.

 

It looks like the disk is fine based on the preclear reports. You say that you precleared it in a separate machine.

 

My guess is that the connection to the drive (either SATA or power) in the new machine is not secure.

 

If you fix that problem, you should be able to restart the rebuild (you may have to remove it from the array, start the array, and then add it back to get unRAID to accept it for rebuild again).

I followed those steps after I verified all cables once again, still getting these errors

 

 

Jul 29 16:05:35 Tower emhttp: shcmd (397): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service

Jul 29 16:05:35 Tower avahi-daemon[7536]: Files changed, reloading.

Jul 29 16:05:35 Tower avahi-daemon[7536]: Service group file /etc/avahi/services/smb.service changed, reloading.

Jul 29 16:05:35 Tower emhttp: shcmd (398): ps axc | grep -q rpc.mountd

Jul 29 16:05:35 Tower emhttp: _shcmd: shcmd (398): exit status: 1

Jul 29 16:05:35 Tower emhttp: Start NFS...

Jul 29 16:05:35 Tower emhttp: shcmd (399): /etc/rc.d/rc.nfsd start |& logger

Jul 29 16:05:35 Tower logger: Starting NFS server daemons:

Jul 29 16:05:35 Tower logger:  /usr/sbin/exportfs -r

Jul 29 16:05:35 Tower logger:  /usr/sbin/rpc.nfsd 8

Jul 29 16:05:35 Tower logger:  /usr/sbin/rpc.mountd

Jul 29 16:05:35 Tower rpc.mountd[8102]: Version 1.2.8 starting

Jul 29 16:05:35 Tower emhttp: shcmd (400): /usr/local/sbin/emhttp_event svcs_restarted

Jul 29 16:05:35 Tower emhttp_event: svcs_restarted

Jul 29 16:05:35 Tower emhttp: shcmd (401): /usr/local/sbin/emhttp_event started

Jul 29 16:05:35 Tower emhttp_event: started

Jul 29 16:05:35 Tower rc.unRAID[8108][8109]: Processing /etc/rc.d/rc.unRAID.d/ start scripts.

Jul 29 16:05:36 Tower avahi-daemon[7536]: Service "Tower" (/etc/avahi/services/smb.service) successfully established.

Jul 29 16:07:38 Tower shfs/user: shfs_readdir: fstatat: Comedy (13) Permission denied

Jul 29 16:07:38 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk8/movies (13) Permission denied

Jul 29 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1

Jul 29 16:07:38 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 348880938. Fsck?

Jul 29 16:07:38 Tower kernel: REISERFS (device md8): Remounting filesystem read-only

Jul 29 16:07:38 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 15067 0x0 SD]

Jul 29 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1

Jul 29 16:07:38 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 348880938. Fsck?

Jul 29 16:07:38 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 15067 0x0 SD]

Jul 29 16:07:38 Tower shfs/user: shfs_readdir: fstatat: Comedy (13) Permission denied

Jul 29 16:07:38 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk8/movies (13) Permission denied

Jul 29 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 25565 does not match to the expected one 2

Jul 29 16:07:38 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 353699823. Fsck?

Jul 29 16:07:38 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [7175 7176 0x0 SD]

Jul 29 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 25565 does not match to the expected one 2

Jul 29 16:07:38 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 353699823. Fsck?

Jul 29 16:07:38 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [7175 7176 0x0 SD]

 

another thing I guess I should mention is that I had another drive which was failing which I replaced before there was a red dot and during the rebuild of that drive this drive md14 failed, I see at the top of my unMenu the following line  Last parity check  16281  days ago .  Parity updated  191599345  times to address sync errors.  I guess with the Parity updated that is not good. Does that have anything to do with this? Have I lost data?

syslog-2014-07-29_1.zip

You should read the "what is parity" link in my sig. I.can't really answer your question. Parity needs to be accurate in order to be used to restore a failed drive. If the parity check, in essence, broke parity, then recovery wouldn't work. But if the parity check fixed parity, then recovery would work fine.

it appears that the problem with drive md14 caused the rebuild to have a problem and showed only the md14 as failed and md8 fine, and now I already sent the drive back to WD so it appears that I lost at least 2 tb of data. When I look under /tower/disk 8 I can see directories but they are all empty.

syslog-20140724-192024_shorted.zip