Re: unRAID Server Release 6.0-beta12-x86_64 - Tophicles & reiserfsck

Hi All!

Was having a fine time with 6beta12 until I got a disk giving me errors. It was a 2TB disk, so I bought a 3TB to replace it.

When it boots now, I get stuck at the following lines:

Dec 11 22:11:35 Angband kernel: REISERFS (device md13): journal params: device md13, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Dec 11 22:11:35 Angband kernel: REISERFS (device md13): checking transaction log (md13)
Dec 11 22:11:35 Angband kernel: REISERFS (device md13): replayed 4 transactions in 0 seconds
Dec 11 22:11:36 Angband kernel: REISERFS (device md13): Using r5 hash to sort names
Dec 11 22:11:36 Angband emhttp: shcmd (80): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md13 /mnt/disk13 |& logger
Dec 11 22:11:36 Angband emhttp: reiserfs: resizing /mnt/disk13

It just hangs at that "resizing" and won't mount any further disks...  any ideas?

*EDIT*

Ok, I was just impatient - it finished mounting after these errors:

Dec 11 22:11:36 Angband kernel: REISERFS (device md13): Using r5 hash to sort names
Dec 11 22:13:08 Angband kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 20302 does not match to the expected one 1
Dec 11 22:13:08 Angband kernel: REISERFS error (device md13): vs-5150 search_by_key: invalid format found in block 414987113. Fsck?
Dec 11 22:13:08 Angband kernel: REISERFS (device md13): Remounting filesystem read-only
Dec 11 22:13:08 Angband kernel: REISERFS error (device md13): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [9436 9438 0x0 SD]
Dec 11 22:13:08 Angband kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 46970 does not match to the expected one 1
Dec 11 22:13:08 Angband kernel: REISERFS error (device md13): vs-5150 search_by_key: invalid format found in block 414997138. Fsck?
Dec 11 22:13:08 Angband kernel: REISERFS error (device md13): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [9436 9443 0x0 SD]
Dec 11 22:13:08 Angband kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 19914 does not match to the expected one 1
Dec 11 22:13:08 Angband kernel: REISERFS error (device md13): vs-5150 search_by_key: invalid format found in block 414989119. Fsck?
Dec 11 22:13:08 Angband kernel: REISERFS error (device md13): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [9436 9439 0x0 SD]
Dec 11 22:15:05 Angband kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 11341 does not match to the expected one 1
Dec 11 22:15:05 Angband kernel: REISERFS error (device md13): vs-5150 search_by_key: invalid format found in block 414981289. Fsck?
Dec 11 22:15:05 Angband kernel: REISERFS error (device md13): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6620 6639 0x0 SD]
Dec 11 22:15:09 Angband kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 41730 does not match to the expected one 1
Dec 11 22:15:09 Angband kernel: REISERFS error (device md13): vs-5150 search_by_key: invalid format found in block 414983300. Fsck?
Dec 11 22:15:09 Angband kernel: REISERFS error (device md13): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6640 6641 0x0 SD]

I'm assuming (from some googling) that these are FS errors from the previous drive and I just need to run reiserfsck --rebuild-tree when the data re-build is finished?

any ideas?

Any more information?

... and, perhaps, the release thread is not the correct place for your query.

I'm assuming (from some googling) that these are FS errors from the previous drive and I just need to run reiserfsck --rebuild-tree when the data re-build is finished?

I moved your post here, as a support issue with the Reiser file system.

You only want to use the --rebuild-tree option if reiserfsck instructs you to.  Start with the --check option, then follow any instructions given.  For more info, please see Check Disk File systems.

I'm assuming (from some googling) that these are FS errors from the previous drive and I just need to run reiserfsck --rebuild-tree when the data re-build is finished?

 

I moved your post here, as a support issue with the Reiser file system.

 

You only want to use the --rebuild-tree option if reiserfsck instructs you to.  Start with the --check option, then follow any instructions given.  For more info, please see Check Disk File systems.

Thank you for both the advice and for moving the post to the correct forum - apologies for panic posting