I have set the "Enable auto start" to "Yes" in Settings -> "Disk Settings". Tried multiple reboots (1) with or without this options = yes/no and (2) with array status staying at "started"/"stopped"  prior to reboot (all combination) but no luck. Looking at the systemlog and the only 2 suspicious log messages seem to be 

Sep 24 13:37:16 Tower emhttpd: shcmd (6): /sbin/modprobe md-mod super=/boot/config/super.dat
Sep 24 13:37:16 Tower kernel: md: unRAID driver 2.9.27 installed
>>>(1)>>>Sep 24 13:37:16 Tower emhttpd: error: get_limetech_time, 286: Connection timed out (110): -2 (7)
>>>(1)>>>Sep 24 13:37:16 Tower emhttpd: Unregistered Trial - no connection (ENOCONN)
Sep 24 13:37:16 Tower emhttpd: Device inventory:
Sep 24 13:37:16 Tower emhttpd: ST1000DM003-1SB102_Z9ACL8WA (sdb) 512 1953525168
Sep 24 13:37:16 Tower emhttpd: USB_SanDisk_3.2Gen1_0101185f2af97aa23644da3d94d11df5c02b3e55a9576b7ef29537f3de3 (sda) 512 30081024
Sep 24 13:37:16 Tower kernel: mdcmd (1): import 0
>>>(2)>>>Sep 24 13:37:16 Tower kernel: md: import_slot: 0 empty
Sep 24 13:37:16 Tower kernel: mdcmd (2): import 1 sdb 64 976762552 0 ST1000DM003-1SB102_Z9ACL8WA
Sep 24 13:37:16 Tower kernel: md: import disk1: (sdb) ST1000DM003-1SB102_Z9ACL8WA size: 976762552 
Sep 24 13:37:16 Tower kernel: mdcmd (3): import 2
Sep 24 13:37:16 Tower kernel: mdcmd (4): import 3
Sep 24 13:37:16 Tower kernel: mdcmd (5): import 4
Sep 24 13:37:16 Tower kernel: mdcmd (6): import 5
Sep 24 13:37:16 Tower kernel: mdcmd (7): import 6
Sep 24 13:37:16 Tower kernel: mdcmd (8): import 7
Sep 24 13:37:16 Tower kernel: mdcmd (9): import 8
Sep 24 13:37:16 Tower kernel: mdcmd (10): import 9
Sep 24 13:37:16 Tower kernel: mdcmd (11): import 10
Sep 24 13:37:16 Tower kernel: mdcmd (12): import 11
Sep 24 13:37:16 Tower kernel: mdcmd (13): import 12
Sep 24 13:37:16 Tower kernel: mdcmd (14): import 13
Sep 24 13:37:16 Tower kernel: mdcmd (15): import 14
Sep 24 13:37:16 Tower kernel: mdcmd (16): import 15
Sep 24 13:37:16 Tower kernel: mdcmd (17): import 16
Sep 24 13:37:16 Tower kernel: mdcmd (18): import 17
Sep 24 13:37:16 Tower kernel: mdcmd (19): import 18
Sep 24 13:37:16 Tower kernel: mdcmd (20): import 19
Sep 24 13:37:16 Tower kernel: mdcmd (21): import 20
Sep 24 13:37:16 Tower kernel: mdcmd (22): import 21
Sep 24 13:37:16 Tower kernel: mdcmd (23): import 22
Sep 24 13:37:16 Tower kernel: mdcmd (24): import 23
Sep 24 13:37:16 Tower kernel: mdcmd (25): import 24
Sep 24 13:37:16 Tower kernel: mdcmd (26): import 25
Sep 24 13:37:16 Tower kernel: mdcmd (27): import 26
Sep 24 13:37:16 Tower kernel: mdcmd (28): import 27
Sep 24 13:37:16 Tower kernel: mdcmd (29): import 28
Sep 24 13:37:16 Tower kernel: mdcmd (30): import 29
>>>(2)>>>Sep 24 13:37:16 Tower kernel: md: import_slot: 29 empty

However I am not sure if one of them are the root cause or actually no of them are.

Some clue that I can think of

1. I am still on a trail license which may have some limitation. However this seems not true because I could not find any documentation on the website regarding this.

2. The Sandisk flash drive was reported it comes without a GUID. I managed to install manually following an official guide. I am wondering if the "malfunctioning" flash drive is causing the trial license not binded correctly?

3. The HW that I am running Unraid is a QNAP 462 NAS (yeah.. I know it sounds ridiculous because it is shipped with a charged SW. I just like the small form of factor and it can sit near my desk) but I doubt it's the least possible cause. Again, I am not sure regarding this.

I am looking for any suggestions/hints/answers to help me out. Thanks a lot.

 

tower-diagnostics-20240925-2027.zip

Edited September 25, 20241 yr by baoooooo

The LAN connection is taking a long time to come, and it's still not up when Unraid checks the license:

 

Sep 24 13:37:16 Tower emhttpd: error: get_limetech_time, 286: Connection timed out (110): -2 (7)

 

Is the LAN really only 100Mbits?

 

Sep 24 13:37:18 Tower dhcpcd[1088]: br0: carrier acquired
Sep 24 13:37:18 Tower kernel: bond0: (slave eth0): link status definitely up, 100 Mbps full duplex
Sep 24 13:37:18 Tower kernel: bond0: (slave eth0): making interface the new active one

 

No.. it's a NAS essentially. It comes with 2 *2.5Gb Ethernet port. Thanks for your input - I might need to have a test with it's original software to verify its builtin NICs(although it's a new HW just purchsed. ). 

Linking at 100Mbit could indicate a cable or switch problem, or even the NIC, and be the reason why it's taking so long.

Really appreciate. Yes, it is exactly the reason. The built-in NICs are proven good after my test. The malfunctioning part  is either the network cable or the RJ 45 port. I moved my NAS to another room and connected to a different port , now everything is fine. 

Guess that I would spend some time diagnostic which part of the cable/port goes wrong.

 

Thanks!

The cable would be my first suspect.   A 100 Mbps connection only requires 2 twisted pairs in the cable to be functioning correctly, whereas the faster speeds all require 4 twisted pairs.

Absolutely right. I didn't pay attention to the link speed info before JorgeB pointed out this 😅