starred/motioneye

Fork 0

mirror of https://github.com/motioneye-project/motioneye.git synced 2026-03-02 22:57:06 -05:00

how to delete recorded video's on a raspberry pi in terminal #2627

New issue

Closed

opened 2026-02-28 01:16:09 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 01:16:09 -05:00

Owner

Originally created by @bob59 on GitHub (May 12, 2025).

I made a remote nestbox camera, using a Raspberry Pi 3 B running Bullseye with Motioneye, I was away for a few days and as the eggs hatched the birds were in/out a lot, I tried to access Motioneye on my local network but could not connect, I could only connect to the Raspberry Pi via puTTY, it looks like the card is full.

I found several folders containing video's at var/lib/motioneye/Camera1, but if I try to delete them using rm, I get an error
rm: cannot remove '2025-05-06/13-48-37.mp4.thumb' :Read-only file system

could someone help please

thanks

Originally created by @bob59 on GitHub (May 12, 2025). Hi I made a remote nestbox camera, using a Raspberry Pi 3 B running Bullseye with Motioneye, I was away for a few days and as the eggs hatched the birds were in/out a lot, I tried to access Motioneye on my local network but could not connect, I could only connect to the Raspberry Pi via puTTY, it looks like the card is full. I found several folders containing video's at var/lib/motioneye/Camera1, but if I try to delete them using rm, I get an error rm: cannot remove '2025-05-06/13-48-37.mp4.thumb' :Read-only file system could someone help please thanks

deekerman closed this issue

2026-02-28 01:16:11 -05:00

deekerman commented

2026-02-28 01:16:13 -05:00

Author

Owner

@saadqaz1 commented on GitHub (May 12, 2025):

Sounds like the pi put itself into RO mode to protect the storage. You might want to try running fsck or fdisk and then try removing the files. See https://askubuntu.com/questions/1322160/ubuntu-20-04-raspberry-pi-cant-write-anything-every-file-seems-to-be-in-read

@saadqaz1 commented on GitHub (May 12, 2025): Sounds like the pi put itself into RO mode to protect the storage. You might want to try running fsck or fdisk and then try removing the files. See https://askubuntu.com/questions/1322160/ubuntu-20-04-raspberry-pi-cant-write-anything-every-file-seems-to-be-in-read

deekerman commented

2026-02-28 01:16:15 -05:00

Author

Owner

@bob59 commented on GitHub (May 13, 2025):

saadqaz1 you were right, as soon as I changed to RW I could delete the video files, the usage went from 100% to 16%, but I still can't connect to motioneye
I did try taking a test picture via terminal but that failed, so I tried libcamera-hello, result was no camera connected, so not sure if the camera has gone bad
could motioneye block access to the camera ?, also even if the camera is not connected should I still be able to connect to motioneye

thanks
bob59

@bob59 commented on GitHub (May 13, 2025): saadqaz1 you were right, as soon as I changed to RW I could delete the video files, the usage went from 100% to 16%, but I still can't connect to motioneye I did try taking a test picture via terminal but that failed, so I tried libcamera-hello, result was no camera connected, so not sure if the camera has gone bad could motioneye block access to the camera ?, also even if the camera is not connected should I still be able to connect to motioneye thanks bob59

deekerman commented

2026-02-28 01:16:15 -05:00

Author

Owner

@MichaIng commented on GitHub (May 13, 2025):

motionEye/motion can hog the camera device, when doing motion detection or while viewing the camera stream via web UI.

However, motion does not naively support the libcamera API. So if you have an RPi camera module attached and the "modern" camera API enabled, it won't be able to handle it with motionEye, without adding libcamerafy: #2425

What do you mean with "can't connect to motioneye"? You mean the web interface is not accessible? Check the service status:

sudo systemctl status motioneye

To test the camera module with libcamera-hello, it might be needed to stop the motionEye service first:

sudo systemctl stop motioneye

@MichaIng commented on GitHub (May 13, 2025): motionEye/motion can hog the camera device, when doing motion detection or while viewing the camera stream via web UI. However, motion does not naively support the libcamera API. So if you have an RPi camera module attached and the "modern" camera API enabled, it won't be able to handle it with motionEye, without adding `libcamerafy`: #2425 What do you mean with "can't connect to motioneye"? You mean the web interface is not accessible? Check the service status: ```sh sudo systemctl status motioneye ``` To test the camera module with `libcamera-hello`, it might be needed to stop the motionEye service first: ```sh sudo systemctl stop motioneye ```

deekerman commented

2026-02-28 01:16:15 -05:00

Author

Owner

@bob59 commented on GitHub (May 13, 2025):

Michalng,

thank you for your reply, it was the web interface that I could not reach, I checked the service status of motioneye, the result was Active: failed motioneye-service: Failed with result 'exit-code'

after restarting the motioneye service I can now access the web interface, so I am going to call that a win, not sure why the service did not start when I rebooted the RPi, as it has always been ok before, but it is now working
thanks again
bob59

@bob59 commented on GitHub (May 13, 2025): Michalng, thank you for your reply, it was the web interface that I could not reach, I checked the service status of motioneye, the result was Active: failed motioneye-service: Failed with result 'exit-code' after restarting the motioneye service I can now access the web interface, so I am going to call that a win, not sure why the service did not start when I rebooted the RPi, as it has always been ok before, but it is now working thanks again bob59

deekerman commented

2026-02-28 01:16:15 -05:00

Author

Owner

@MichaIng commented on GitHub (May 14, 2025):

Okay great.

In case it is not accessible again, check the full service logs:

journalctl -u motioneye

I'll mark this issue as closed then. Feel free to reopen if required.

@MichaIng commented on GitHub (May 14, 2025): Okay great. In case it is not accessible again, check the full service logs: ```sh journalctl -u motioneye ``` I'll mark this issue as closed then. Feel free to reopen if required.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/motioneye#2627

No description provided.

Rows
Columns