x64 system running 18.04.20 doesn't work too well
-
@substring If it's easier I'm happy to roll back to 18.03.30 and wait for the next release for this fix
-
@shamanmogz i don't get it ... It does find th root partition but can't have a share. Can you
fdisk /dev/sdathenpthen enter and copy the result ? Press q then enter to quit -
@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 -
@shamanmogz i think i get it : how big is yout drive ? The
device has more than 2^32 sectors, can't use all of themlooks like we can't build the share partition. -
@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?
-
@shamanmogz you make me search real deep ...
Recalbox uses a MBR partition table, not GPT. This limits the numver of sectors to 2^32, which is around 2TB.Going to GPT may not be a good idea yet.
-
@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.
-
@shamanmogz why do you need that much space ? If it's fully loaded es will be real slow probably.
And no, we could eventually have a 2TB internal share, but nothing more, the last TB would be wasted
Former dev - Please reply with @substring so that i am notified when you answer me
Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé -
@substring for a full collection of all systems, 2TB is not enough
-
@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.
-
@shamanmogz you would be a good guinea pig for some advanced logging i've been working on. Would you agree to give a try to it ? You'd just need to change the updates.type value in recalbox.conf, make the upgrade and report some logs
-
@Substring yeah i'm cool with that. is there a better way to do this rather than using forum posts?
-
@shamanmogz discord ?
-
@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?
-
@shamanmogz we've advertised it some days ago. No need for a mic
By the way, we can do anneasier way : run
bash -x /etc/init.d/S11share startand give me the output please -
@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 -
@shamanmogz d**n my bad. Reboot it then
cd / /etc/init.d/S31emulationstation stop /etc/init.d/S92virtualgamepads stop bash -x /etc/init.d/S11share start -
@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.
-
@shamanmogz i'm on holidays for now, ping me in a week for such a delicate topic
-
@shamanmogz said in x64 system running 18.04.20 doesn't work too well:
My system is a 64bit core 2 DUO (E6750) with a GT710 and 4GBs of RAM, 3TB HDD
Hi Shamanmogz,
I intend to buy a MSI GT 710 1GD3H LP --> according to what you say, GT710 works fine with RecalBox ?Thanks
