@substring I just realised that although I changed the update option in the UI after a power cycle it hasn't persisted (so my last set of test results was invalid). Maybe I should change the updates.type value in the recalbox.conf file itself? If you agreem what should that value be?

Also on a different note, I have 4x 2GB ram sticks kicking about. I tried to add them in but Recalbox refuses to boot. Is there a max ram limitation (i have a 64 bit processor and am using the 64 bit build). Actually on that note, how do I know if my GT 710 graphics card has been installed properly?

lastly sorry for the delay - was away for the long weekend.

@substring said in x64 system running 18.04.20 doesn't work too well:

bash -x /etc/init.d/S11share start

Note: I'm back on a 0.5 TB drive and it's running ok

Using username "root".
root@recalbox's password:
# bash -x /etc/init.d/S11share start
+ test start = stop
+ test start '!=' start
+ SHARECONFFILE=/boot/recalbox-boot.conf
++ /recalbox/scripts/recalbox-part.sh share_internal
+ INTERNALDEVICE=/dev/sda3
++ cat /boot/recalbox-boot.conf
++ grep sharedevice=
++ head -n1
++ cut -d= -f2
+ SHAREDEVICE=INTERNAL
+ [[ 0 -ne 0 ]]
+ [[ INTERNAL == '' ]]
+ INTERNALDEVICETYPE=ext4
++ getMaxTryConfig /boot/recalbox-boot.conf
++ SHARECONFFILE=/boot/recalbox-boot.conf
+++ grep -E '^[ \t]*sharewait[ \t]*=' /boot/recalbox-boot.conf
+++ sed -e 's+^[ \t]*sharewait[ \t]*=++'
++ X=
++ echo ''
++ grep -qE '^[0-9][0-9]*$'
++ echo 7
+ MAXTRY=7
+ NTRY=0
+ test -e /dev/sda3
+ RMODE=INTERNAL
+ echo INTERNAL
+ grep -qE '^DEV '
+ MODE=INTERNAL
+ case "${MODE}" in
+ /recalbox/scripts/recalbox-mount.sh ext4 1 /dev/sda3 /recalbox/share
mount: mounting /dev/sda3 on /recalbox/share failed: Device or resource busy
+ mount -t tmpfs -o size=128M tmpfs /recalbox/share
+ ls /var/run/usbmount.delay
+ read RULE
+ touch /var/run/recalbox.share.mounted
+ logpath=/recalbox/share/system/logs
+ for bootlogfile in '/tmp/logappend-*.*'
++ echo '/tmp/logappend-*.*'
++ sed 's|/tmp/logappend-||'
+ destfile='*.*'
+ cat '/tmp/logappend-*.*'
/etc/init.d/S11share: line 289: /recalbox/share/system/logs/*.*: No such file or                                                                          directory
+ rm '/tmp/logappend-*.*'
rm: can't remove '/tmp/logappend-*.*': No such file or directory

@Substring sure, just installing it. Note i don't have a mic on this system - i can get hold of one in a few days, but for now it's just text chat. What's your server?

@Substring yeah i'm cool with that. is there a better way to do this rather than using forum posts?

@substring It's more to do with i have a 3TB HDD kicking around so why not use it. I'm flashing the 0.5TB as I type.

@Substring Ok I will roll back to my 0.5TB drive for now unless you think I can partition my 3TB to give me 2x 1.5TB internal shares.

@Substring My hard drive is now 3TB.

• When I started out I was using a 0.5TB hard drive on 18.03.30
• I upgraded that drive to 18.04.20 using the inbuilt UI in recalbox
  Then the problems started to happen
• I then changed drives to 3TB and used a fresh 18.04.20 image

Is there a maximum HDD that is supported?

@Substring Ran fdisk as requested

# fdisk /dev/sda
fdisk: device has more than 2^32 sectors, can't use all of them

The number of cylinders for this disk is set to 267349.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1           9       65536   c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/sda2               9         311     2424018  83 Linux
Partition 2 does not end on cylinder boundary

Command (m for help): q

@substring If it's easier I'm happy to roll back to 18.03.30 and wait for the next release for this fix

@Substring I've listed my drives and get:

# cat /proc/mounts
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=1978844k,nr_inodes=494711,mode=755 0 0
/dev/sda2 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=777 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
tmpfs /var tmpfs rw,relatime 0 0
tmpfs /run tmpfs rw,relatime 0 0
tmpfs /recalbox/share tmpfs rw,relatime,size=131072k 0 0
/dev/sda1 /media/usb0 vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocha**et=utf8,shortname=mixed,flush,errors=remount-ro 0 0

or:

# blkid
/dev/sda2: LABEL="RECALBOX" UUID="3638b519-b279-4f9a-981c-cce4de83472f" TYPE="ext4"
/dev/sda1: LABEL="BOOT" UUID="7DD8-6D51" TYPE="vfat"

@Substring

Afraid not, I tried making a change as you suggetsed and rebooting the machine, but still I get Storage N/A and settings don't persist.

@Substring & @paradadf I re-ran the scripts augmenting the commands from my previous attempt and got the following results:

# sh ./recalbox-part.sh boot
/dev/sda1
# sh ./recalbox-part.sh system
/dev/sda2
# sh ./recalbox-part.sh share_internal
/dev/sda3

@Substring need me to run it again or slightly differently?

@substring ok my bad - i didn't realise that the commands you gave me wouldn't run the script as well.

Using the commands:

• cd /recalbox/scripts
• chmod +x /recalbox/scripts/recalbox-part.sh
• sh ./recalbox-part.sh

I get the following:

./recalbox-part.sh: line 1: syntax error near unexpected token newline' ./recalbox-part.sh: line 1: <!DOCTYPE html>'

This looks like the wget did something wrong (or i did), so I followed the link to get the correct .sh file and using vi edited the recalbox-part.sh above. I now end up with:

./recalbox-part.sh <boot|system|share_internal|prefix x|previous x>
boot: the recalbox boot partition
system: the recalbox system partition
share_internal: the recalbox share internal partition
prefix x: the disk of the partition x (without the partition number)
previous x: the partition before x on the same disk

I think this is far as i can go without more help (i have 1% linux skill)

@Substring Thanks for helping out, I appreciate your fit this in around your other life duties.

I tried the commands as requested:

Using username "root".
root@recalbox's password:

mount -o remount, rw /

wget -O /recalbox/scripts/recalbox-part.sh https://gitlab.com/recalbox/recalbox/blob/c251d7eb56c5d12622c5189e48d23dc9ec79775b/board/recalbox/fsoverlay/recalbox/scripts/recalbox-part.sh

--2018-04-30 20:28:13-- https://gitlab.com/recalbox/recalbox/blob/c251d7eb56c5d12622c5189e48d23dc9ec79775b/board/recalbox/fsoverlay/recalbox/scripts/recalbox-part.sh
Resolving gitlab.com... 52.167.219.168
Connecting to gitlab.com|52.167.219.168|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: '/recalbox/scripts/recalbox-part.sh'

/recalbox/scripts/r [ <=> ] 33.10K --.-KB/s in 0.006s

2018-04-30 20:28:14 (5.63 MB/s) - '/recalbox/scripts/recalbox-part.sh' saved [33898]

Sadly even after a reboot (via command or by making a change to the language causing a reboot) it did not work.

Something that is interesting - I have noticed that the SHA-256 and MD5 for the WINSCP connection changes after every reboot - but i guess this is to be expected if it's a new live instance running every time.

@Substring I'm at home this evening if you have any scripts you want me to run.

@Substring I'm happy to run any scripts for you providing i can run them using WINSCP's console (or i can try PUTTY)

@Substring

I'm not sure what you mean by that - or more importantly I'm not sure how to fix it.

As far as I know it was working in 03.30 for a few weeks, I was playing a few roms - then the update started making it act up. I did a fresh image burn using etcher on the hard drive (internally attached on another PC). The fresh burn of the image was done in the exact same way as the first time. Why would this version loose the share on the hard drive?

@Substring

I used the web base manager to run the script : https://file.ac/HUuSHVBzgdE/

@Substring

I tried running the script in WINSCP's console and got the following:

/recalbox/scripts$ /recalbox/scripts/recalbox-support.sh
/recalbox/scripts/recalbox-support.sh: line 43: lsmod: command not found
/recalbox/scripts/recalbox-support.sh: line 50: ifconfig: command not found
/recalbox/scripts/recalbox-support.sh: line 59: blkid: command not found
BusyBox v1.25.1 (2018-04-20 08:03:10 UTC) multi-call binary.

Usage: rm [-irf] FILE...

Remove (unlink) FILEs

-i	Always prompt before removing
-f	Never prompt
-R,-r	Recurse

Unable to init SDL: No available video device
/recalbox/share/saves/recalbox-support-20180428220047.tar.gz

I'm not very linux savy so apologies if i'm missinng something obvious