Balog Dániel

The manufacturer's data sheet https://www.transcend-info.com/Products/No-642 For the serial console, I am using Putty, I would assume that it's more of a board issue, but when I reconnect, i get some additional communication. For the back USB, I plugged it in prior to power on. Regarding the boot parameter, is that difficult to set up?

Currently I have Helios64_bullseye_current_5.10.63 on the eMMC, and if I remove the SD card, everything works, and I can boot with or without the SSD plugged in. The SD card has bookworm_6.6.36 (and upgrades), the logs are from OS on SD card with boot with and without SSD. The external\internal SSD is that under normal operation, I would have the SSD plugged in, within the closed case (thus 'internal' SSD), that's why it's not trivial to simply unplug it when I need to restart. I have also tested to plug in the SSD after boot (works flawlessly) and to plug this into the back USB (fails, but it just thew an error that COM is disconnected, so not really sure what the actual error is, will keep digging). The SSD notes 1.5 A & 3.3 V, but I can't find any markings on the adapter itself (and the details on Amazon where I got it from are not specifying anything)

@mrjpaxton The setup is 5 disk RAID6 for 'cold' storage (with ~20 minute disk spin down) that I access rarely, and a 'hot' SSD to store downloads, temp files, and anything that's not OS related. The OS should be separated from this (previously it was on MMC, but as I did not have a backup, I lost access due to something and had to reflash, thus losing all config) Regarding the other boot option, Neither HDDs or SSD should not have any boot related files, just data. As for the main question of why it's plugged in in the first place, I use the USB header for the front panel for an internal SSD, but as the board's SSD slot can't be used if you use all 5 disks, this was the best workaround I could find. I would really prefer to boot from SD, as I don't know the expected life of the eMMC, and how badly I may have abused it, so it's safer to expect SD card to fail and plan accordingly. SD Card is UHS Class 3, and I am not doing anything that should need high IO for the OS.

@mrjpaxton I flashed the SD card using etcher, (Armbian_24.5.3_Helios64_bookworm_current_6.6.36_minimal.img), apt-get update && upgrade. Based on the schematics, my best guess is I2C is somehow related to the on-board battery, that's why I was hesitant to disable it (I'll take a look without the SSD drive if it's loaded). I had a misadventure with flashing a corrupted disk image to MMC, that was fixed by the transfer process you have noted (the mmc currently has Armbian_21.08.2_Helios64_buster_current_5.10.63) but my main concern is to keep everything on the SD card, so I can make regular backups easily, and simply replace the card if it breaks (or revert to a backup if an upgrade somehow breaks the system, as that's what got me here in the first place). Conceptually, that should be something that should be doable right?

Hello Everyone, I have installed 6.6.39, and everything is running fine, except for one issue that I simply can't work out. My setup may be a bit unusual, instead of using the internal M2, I have an USB-SATA adapter plugged in to the front USB header on the board. This somehow prevents booting from SD card, and I simply can't work out what goes wrong. If I unplug the drive, all is well. Did anyone encounter a similar issue? disk.log no disk.log