thephoneguy

I ended up restarting the check, and doing 4 and it went fine. seems 8 is again hung at the exact same point vpf-10260: The file we are inserting the new item (2384842 2904006 0xb59 DRCT (2), len 352, location 3744 entry count 65535, fsck need 1, format new) into has no StatData, insertion was skipped its been there with no sign of moving. What is the next step, been a long time now with no data access.

The putty has not progressed past the last line at Len 352.....is it hung?

I went away for a few days, figured it would be done by then, when I looked at the system, it had rebooted, annd drive 4 and 8 still nothing showing. Restarted the rebuild-tree on md8 last night at 9pm, and it appears to be still running. Only thing is now the GUI is non responsive. I can ping it, and it would appear that the putty session is still going/ Here si a cut and paste of what my putty session looks like: StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0xd26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x111a001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x150e001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x1902001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x1cf6001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x20ea001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x24de001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x28d2001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2244903 2244925 0x2cc6001 IND (1), len 2984, location 1112 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (640055 1212460 0x579 DRCT (2), len 1048, location 3048 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (622918 1069995 0x1 DRCT (2), len 3344, location 752 entry count 65535, fsck need 1, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (1406053 1406056 0x47f001 IND (1), len 2688, location 1408 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (1406053 1406064 0x370001 IND (1), len 448, location 3648 entry count 0, fsck need 1, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (1406053 1406074 0x4df001 IND (1), len 2052, location 2044 entry count 0, fsck need 1, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2322558 2634590 0x1 DRCT (2), len 560, location 3536 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (632370 5186571 0x1 DRCT (2), len 1024, location 3072 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4236023 4236137 0xa31 DRCT (2), len 736, location 3360 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (737080 737333 0x1 IND (1), len 40, location 4056 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (737080 737466 0x1 DRCT (2), len 2928, location 1168 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2381211 2859358 0x1 IND (1), len 12, location 4084 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2367930 100249743 0x701001 IND (1), len 392, location 3704 entry count 12, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2366107 3183176 0x499 DRCT (2), len 1408, location 2688 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452387 0x288001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (3504346 3504350 0x39001 IND (1), len 452, location 3644 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1456686 0x411001 IND (1), len 424, location 3672 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1458651 0x3e3001 IND (1), len 268, location 3828 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1458651 0x8d001 IND (1), len 3684, location 412 entry count 0, fsck need 1, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1459339 0x1 IND (1), len 928, location 3168 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1459329 0x1 IND (1), len 1344, location 2752 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452244 0x52c4001 IND (1), len 240, location 3856 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452235 0x80001 IND (1), len 1536, location 2560 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452503 0x52ca001 IND (1), len 216, location 3880 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452235 0x80001 IND (1), len 1536, location 2560 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452503 0x52ca001 IND (1), len 216, location 3880 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452490 0x51e6001 IND (1), len 1128, location 2968 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (966842 1040117 0x4b0f1001 IND (1), len 2340, location 1756 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x1b9001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x5ad001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x9a1001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0xd95001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x1189001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x2159001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x254d001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x2d35001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x3129001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x351d001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x3911001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x3d05001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x40f9001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x44ed001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x48e1001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x4cd5001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452570 0x50c9001 IND (1), len 2268, location 1828 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4105742 4105760 0xd001 IND (1), len 44, location 4052 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1452068 0x5227001 IND (1), len 868, location 3228 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1453931 0x50ed001 IND (1), len 2124, location 1972 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (1397761 1397766 0x13a001 IND (1), len 2364, location 1732 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (177307 1453932 0x1ca001 IND (1), len 216, location 3880 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2926155 2926163 0xe32001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (533105 938083 0x689 DRCT (2), len 1280, location 2816 entry count 65535, fsck need 1, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (4377301 4377334 0x25430001 IND (1), len 3428, location 668 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2391252 2807559 0x2a1 DRCT (2), len 448, location 3648 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2369237 3049113 0x1 IND (1), len 124, location 3972 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2365141 3151187 0x309 DRCT (2), len 816, location 3280 entry count 65535, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (807598 840703 0x2e72001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (529331 536573 0xb001 IND (1), len 432, location 3664 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (535931 791304 0x1 IND (1), len 76, location 4020 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped vpf-10260: The file we are inserting the new item (2384842 2904006 0xb59 DRCT (2), len 352, location 3744 entry count 65535, fsck need 1, format new) into has no StatData, insertion was skipped

Trurl, I am on 5.0.6, so no docker. I am watching both activity and main page for disk read/ writes. As of now, I am still seeing a 10 thousand + read/writes per hour on md8. Some to parity. Below is a paste of the log. I watched the putty session for a lng time, it found all kinds of things to solve, so its been busy. The CPU usage is fixed at 25% on a Core2 Quad and when it was doing lots of read/writes, it was averaging 140MBS. now there is a blip here and there so not sure what its doing. tail -n 40 -f /var/log/syslogFeb 23 04:40:01 media-svr syslogd 1.4.1: restart. I attached the screenshot of the stats rebuild stat.doc

Coming up on 20 hours and still going on md8. hope md4 does not take this long. My syslog is blank, is that normal?

It wants a rebuild tree on md8, doing that now and will then see what it nets. Looks like its going to be a bit, so will report the results. Then on to md4

unraid is the backup plan. I did have it go to shit way back in 4.7 and had to use a reiser file reader to read the files off the drives one by one and move them to a new system. It is, as they say, " a series of unfortunate events" and many of the people I know who have unraid have a horror story or two to tell. I could have avoided this, but I put me last, as I do IT for a living, and ended up using the drives (a few times) that I ordered for customers instead of myself. i just sent away 2 x 4TB WD's today for warranty, so I will have some spares if things go to boom boom again. I keep most of my data on the server, and monitor drives for age. i replace at the 4 year mark (either because they are old or because its time for a bigger drive. I have 11 drives now, and they are almost all 4TB, and when i started my parity was 1TB and the rest were 500/640/750 drives. I have tried many different hardware setups, but find the intel mobo with ICH7 or higher to be just fine. I have two other unraid servers, and am using BTSync (Now resilio) and may now include all of my real data (docs, photos ect) as I know I can replace (slowly) the thousands of movies and TV i have in my collection for media streaming. of the 21.5TB i have in my 30TB array, only 1~1.5 is real data, the rest is media.

OK, will just go on with my day and hope for the best. Should be able to run other commands tonight after rebuild. I am assuming from above that I should do the check on md8 before the rebuild tree on md4, correct?

Is there any benefit to doing that, running the rebuild in maintenance mode? Also, are you saying that I will need to do the drive check on disk 8 as well as 4? and which should I complete first? the data on 8 is critical, 4 not so much. I read and re read the section in the wiki on the drive check, and made sure to use md4 as apposed to sdj to keep parity intact. Just waiting for the sick feeling in my stomach to go away

OK, just so i understand you correctly, what are steps and in what order? I hate being pressured, and cannot risk a mistake. Do I stop the rebuild?

tail -n 40 -f /var/log/syslogFeb 21 10:38:40 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:38:45 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:38:45 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:38:45 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:38:50 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:38:50 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:38:50 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:38:55 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:38:55 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:38:55 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:05 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:05 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:05 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:10 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:10 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:10 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:15 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:15 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:15 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:20 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:20 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:20 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:25 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:25 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 12204 does not match to the expected one 2Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 790971552. Fsck?Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 694046 0x0 SD]Feb 21 10:39:25 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 12204 does not match to the expected one 2Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 790971552. Fsck?Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 694046 0x0 SD]Feb 21 10:39:25 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 12204 does not match to the expected one 2Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 790971552. Fsck?Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 694046 0x0 SD]Feb 21 10:39:25 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 12204 does not match to the expected one 2Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 790971552. Fsck?Feb 21 10:39:25 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 694046 0x0 SD]Feb 21 10:39:30 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:30 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:30 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:35 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:35 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:35 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:40 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:40 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:40 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:45 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:45 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:45 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:50 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:50 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:50 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD]Feb 21 10:39:55 media-svr kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 64569 does not match to the expected one 2Feb 21 10:39:55 media-svr kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 688030382. Fsck?Feb 21 10:39:55 media-svr kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [592643 592644 0x0 SD] Time keeps reverting to Arizona -7, its actuall y -8 and this is current log

How do i restore the SMB paths? When i browse to the root of the share \\media-svr\ i see all the shares, but they show empty. If you browse to the individual disks (with the exception of 4 and 8 ) I see the contents the way unraid spreads the contents around as i use high water for my drive scenario. I also accurately see the drive usage under stats. This was the case AFTER i did the rebuild on 4, just assumed it was something to do with the rebuild and it needed a reboot. Kind of scared.

Im seriously stressing now, as I cannot see any files on my server, just the folder shares. WTF?!! I can click the folder icon beside each drive and see contents, but the actual SMB paths are empty.

I had another drive pop while doing the rebuild so will wait until its done. I have learned the lesson to make sure you replace a drive once it goes red, and quickly. SO not going to chance this one. Will run the rebuild tree after my drive 8 rebuilds. Stay tuned and thank you again.

This is after the check and rebuild root@media-svr:~# reiserfsck --check /dev/md4 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md4 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Feb 21 09:42:44 2017 ########### Replaying journal: No transactions found Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted (core dumped)