DigitalMaestro

Thank you for all the feedback and help. I think removing those lines may have done the trick! Now the "Starting go script" is immediately followed by "Starting emhttpd" Also the web GUI is now active much faster. I was accustomed to waiting 30 seconds to a minute after the login prompt appeared on the monitor after bootup before I could load the web GUI in the browser from another computer. Now the browser can navigate to the web GUI almost immediately after the login prompt appears. System auto started as expected. Since the failure was intermittent, I'll need to see a few shutdown cycles before I am 100% certain that the problem is resolved but I'm pretty sure it is. Thanks once again! DM

My old system had Marvell controllers. New system does not. I simply built the new system then moved the disks and flash drive over. Was there something I needed to do the clean up the go file? Any other file cleanup required? Thanks DM

Yes, the BIOS is configured to automatically (re)start the computer when power is applied. DM

I do have auto-start enabled in Disk Settings. Scenario: I am testing the UPS shutdown settings. Unraid successfully initiates shutdown once the UPS hits the defined runtime. When I plug the UPS back into the mains, the computer restarts. Unraid loads successfully but does not start the array (array status is 'Array Stopped'). However the array configuration is shown as valid in the "Main" section. Interestingly, if I then click the Reboot button, Unraid reboots and subsequently auto-starts the array as expected. Is there an additional configuration step needed to enable auto-start after UPS shutdown? Diags attached (created after first reboot from UPS shutdown when array did not auto-start). Any insight appreciated. Edit: I went ahead and tested three scenarios after this auto-start failure to see if I could glean anymore insight Reboot - Unraid auto starts properly Shudown - After manually powering up the computer Unraid auto starts properly UPS shutdown - In this case Unraid did auto start correctly. So it appears that the issue may not be UPS related after all. The core question is thus: Why would Unraid intermittently not auto start even though it reports the array configuration as valid? Thanks DM diagnostics-20220415-1431.zip

Many, many thanks to the OP for starting this thread and persevering to a solution. I recently obtained an APC SMT1500C and was experiencing the same issues. This thread saved me countless hours of troubleshooting. I could not find the cable indicated (AP940-0625A) at a reasonable price but I did find another cable that works, AP940-1525A, at a price I could stomach. The cables are equivalent, the only difference being that the AP940-1525A is 15 feet versus 6 feet for the AP940-0625A. So this provides an alternative for anyone having trouble finding the cables. I can confirm that the AP940-1525A is working in my setup. Thanks again D

Upgraded a few days ago from 6.5.3 to 6.6.5. Everything has been running smoothly since (including Dockers and VMs). Cheers DM

I ran into a similar situation recently. I converted my physical Windows 10 machine to a VM on unRaid and also could not get it to activate. I actually phoned Microsoft support and they recommended that I chose "Change Product Key" from the activation dialog and then re-enter the product key from the OEM licence. In my case that worked. DM

To close the loop on this topic (and to aid anyone doing a Google search), I never got this to work. Based on research in this forum and others I instead purchased this adapter from Startech and it performs like a champ. I can now access all drives in my external hard drive dock. Cheers DM

On further research in this forum I discovered this link. I did try the suggestions in that post but to no avail. It seems that the OP's problem from that post was that no drives connected to the controller were recognized whereas I see the first drive but no others. Not withstanding that , I think the post is onto something. In my case, I think the wrong driver is being loaded. I used lspci and noticed that the driver loaded for my Marvell 88se61xx chip is the IDE driver whereas I want the SATA controller driver loaded (the SATA driver would presumably be able to use the port multiplier feature). There is another Marvell chip on my motherboard which provides two internal SATA 6G ports and the correct driver is loaded for that chip. If there is a SATA controller driver for the Marvell 88SE61xx then how do I force it to load? Thanks DM

Understood, thanks. However given that I only have one desktop computer and need to preserve the current Windows install until I have fully configured unraid and can then run the Windows install as a VM then I was hoping this route would work. I don't have enough drive bays/ports to contain both the current Windows install and the new unraid install hence my need to run the unraid install temporarily via the 4 bay port multiplier dock. Regards DM

Hi, I am looking to build an unraid server and am testing functionality before making a purchase. I have an existing computer running Windows. My plan is to convert this computer to an unraid server and run the existing Windows install as a VM. However I have run across an issue. I would like to configure unraid while still keeping my existing Windows install active (since it is currently a media server for the home). To that end I bought a Mediasonic 4 bay eSATA dock with the intent to use this dock to hold the drives for the unraid array while I configure them. Once configured and confirmed working I could then move the drives into the system proper and boot the Windows install as a VM. My motherboard is an Asus P7H57D-V EVO with an eSATA port powered by a Marvell 88SE6111 (aka 88SE6121) chip. This chip supports the port multiplier function required by the aforementioned 4 bay dock. The dock works fine in Windows. If I install multiple drives in the dock then I can see all of the drives in the Windows disk manager so this confirms that the port multiplier feature is working correctly. However when I boot with unraid I only see one drive in the dock even if multiple drives are installed. Is there some special configuration needed to activate port multiplier support? This is critical for me as I need to be able to use the dock to configure unraid before moving the drives to the chassis so that I can preserve the ability to boot into Windows until everything is converted (no available SATA ports left on the motherboard that I can use for unraid hence the need for the 4 bay dock) Can someone please assist? Thanks in advance DM