I followed procedure from a different forum post to:

 

A) set the drive as "unassigned"

B) bring  the raid up in maintenance mode

C) perform reiserfsck --check on the drive

 

it responded with:

 

reiserfs_open: the reiserfs superblock cannot be found on /dev/md8.

Failed to open the filesystem.

 

If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then superblock is currupted and you need to run this utility with --rebuild-sb.

 

I'm wanting to super careful at this point, ... should I go ahead and perform this procedure?

I'm so sorry, I realize I posted this in an inproper location. ... I also understand any hesitancy in offering help with this.  I'm trying to find documentation on how to answer the proper questions once I administer this command? any help?

I copied pasted from a previous reference the following answers to questions in the reiserfsck --rebuild-sb ...

 

are these still correct in newer versions of unraid (I'm using 5.0.4 (once again I'm sorry I posted this entire thread in the wrong location))

 

-- copy paste ---

 

It told me to run with the “--rebuild-sb option” if I was sure.  If ever you have to run with this option, it asks you a bunch of questions.  Here are the correct responses (many thanks to Tom for helping me through these):

 

1.  The version of reiserfs is 3.6.x.  This is for unRAID 4.2.1.  (This is NOT the default, so be careful)

2.  Block size is 4096 (default)

3.    “No journal device was specified.  (If journal is not available, re-run with --no-journal-available option specified)”  Is journal default?”  (Answer Y)

4.  “Do you use resizer?” (Answer N)

5.  It tells you that a new uuid has been generated. 

6.    “rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header?”  Answer Y

7.  The following info is displayed:

 

Reiserfs super block in block 16 on 0x901 of format 3.6 with standard journal

Count of blocks on the device: 73264320

Number of bitmaps: 2236

Blocksize: 4096

Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0

Root block: 0

Filesystem is NOT clean

Tree height: 0

Hash function used to sort names: not set

Objectid map size 0, max 972

Journal parameters:

        Device [0x0]

        Magic [0x0]

        Size 8193 blocks (including 1 for journal header) (first block 18)

        Max transaction length 1024 blocks

        Max batch size 900 blocks

        Max commit age 30

Blocks reserved by journal: 0

Fs state field: 0x1:

        some corruptions exist.

sb_version: 2

inode generation number: 0

UUID: <my UUID removed>

LABEL:

Set flags in SB:

Is this ok ? (y/n)[n]:

 

8.  Answer “Y”. 

9.  With amazing speed the program does its thing and ends

- - - -