Open ViX Downloads Before v6.2 - Any Links?

[Huevos]

The Information says
Detected devices: SanDisk (Cruzer Blade) External (USB) 31.39 GB - Free 24.41 GB

So I suggest that something else must have provoked the crash.

Both those crash logs say "Read-only file system".

[twol]

... and 21:40:03.3407 {BackupManager] Backup failed - e. g. wrong backup destination or no space left on backup device

So also might be worth checking both space and that HDD is the device you are expecting it to be!

[twol]

Hit Twol
I created a crash on which I only came out by re-flashing the image.
This is what I did:
I wanted to import some more song and did not find a video button on my remote. So I thought I would enable "update database at Start" and disable Hide Plugin during update. After the crash I made a reboot and tried to enter again the the MP3Browser to set it back, but it crashed just when entering.

I attach you the crash logs.

nekrub2

PS. Never change a winning horse ;-)

video button or "pvr" is the movie "playlist" button on remote

[Huevos]

... and 21:40:03.3407 {BackupManager] Backup failed - e. g. wrong backup destination or no space left on backup device

So also might be worth checking both space and that HDD is the device you are expecting it to be!

Yes but shouldn't crash. Crash is this:

21:40:03.3407 {BackupManager] Backup failed - e. g. wrong backup destination or no space left on backup device
21:40:13.3968 [MessageBox] Timeout!
21:40:13.4205 Traceback (most recent call last):
21:40:13.4211   File "/usr/lib/enigma2/python/StartEnigma.py", line 224, in processDelay
21:40:13.4299     callback(*retval)
21:40:13.4311 TypeError: BackupFiles.BackupComplete() takes 1 positional argument but 2 were given

Hopefully fixed with this:
https://github.com/OpenViX/vix-core/...e06b31c7564d3f

[nekrub2]

Hi Huevos

On your link I see src/BackupManager.py

Where would I have to copy this file in and would I need a reboot afterwards?

[Orlandox]

\Root\usr\lib\enigma2\python\Plugins\SystemPlugins \ViX\

[Huevos]

Hi Huevos

On your link I see src/BackupManager.py

Where would I have to copy this file in and would I need a reboot afterwards?

Just wait until the next build. But anyway why is /media/hdd read only. Have you touched a write protect slider on the card?

[nekrub2]

The USB is not write protect. I just made a new backup through the Backup Manager. It says under device: /media/hdd/
So it can't be completely write protect. I only can assume that some files for the cover pictures or the lyrics were by any reason write protected. The best is to remove the USB from my sat box, put it into my laptop and explore it under Linux Mint 21.

[Willo3092]

I noticed that some recordings had failed last night due to /media/hdd not being writeable. Mount Manager showed that the drive was marked as read only.
I did a full reboot and the drive won't mount at all now. I haven't had chance to investigate further yet. OpenViX 6.2.010 (2022-09-05) dev build on a GigaBlue UHD UE 4K.
My logs are set to save to hdd but I noticed there is a crash log in /home/root/.

Enigma2_crash_2022-09-21_06-51-43.log

I think it is probably generated because I have no hdd rather than showing why it was set to R/O

[Huevos]

I noticed that some recordings had failed last night due to /media/hdd not being writeable. Mount Manager showed that the drive was marked as read only.
I did a full reboot and the drive won't mount at all now. I haven't had chance to investigate further yet. OpenViX 6.2.010 (2022-09-05) dev build on a GigaBlue UHD UE 4K.
My logs are set to save to hdd but I noticed there is a crash log in /home/root/.

Enigma2_crash_2022-09-21_06-51-43.log

I think it is probably generated because I have no hdd rather than showing why it was set to R/O

That crash log is not related. Something went wrong in ABM run. You would need to retest with the latest version of dvbreader.py so the line number in the crash correspond with the current version.

No idea why your HDD is not writeable.

[twol]

I noticed that some recordings had failed last night due to /media/hdd not being writeable. Mount Manager showed that the drive was marked as read only.
I did a full reboot and the drive won't mount at all now. I haven't had chance to investigate further yet. OpenViX 6.2.010 (2022-09-05) dev build on a GigaBlue UHD UE 4K.
My logs are set to save to hdd but I noticed there is a crash log in /home/root/.

Enigma2_crash_2022-09-21_06-51-43.log

I think it is probably generated because I have no hdd rather than showing why it was set to R/O

Dmsg shows error:
3.419268] scsi 2:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
<5>[ 3.428685] sd 2:0:0:0: Attached scsi generic sg0 type 0
<5>[ 3.434637] sd 2:0:0:0: [sda] 240353280 512-byte logical blocks: (123 GB/115 GiB)
<5>[ 3.447080] sd 2:0:0:0: [sda] Write Protect is on
<7>[ 3.451834] sd 2:0:0:0: [sda] Mode Sense: 43 00 80 00
<5>[ 3.459208] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
<6>[ 3.498232] sda: sda1
<5>[ 3.502689] sd 2:0:0:0: [sda] Attached SCSI removable disk
<5>[ 3.556820] random: nonblocking pool is initialized
<6>[ 3.871703] EXT4-fs (mmcblk0p5): re-mounted. Opts: nodelalloc,data=journal
<6>[ 4.167945] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
<3>[ 4.174878] EXT4-fs (sda1): write access unavailable, cannot proceed
<3>[ 4.194909] EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (2c0)
<3>[ 4.206148] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (2c4)
<4>[ 4.221346] UDF-fs: warning (device sda1): udf_fill_super: No partition found (2)

[Willo3092]

I'll try another hdd later on. I added my post to this thread because nekrub2's hdd had suddenly become R/O as well. Just wondered if it was related.

[nekrub2]

I removed the USB HDD and plugged it into my laptop on the windows 7 partition. Indeed the directory mp3browser and its underlying sub-directories cache and db had the read only attribute. so I set them to read and write and attached the stick back to the box. When trying to update the MP3Browser database the box crashed again. This time I could read one error, saying
FAT-fs (sda1): error, fat_free_clusters: deleting FAT entry beyond EOF.
FAT-fs (sda1): Filesystem has been set read-only.

Could it be that I have a buggy stick and as soon as openvix detects this it sets it read-only?

I attach the crash log.

[bbbuk]

FAT-fs (sda1): error, fat_free_clusters: deleting FAT entry beyond EOF.
FAT-fs (sda1): Filesystem has been set read-only.

Could it be that I have a buggy stick and as soon as openvix detects this it sets it read-only?

I attach the crash log.

If this is a FAT/FAT32 formatted USB then I would plug this into a Windows device and do a full chkdisk (not quick).

It's talking about deleting File Allocation Table entry beyond the End of File so this doesn't sound promising

[nekrub2]

Dear all
I could fix my problem. 1. I made a chkdsk under windows (after copying the whole content on the HD). With this a big part of the problem was solved. When trying to import again it crashed again but this time I could read out that it had something to do with the character sets (windows versus UTF-8). And indeed, under Linux I could see file names that were broken because they had special characters in, which are different in the two system. After manual editing the files over ftp I did a now mp3browser update and it worked. 127 songs were imported.

Just for your information I attach the crash log related to the file names.

nekrub2