Issues after replacing failed HDD

[Userpaul]

Unraid 6.5.3

After replacing failed HDD with new hdd and rebooting a parity check and rebuild ran okay. I did have a considerable number of parity issues on two hdds when complete but everything looked okay. All files present. After running parity check again to correct errors I now have some issues i have not come across before. My replacement hdd shows that it has files 720gb used 1.28tb free. Original disk was 750gb. But i cannot access the files or see them.

This seems to be the issue?

"Dec 5 17:44:46 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Dec 5 17:44:46 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 27557505. Fsck? Dec 5 17:44:46 Tower kernel: REISERFS (device md14): Remounting filesystem read-only"

 

Any help or suggestions would be appreciated

 

Thank you

 

Paul

 

https://screenshots.firefox.com/7yaWZJaxmsYSmYK4/tower

tower-syslog-20181205-1903.zip

[JorgeB]

You need to check filesystem on disk14, but current syslog doesn't show the rebuild, depending on what exactly you mean by this

10 minutes ago, Userpaul said:

I did have a considerable number of parity issues on two hdds when complete but everything looked okay.

rebuilt disk might be corrupt/missing data.

[Userpaul]

i replaced hdd and when i rebooted unraid said it was doing parity and rebuild

2018-12-03, 05:24:4515 hr, 15 min, 2 sec91.1 MB/sOK errors 178771813  < Parity check and rebuild of new hdd

[JorgeB]

Any errors aren't good, but without the syslog covering the rebuild can't say what happened exactly and how bad it was, you should have stopped there and asked for help the moment errors were reported.

 

 

[Userpaul]

Running now

 

 

reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md14 Will put log info to 'stdout' ########### reiserfsck --check started at Wed Dec 5 19:39:32 2018 ########### Replaying journal:

Response

Replaying journal: Done. Reiserfs journal '/dev/md14' in blocks [18..8211]: 6 transactions replayed Checking internal tree.. finished Comparing bitmaps..Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Wed Dec 5 19:41:08 2018 ########### block 154707197: The level of the node (0) is not correct, (1) expected the problem in the internal node occured (154707197), whole subtree is skipped block 65798147: The level of the node (0) is not correct, (2) expected the problem in the internal node occured (65798147), whole subtree is skipped block 177125720: The level of the node (0) is not correct, (3) expected the problem in the internal node occured (177125720), whole subtree is skipped vpf-10640: The on-disk and the correct bitmaps differs.

 

I'm reading this ..http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems