Ebein

Nov 20 21:04:47 AVA emhttpd: shcmd (31): /usr/local/sbin/set_ncq sde 1 Nov 20 21:04:47 AVA root: set_ncq: setting sde queue_depth to 1 Nov 20 21:04:47 AVA emhttpd: shcmd (32): echo 128 > /sys/block/sde/queue/nr_requests Nov 20 21:04:47 AVA kernel: mdcmd (39): start STOPPED Nov 20 21:04:47 AVA kernel: unraid: allocating 25980K for 1280 stripes (5 disks) Nov 20 21:04:47 AVA kernel: md1: running, size: 7814026532 blocks Nov 20 21:04:47 AVA kernel: md2: running, size: 7814026532 blocks Nov 20 21:04:47 AVA kernel: md3: running, size: 7814026532 blocks Nov 20 21:04:47 AVA emhttpd: shcmd (33): udevadm settle Nov 20 21:04:47 AVA emhttpd: Autostart disabled Nov 20 21:04:47 AVA kernel: mdcmd (40): stop Nov 20 21:04:47 AVA kernel: md1: stopping Nov 20 21:04:47 AVA kernel: md2: stopping Nov 20 21:04:47 AVA kernel: md3: stopping Nov 20 21:04:48 AVA avahi-daemon[3231]: Server startup complete. Host name is AVA.local. Local service cookie is 2026875622. Nov 20 21:04:49 AVA avahi-daemon[3231]: Service "AVA" (/services/ssh.service) successfully established. Nov 20 21:04:49 AVA avahi-daemon[3231]: Service "AVA" (/services/smb.service) successfully established. Nov 20 21:04:49 AVA avahi-daemon[3231]: Service "AVA" (/services/sftp-ssh.service) successfully established. Nov 20 21:04:49 AVA kernel: r8169 0000:18:00.0 eth0: link up Nov 20 21:04:49 AVA kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Nov 20 21:04:51 AVA ntpd[1888]: Listen normally on 3 eth0 192.168.1.200:123 Nov 20 21:04:51 AVA ntpd[1888]: bind(22) AF_INET6 fe80::329c:23ff:fee3:7408%11#123 flags 0x11 failed: Cannot assign requested address Nov 20 21:04:51 AVA ntpd[1888]: unable to create socket on eth0 (4) for fe80::329c:23ff:fee3:7408%11#123 Nov 20 21:04:51 AVA ntpd[1888]: failed to init interface for address fe80::329c:23ff:fee3:7408%11 Nov 20 21:04:51 AVA ntpd[1888]: new interface(s) found: waking up resolver Nov 20 21:04:51 AVA avahi-daemon[3231]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::329c:23ff:fee3:7408. Nov 20 21:04:51 AVA avahi-daemon[3231]: New relevant interface eth0.IPv6 for mDNS. Nov 20 21:04:51 AVA avahi-daemon[3231]: Registering new address record for fe80::329c:23ff:fee3:7408 on eth0.*. Nov 20 21:04:54 AVA ntpd[1888]: Listen normally on 5 eth0 [fe80::329c:23ff:fee3:7408%11]:123 Nov 20 21:04:54 AVA ntpd[1888]: new interface(s) found: waking up resolver Nov 20 21:04:54 AVA avahi-daemon[3231]: Leaving mDNS multicast group on interface br1.IPv6 with address fe80::9c99:cff:fea5:a1ef. Nov 20 21:04:54 AVA avahi-daemon[3231]: Joining mDNS multicast group on interface br1.IPv6 with address 2601:40c:c000:6370:6a1c:a2ff:fe12:9276. Nov 20 21:04:54 AVA avahi-daemon[3231]: Registering new address record for 2601:40c:c000:6370:6a1c:a2ff:fe12:9276 on br1.*. Nov 20 21:04:54 AVA avahi-daemon[3231]: Withdrawing address record for fe80::9c99:cff:fea5:a1ef on br1. Nov 20 21:23:20 AVA ntpd[1888]: receive: Unexpected origin timestamp 0xdf9f3bca.656d4e7c does not match aorg 0000000000.00000000 from [email protected] xmt 0xdf9f4018.0e585f0f Nov 20 21:23:20 AVA ntpd[1888]: receive: Unexpected origin timestamp 0xdf9f3bca.656f1815 does not match aorg 0000000000.00000000 from [email protected] xmt 0xdf9f4018.106d4f88 Nov 20 21:24:31 AVA nginx: 2018/11/20 21:24:31 [error] 3285#3285: *101 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.6, server: , request: "GET //wsproxy/5700/ HTTP/1.1", upstream: "http://127.0.0.1:5700/", host: "ava" Nov 20 21:24:31 AVA nginx: 2018/11/20 21:24:31 [error] 3285#3285: *103 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.6, server: , request: "GET //wsproxy/5701/ HTTP/1.1", upstream: "http://127.0.0.1:5701/", host: "ava" This is my log after the last crash and restart.

Its plugged into a (USB2.0) 9 pin adapter on the MB.

Logging into the web gui on the server ( couldnt login remotely ) It had forgotten I had cache drives, but remembered the data/parity layout, and reversed my ethernet ports, and forgotten the server name/description. VM's, Dockers and Apps all still in place...

Last 2 nights system has crashed, This morning it reboots to Tower again. This is making me crazy.

And once the parity is done i need to update my key file

Thanks for the help everyone, now to let the Parity run for the next 14 hours

Fantastic! Now we are cooking with gas!

No Joy, still giving me a array stopped invalid configuration

ok ill give that a try

I assigned them all as data, to see which drive was unformated, then set it to no device and tried to move it to parity.

sdd is the parity device ive set it to no device in the array devices, then set it in parity. though now it says invalid array and wont let me start it.

Thanks Frank, will report back shortly

New Samsung 32gb Flash drive, 6.6.5 stable installed. added back the cache drives, added all my HDD as data, how do i determine which are formatted and which aren't after adding them?

Thanks Frank, I've been using the Micro center drive just to test the USB connections, and all of the ports seem to work flawlessly with the microcenter drive where the original Lexar drive would no longer boot reliably, and im guessing it was damaged when the MB bit the dust, I have a Samsung drive(32gb) arriving tomorrow( $10 amazon, gotta love prime ) that I will do the new 'permanent' Install on. Good to know it uses the serial numbers for drive assignment. I have 3x8TB data drives, 1x8TB parity, and 2x500GB cache drives(mirrored?)

The motherboard was replaced also, so I am not sure of the drive assignments as an exact replacement for the board wasn't possible, so I'm unsure if the drive assignments will help unless it uses the Drives serial number or something for the setup. Thanks!