6 replies to this topic

[Isaac]

Hi,

 

I've installed "enigma2-plugin-extensions-backupsuite", opened it under Plugins and did a backup to my HDD (green key).

Everything looked good, see the finish dialog.

 

But my whole HDD is completely blank/empty now     

root@sf8008:/media/hdd# ls -la
root@sf8008:/media/hdd#

What I don't understand is that df -h still shows that 383.7G from 465.5G are used 

 

root@sf8008:/media/hdd# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/mmcblk0p16           7.1G      1.4G      5.4G  21% /
devtmpfs                458.3M      4.0K    458.3M   0% /dev
tmpfs                    64.0K         0     64.0K   0% /media
tmpfs                   458.6M    264.0K    458.3M   0% /run
tmpfs                   458.6M    828.0K    457.8M   0% /var/volatile
/dev/sdb1               465.5G    383.7G     81.8G  82% /media/hdd

 

Receiver

Marke & Modell: Octagon SF8008 4K Combo

Chipsatz (Frontprozessor-Version): 3798mv200 (0 )

Hauptspeicher: 697548 KB frei / 948868 KB insgesamt

 

Software

OE-System: PLi-OE

Firmware-Version: OpenPLi develop (2025-01-07-develop)

Kernel / Treiber: 4.4.35 / 20240104

 

root@sf8008:/media/hdd# opkg info enigma2-plugin-extensions-backupsuite
Package: enigma2-plugin-extensions-backupsuite
Version: git560+4501eb8-r0.0
Depends: enigma2-plugin-extensions-backupsuite, mtd-utils, mtd-utils-ubifs, ofgwrite
Status: install ok installed
Section: base
Architecture: cortexa15hf-neon-vfpv4
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
MD5Sum: 5b5ca7cc07795ef15ae0dd69c6b3c4f7
Size: 86808
Filename: enigma2-plugin-extensions-backupsuite_git560+4501eb8-r0.0_cortexa15hf-neon-vfpv4.ipk
Source: enigma2-plugin-extensions-backupsuite.bb
Description: Enigma2 Plugin: extensions-backupsuite
Installed-Size: 364518
Installed-Time: 1736422889

 

 BackupSuite.log   28.97KB   2 downloads

Attached Files

•  2025-01-09_Screenshot_4687.png   824.97KB   0 downloads
•  2025-01-09_Screenshot_4689.png   319.74KB   0 downloads

Edited by Tech, Today, 16:38.

[Isaac]

BackupSuite.log can also be found here: https://pastecode.io/s/ss41mbyy

 

(because I can't download the log file from post 1)

[Isaac]

dmesg grep for "error"

root@sf8008:~# dmesg | grep err
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
ahci: probe of f9900000.hiahci failed with error -1
blk_update_request: I/O error, dev sdb, sector 62914832
blk_update_request: I/O error, dev sdb, sector 62914840
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #19201: block 7864352: comm vsftpd: unable to read itable block
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #125: block 1064: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #126: block 1064: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #285441: block 116916256: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #58881: block 24117280: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #17921: block 7340064: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #102: block 1063: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #102401: block 41943072: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #122: block 1064: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs error (device sdb1): __ext4_get_inode_loc:4107: inode #129: block 1065: comm vsftpd: unable to read itable block
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs (sdb1): previous I/O error to superblock detected
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm find: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm rm: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm enigma2: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm enigma2: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm enigma2: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm enigma2: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm find: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm rm: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm vsftpd: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm vsftpd: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm ls: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm ls: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm vsftpd: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm ls: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm opkg: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm sh: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm sh: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm micro: error -5 reading directory block
EXT4-fs warning (device sdb1): dx_probe:739: inode #2: lblock 0: comm vsftpd: error -5 reading directory block

[Isaac]

complete dmesg can be found here: https://pastecode.io/s/sprz7t6r

[catastrofus]

Looks like your disk (sdb1) has died.

[Isaac]

I shutdown my SF8008 and started it again - now everything is back to normal - HDD is working again and has all the files/folders (inclusive the fullbackup from the BackupSuite) on it.

 

Very strange - best thing to do is make sure to have a full backup from the whole disk/hdd and look for a new hdd I think 

[Tech]

BackupSuite.log can also be found here: https://pastecode.io/s/ss41mbyy

 

(because I can't download the log file from post 1)

I have edited the message and the log can now be retrieved.