SD Card full - log files
-
Hi, I have encountered an issue where my 32GB SD Card has become complete full and I am unable to copy over new ROMs, save images using scraper etc. I have only been running RetroPie for a few weeks.
Further investigation by SSH and running command df -h suggests the /dev/root folder contains some 30GB of data.
Filesystem Size Used Avail Use% Mounted on
/dev/root 30G 30G 0 100% /
devtmpfs 370M 0 370M 0% /dev
tmpfs 375M 0 375M 0% /dev/shm
tmpfs 375M 39M 337M 11% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 375M 0 375M 0% /sys/fs/cgroup
/dev/mmcblk0p1 57M 22M 36M 39% /boot
tmpfs 75M 0 75M 0% /run/user/1000Further drilling into the /dev/root folder by running ncdu / reveals that folder /var/log contains 3 log files of some 8.7GB in size.
8.7 GiB [##########] syslog
8.7 GiB [######### ] kern.log
8.7 GiB [######### ] messages
280.0 KiB [ ] dpkg.log
280.0 KiB [ ] daemon.log
228.0 KiB [ ] /apt
40.0 KiB [ ] wtmp
. 36.0 KiB [ ] /samba
28.0 KiB [ ] auth.log
12.0 KiB [ ] user.log
8.0 KiB [ ] debug
4.0 KiB [ ] lastlog
4.0 KiB [ ] alternatives.log
4.0 KiB [ ] fontconfig.log
0.0 B [ ] faillog
0.0 B [ ] btmp
0.0 B [ ] bootstrap.logI would appreciate any help in:
- emptying these log files
- preventing these log files filling up in the future
Thanks in advance for your help
-
You can just delete the files outright
sudo rm -f /var/log/syslog /var/log/kern.log /var/log/messagesHowever, you should first take a look at them to see why they're so large
sudo tail /var/log/messagesThere's probably an error/warning message repeated indefinitely and fills up the logs. Deleting them now will reclaim your space, but likely they'll fill up again unless you fix the problem that generates these messages. Since you didn't give any informations about your system (as requested in https://retropie.org.uk/forum/topic/3/read-this-first), it's difficult to know what could possibly be wrong.
-
@mitu thanks for your thoughts. I will give these a go.
I am running a RPi3+ with a 32GB SD Card. Running RetroPie 4.4 with a prebuilt image downloaded from the official website.
-
For the 3B+, I remember seeing this issue with warnings being generated when the power supply is not stable. If that's the case (look in the log files), then I suggest getting a proper power source.
-
Ok I will check this also. I did purchase a 5V 3A power source specifically for use with my setup.
link text -
@mitu this is the result of running sudo tail /var/log/syslog
Jun 2 22:12:55 retropie kernel: [ 906.358018]
Jun 2 22:12:55 retropie kernel: [ 906.359004] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.359004]
Jun 2 22:12:55 retropie liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Jun 2 22:12:55 retropie kernel: [ 906.360025] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.360025]
Jun 2 22:12:55 retropie kernel: [ 906.361005] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.361005]
Jun 2 22:12:55 retropie liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]This is the result of running sudo tail var/log/kern.log
Jun 2 22:12:55 retropie kernel: [ 906.343998]
Jun 2 22:12:55 retropie kernel: [ 906.344997] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.344997]
Jun 2 22:12:55 retropie kernel: [ 906.345998] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.345998]
Jun 2 22:12:55 retropie kernel: [ 906.346997] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.346997]
Jun 2 22:12:55 retropie kernel: [ 906.347997] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.347997]and this is the result of running sudo tail /var/log/messages
Jun 2 22:12:55 retropie kernel: [ 906.358018]
Jun 2 22:12:55 retropie kernel: [ 906.359004] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.359004]
Jun 2 22:12:55 retropie liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Jun 2 22:12:55 retropie kernel: [ 906.360025] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.360025]
Jun 2 22:12:55 retropie kernel: [ 906.361005] WARN::dwc_otg_handle_mode_mismatch_intr:68: Mode Mismatch Interrupt: currently in Host mode
Jun 2 22:12:55 retropie kernel: [ 906.361005]
Jun 2 22:12:55 retropie liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]Any ideas? A bit of googling implies it may be related to the NesPi case and Xbox 360 wireless dongle, both of which I use. :(
-
@chris3lx Take the Pi out of the case and see if you get the same messages in the logs. If not, then the case has some faulty USB connectors.
-
I have the same problem using a RPi3 in a NESPi case with a Xbox 360 wireless dongle. I've disabled the logging to syslog & kern.log and set loglevel to 0 and the messages file still grows at about 1MB/s unless I unplug the only controller I've got... marvelous :)
-
@amigadude Do you get the same problem without the Pi in the NesPi case ?
-
Just removed the top of the case and plugged the Xbox 360 wireless dongle into 1 of the RPi3 USB sockets and the messages file isn't getting any bigger... seems like it's a combination of the NESPi hub and the dongle :(
-
@amigadude said in SD Card full - log files:
seems like it's a combination of the NESPi hub and the dongle :(
Thanks for testing this out.
-
Solved it the old fashioned way and cut a hole in the left side of the case just big enough to allow access to one of the RPi3's USB sockets :)
I will test the hub with a few other controllers when I can.
-
@amigadude said in SD Card full - log files:
I will test the hub with a few other controllers when I can.
Checked using my MS wireless keyboard and with it plugged into the same port as the dongle was the logs and messages files do grow slowly... same messages but only a few kb per minute.
If I plug the same keyboard dongle into the USB ports hidden under the flap the files don't grow at all... so the problem only seems to affect the 2 USB ports on the front right of the case.
-
@amigadude this is exactly what i have been seeing.
-
@amigadude said in SD Card full - log files:
@amigadude said in SD Card full - log files:
I will test the hub with a few other controllers when I can.
Checked using my MS wireless keyboard and with it plugged into the same port as the dongle was the logs and messages files do grow slowly... same messages but only a few kb per minute.
If I plug the same keyboard dongle into the USB ports hidden under the flap the files don't grow at all... so the problem only seems to affect the 2 USB ports on the front right of the case.
interesting that it doesn't occur when plugging into the usb ports under the flap. I need to try this out
-
It's been six months since you were all discussing this, but I've just run into this issue myself. Same deal: rp3b+, most recent retropie image, nespi case, third party xbox 360 usb hub coming out of the front right ports. My logs called "messages", "kern.log" and "syslog" all constantly grow at the same rate with the exact same error message.
I read all of your discussion and then tried switching the usb hub to one of the ports under the flap. At first, it simply wasn't recognizing the controller, so I tried reconfiguring it. This didn't work: the controller's buttons would only register sporadically, and sometimes the whole screen would lock up. Logging into the pi from my computer I was able to run sudo reboot now, but then emulationstation wouldn't load and instead I'd get a totally unresponsive command line that says "segmentation fault" at the top. Unplugging the hub, re-plugging in one of the front right ports, and rebooting, I was returned to emulationstation with a functioning controller. However, I'm right back to having three log files that grow infinitely.
Did anyone find a solution to this?
FYI, I'm running a pretty stock rp3b+. I'm not running any overclocking, the only change is I have bluetooth disabled with dtoverlay=pi3-disable-bt in config.txt, and my roms load off a usb thumb drive that's directly plugged into the pi itself (no hub).
-
@GingerKanye said in SD Card full - log files:
Did anyone find a solution to this?
Returning the NesPI case and getting a proper case would be a solution. There's nothing here that RetroPie (or Linux) can do if the hardware is faulty.
For workarounds - you can see how people have been coping with this problem in this topic. If you have the proper experience and tools, you can attempt to fix the hardware (see here for an example).
-
I'm having the same issue on a Pi 3B+ built into a Picade. No NESPi, no USB hub. The only hardware is a Picade (Picade X Hat installed on the pi) and occasionally I connect a USB keyboard. I used the Retropie 4.4 image.
In /var/log, the files syslog, messages, kern.log were all 1.5G
Upon inspection, most common message was also the dwc_otg_handle_mode_mismatch_intr line. After I used
sudo truncate --size 0 [FILENAME]to clear them, they immediately started growing again with that message.I'm now upgrading everything, hoping that the logging spam has been fixed in the meanwhile, cause the 4.4 image is from April 2018. Otherwise I'll have to try and find a way to suppress it or to automatically clean the logs, but I don't really know where/how.
Update: the update helped, the log files are no longer flooded and I actually gained a whopping 4.5GB by cleaning them. Working with 16GB sdcards will make you care about filesizes again. And I had an epiphany: the USB keyboard I use also has 2 USB ports (to connect a mouse to it for instance) so it is also some sort of USB hub!
Update 2: lost all keybindings and videos are starting to turn blue (vlc). Probably going to go back to an image backup... Hmgrmpf.
Update 3: tl;dr version: I ended up reverting to a backup image, cleared the logs, ran
sudo rpi-updateto get new firmware and the logs are no longer growing when I connect my keyboard-with-hub. -
I also have the same condition with the Pi 3B+ and NESPi+ case running most recent RetroPie 4.4 release. It seems to happen with all wireless dongles connected in to the NESPi case ports (wireless Keyboard, and Xbox 360 adapter for sure). I found a couple different threads in the forum about it and I believe they found the reason, https://github.com/raspberrypi/linux/issues/2408, and I believe they were working on a fix, but I have not seen the true fix anywhere.
(If anyone has it and a step-by-step, I'd be grateful)**I did find a temporary workaround though, without having to revert to previous Pi versions-
Use another USB hub (like a laptop 4-port) to connect to the NESPi case, and then connect your devices in to that. It appears to cancel out whatever mismatch there is between the pi and NESPi USB hub.It's a bit unsightful but it prevents a lot of re-imaging and reversion to a previous release. Hopefully a solution will be embedded in to the next release as the NESPi case is great!
*I have been successful using either an Insignia 4 port USB2.0 Hub (N5-PCH5420) and also with a Sabrent 4 port USB3.0 Hub (HB-MNBW). Not sure if a powered USB hub will do the same but worth a try before frustrating yourself to no avail looking for a solution.
My devices connected were a Microsoft Xbox 360 Wireless adapter, and Logitech K400r wireless USB keyboard.
Good luck out there..
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.