Unprotected array stopped booting day before my replacement drive arrived

[MrFunbun]

Not sure what the most relevant information to provide is but my eleven disk plus cache array had one drive crap out on me and I, now sadly, continued using it.  It started having issues (file already in use) when I was transferring files to a user share so I went to restart the server but it repeatedly failed to unmount the user shares.  I powered it down and on reboot it would go to the tower login: but has no access to the web interface although the flash drive is mounted as an accessible network drive.  I started doing file system checks on my drives and one came back recommending --rebuild--tree so I did that over night, but it still has the same issue.  If I remove the drive I can boot and access the array via web.  The whole thing seems FUBAR and I am fully ready to accept the loss of data on the drives (although preferably not), but I would like to at least get the whole system running again and fix why having one specific drive in my system is causing such a peculiar bug.

 

Drives in question are 2TB WD blacks, more specifications available but not sure what is relevant.

syslog_2012-14-08.txt

[MrFunbun]

I know that earlier my md2 drive --rebuild-tree hadn't finished but I manage to have it run successfully now but the web interface still won't work although i can pink tower and the flash drive is mounted via network.