OMG. You really should make this more noticeable For somebody like me, whose only Linux experience is, to play around with Tomato, Libreelec & Coreelec, you don't think that something more might be needed. No matter it runs now ... Thx a lot

I want to put a banana Pi M1 plus a 2.5" SATA drive in a plastic box with only the ethernet and USB ports exposed. This means the onboard power button is not accessible to boot the board. Are you able to power on the board using the GPIO pins? If so please could someone advise which pins to connect to? I also aim to put a 5.5 x 2.1mm barrel connection on the box (with a latching press button switch for isolation) for the +5v supply and connect a short micro USB connector from the barrel socket to the board and also attach the SATA power leads directly rather than powering from the board 2 pin connector to take the load off the micro USB input.

Thanks @bedna Ive now got it working with read write execute on the share via Windows. I searched the Ubuntu forums and foud a couple of posts relating to the issue I was hving with an exfat formatted hard drive. For anyone else searching this forum the answer was to edit the fstab file as follows: To enable read-write access for an exFAT drive in /etc/fstab, add rw,uid=1000,gid=1000,umask=000 to the options field. Using umask=000 ensures all users have read/write access, while setting the uid and gid to your user ID (typically 1000) assigns ownership to your account. Also from Reddit Linux Add this to your /etc/fstab file (replacing the UUID and mount point): UUID=XXXX-XXXX /mnt/exfat exfat defaults,uid=1000,gid=1000,umask=000,nofail 0 0 Key Options Explained rw: Explicitly mounts the drive as read-write. uid=1000,gid=1000: Sets the user and group owner to your user account, preventing root-only lockouts. Use the id command to check your actual UID if needed. umask=000: Sets permissions to 777 (read/write/execute for all), which is usually necessary because exFAT doesn't support native Linux permissions. nofail: Allows the system to boot even if the drive is unplugged. To remove the guest share that appeared all I did was remove the [Global] settings inserted from the Samba wiki i.e. [global] map to guest = Bad User log file = /var/log/samba/%m log level = 1 server role = standalone server [guest] # This share allows anonymous (guest) access # without authentication path = /srv/samba/guest/ read only = no guest ok = yes guest only = yes All working correctly now. I just need to mount the board in a small plastic box and change the IP address to a static one on my daughters subnet.🙂

https://paste.armbian.com/xacimaxamo here's the output from the build from Bigtreetech repo (https://github.com/bigtreetech/build)

Did you ran apt update + upgrade + reboot before ? Edit: we might add warning if installed and running kernel version differs. I ran into this problem myself.