Unmountable disk(s) present

[cybrey]

I had an unmountable disk (2TB) present which I thought was a dead disk. So I precleared a new 3TB disk and went to add it in to replace the disk. I now have a completely different 2TB showing as unmountable and the new 3TB disk is also showing the same. 

 

I have done some reading around but I'm a bit of a loss what to do. Attached is the output from the diagnostics. I've also run reiserfsck --check which has shown 0 errors. 

 

 

Any help would be greatly appreciated.

 

 

 

tower-diagnostics-20171021-1305.zip

[JorgeB]

You have two invalid disks with single parity, so you're beyond your current redundancy.

 

 

[JorgeB]

As for the best way to proceed, disk2 dropped offline, you'll want to power off, check cabling, power back on and grab new diags.

 

Is old disk7 still readable or is it completely dead?

[cybrey]

I dropped disk7 back in and rebooted. It wasn't visible at all. 

 

I then powered the machine down, removed the old disk7 and put the new 3TB disk in. The WebGui won't come up now. 

 

On watching the boot there is a significant delay with the following message "ata10: COMRESET failed.. retrying". 

[JorgeB]

ATA10 was disk5 on previous diags, though it may have changed on reboot, check cabling on all disks.

[cybrey]

Thank you for your help so far, its hugely appreciated. 

 

The cable to disk 5 was very loose and not fitting snuggly, so I swapped it out for a new one and the machine booted. (Thankfully)

 

I'm back in the same position (see original screenshot) I was in before though. I've run diagnostics again and attached. 

 

 

tower-diagnostics-20171021-1537.zip

[JorgeB]

Disk2 is back online but SMART is disable, on the console type:

 

smartctl -s on /dev/sdg

 

Then grab and post new diags.

[cybrey]

Command ran successfully and SMART enabled, new diags below. 

tower-diagnostics-20171021-1555.zip

[JorgeB]

SMART looks fine, there are a few CRC errors, so disk2 most likely went offline due to a bad cable or connection, you may want to replace it also just to rule it out.

 

Now if old disk7 is dead your options are limited, you can try this, it should work but it may not depending on the sequence of events that left you with the two invalid disks, but first you need to update unRAID, you're running a very old release that has a trust parity bug, so first update to v6.3.5, reboot, confirm that you're now on v6.3.5 and then do this:

 

-Tools -> New Config -> Retain current configuration: All -> Apply

-check all assignments and if needed assign any missing disk(s), use the new 3TB disk for disk7

-check both "parity is already valid" and "maintenance mode" before starting the array

-start the array

-stop array, unassign disk7

-start array, check that disk2 and emulated disk7 mount and contents look correct

-if either fails to mount grab and post new diags, if both mount proceed

-stop array, reassign disk7

-start array to begin rebuild

 

 

[cybrey]

I'll update to v6.3.5 now and come back in a few hours (Need to work out how to update first)

[cybrey]

Disk2 is back!! 

 

 

Its still saying Disk7 is unmountable, however its started rebuilding the array?

 

 

 

[cybrey]

I think we're all good now; 

 

The parity sync is running (will be done in 16 hours). 

 

Many many thanks for your help!!

 

Going to try and work out how I can get a second parity into the machine now. I have physical space, just no free SATA ports. 

 

 

[JorgeB]

I posted to stop if one the disks was unmountable, but it's not a problem to continue, just no point in rebuilding if the filesystem is unfixable, though since it's reiser it should be fixable, let the rebuild finish, and then run reiserfsck on disk7:

 

-stop the array

-start the array in maintenance mode

-on the console type:

 

reiserfsck /dev/md7

Post the output if in doubt on how to proceed.

[JorgeB]

Just now, cybrey said:

I think we're all good now; 

 

Looks like you formatted disk7, was it empty?

[cybrey]

Yes was entirely empty, was the brand new disk. 

[JorgeB]

3 minutes ago, cybrey said:

Yes was entirely empty, was the brand new disk. 

 

Good, I though it contained data, all good then, just let the rebuild finish.