I had a drive go unmountable on Monday so last night i went through the normal process of swapping drives (Stop array, unassign drive, start array, stop array, add new drive, start array, rebuild) and this morning after the rebuild was completed it says the new drive is also unmountable, on top of that now i have a red x on parity as well.  I still have the old drive in the box just unassigned so i mounted it using the Unassigned Devices plugin and i can view all of the data that was on the drive in the first place.

 

My question is more so how to handle this now. Do i format the the newly rebuilt drive and then correct my parity somehow then transfer data from the apparently ok drive back to the array?

 

Whats my best process here for not losing data and making everything happy again.

storage-diagnostics-20160407-0822.zip

I had a drive go unmountable on Monday so last night i went through the normal process of swapping drives (Stop array, unassign drive, start array, stop array, add new drive, start array, rebuild) and this morning after the rebuild was completed it says the new drive is also unmountable

 

This is expect, rebuilding will fix a failed (disabled) disk, not an unmountable one, these are usually caused by filesystem issues.

 

Start by posting diagnostics (tools > diagnostics).

Diagnostics added to first post. For reference (not sure if it matters) sdp is the original drive, sdl is the newly rebuilt drive.

Parity disk dropped offline, so there's no SMART info.

 

Shutdown server, check/replace parity cables, power on and post new diagnostics.

Your log show errors on various disks, probably all connected to the same controller:

 

Parity and disks 3,8,9,11,12 and 13

When i stopped the array the slot the parity disk is supposed to be in was empty and the parity disk was listed in the unassigned devices section. I rebooted and when it came back online the correct drive was assigned to the parity slot. I started the array back up but the parity drive still has a red x. I ran a smart test and it passes everything. Im not sure diagnostics will help since its still red x but i have attached that and the syslog below.

storage-diagnostics-20160407-0951.zip

storage-syslog-20160407-0951.zip

Your issues are probably caused by the controller connected to the disks listed above.

 

 

I swapped controller cards and my parity is still at a red x. I have attached updated diagnostics as well

storage-diagnostics-20160407-1257.zip

I swapped controller cards and my parity is still at a red x. I have attached updated diagnostics as well

it will stay a red x until it has been rebuilt.

@itimpi - so what is my next step? I have never rebuilt parity before so im not sure i know how to do that. Also, what do i do with the rebuilt drive that is still unmountable?

If parity is the only drive with red X then you rebuild it just like any other. You may have to start the array with it unassigned first to get unRAID to "forget" it. Then stop, assign, start to rebuild.

 

The unmountable drive will have to be corrected with filesystem tools. Search wiki for Check Disk File Systems.

@trurl - would you recommend taking care of parity first then dealing with the unmountable drive or vice versa?

 

Also, i just ran a reiserfsck --check on the unmountable drive and it tells me it cant find the superblock

Also, i just ran a reiserfsck --check on the unmountable drive and it tells me it cant find the superblock

What was the exact command you ran?  Often this message is due to an incorrect device name being used.

I used: reiserfsck --check /dev/sdl1

Are all your data drives ReiserFS?

 

You do have one disk with one pending sector, but with your drive count I think I would go ahead and build parity. Then you would deal with the filesystem by using md# instead of sdX1 in the command.

A majority of my drives are ReiserFS but the newest drives i have added are xfs. Do i need to remove the unmountable drive before i rebuild parity or does it really not matter. Also, if i leave it in should i repair that drive before rebuilding parity?

A majority of my drives are ReiserFS but the newest drives i have added are xfs. Do i need to remove the unmountable drive before i rebuild parity or does it really not matter. Also, if i leave it in should i repair that drive before rebuilding parity?

Well I sort of already answered all this in my previous, but to clarify:

 

If you remove the unmountable drive before rebuilding parity then you will have to New Config and rebuild parity again when you add the other drive back.

 

You can repair the filesystem after building parity by specifying the md# device instead of the sdX1 partition. For example if it is disk8 then you would do the rebuild on md8 instead of sdl1. Using the md device includes parity in any corrections written so parity will be maintained. All this is covered in the wiki article.

I stopped the array, removed the parity drive, started in maintenance mode, stopped the array, re-added the parity drive and started it back up. I got a message stating that a parity-sync had started but nowhere on the main page does it say anything about the parity sync or anything like that. I have attached a screenshot.

Added a syslog

 

EDIT: Now the Parity disk is spun down so it obviously is not doing anything

 

EDIT2: I thought maybe i would try to repair the disk that is unmountable so i ran a reiserfsck --check /dev/md7 as trurl suggested and get: bread: Cannot read the block (2): (Input/output error).

 

if i run reiserfsck --check /dev/sdl1 then it tells me it cannot find the superblock ---- should i do this or try some other method of getting the parity sync to work?

storage-syslog-20160407-1530.zip