lloyd094
-
Posts
11 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by lloyd094
-
-
25 minutes ago, gprovost said:
Yeah something is really no quite right here. Actually in Test 2 one of the HDD is detected, so could still be a SATA cable/connection issue.
Any chance you have some spare SATA cable from somewhere else that you could try ?
Actually I do! I replaced them, but no luck :-/ http://ix.io/20Qt
-
On 11/3/2019 at 6:56 PM, gprovost said:
@lloyd094 Based on the logs effectively something is wrong with disks attached to SATA port 1 and port 2. Hard to guess what's the root cause.
[ 11.593597] ata1: softreset failed (1st FIS failed) [ 11.594024] ata2: softreset failed (1st FIS failed) [ 21.593168] ata2: softreset failed (1st FIS failed) [ 21.593809] ata1: softreset failed (1st FIS failed) [ 56.593597] ata2: softreset failed (1st FIS failed) [ 56.593600] ata2: limiting SATA link speed to 3.0 Gbps [ 56.594023] ata1: softreset failed (1st FIS failed) [ 56.594026] ata1: limiting SATA link speed to 3.0 Gbps [ 61.805168] ata2: softreset failed (device not ready) [ 61.805171] ata2: reset failed, giving up [ 61.813167] ata1: softreset failed (device not ready) [ 61.813170] ata1: reset failed, giving upYou will have to do the following tests in the exact sequence in order to narrow down the issue.
1. Disconnect the disks connected to SATA port 3 and 4, and see after reboot if then suddenly SATA port 1 and 2 works. If it works, then maybe still an issue with the PSU.
2. Use the cables that was used for SATA port 3 and 4 for SATA port 1 and 2. If it works, then could be bad SATA cables.
3. Use the HDD that was connected to SATA port 3 and 4 with SATA port 1 and 2. If it works, then could be HDD issue, if it doesn't then can be a board issue.
I mean you see the logic, we need to narrow down the issue to understand the root cause.
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.
I appreciate the help so far!
-
13 minutes ago, gprovost said:
@lloyd094 Just to be sure, at the prompt 'Current password' you enter again 1234 ?
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.
-
31 minutes ago, gprovost said:
Have you try with another usb cable ? I have already experienced more than once a usb cable with the microUSB side a bit quirky.
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 -
3 minutes ago, gprovost said:
Do you see under Windows device manager a device detected as something like 'USB Serial Port (COMxx)' ?
Are you able to connect via SSH ?
How do you know the HDDs drop if you can't connect to the console / terminal ?
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. -
6 minutes ago, gprovost said:
Ok then it's time to share some logs in order to see what happen when the disks drop from the system. Start your system with the HDDs connected and run from the terminal armbianmonitor -u then post the generated url link here.
How long your system has been running without issue before you start realizing this issue with dropping HDD ?
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.
-
18 hours ago, gprovost said:
Do you have multimeter/voltmeter? Could you measure DC voltage on molex power connector shown on photo below?
Expected measured value,
on 5V rail: 4.90 V - 5.20 V
on 12V rail: 11.90 V - 12.5 V
If 5V is outside that range, that mean the onboard regulator is faulty (board problem).
If 12V is outside that range, that mean the power supply is faulty.
Just tested - fortunately (or unfortunately), DC voltage on both molex connectors appear to be within the listed values above.
-
On 10/28/2019 at 8:16 PM, gprovost said:
Based on what you say it seems LED1 is ON, but do you see it blinking ?
If yes, then it means your system is up and running, therefore your issue is effectively on establishing the serial connection.
If no, then it means something else is wrong and that could explain why you don't see anything on the serial console.
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.
Helios4 Support
in Marvell mvebu
Posted
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)