x64 system running 18.04.20 doesn't work too well
-
@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 diskI think this is far as i can go without more help (i have 1% linux skill)
-
@shamanmogz d**n i should have hit the "download" button for the link
-
@Substring need me to run it again or slightly differently?
-
@shamanmogz in case the script didn‘t run well, try it with the correct (raw) address:
https://gitlab.com/recalbox/recalbox/raw/c251d7eb56c5d12622c5189e48d23dc9ec79775b/board/recalbox/fsoverlay/recalbox/scripts/recalbox-part.sh -
@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 -
@shamanmogz it should be fine by now
-
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 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 0or:
# blkid /dev/sda2: LABEL="RECALBOX" UUID="3638b519-b279-4f9a-981c-cce4de83472f" TYPE="ext4" /dev/sda1: LABEL="BOOT" UUID="7DD8-6D51" TYPE="vfat" -
@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?
