RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    MicroSD Retropie On

    Scheduled Pinned Locked Moved Help and Support
    microsdsdcardstartnewused
    19 Posts 2 Posters 2.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • EfriimE
      Efriim
      last edited by Efriim

      I recently started a new image on a recently purchased used 64gb Samsung Evo Plus.
      RetroPie Image 4.4 updated and about half full already.

      I was updating reicast from source, and I came back to consecutive mmcblk0p2 ext4 i/o read failures, is this a positive sign of a corrupted sdcard?
      I guess it is worth noting that the sdoverclock is set to 100, on my 32gb Samsung Evo+ UHS1 this had never occurred with same. Also worth noting, the reicast source is not building properly emulator/reicast/binary segfaults .../RetroPie-Setup/tmp/build/reicast...

      Also general RetroPie love and starting from new images.
      Will start with Run command Launching Images
      https://retropie.org.uk/forum/topic/4611/runcommand-system-splashscreens

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by

        Remove any overclocking and try again. Run a fsck on boot to make sure you get rid of the filesystem issues and then re-run a package update to make sure the binaries are not corrupted.

        EfriimE 1 Reply Last reply Reply Quote 0
        • EfriimE
          Efriim @mitu
          last edited by Efriim

          @mitu
          I removed ram and sdcard overclocks, reset then updated reicast from source.
          The reicast build was corrupted, this very well may have caused the memorycard error by itself.
          The reicast binary install still work okay.

          The original memory card i/o address read error did occur after trying to run the reicast binary a few times directly in command line. I did not get the specifics of the error, but it was every ~5 seconds or so a new one at the same address, it was at a directory in var, sgml or dkms. Don't need it explained I think I understand, I'm pretty certain it was the corrupted binary.

          mituM 1 Reply Last reply Reply Quote 0
          • EfriimE
            Efriim
            last edited by Efriim

            Fstab mount and samba share

            And here is using fstab to mount a usb drive and then adding a samba share.

            memorize the uuid of the usb sda1 or sda2, or write it down, or open another terminal.
            ls -l /dev/disk/by-uuid/ or sudo blkid
            1A92-F7C1 -> ../../sda1

            Edit fstab and add a line after the other mounts for the usb, replacing UUID, with the one for your device and, and mount path for your own setup. The device could also use fstype auto, ntfs-3g, ext3, and different options defaults if that is the format you use.
            sudo nano /etc/fstab

            device/uuid        mount                          fstype options                          
            UUID=1A92-F7C1   /home/pi/RetroPie/memorycard   vfat   defaults,noatime,users,rw,uid=pi,gid=pi   0   0
            

            Note it is also possible to add a NFS network or share to the fstab to be mounted on availability.

            Create the dirctory for the mount
            mkdir /home/pi/RetroPie/memorycard

            And finally add the samba share, at the bottom of this file using ctrl+K ctrl+U to copy one of the other entries is helpful
            sudo nano /etc/samba/smb.conf

            [memorycard]
            comment = memorycard
            path = "/home/pi/RetroPie/memorycard"
            writeable = yes
            guest ok = yes
            create mask = 0644
            directory mask = 0755
            force user = pi
            

            The usbromservice could be uninstalled if from retropiepackages if it is unused.

            here are links describing more of the same.
            https://help.ubuntu.com/community/Fstab
            https://gist.github.com/etes/aa76a6e9c80579872e5f
            https://www.raspberrypi-spy.co.uk/2014/05/how-to-mount-a-usb-flash-disk-on-the-raspberry-pi/

            1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator @Efriim
              last edited by

              @Efriim said in MicroSD Retropie On:

              The reicast build was corrupted, this very well may have caused the memorycard error by itself.

              I doubt that, it's most likely the other way around - due to SDcard/filesystem errors, the binary was corrupted.

              EfriimE 1 Reply Last reply Reply Quote 0
              • EfriimE
                Efriim @mitu
                last edited by

                @mitu
                Doubly doubted, on another sdcard the reicast source is not built correctly and the binaries are corrupted.

                mituM 1 Reply Last reply Reply Quote 0
                • mituM
                  mitu Global Moderator @Efriim
                  last edited by

                  @Efriim Can you post the compilation log, from $HOME/RetroPie-Setup/logs, on pastebin.com ?

                  EfriimE 1 Reply Last reply Reply Quote 0
                  • EfriimE
                    Efriim @mitu
                    last edited by Efriim

                    @mitu
                    Good idea. I didn't know where to look for the log. I had packed up my things but it is a good thing I decided to unpack because I forgot my powersupply.

                    500kb limit
                    https://pastebin.com/Br5fJtec part1 lines 1-500
                    https://pastebin.com/gJSZWPaJ part2 501-xx

                    line 405: part1

                    /home/pi/RetroPie-Setup/tmp/build/reicast/shell/linux/../../core/deps/libelf/elf32.cpp:137:10: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
                       return "<corrupted>";
                    

                    Actual errors when running reicast.

                    ./reicast.sh
                    ./reicast.sh: line 88:  3320 Trace/breakpoint trap   "$rootdir/emulators/reicast/bin/reicast" "${params[@]}" > /dev/null
                    
                    ./reicast
                    Config dir is: /home/pi/.reicast/
                    Data dir is:   /home/pi/.reicast/
                    Personality: 00C00000
                    Updated personality: 00800000
                    found libbcm_host
                    rpi2: bcm_init
                    ARM VFP-Run Fast (NFP) enabled !
                    Linux paging: 4096 00001000 00000FFF
                    MAP 00800000 w/ 25165824
                    MAP 20000000 w/ 25165824
                    MAP 04000000 w/ 16777216
                    MAP 06000000 w/ 16777216
                    MAP 0C000000 w/ 0
                    vmem reserve: base: 539F0000, aram: 739f0000, vram: 579F0000, ram: 5F9F0000
                    Mem alloc successful!
                    
                    EGL config: 0x1, 0x1, 0x1 640x480
                    SIGSEGV @ 0 -> (nil) was not in vram, dynacode:0
                    Fatal error : segfault
                     in fault_handler -> /home/pi/RetroPie-Setup/tmp/build/reicast/shell/linux/../../core/linux/common.cpp : 107
                    
                    Trace/breakpoint trap
                    

                    line 601, part2: l100
                    is the only instance of ../core/linux/common.cpp

                    1 Reply Last reply Reply Quote 0
                    • mituM
                      mitu Global Moderator
                      last edited by

                      That error doesn't mean that the binary is 'corrupted', it's just that it's crashing due to other circumstances.

                      EfriimE 1 Reply Last reply Reply Quote 0
                      • EfriimE
                        Efriim @mitu
                        last edited by

                        @mitu
                        But does not the log file line 405 mean that elf32.cc is corrupt, and thus the executable binary is too?

                        mituM 1 Reply Last reply Reply Quote 0
                        • mituM
                          mitu Global Moderator @Efriim
                          last edited by

                          @Efriim said in MicroSD Retropie On:

                          405 mean that elf32.cc is corrupt

                          No, that's a compilation warning - not an error - for the following line from the source code.

                          1 Reply Last reply Reply Quote 0
                          • EfriimE
                            Efriim
                            last edited by

                            Reicast source is still not working in retropie packages.


                            And here is safe shutdown script for retroflag cases and more, https://github.com/crcerror/retroflag-picase
                            Install safeshutdown:
                            wget -O - "https://raw.githubusercontent.com/crcerror/retroflag-picase/master/install.sh" | sudo bash

                            And some extra scriptmodule packages
                            Exult - Ultima VII
                            wget -O ~/RetroPie-Setup/scriptmodules/ports/exult.sh - "https://raw.githubusercontent.com/amigagamer/ExultRetropie/master/exult.sh"

                            Extra scripts
                            https://github.com/zerojay/RetroPie-Extra

                            mituM 1 Reply Last reply Reply Quote 0
                            • mituM
                              mitu Global Moderator @Efriim
                              last edited by

                              @Efriim said in MicroSD Retropie On:

                              Reicast source is still not working in retropie packages.

                              I'll give it a shot later to see how it works - does the binary work ? Is there any specific game you tried ?

                              EfriimE 1 Reply Last reply Reply Quote 0
                              • EfriimE
                                Efriim @mitu
                                last edited by

                                @mitu
                                The binary works fine. I hear that the reicast source was updated is why I wanted to build the latest.

                                1 Reply Last reply Reply Quote 0
                                • mituM
                                  mitu Global Moderator
                                  last edited by

                                  OK, so when installing from source, I get the same crash, so something must have been changed upstream. I'll try to get a bisect working.

                                  1 Reply Last reply Reply Quote 0
                                  • mituM
                                    mitu Global Moderator
                                    last edited by

                                    Seems like an upstream issue, which is solved, but not yet merged - https://github.com/RetroPie/RetroPie-Setup/issues/2700 (leading to the a bug report on the Reicast repo - https://github.com/reicast/reicast-emulator/issues/1537).

                                    Bisecting the issue points to an older commit (a808a8f3).

                                    EfriimE 1 Reply Last reply Reply Quote 0
                                    • EfriimE
                                      Efriim @mitu
                                      last edited by

                                      @mitu
                                      Yeah it looks like I had problems installing the source a few months ago too.

                                      I had a couple questions. In my fstab

                                      UUID=1A92-F7C1   /home/pi/RetroPie/memorycard   vfat   defaults,noatime,users,rw,uid=pi,gid=pi   0   0
                                      

                                      I thought this would mount on availability, do you know what options are added, for automount and so that it wont hang a startup process during boot for 180 seconds, when the usb is unplugged?

                                      My other question, I don't know probably couldn't answer, on my last retropie installation, I had a startup time of around 15 seconds. I think i have done everything that I did on my last installation but I can still only get 18 seconds. Any ideas?

                                      mituM 1 Reply Last reply Reply Quote 0
                                      • mituM
                                        mitu Global Moderator @Efriim
                                        last edited by

                                        I had a couple questions. In my fstab

                                        UUID=1A92-F7C1   /home/pi/RetroPie/memorycard   vfat   defaults,noatime,users,rw,uid=pi,gid=pi   0   0
                                        

                                        I thought this would mount on availability, do you know what options are added, for automount and so that it wont hang a startup process during boot for 180 seconds, when the usb is unplugged?

                                        Automount is handled by the usbautomount service. If you don't have the disk permanently attached, then it's best to use the usbautomount service.

                                        My other question, I don't know probably couldn't answer, on my last retropie installation, I had a startup time of around 15 seconds. I think i have done everything that I did on my last installation but I can still only get 18 seconds. Any ideas?

                                        Startup times can be diagnosed with systemd-analyze - look into it to determine where the system spends it's time.

                                        EfriimE 1 Reply Last reply Reply Quote 0
                                        • EfriimE
                                          Efriim @mitu
                                          last edited by Efriim

                                          The disk I plan on leaving attached. I'll look into options for mount; is option "nofail" supposed to mean that it will give up trying to mount if it is non-available?

                                          systemd-analyze blame
                                          the top four are nmbd.service 10.8s and hciuart.service 6.4s
                                          then raspi-config.service 1.3s and smbd.service 1s

                                          one is the net bios name server i was pretty sure I dont use that so i disabled it with
                                          sudo systemctl stop nmbd
                                          sudo systemctl disable nmbd

                                          I do use bluetooth, It seems like it is unusually slow. Reading dmesg:
                                          uart-pl011 3f201000.serial: no DMA platform data
                                          brcmfmac: power management disabled
                                          and brcmfmac: brcmf_c_preinit_dcmds; look like firmware warnings

                                          raspi-config is probably nominal, though I don't know what it is calling or doing at startup.

                                          I use samba smbd.service.

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post

                                          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.