Disk 2 was a new drive, i formatted it but it wont join the array.

 

this is the first time i have ever added a new drive.

 

Edited April 15, 20179 yr by Greygoose

You should post your diagnostics before you reboot / shut off

 

disk 2 is part of the array (otherwise it wouldn't be appearing in the first pic).

disk 1 got disabled pretty much at the beginning of array start (based upon the number of reads / writes to it).  Odds on since this happened when you added disk 2 is that you slightly jarred the cabling to disk1.  Reseat all the cabling to all the drives at both ends.

 

After that, and resetting the system, you will have to stop array, set disk 1 to be not installed, start array, stop array, set disk 1 back to what its supposed to be, start array and it will begin to rebuild.

Thanks Squid,

 

Here is diagnostics file, ill do as you say.

 

 

mediaserver-diagnostics-20170415-1237.zip

Diags were after you reboot, so nothing of any consequence as to what led up to the disabling of the drive.  SMART is clean on it short of a single pending sector (which when you rebuild will either become a reallocated sector or show more pendings)

 

Its more curious as to why disk1 can't be written to though.  There's no mounting errors of the emulated drive that I see.  But we'll jump off that bridge when we hit it.

 

Disk1 is completely full, and because of Downloads share setting it's not writing to disk2:
 

# Generated settings:
shareComment=""
shareInclude="disk1"

Remove disk1 from the included disks (or add disk2)

Edited April 15, 20179 yr by johnnie.black

9 minutes ago, johnnie.black said:

Disk1 is completely full, and because of Downloads share setting it's not writing to disk2:

I didn't even look at the screen shot, but df shows that it's not hence my comment

/dev/md1        1.9T  1.7T  183G  91% /mnt/disk1
/dev/md2        1.9T  131M  1.9T   1% /mnt/disk2

 

1 minute ago, Squid said:

I didn't even look at the screen shot, but df shows that it's not hence my comment

/dev/md1        1.9T  1.7T  183G  91% /mnt/disk1
/dev/md2        1.9T  131M  1.9T   1% /mnt/disk2

 

 

That is strange, I've seen disparity before with btrfs, don't remember seeing that with xfs, OP should run xfs_repair on that disk.

Hi,

 

Ok it looks like Squid comment has resolved the issue.

 

Johnnie, the screenshot was taken before the log file was posted and i deleted a file to free up some HDD space.

9 minutes ago, Greygoose said:

Johnnie, the screenshot was taken before the log file was posted and i deleted a file to free up some HDD space.

 

OK, that makes sense, so you just need to remove disk1 from the included disks.