Had a power loss and my apcupsd settings weren't set properly (lack of testing on my part!), and upon reboot, my server comes up and:

 

• I cannot access via HTTP via 10.0.1.4:81, which is the pprt emhttp is running on. TCP pings using psping show the port is open and responding, and `ps -aux | grep http` shows it's emhttp is running, but I receive a "connection reset" from Chrome/IE/Edge, etc.

• root@LennyR4:/mnt# ps -aux | grep http
  root      5228  0.0  0.0  19952  3640 ?        S    09:25   0:00 /usr/local/sbin/emhttp -p 81

• I can access via SSH
• Docker is not running any longer, /mnt/user/docker doesn't exist - uses BTRFS RAID 1 cache drives

• root@LennyR4:/mnt# docker ps
  Cannot connect to the Docker daemon. Is the docker daemon running on this host?

• Cannot connect to SMB shares, though smbd is running.
• It appears that some disks are missing from /mnt, though all show up in /dev/sd*. Note that not all disks are in the array, there are some that are unmounted and sitting in "Unassigned Devices" plugin waiting for a use. I can't tell you which at the moment, of course, since the Web UI won't load for me.

  root@LennyR4:/mnt# ls /mnt
  cache/  disk1/  disk10/  disk11/  disk12/  disk13/  disk14/  disk15/  disk2/  disk3/  disk4/  disk5/  disk6/  disk8/  disk9/  disks/  user/
  root@LennyR4:/mnt# ls /dev/sd*
  /dev/sda   /dev/sdc   /dev/sde   /dev/sdg   /dev/sdi   /dev/sdk   /dev/sdm   /dev/sdo   /dev/sdq   /dev/sds   /dev/sdu   /dev/sdw   /dev/sdy
  /dev/sda1  /dev/sdc1  /dev/sde1  /dev/sdg1  /dev/sdi1  /dev/sdk1  /dev/sdm1  /dev/sdo1  /dev/sdq1  /dev/sds1  /dev/sdu1  /dev/sdw1  /dev/sdy1
  /dev/sdb   /dev/sdd   /dev/sdf   /dev/sdh   /dev/sdj   /dev/sdl   /dev/sdn   /dev/sdp   /dev/sdr   /dev/sdt   /dev/sdv   /dev/sdx
  /dev/sdb1  /dev/sdd1  /dev/sdf1  /dev/sdh1  /dev/sdj1  /dev/sdl1  /dev/sdn1  /dev/sdp1  /dev/sdr1  /dev/sdt1  /dev/sdv1  /dev/sdx1

   

 

I've linked the diagnostics zip from my Dropbox folder that I ran via SSH, and would love some assistance on figuring out what's going on and what I can do. 

 

Diagnostics:

lennyr4-diagnostics-20170303-0944.zip

Edited March 3, 20179 yr by ryanborstelmann

Update: since /dev/disk7 was missing from boot, and I noticed a load of issues with it in the Syslog, I ran xfs_repair -v /dev/md7, then xfs_repair -v -L /dev/md7. Once this completed (one minute or so), I was able to start the array.

 

No user shares were present, but I was now able to perform a clean shutdown and reboot, after which everything looks solid. Will run a parity check just in case, but this can be considered solved.