[NOT SOLVED]Motherboard Replaced... now what

[whipdancer]

Based on the screen-shot you attached, Unraid is expecting a drive in the #3 slot.

I haven't reduced/expanded the number of data drives in several years so this may have changed...

If you previously had all 4 drives as data, then (I think I remember this correctly) you need to remove from your last data slot (#4 in your case). I don't think you can fill the data slots out of order.

Regardless, I don't think you can have #3 empty and #4 filled.
 

[Ebein]

ok ill give that a try

 

[whipdancer]

Ok, just look at your diagnostics file. I see that you had 3 data drives.

I think moving the drive that is in #4 to #3 should work.

[Ebein]

No Joy, still giving me a array stopped invalid configuration

[Frank1940]

Let's try this.  You now have a picture of how you want the drives assigned  (your screen capture).  Stop the array.   Go to   Tools   >>>  New configuration 

 

Then click Retain current configuration:, then select None, then check Yes I want to do this, click Apply then Done.  Go back to the Main page and verify that all of the disk are assigned to the proper slots. (You use the serial  numbers to do this.)  Now click the Start button.  

[Ebein]

Fantastic!  Now we are cooking with gas!

 

[John_M]

38 minutes ago, whipdancer said:

Regardless, I don't think you can have #3 empty and #4 filled.

For the record, you can have gaps. The problem was that, having done a New Config and tried to start the array, you had committed that new configuration. It was only a test, in order to discover which disk was the parity disk, so doing another New Config with everything in the right place was the correct thing to do.

[Ebein]

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

 

[Ebein]

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

 

[itimpi]

18 hours ago, Ebein said:

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.

Once you have determined which drive is parity then the next step is to a Tools->New Config and set up the drives as required before starting the array again.   When you do the New Config I would recommend selecting the option to keep current assignments, and then after doing it return to the Main Tab and make any alterations required before starting the array as this reduces the chances of you making an error.

[Ebein]

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

[Ebein]

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...

[Frank1940]

Be sure that you have the boot drive plugged into a USB2 port (usually, a black plastic insert).  (Some MB/BIOS's USB3 ports have had problems getting properly passed on during the boot process.) 

[Ebein]

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

 

[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.