Errno 28 No space left on device error on startup

[fbns07]

Trying to help a friend resolve an issue with his Beyonwiz V2.

On staying the unit up, it goes through the regular startup process, an error message comes up that says Errno 28 No space left on device. It then goes into an infinite rebooting loop, constantly showing the same error message.

I can't figure out how to break out of the boot loop or what else to try to fix this.

Any of the gurus on this forum seen this before (couldn't find anything in search)?

Any other suggestions?

Thanks!

[prl]

At what point in the startup does the message come up, and does it show any other information?

[fbns07]

It comes up at 49% during the boot process.

This is the text (extracted from a photo of the screen):

"We are really sorry. Your receiver encountered a software problem, and needs to be restart Please send the logfile /tmp/Enigma2_crash.log to the Beyonwiz forum. Your receiver will restart in 10 seconds!

(2109) 45.633> [SCREENNAME] InfoBar

(2109) 45.639> [Skin] processing screen Volume: (2109) 45.646> [Skin] processing screen Mute:

(2109) 45.650> [Volume] setValue 40

(2109) 45.650> [eDVBVolumecontrol] Setvolume: raw: 100 100, -1db: 00 (2109) 45.650> [eDVBVolumecontrol] Setvolume: raw: 40 40, -1db: 38 38

45.707> [Skin] processing screen Scart:

{2109}< (2109) 45.712> [Skin] processing screen AutoVideoModeLabel:

(2109) 45.714> EXCEPTION IN PYTHON STARTUP CODE:

(2109) 45.714>

45.714> Traceback (most recent call last): (2109)< 45.714> File "/usr/lib/enigma2/python/mytest.py", line 789, in <module>

(2109)

(2109) 45.715> runScreenTest() (2109)< 45.715> File "/usr/lib/enigma2/python/mytest.py", line 602, in runScreenTest

(2109) 45.715>

profile_final() (2109) 45.715> File "/usr/lib/enigma2/python/Tools/Profile.py", line 77, in profile final

{2109}< 45.715> IOError: [Errno 28] No space left on device

(2109) 45.716>

{2109}< 45.721> [MAIN] (exit code 5)

[MrQuade]

Sounds a if there was no HDD installed in the V2, and a recording then went and filled up all your flash memory, making it impossible the the UI to write new files and continue to run.

You may be able to telnet/ssh into the box and delete some files (the offending recordings) if the network is running (and you had set up a password previously).

Alternatively, a reinstallation of the firmware from USB would clear out the flash memory.

[prl]

Your firmware flash appears to have been filled with files.

You can fix the problem short term by re-installing the firmware from USB.

However, if the problem that caused the flash to fill is still there, the problem will return.

Have you somehow set the timeshift recording to be made to the firmware flash?

[prl]

Sounds a if there was no HDD installed in the V2, and a recording then went and filled up all your flash memory, making it impossible the the UI to write new files and continue to run.

That, on its own, won't fill the flash. The V2 will run just fine as a diskless set-top box.

[MrQuade]

Sounds a if there was no HDD installed in the V2, and a recording then went and filled up all your flash memory, making it impossible the the UI to write new files and continue to run.

That, on its own, won't fill the flash. The V2 will run just fine as a diskless set-top box.

After the flash had been completely filled by a recording?

Most diskless pvrs don't record and timeshift and wouldn't end up crowding out their OS.

[prl]

Sounds a if there was no HDD installed in the V2, and a recording then went and filled up all your flash memory, making it impossible the the UI to write new files and continue to run.

That, on its own, won't fill the flash. The V2 will run just fine as a diskless set-top box.

After the flash had been completely filled by a recording?

Most diskless pvrs don't record and timeshift and wouldn't end up crowding out their OS.

I set a timer, shut down, unplugged the HDD, and restarted. When the timer started, I got an "Error while preparing to record. Disk full?" popup and the timer state was set to failed. It didn't fill the HDD. The same thing if the V2 was just running diskless and I set a record timer and let it run.

[fbns07]

Thanks everyone for your help and insights.

Unfortunately, I've not been able to get the V2 to reinstall the firmware from a USB. Every time you select "Recovery from USB" after less than a second there is an error message "Error downloading file" and the panel on the V2 says "E02".

Are there any other suggestions on what I could try? (I'm starting to think there is something wrong with the onboard memory.)

[MrQuade]

Unfortunately, I've not been able to get the V2 to reinstall the firmware from a USB. Every time you select "Recovery from USB" after less than a second there is an error message "Error downloading file" and the panel on the V2 says "E02".

Are there any other suggestions on what I could try? (I'm starting to think there is something wrong with the onboard memory.)

Did you unzip the contents of the zip file onto the root directory of the USB stick? (there are 2 files inside the zip)

[fbns07]

Thanks for the tip - I double-checked and everything seemed fine.

I refomatted the USB stick (again), redid the process and success! It reinstalled and is now working again.

Will keep a close watch on the performance going forward to see if this happens again. I've already checked the attached drive, it is not full so I don't think that was the cause. Hopefully it was just a glitch.

Thanks so much for all your help everyone! Really appreciate it.