Raspi-config issue : cannot Expand file, error, not a SD card
-
@Gantz Reflash the image on the card. Something is very wrong with your file system.
-
@AlexMurphy thank for your comment. I have try to edit my post above but the system wounld let me due to my post was reports as spam
here my df -h command
terminate called after throwing an instance of 'Boost::filesystem::filesystem_error' what(): boost::filesystem:status: No space left on device: "/home/pi/.emlationstation" aborted -bash:/home/pi/.profile: No space lefdt on device pi@retropie:$ df -h Fliesystem Size Used Avail Use% mounted on dev 404M 0 404M 0% /dev none 28G 28G 0 100% / tmpfs 415M 0 415M 0% /dev/shm tmpfs 415M 5.9M 415M 2% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 415M 0 415M 0% /sys/fs/cgroup /dev/mmcblk0p1 127M 39M 89M 31% /boot tmpfs 83M 0 83M 0% /run/user1000
as my understand, there is suppose to be a /dev/root in the system. how do i mount it?
-
@Gantz I'm running ROMs from a USB drive, but here's an example of a "good" or "working" file system. I'm running RetroPie 4.1.21 on the latest version of Raspbian.
$ uname -a Linux genesis-pi 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux
$ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 29G 3.2G 25G 12% / devtmpfs 364M 0 364M 0% /dev tmpfs 368M 0 368M 0% /dev/shm tmpfs 368M 5.3M 363M 2% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 368M 0 368M 0% /sys/fs/cgroup /dev/mmcblk0p1 57M 21M 37M 36% /boot /dev/sda1 232G 39G 194G 17% /media/usb0
-
@Gantz In terminal type
sudo mount -o remount,rw /
but really this doesn't seem to be your issue as it says root is mounted just not seeing the file system at/dev/root
.I would also be concerned that it states 100% use. -
@AlexMurphy is any possibility for 100% used from pishrink? i have shrink image file from 32GB to 27GB to fit into Kingston class 10 Micro sd.
actually, my first boot. there is no device is mount.
My pi is be able to boot but cannot get into emulation system and raspi-config to expand file system as well.
then, i google to find how to mount boot device, /dev/mmcblk0p1.
after that, It was mounted and raspi-config is work but still get the error,"is not an SD card" from expand file system. then i df -h command as above.I have mounted image via ubuntu. It seem to be fine. as my understand, My image is fine but Im so new for linux system. it might be something that i missed or some mistake that i have no idea how to look.
-
@obsidianspider said in Raspi-config issue : cannot Expand file, error, not a SD card:
29G 3.2G 25G 12% /
$ uname -a Linux retropie 4.4.32v7-aufs #1 SMP Fri Nov 18 23:17:35 CET 2016 armv7l GNU/Linux
i believe that my issue is, how to get /dev/root working.
Thank you for your comment. -
I have running a disk check, and i got this
pi@retropie$ /sbin/fsck fsck from util-linux 2.25.2 e2fsck 1.42.12 (29 Aug 2014) fsck.ext4: Permission denied while trying to open /dev/mmcblk0p2 You must have r/w access to the filesystem or be root
and i also try to edit on my fstab as follow script
proc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults 0 2 /dev/mmcblk0p2 / ext4 defaults,noatime 0 1
after reboot, the result is still the same
terminate called after throwing an instance of 'Boost::filesystem::filesystem_error' what(): boost::filesystem:status: No space left on device: "/home/pi/.emlationstation" aborted -bash:/home/pi/.profile: No space left on device
if anybody have a clue, please guide me the right direction. I would be appreciated.
-
@Gantz did you try the comnand I suggested? This remounts the root partition with read/write priviliges.
-
you cant run a disk check from non root when it is mounted.
Are you running berryboot ?
Your partition is full - which image did you shrink ? You are out of space. That's the only issue.
-
@BuZz yes. i'm using berry boot. I got the original image from someone. But the image size is bigger than my sd card. So, i shrunk the image.
here is i did shrunk the image via ubuntu again.
e2fsck 1.42.13 (17-May-2015) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information retropie: 268081/1949696 files (0.9% non-contiguous), 7422437/7776128 blocks resize2fs 1.42.13 (17-May-2015) ERROR: Image already shrunk to smallest size sitt@sitt:/media/sitt/Sitt External/Pie/Pi$ df -h Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs 392M 6.5M 386M 2% /run /dev/sda1 455G 160G 273G 37% / tmpfs 2.0G 228K 2.0G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs 392M 56K 392M 1% /run/user/1000 /dev/sdc1 127M 39M 89M 31% /media/sitt/0163-7A11 /dev/sdc2 28G 28G 0 100% /media/sitt/berryboot
-
@AlexMurphy i did as you advice but noting happen. then i run df command after reboot. i got same result.
terminate called after throwing an instance of 'Boost::filesystem::filesystem_error' what(): boost::filesystem:status: No space left on device: "/home/pi/.emlationstation" aborted -bash:/home/pi/.profile: No space left on device pi@retropie:$ df -h Fliesystem Size Used Avail Use% mounted on dev 404M 0 404M 0% /dev none 28G 28G 0 100% /
-
I recommend this image:
https://retropie.org.uk/download/
Guaranteed to work and you'll know how to fix things when they break.
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.