JPW

  • Content Count

    3
  • Joined

  • Last visited

  1. A few updates on my testing: As there did not seem to be a cable problem, I swapped the Sata port 1 and 2 cables back to match the wiki build document. Note: the UPS battery is not connected. I did attempt to downgrade the Seagate Barracuda SSD 120 1TB to 3.1 specifications. The downgrade failed on an error so that avenue has been abandoned. I acquired a new Samsung SSD 860 EVO 1 TB hoping that it works better than the Cuda 120 SSD. I retested 5 different drives on each Sata port. The drives were WD RED 10TB #2 (two Red 10TB drives tested are labeled #2 a
  2. I installed Debian/Armbian 5.8 image from Kobol wiki: Armbian_20.08.21_Helios64_buster_current_5.8.17.img.xz I swapped the cables for Sata 1 and Sata 2 ports. The SSD drive was not recognized on either port. So, back to basics. Using a single WD Red 10TB HHD (factory fresh: no portioning, no formatting), I tested each slot. The WD HHD was recognized on all 5 Sata ports. So, not a cable problem. Repeating the process with the Seagate Barracuda SSD 120 drive (factory fresh), the SSD is not visible on ports 1, 2, 3, and 4 but is visible on Sata port 5. With a 2nd factor
  3. I just received my Helios64 system and built it today. The build included 3 drives, a SSD in port 1 and two HHD's on port 2 and 3. After the build, I installed Debian Kernel: 5.8 on an micro SD card. The system booted but only showed the drives in port 2 and 3. I have moved the drive in port 1 to port 4, rebooted and the SSD drive shows up. Also, a HDD in port 1 does not show up: no blue Light on the front panel and not visible in "fdisk -l" . The output from ' dmesg | grep "ata" ' results in: with the 'ata1: SATA link down (SStatus 0 SControl 300)' message repeating a