lloyd094

Okay - I have tested each drive twice: once on SATA_1 and once on SATA_4. Here's the results: Alpha SATA_4 | http://ix.io/20Qx SATA_1 | http://ix.io/20Qy Beta SATA_4 | http://ix.io/20QB SATA_1 | http://ix.io/20QA Charlie SATA_4 | http://ix.io/20QD SATA_1 | http://ix.io/20QE Delta SATA_4 | http://ix.io/20QH SATA_1 | http://ix.io/20QG (Delta has click of death - time to RMA this one)

Actually I do! I replaced them, but no luck :-/ http://ix.io/20Qt

Thanks for providing me with the instructions to follow for troubleshooting. I believe that it is indeed a board issue unfortunately: Sequence 1 | Sequence 2 | Sequence 3 Let me know if there's something else I should try, and as always thanks for the help.

Okay, I finally got things up and going system-wise. The updated OS actually seems a good deal more stable than the image I originally had too! However, I am still running into the issue of not getting all my drives detected. I have four 5TB HDDs in the system, though it only appears to detect two of them. armbianmonitor -u I appreciate the help so far!

Wow. I feel incredibly stupid. Well, thanks for the help on that. I'll play with it tomorrow, and I'll see if it all goes smoothly. I hope the system was just borked instead of something going bad.

Well, I went through probably 5 beforehand. Guess the sixth one worked. Unfortunately I can only get so far though, as i get a loop upon attempting to set password (I've reimaged the SD card a few times to be sure): Debian Buster with Armbian Linux ttyS0 helios4 login: root Password: You are required to change your password immediately (administrator enforced) Changing password for root. Current password: Authentication token manipulat Debian Buster with Armbian Linux ttyS0

Unfortunately, no - nothing as a COM port is shown, even with the drivers as instructed in the wiki. It simply doesn't show anything. As for SSH and the HDD drop, I wiped the system when I was first troubleshooting because I thought it was the installation itself that got borked. So beforehand, I remember looking though via SSH seeing errors saying that the system could not find the HDDs as previously mentioned. At one point in troubleshooting it appeared that part of it could have been due to connections with the wiring, but it didn't seem to be the wires themselves - hence why I think the board possibly died. So, the only option I can do to get into the device is through the COM port so I can finish setting up the new OS image.

Hey, so that's part of the problem - I can't seem to log in via the Com port. No matter what I do, or on what computer I've tried, I cannot get the com port to show up.

Just tested - fortunately (or unfortunately), DC voltage on both molex connectors appear to be within the listed values above.

LED1 is blinking, but I'm wondering if somehow the board is dying? It might explain why the hard drives started dropping like flies on the system itself, but when I tested them elsewhere they were fine. When it comes to the Com port connection, I set it up myself when I first got the device. Now it doesn't seem to want to communicate at all, and I've tried connecting with two different computers (both Win10).

I am running into a strange issue I can't seem to resolve. Recently I've noticed that some of my drives have stopped responding (I figured bad drives), but upon testing them in another system, they work just fine. I have wiped my system and made a new SD with the latest image, but cannot log in via the COM port (Windows 10). I have followed the instructions given on the Wiki to ensure I've done the right steps. The device itself has a few lights (if it helps): (1) green light by the power port, (2) LED1 near the reset button, and (3) blinking yellow light on the LAN port. Any help would be greatly appreciated. This has been a good headache so far.