Recently I have been testing Lakka on my Cubietruck. I installed image on my sd card and it runs perfectly. I added BIOS and some roms of diferent consoles to test it and I am very happy with the results, but storage space in sd card is not enough to save all games I desire. So now I want to use a 300 GB Sata Drive to storage my roms and other data.
There is a way to install a Lakka image on my Sata Drive and boot from it? Or almost a way to access to roms storaged in my Sata Drive from my Sd card Lakka image?
I’m trying to get lakka to recognise the internal sata drive, but without luck so far. aparently it’s supposed to automount it, but it simply doesn’t. the drive is a 160gig hitachi drive, formatted with ntfs, fully packed with roms. under other distros such as slovenia’s debian image i can access the drive, although i have to mount it manually.
edit: I had to ssh into the cubietruck and mount /dev/sda1 /media for a test. that works, but then i still have to point retroarch via gui to the right rom directory… i’m using the latest stable release for the cubie.
any suggestions on how to get the automount to work? i’m not too familiar with linux though, but so far i found my way around. ps uax shows no udevil service running. only udev… is there a difference? (stupid question… i know)
do i have to use a nightly build? anyway, i apreciate any hints.
cheers
edit 2: sorted it out i think, but only via an openelec workaround. i had to create an autostart shell script in /storage/system/.config/ which will be read by lakka during boot.
for all newbies like me, here’s a short guide:
log into your device via ssh (putty or other ssh client). lakka uses root / root as user and pw.
careful, you’re logged in as superuser, so don’t mess with the system…
find out what device / partition you need to mount with the commands “lshw” or “lsblk”. in my case it was device sda partition 1 (sda1)
then change directory to:
cd /storage/.config/
invoke a text editor of your choice, i use nano. if you write anything after “nano” it will create a file with the stuff behind nano ( “nano lol” without quotation marks creates a file with the name “lol”)
now insert the mount command to mount your partition (here /dev/sda1) to a folder. i chose /storage/roms as lakka apparently only looks for roms in this folder…
type the following:
(
mount /dev/sda1 /storage/roms
) &
if you need to execute more commands, type a semi-colon after your first command and simply start a new line e.g.
now that you’re done, press CTRL + X to close nano. it will ask you if you want to save the changes -> yes.
now i don’t know if the file needs to be executable or not. anyway, i made it executable with
chmod +x autostart.sh
you can reboot your device now. i used “reboot” in the console, but if your device has buttons you can use them as well.
that should be it. lakka should mount your hard drive during the next boot.
note for all linux newbies like me: your storage device names might vary depending on what device you use , i.e. pc / raspberry etc. if you use more than one external device look for sda 0, 1, 2 etc / sdb 0, 1, 2 etc. if you have a pc with internal hdds and additional usb storage media you will also find hda 0, 1, 2 etc and hdb 0, 1, 2 and so on and so forth, hda / hdb being the internal hard drives, and maybe additional external sda / sdb / sdc drives. linux was quite confusing for me at the beginning, so i wanted to share my “insights”
hello, do you know if a wd elements usb3.0 2TB would auto mount or work using your workaround method? When i plug http://www.newegg.com/Product/Product.aspx?Item=N82E16822236519 into the ubs port of odroid c1, it does not mount…and there’s clicking sound (no sound when plug into PC). The clicking sound may be is saying there is not enough power?
