November 25, 20178 yr Community Expert Try upgrading to v6, it will have a more recent release of reiser progs.
November 25, 20178 yr Author just for information, i upgraded UNRAID OS to v6 and run the same diagnostics and still show the same error. I did a --rebuild function but still same.
November 25, 20178 yr Community Expert Then your best bet is to copy everything you can from disk8 and format it, since you're already on v6 use xfs, reiser is dead.
November 25, 20178 yr Community Expert One more thing, what Itimpi mentioned about how much RAM may also be a factor, though I've only seen the lack of RAM problem during a --rebuild-tree and it doesn't segfault, still if you have 1GB of RAM or less you may want to try adding some more. Running memtest is also a good idea.
November 26, 20178 yr Author 15 hours ago, johnnie.black said: One more thing, what Itimpi mentioned about how much RAM may also be a factor, though I've only seen the lack of RAM problem during a --rebuild-tree and it doesn't segfault, still if you have 1GB of RAM or less you may want to try adding some more. Running memtest is also a good idea. I have 4GB of ram. 15 hours ago, johnnie.black said:
November 26, 20178 yr Community Expert Then try to copy everything from it and re-format, mounting the disk read-only may help accessing its data, after array start type: mount -o remount,ro /dev/md8
November 26, 20178 yr Author 15 hours ago, johnnie.black said: One more thing, what Itimpi mentioned about how much RAM may also be a factor, though I've only seen the lack of RAM problem during a --rebuild-tree and it doesn't segfault, still if you have 1GB of RAM or less you may want to try adding some more. Running memtest is also a good idea. I have 4GB of ram. Quote How about i run -rebuild-tree ? I only try -rebuild-sb
November 26, 20178 yr Community Expert 1 minute ago, bravob said: How about i run -rebuild-tree ? I though you already tried that when you wrote: 16 hours ago, bravob said: I did a --rebuild function but still same. --rebuild-sb would never help in your situation, --rebuild-tree might help, you should definitely try that.
November 26, 20178 yr Community Expert Also make sure you don't run --rebuild-tree after reiserfsck having already segfaulted, i.e., reboot if needed to start a clean run.
November 28, 20178 yr Author On 11/26/2017 at 4:10 AM, johnnie.black said: One more thing, what Itimpi mentioned about how much RAM may also be a factor, though I've only seen the lack of RAM problem during a --rebuild-tree and it doesn't segfault, still if you have 1GB of RAM or less you may want to try adding some more. Running memtest is also a good idea. I have 4GB of ram. Quote I am seeing new errors after rebuild tree md8... How should i fix further ? Nov 28 07:59:25 Tower kernel: REISERFS error (device md5): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [26802 26804 0x0 SD] Nov 28 07:59:25 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13791 does not match to the expected one 1 Nov 28 07:59:25 Tower kernel: REISERFS error (device md5): vs-5150 search_by_key: invalid format found in block 190298904. Fsck? Nov 28 07:59:25 Tower kernel: REISERFS error (device md5): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [26808 26809 0x0 SD] Nov 28 08:09:50 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:09:50 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:09:50 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:09:50 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:11:39 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:11:39 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:11:39 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:11:39 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:12:17 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:12:17 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:12:17 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:12:17 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:12:17 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:12:17 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:12:17 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:12:17 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:12:17 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:12:17 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:12:17 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:12:17 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:12:24 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:12:24 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:12:24 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:12:24 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:12:28 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Nov 28 08:12:28 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:12:28 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:12:28 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD] Nov 28 08:12:31 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Nov 28 08:12:31 Tower kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 322339502. Fsck? Nov 28 08:12:31 Tower kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 21 0x0 SD]
November 28, 20178 yr 1 hour ago, bravob said: Nov 28 08:12:28 Tower shfs/user: err: shfs_readdir: fstatat: _Chinese_ (13) Permission denied Not sure what that is, but it looks suspect...
November 28, 20178 yr Author 2 hours ago, FreeMan said: Not sure what that is, but it looks suspect... This is a folder name which i store chinese stuff. I saw some io errors.. do i need to run rebuild for md4 ? I don’t understand why unraid did not flag any errors during writing and yet so many of my disks are having issue.
November 28, 20178 yr Community Expert 7 hours ago, bravob said: How should i fix further ? Filesystem on disk4 also needs to be checked, also like I said before and if you havent't yet you should run memtest before doing that to make sure your RAM isn't bad and corrupting the filesystems.
November 28, 20178 yr Community Expert The last log snippet (at the start)also showed possible corruption on disk5. i would carefully check all cabling and as suggested run a memtest before proceeding. This many disk showing corruption is a bit worrying. There may well be some underlying problem causing this that has not yet been identified. You probably want to run a disk check on all disks at this point just to be sure.
November 28, 20178 yr Community Expert Run memtest from the unRAID boot menu for at least 24 hours, only if there are no errors proceed with checking the other disks.
November 28, 20178 yr Community Expert 9 hours ago, bravob said: How to run disk check on each disk for unraid ? If you start the Array in Maintenance mode then clicking on a drive in the Main tab takes you to a page where you can run the file system check for that drive. You can also run the SMART checks on the drive from there. Edited November 28, 20178 yr by itimpi
November 29, 20178 yr Author I didn’t run memtest for 24hours due to time constraint on my part. But it has been running for around 10 hours no error as you can see from screenshot.
November 29, 20178 yr Author 7 hours ago, itimpi said: If you start the Array in Maintenance mode then clicking on a drive in the Main tab takes you to a page where you can run the file system check for that drive. You can also run the SMART checks on the drive from there. Does this check do any rebuild and fixing ?
November 29, 20178 yr Author 17 hours ago, itimpi said: The last log snippet (at the start)also showed possible corruption on disk5. i would carefully check all cabling and as suggested run a memtest before proceeding. This many disk showing corruption is a bit worrying. There may well be some underlying problem causing this that has not yet been identified. You probably want to run a disk check on all disks at this point just to be sure. Could it be sas/raid card issue ? How do i verify such issue ?
November 29, 20178 yr Community Expert 15 hours ago, bravob said: Does this check do any rebuild and fixing ? By default it does a --check, you can add the appropriate option to the command if needed, e.g., --rebuild-tree, you can also use the console like you did with disk8, start in maintenance mode and just replace X with the disk number: reiserfsck /dev/mdX 15 hours ago, bravob said: Could it be sas/raid card issue ? How do i verify such issue ? Possible, are all disks on the same controller? Do you have some free SATA ports you could change things around? In doubt post the full diagnostics.
Archived
This topic is now archived and is closed to further replies.