tmb

I’ve googled it but can’t decide, the drive works just fine (it’s the 1st of the three disks I have in the box), no performance issues when copying from/to the box. I’m currently on “Armbian 20.11”, barely get the time to play with the setup due to work assignments, plan to update soon. Thanks! (PS. Newbie here) [ 13.298079] ata1: softreset failed (1st FIS failed) [ 18.449169] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 18.467303] ata1.00: ATA-10: ST6000VN0033-2EE110, SC60, max UDMA/133 [ 18.467315] ata1.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 18.470029] ata1.00: configured for UDMA/133 [ 18.470721] scsi 0:0:0:0: Direct-Access ATA ST6000VN0033-2EE SC60 PQ : 0 ANSI: 5 [ 18.472237] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5 .46 TiB) [ 18.472247] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 18.472299] sd 0:0:0:0: [sda] Write Protect is off [ 18.472309] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.472393] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 18.580573] sda: sda1 [ 18.583350] sd 0:0:0:0: [sda] Attached SCSI disk [ 18.949151] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 18.959809] ata2.00: ATA-10: ST6000VN0033-2EE110, SC60, max UDMA/133 [ 18.959822] ata2.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 18.962526] ata2.00: configured for UDMA/133 [ 18.963133] scsi 1:0:0:0: Direct-Access ATA ST6000VN0033-2EE SC60 PQ : 0 ANSI: 5 [ 18.964436] sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5 .46 TiB) [ 18.964451] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 18.964520] sd 1:0:0:0: [sdb] Write Protect is off [ 18.964534] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 18.964651] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 19.017200] sdb: sdb1 [ 19.019847] sd 1:0:0:0: [sdb] Attached SCSI disk [ 19.441176] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 19.450989] ata3.00: ATA-10: ST6000VN0033-2EE110, SC60, max UDMA/133 [ 19.451001] ata3.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 19.453715] ata3.00: configured for UDMA/133 [ 19.454064] scsi 2:0:0:0: Direct-Access ATA ST6000VN0033-2EE SC60 PQ : 0 ANSI: 5 [ 19.455164] sd 2:0:0:0: [sdc] 11721045168 512-byte logical blocks: (6.00 TB/5 .46 TiB) [ 19.455178] sd 2:0:0:0: [sdc] 4096-byte physical blocks [ 19.455248] sd 2:0:0:0: [sdc] Write Protect is off [ 19.455262] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 19.455378] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 19.507285] sdc: sdc1 [ 19.509063] sd 2:0:0:0: [sdc] Attached SCSI disk [ 19.767590] ata4: SATA link down (SStatus 0 SControl 300) [ 20.079588] ata5: SATA link down (SStatus 0 SControl 300)

Hi again, Yes, the lights were solid blue after boot (power and hdds, nothing else), so the comment about not getting a clean boot make sense. I was monitoring the router but no ip was coming up for it, so this again makes sense as it wasn’t really booting with the sd card. Here’s what actually worked last evening (don’t remember the exact order): - Changed the sd card image from Armbian_20.08.13_Helios4_buster_current_5.8.16.img to Armbian_20.11_Helios64_buster_current_5.9.10.img (yes, using Etcher), initially I was using the older image for what seemed to be stability reasons… - Before burning the image again - reformatted the card from exFAT to FAT in Windows 10 (as mentioned, not really much experience with Linux so this might have been the cause) - Moved the device from the left side of my desk to the right It powered up and connected via usb - COM6 with my desktop as I was checking anyway every time before trying (for example desktop was always COM6, laptop always COM3). Looks fine now, power light on, system light blinking, no hdd lights (as I don’t have any yet). Even installed OMV which took about 20 mins, but I am able to access it. Now off to buying disks, fun times ahead Thanks for your time, people!

Hey, thanks! I’ve seen the Maskrom and will keep it as a last option for two reasons: - I’d still like to boot from the sd card – just to experiment with the device and decide on the final setup. - It looks a bit more complicated (or risky). I will still try to test & understand why I cannot boot from the sd card yet.

Hi folks, I got my helios64, assembled it during the weekend and can’t seem to actually install it. Here are some of the things I tried (I'm on windows 10 btw, I don’t have hdd drives yet, I assume this would not be an issue): · 2 sd cards (one of which is a Samsung as recommended in the wiki), two computers (with correct com ports as visible in the device manager, driver is installed), tried both on usb2 and usb3 · USB cable has been trimmed to fit the case properly - also tried with the back panel off and directly connected to the board · the devices starts up as soon as I plug in the power cord - I then use the power button to shut if off, then open the console and start it up (I did use the 4 seconds to shut it off and make sure the leds are not on) · (when I plug it in, the system light turns on red for just a millisecond, and then off, and all other light blue) After start-up: - No light on the system led, not even blinking. - Power and hdd leds are all blue (constant on). Anything I should be trying next? Thanks for reading. PS. Not really much an expert on linux, last time I used it was years ago when I was tweaking my prior nas.