Internal DB storage is dropped after xxx time since upgrade to 6.1. **solved**

This section covers the Meteobridge PRO, PRO2, NANO SD, Raspberry Pi and VM platforms exclusively

Moderator: Mattk

Post Reply
robr57
Senior Boarder
Senior Boarder
Posts: 43
Joined: Fri Jan 03, 2020 2:37 pm
Contact:

Internal DB storage is dropped after xxx time since upgrade to 6.1. **solved**

Post by robr57 »

Since upgrade to 6.1 on PRO (Red) the internal storage gets dropped after xxx hours.
This issue is in addition to the other issue that I posted before.

After cold reboot (power off / on) the system is back on, but obviously the last hours off data is lost.

I cannot determine what is causing it, but it seems to be a memory or USB problem.

In system log I do not see problem with the internal USB storage during boot.

Fri Dec 27 17:04:17 2024 user.emerg syslog: HW: Carambola2
Fri Dec 27 17:04:17 2024 user.emerg syslog: FW: 1.4
Fri Dec 27 17:04:17 2024 user.emerg syslog: MAC: C4:93:00:10:1B:3A
Fri Dec 27 17:04:22 2024 user.emerg syslog: USB stick /dev/sda1 detected
Fri Dec 27 17:04:23 2024 user.emerg syslog: rescue download to be started
Fri Dec 27 17:04:23 2024 user.emerg syslog: rescue download ended
Fri Dec 27 17:04:23 2024 user.emerg syslog: LED path: /sys/class/leds/carambola2:green:system
Fri Dec 27 17:04:23 2024 user.emerg syslog: Meteobridge PRO storage, port 4, device /dev/sdb.
Fri Dec 27 17:04:23 2024 user.emerg syslog: Use existing formatted USB storage
Fri Dec 27 17:04:24 2024 user.emerg syslog: start filesystem check: /dev/sdb
Fri Dec 27 17:04:24 2024 user.emerg syslog: /dev/sdb: clean, 135/61440 files, 121585/245632 blocks

But in system log I found this today:

Sat Dec 28 11:33:09 2024 kern.info kernel: [ 976.100000] usb 1-1.4: reset high-speed USB device number 5 using ehci-platform
But this seems not causing the problem, as the system is still up after this message.

Boris, any clue what goes on ?

Next time I will try to get the full log before reboot.
User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 7854
Joined: Mon Oct 01, 2007 10:51 pm

Re: Internal DB storage is dropped after xxx time since upgrade to 6.1

Post by admin »

When you have a partial defective internal USB hub chip, this can have the effect of resets/drops of USB connections. But there are also events, when Meteobridge does a USB reset. To judge on this, I need the complete dmesg and a remote login will also help.

If it is a USB hub chip defect, I will repair this.
robr57
Senior Boarder
Senior Boarder
Posts: 43
Joined: Fri Jan 03, 2020 2:37 pm
Contact:

Re: Internal DB storage is dropped after xxx time since upgrade to 6.1

Post by robr57 »

Boris,

this is the current log. It seems a problem with the internal disk. It is automatic restarting it seems.

Is it possible to repair ? How can I provide access ?

Thanks in advance.

oled (27.12.2024 17:03:54): process started.
setup (28.12.2024 12:18:06): use UTC stamp 2024-12-28 11:18:06 (1 tries)
dbase (28.12.2024 12:18:15): process started.
dbase (28.12.2024 12:18:16): Content of RAM database restored.
wnetd (28.12.2024 12:18:18): process started.
wnetd (28.12.2024 12:18:18): send data thread started (pid:2343 tid:2345)
system (28.12.2024 12:18:18): start of logging process initiated.
logger (28.12.2024 12:18:19): databases connected. Update interval 3600 seconds.
logger (28.12.2024 12:18:19): data logger started.
logger (28.12.2024 12:18:23): connect station 0 (Meteostick Vantage via USB serial).
logger (28.12.2024 12:18:23): connect station 1 (AirLink via SW Driver).
logger (28.12.2024 12:18:23): connect station 9 (System Data via Plug-in).
logger (28.12.2024 12:18:24): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (28.12.2024 12:18:24): services paused.
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), transmitter 2 registered as Soil
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), transmitter 3 registered as Wind
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), debug off
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), verbose off
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), filter on
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), rx threshold set to -90db
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), listening to transmitter 1 2 3
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), bandwidth narrow
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (28.12.2024 12:18:25): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
dbase (28.12.2024 12:19:02): database sync done (87 tables, 49/2354 writes).
logger (28.12.2024 12:20:19): give up waiting for sensors after 120 secs.
logger (28.12.2024 12:20:19): services activated.
dbase (28.12.2024 12:32:08): cannot insert into 'th11hum_min' (after 100 tries in 9601ms): database is locked (5)
dbase (28.12.2024 12:32:08): rollback on insert forced (1) (storemin): th11hum
dbase (28.12.2024 12:33:12): cannot insert into 'th10hum_min' (after 100 tries in 40132ms): database is locked (5)
dbase (28.12.2024 12:33:12): rollback on insert forced (1) (storemin): th10hum
backup (28.12.2024 13:22:11): backup media size is 29.3G (28.9G free).
backup (28.12.2024 13:25:32): backup completed: dbase-202412281322 (422.3M)
logger (28.12.2024 14:01:07): DB cannot retrieve 'th0temp_hour' (100 tries, 9115ms): database is locked (5)
dbase (28.12.2024 14:01:14): cannot commit (after 0 tries in 32024ms): disk I/O error (10)
dbase (28.12.2024 14:01:14): cannot rollback (after 0 tries in 1ms): cannot rollback - no transaction is active (1)
dbase (28.12.2024 14:01:14): failed with step exist record on 'th13signal_hour' (after 0 retries in 1ms): unable to open database file (14)
dbase (28.12.2024 14:01:14): rollback on update forced (min): th13signal
system (28.12.2024 14:06:13): stop of logging process initiated.
logger (28.12.2024 14:06:13): parent process received termination signal (15).
logger (28.12.2024 14:06:13): child process received termination signal (15).
logger (28.12.2024 14:06:13): disconnect station 0 (Meteostick Vantage): exit
logger (28.12.2024 14:06:13): disconnect station 1 (AirLink): exit
logger (28.12.2024 14:06:13): disconnect station 9 (System Data): exit
test5m (28.12.2024 13:06:14): USB storage remounted: /dev/sdc
dbase (28.12.2024 14:06:14): process started.
system (28.12.2024 14:06:15): start of logging process initiated.
logger (28.12.2024 14:06:15): databases connected. Update interval 3600 seconds.
logger (28.12.2024 14:06:16): data logger started.
logger (28.12.2024 14:06:16): error (125) while doing bind (port 5557): Address already in use
logger (28.12.2024 14:06:16): killed process "23773/sleep" listening to port 5557.
logger (28.12.2024 14:06:45): databases connected. Update interval 3600 seconds.
logger (28.12.2024 14:06:45): data logger started.
logger (28.12.2024 14:06:47): connect station 0 (Meteostick Vantage via USB serial).
logger (28.12.2024 14:06:47): connect station 1 (AirLink via SW Driver).
logger (28.12.2024 14:06:47): connect station 9 (System Data via Plug-in).
logger (28.12.2024 14:06:47): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (28.12.2024 14:06:47): services paused.
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), transmitter 2 registered as Soil
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), transmitter 3 registered as Wind
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), debug off
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), verbose off
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), filter on
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), rx threshold set to -90db
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), listening to transmitter 1 2 3
logger (28.12.2024 14:06:48): station 0 (Meteostick Vantage), bandwidth narrow
logger (28.12.2024 14:06:49): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (28.12.2024 14:06:49): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
dbase (28.12.2024 14:07:11): database sync done (87 tables, 116/3241 writes).
logger (28.12.2024 14:08:47): give up waiting for sensors after 120 secs.
logger (28.12.2024 14:08:47): services activated.
logger (28.12.2024 15:01:11): DB cannot retrieve 'wind0wind_year' (100 tries, 9081ms): database is locked (5)
logger (28.12.2024 15:01:21): DB cannot retrieve 'wind0wind_year' (100 tries, 9088ms): database is locked (5)
logger (28.12.2024 15:01:30): DB cannot retrieve 'rain0total_day' (100 tries, 9068ms): database is locked (5)
dbase (28.12.2024 15:01:35): cannot commit (after 0 tries in 32963ms): disk I/O error (10)
dbase (28.12.2024 15:01:35): cannot rollback (after 0 tries in 1ms): cannot rollback - no transaction is active (1)
dbase (28.12.2024 15:01:35): failed with step exist record on 'th1!8wetbulb_hour' (after 0 retries in 30ms): disk I/O error (10)
dbase (28.12.2024 15:01:35): rollback on update forced (min): th1!8wetbulb
dbase (28.12.2024 15:01:35): cannot rollback (after 0 tries in 1ms): cannot rollback - no transaction is active (1)
system (28.12.2024 15:06:39): stop of logging process initiated.
logger (28.12.2024 15:06:39): parent process received termination signal (15).
logger (28.12.2024 15:06:39): child process received termination signal (15).
logger (28.12.2024 15:06:39): disconnect station 0 (Meteostick Vantage): exit
logger (28.12.2024 15:06:39): disconnect station 1 (AirLink): exit
logger (28.12.2024 15:06:39): disconnect station 9 (System Data): exit
test5m (28.12.2024 14:06:41): USB storage remounted: /dev/sdd
dbase (28.12.2024 15:06:41): process started.
system (28.12.2024 15:06:41): start of logging process initiated.
logger (28.12.2024 15:06:42): databases connected. Update interval 3600 seconds.
logger (28.12.2024 15:06:42): data logger started.
logger (28.12.2024 15:06:43): connect station 0 (Meteostick Vantage via USB serial).
logger (28.12.2024 15:06:43): connect station 1 (AirLink via SW Driver).
logger (28.12.2024 15:06:43): connect station 9 (System Data via Plug-in).
logger (28.12.2024 15:06:44): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (28.12.2024 15:06:44): services paused.
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), transmitter 2 registered as Soil
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), transmitter 3 registered as Wind
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), debug off
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), verbose off
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), filter on
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), rx threshold set to -90db
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), listening to transmitter 1 2 3
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), bandwidth narrow
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (28.12.2024 15:06:45): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
dbase (28.12.2024 15:07:22): database sync done (87 tables, 14/3389 writes).
logger (28.12.2024 15:08:43): give up waiting for sensors after 120 secs.
logger (28.12.2024 15:08:43): services activated.

In the System Log
Sat Dec 28 11:22:17 2024 user.emerg syslog: - init complete -
Sat Dec 28 11:33:09 2024 kern.info kernel: [ 976.100000] usb 1-1.4: reset high-speed USB device number 5 using ehci-platform
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.080000] sd 1:0:0:0: Device offlined - not ready after error recovery
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.080000] sd 1:0:0:0: [sdb] Unhandled error code
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.090000] sd 1:0:0:0: [sdb]
Sat Dec 28 13:01:14 2024 kern.warn kernel: [ 6261.090000] Result: hostbyte=0x05 driverbyte=0x00
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.090000] sd 1:0:0:0: [sdb] CDB:
Sat Dec 28 13:01:14 2024 kern.warn kernel: [ 6261.100000] cdb[0]=0x2a: 2a 00 00 08 7c 10 00 00 10 00
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.100000] end_request: I/O error, dev sdb, sector 556048
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.110000] sd 1:0:0:0: [sdb] killing request
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.140000] sd 1:0:0:0: [sdb] Unhandled error code
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.150000] sd 1:0:0:0: [sdb]
Sat Dec 28 13:01:14 2024 kern.warn kernel: [ 6261.150000] Result: hostbyte=0x01 driverbyte=0x00
Sat Dec 28 13:01:14 2024 kern.info kernel: [ 6261.160000] sd 1:0:0:0: [sdb] CDB:
Sat Dec 28 13:01:14 2024 kern.warn kernel: [ 6261.160000] cdb[0]=0x2a: 2a 00 00 00 00 00 00 00 10 00
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.160000] end_request: I/O error, dev sdb, sector 0
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.170000] Buffer I/O error on device sdb, logical block 0
Sat Dec 28 13:01:14 2024 kern.warn kernel: [ 6261.170000] lost page write due to I/O error on sdb
Sat Dec 28 13:01:14 2024 kern.err kernel: [ 6261.180000] Buffer I/O error on device sdb, logical block 1
Sat Dec 28 13:01:14 2024 kern.warn kernel: [ 6261.190000] lost page write due to I/O error on sdb
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.190000] Aborting journal on device sdb-8.
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.200000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.200000] JBD2: Error -5 detected when updating journal superblock for sdb-8.
Sat Dec 28 13:01:15 2024 kern.emerg kernel: [ 6261.220000] journal commit I/O error
Sat Dec 28 13:01:15 2024 kern.emerg kernel: [ 6261.220000] journal commit I/O error
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.220000] EXT4-fs (sdb): previous I/O error to superblock detected
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.230000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:15 2024 kern.crit kernel: [ 6261.230000] EXT4-fs error (device sdb): __ext4_journal_start_sb:62: Detected aborted journal
Sat Dec 28 13:01:15 2024 kern.crit kernel: [ 6261.240000] EXT4-fs (sdb): Remounting filesystem read-only
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.250000] EXT4-fs (sdb): previous I/O error to superblock detected
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.250000] sd 1:0:0:0: rejecting I/O to offline device
Sat Dec 28 13:01:15 2024 kern.info kernel: [ 6261.260000] usb 1-1.4: USB disconnect, device number 5
Sat Dec 28 13:01:15 2024 kern.err kernel: [ 6261.360000] EXT4-fs (sdb): previous I/O error to superblock detected
Sat Dec 28 13:01:15 2024 kern.crit kernel: [ 6261.370000] EXT4-fs error (device sdb): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
Sat Dec 28 13:01:15 2024 kern.crit kernel: [ 6261.520000] EXT4-fs error (device sdb): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
Sat Dec 28 13:01:15 2024 kern.info kernel: [ 6261.750000] usb 1-1.4: new high-speed USB device number 6 using ehci-platform
Sat Dec 28 13:01:15 2024 kern.info kernel: [ 6262.130000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sat Dec 28 13:01:15 2024 kern.info kernel: [ 6262.160000] scsi3 : usb-storage 1-1.4:1.0
Sat Dec 28 13:01:16 2024 kern.notice kernel: [ 6263.480000] scsi 3:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
Sat Dec 28 13:01:17 2024 kern.notice kernel: [ 6263.530000] sd 3:0:0:0: Attached scsi generic sg1 type 0
Sat Dec 28 13:01:17 2024 kern.notice kernel: [ 6263.530000] sd 3:0:0:0: [sdc] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
Sat Dec 28 13:01:17 2024 kern.notice kernel: [ 6263.570000] sd 3:0:0:0: [sdc] Write Protect is off
Sat Dec 28 13:01:17 2024 kern.debug kernel: [ 6263.580000] sd 3:0:0:0: [sdc] Mode Sense: 43 00 00 00
Sat Dec 28 13:01:17 2024 kern.err kernel: [ 6263.740000] sd 3:0:0:0: [sdc] No Caching mode page found
Sat Dec 28 13:01:17 2024 kern.err kernel: [ 6263.750000] sd 3:0:0:0: [sdc] Assuming drive cache: write through
Sat Dec 28 13:01:17 2024 kern.err kernel: [ 6264.290000] sd 3:0:0:0: [sdc] No Caching mode page found
Sat Dec 28 13:01:17 2024 kern.err kernel: [ 6264.290000] sd 3:0:0:0: [sdc] Assuming drive cache: write through
Sat Dec 28 13:01:17 2024 kern.info kernel: [ 6264.330000] sdc: unknown partition table
Sat Dec 28 13:01:17 2024 kern.err kernel: [ 6264.330000] sd 3:0:0:0: [sdc] No Caching mode page found
Sat Dec 28 13:01:17 2024 kern.err kernel: [ 6264.340000] sd 3:0:0:0: [sdc] Assuming drive cache: write through
Sat Dec 28 13:01:17 2024 kern.notice kernel: [ 6264.340000] sd 3:0:0:0: [sdc] Attached SCSI removable disk
Sat Dec 28 13:01:21 2024 kern.info kernel: [ 6267.670000] EXT4-fs (sdc): recovery complete
Sat Dec 28 13:01:21 2024 kern.info kernel: [ 6267.670000] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts:
Sat Dec 28 13:06:10 2024 kern.info kernel: [ 6556.980000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sat Dec 28 13:06:10 2024 kern.info kernel: [ 6557.000000] scsi4 : usb-storage 1-1.4:1.0
Sat Dec 28 13:06:11 2024 kern.notice kernel: [ 6558.020000] scsi 4:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
Sat Dec 28 13:06:11 2024 kern.notice kernel: [ 6558.030000] sd 4:0:0:0: [sdc] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
Sat Dec 28 13:06:11 2024 kern.notice kernel: [ 6558.040000] sd 4:0:0:0: Attached scsi generic sg1 type 0
Sat Dec 28 13:06:11 2024 kern.notice kernel: [ 6558.040000] sd 4:0:0:0: [sdc] Write Protect is off
Sat Dec 28 13:06:11 2024 kern.debug kernel: [ 6558.050000] sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
Sat Dec 28 13:06:11 2024 kern.err kernel: [ 6558.050000] sd 4:0:0:0: [sdc] No Caching mode page found
Sat Dec 28 13:06:11 2024 kern.err kernel: [ 6558.060000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
Sat Dec 28 13:06:11 2024 kern.err kernel: [ 6558.070000] sd 4:0:0:0: [sdc] No Caching mode page found
Sat Dec 28 13:06:11 2024 kern.err kernel: [ 6558.070000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
Sat Dec 28 13:06:11 2024 kern.info kernel: [ 6558.100000] sdc: unknown partition table
Sat Dec 28 13:06:11 2024 kern.err kernel: [ 6558.110000] sd 4:0:0:0: [sdc] No Caching mode page found
Sat Dec 28 13:06:11 2024 kern.err kernel: [ 6558.110000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
Sat Dec 28 13:06:11 2024 kern.notice kernel: [ 6558.120000] sd 4:0:0:0: [sdc] Attached SCSI removable disk
Sat Dec 28 13:06:11 2024 kern.info kernel: [ 6558.400000] EXT4-fs (sdc): recovery complete
Sat Dec 28 13:06:11 2024 kern.info kernel: [ 6558.400000] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts:
Sat Dec 28 13:06:14 2024 kern.info kernel: [ 6561.360000] EXT4-fs (sdc): re-mounted. Opts: data=ordered,commit=60,max_batch_time=1000000,min_batch_time=1000000,errors=remount-ro
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.080000] sd 4:0:0:0: Device offlined - not ready after error recovery
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.080000] sd 4:0:0:0: [sdc] Unhandled error code
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.090000] sd 4:0:0:0: [sdc]
Sat Dec 28 14:01:35 2024 kern.warn kernel: [ 9882.090000] Result: hostbyte=0x05 driverbyte=0x00
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.090000] sd 4:0:0:0: [sdc] CDB:
Sat Dec 28 14:01:35 2024 kern.warn kernel: [ 9882.100000] cdb[0]=0x2a: 2a 00 00 00 01 f0 00 00 08 00
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.100000] end_request: I/O error, dev sdc, sector 496
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.110000] Buffer I/O error on device sdc, logical block 62
Sat Dec 28 14:01:35 2024 kern.warn kernel: [ 9882.110000] lost page write due to I/O error on sdc
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.120000] sd 4:0:0:0: [sdc] killing request
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.150000] sd 4:0:0:0: [sdc] Unhandled error code
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.150000] sd 4:0:0:0: [sdc]
Sat Dec 28 14:01:35 2024 kern.warn kernel: [ 9882.160000] Result: hostbyte=0x01 driverbyte=0x00
Sat Dec 28 14:01:35 2024 kern.info kernel: [ 9882.160000] sd 4:0:0:0: [sdc] CDB:
Sat Dec 28 14:01:35 2024 kern.warn kernel: [ 9882.160000] cdb[0]=0x2a: 2a 00 00 00 02 28 00 00 08 00
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.170000] end_request: I/O error, dev sdc, sector 552
Sat Dec 28 14:01:35 2024 kern.err kernel: [ 9882.170000] Buffer I/O error on device sdc, logical block 69
Sat Dec 28 14:01:35 2024 kern.warn kernel: [ 9882.180000] lost page write due to I/O error on sdc
Sat Dec 28 14:01:36 2024 kern.err kernel: [ 9882.190000] Aborting journal on device sdc-8.
Sat Dec 28 14:01:36 2024 kern.err kernel: [ 9882.190000] sd 4:0:0:0: rejecting I/O to offline device
Sat Dec 28 14:01:36 2024 kern.err kernel: [ 9882.200000] JBD2: Error -5 detected when updating journal superblock for sdc-8.
Sat Dec 28 14:01:36 2024 kern.info kernel: [ 9882.200000] usb 1-1.4: USB disconnect, device number 6
Sat Dec 28 14:01:36 2024 kern.emerg kernel: [ 9882.220000] journal commit I/O error
Sat Dec 28 14:01:36 2024 kern.crit kernel: [ 9882.220000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm databased: reading directory lblock 0
Sat Dec 28 14:01:36 2024 kern.crit kernel: [ 9882.230000] EXT4-fs (sdc): Remounting filesystem read-only
Sat Dec 28 14:01:36 2024 kern.crit kernel: [ 9882.340000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
Sat Dec 28 14:01:36 2024 kern.crit kernel: [ 9882.360000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm databased: reading directory lblock 0
Sat Dec 28 14:01:36 2024 kern.crit kernel: [ 9882.460000] EXT4-fs error (device sdc): ext4_wait_block_bitmap:466: comm databased: Cannot read block bitmap - block_group = 5, block_bitmap = 66
Sat Dec 28 14:01:36 2024 kern.crit kernel: [ 9882.470000] EXT4-fs error (device sdc): ext4_discard_preallocations:3935: comm databased: Error loading buddy information for 5
Sat Dec 28 14:01:36 2024 kern.info kernel: [ 9883.210000] usb 1-1.4: new high-speed USB device number 7 using ehci-platform
Sat Dec 28 14:01:37 2024 kern.info kernel: [ 9883.490000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sat Dec 28 14:01:37 2024 kern.info kernel: [ 9883.490000] scsi5 : usb-storage 1-1.4:1.0
Sat Dec 28 14:01:37 2024 kern.crit kernel: [ 9883.710000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm test5m.sh: reading directory lblock 0
Sat Dec 28 14:01:37 2024 kern.crit kernel: [ 9884.170000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
Sat Dec 28 14:01:38 2024 kern.notice kernel: [ 9884.880000] scsi 5:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
Sat Dec 28 14:01:38 2024 kern.notice kernel: [ 9884.900000] sd 5:0:0:0: [sdd] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
Sat Dec 28 14:01:38 2024 kern.notice kernel: [ 9884.910000] sd 5:0:0:0: Attached scsi generic sg1 type 0
Sat Dec 28 14:01:38 2024 kern.notice kernel: [ 9884.930000] sd 5:0:0:0: [sdd] Write Protect is off
Sat Dec 28 14:01:38 2024 kern.debug kernel: [ 9884.940000] sd 5:0:0:0: [sdd] Mode Sense: 43 00 00 00
Sat Dec 28 14:01:38 2024 kern.err kernel: [ 9884.980000] sd 5:0:0:0: [sdd] No Caching mode page found
Sat Dec 28 14:01:38 2024 kern.err kernel: [ 9884.980000] sd 5:0:0:0: [sdd] Assuming drive cache: write through
Sat Dec 28 14:01:38 2024 kern.err kernel: [ 9885.010000] sd 5:0:0:0: [sdd] No Caching mode page found
Sat Dec 28 14:01:38 2024 kern.err kernel: [ 9885.020000] sd 5:0:0:0: [sdd] Assuming drive cache: write through
Sat Dec 28 14:01:38 2024 kern.info kernel: [ 9885.130000] sdd: unknown partition table
Sat Dec 28 14:01:38 2024 kern.err kernel: [ 9885.140000] sd 5:0:0:0: [sdd] No Caching mode page found
Sat Dec 28 14:01:38 2024 kern.err kernel: [ 9885.140000] sd 5:0:0:0: [sdd] Assuming drive cache: write through
Sat Dec 28 14:01:38 2024 kern.notice kernel: [ 9885.150000] sd 5:0:0:0: [sdd] Attached SCSI removable disk
Sat Dec 28 14:01:43 2024 kern.info kernel: [ 9889.940000] EXT4-fs (sdd): recovery complete
Sat Dec 28 14:01:43 2024 kern.info kernel: [ 9889.950000] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts:
Sat Dec 28 14:06:36 2024 kern.info kernel: [10183.140000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sat Dec 28 14:06:36 2024 kern.info kernel: [10183.140000] scsi6 : usb-storage 1-1.4:1.0
Sat Dec 28 14:06:37 2024 kern.notice kernel: [10184.150000] scsi 6:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
Sat Dec 28 14:06:37 2024 kern.notice kernel: [10184.160000] sd 6:0:0:0: Attached scsi generic sg1 type 0
Sat Dec 28 14:06:37 2024 kern.notice kernel: [10184.160000] sd 6:0:0:0: [sdd] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
Sat Dec 28 14:06:37 2024 kern.notice kernel: [10184.170000] sd 6:0:0:0: [sdd] Write Protect is off
Sat Dec 28 14:06:37 2024 kern.debug kernel: [10184.180000] sd 6:0:0:0: [sdd] Mode Sense: 43 00 00 00
Sat Dec 28 14:06:37 2024 kern.err kernel: [10184.180000] sd 6:0:0:0: [sdd] No Caching mode page found
Sat Dec 28 14:06:37 2024 kern.err kernel: [10184.190000] sd 6:0:0:0: [sdd] Assuming drive cache: write through
Sat Dec 28 14:06:37 2024 kern.err kernel: [10184.200000] sd 6:0:0:0: [sdd] No Caching mode page found
Sat Dec 28 14:06:37 2024 kern.err kernel: [10184.200000] sd 6:0:0:0: [sdd] Assuming drive cache: write through
Sat Dec 28 14:06:37 2024 kern.info kernel: [10184.210000] sdd: unknown partition table
Sat Dec 28 14:06:37 2024 kern.err kernel: [10184.220000] sd 6:0:0:0: [sdd] No Caching mode page found
Sat Dec 28 14:06:37 2024 kern.err kernel: [10184.220000] sd 6:0:0:0: [sdd] Assuming drive cache: write through
Sat Dec 28 14:06:37 2024 kern.notice kernel: [10184.230000] sd 6:0:0:0: [sdd] Attached SCSI removable disk
Sat Dec 28 14:06:37 2024 kern.info kernel: [10184.310000] EXT4-fs (sdd): recovery complete
Sat Dec 28 14:06:37 2024 kern.info kernel: [10184.310000] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts:
Sat Dec 28 14:06:41 2024 kern.info kernel: [10187.660000] EXT4-fs (sdd): re-mounted. Opts: data=ordered,commit=60,max_batch_time=1000000,min_batch_time=1000000,errors=remount-ro


In the Kernel-log
6261.080000] sd 1:0:0:0: Device offlined - not ready after error recovery
[ 6261.080000] sd 1:0:0:0: [sdb] Unhandled error code
[ 6261.090000] sd 1:0:0:0: [sdb]
[ 6261.090000] Result: hostbyte=0x05 driverbyte=0x00
[ 6261.090000] sd 1:0:0:0: [sdb] CDB:
[ 6261.100000] cdb[0]=0x2a: 2a 00 00 08 7c 10 00 00 10 00
[ 6261.100000] end_request: I/O error, dev sdb, sector 556048
[ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.110000] sd 1:0:0:0: [sdb] killing request
[ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.110000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.140000] sd 1:0:0:0: [sdb] Unhandled error code
[ 6261.150000] sd 1:0:0:0: [sdb]
[ 6261.150000] Result: hostbyte=0x01 driverbyte=0x00
[ 6261.160000] sd 1:0:0:0: [sdb] CDB:
[ 6261.160000] cdb[0]=0x2a: 2a 00 00 00 00 00 00 00 10 00
[ 6261.160000] end_request: I/O error, dev sdb, sector 0
[ 6261.170000] Buffer I/O error on device sdb, logical block 0
[ 6261.170000] lost page write due to I/O error on sdb
[ 6261.180000] Buffer I/O error on device sdb, logical block 1
[ 6261.190000] lost page write due to I/O error on sdb
[ 6261.190000] Aborting journal on device sdb-8.
[ 6261.200000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.200000] JBD2: Error -5 detected when updating journal superblock for sdb-8.
[ 6261.220000] journal commit I/O error
[ 6261.220000] journal commit I/O error
[ 6261.220000] EXT4-fs (sdb): previous I/O error to superblock detected
[ 6261.230000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.230000] EXT4-fs error (device sdb): __ext4_journal_start_sb:62: Detected aborted journal
[ 6261.240000] EXT4-fs (sdb): Remounting filesystem read-only
[ 6261.250000] EXT4-fs (sdb): previous I/O error to superblock detected
[ 6261.250000] sd 1:0:0:0: rejecting I/O to offline device
[ 6261.260000] usb 1-1.4: USB disconnect, device number 5
[ 6261.360000] EXT4-fs (sdb): previous I/O error to superblock detected
[ 6261.370000] EXT4-fs error (device sdb): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
[ 6261.520000] EXT4-fs error (device sdb): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
[ 6261.750000] usb 1-1.4: new high-speed USB device number 6 using ehci-platform
[ 6262.130000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 6262.160000] scsi3 : usb-storage 1-1.4:1.0
[ 6263.480000] scsi 3:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
[ 6263.530000] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 6263.530000] sd 3:0:0:0: [sdc] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
[ 6263.570000] sd 3:0:0:0: [sdc] Write Protect is off
[ 6263.580000] sd 3:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 6263.740000] sd 3:0:0:0: [sdc] No Caching mode page found
[ 6263.750000] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 6264.290000] sd 3:0:0:0: [sdc] No Caching mode page found
[ 6264.290000] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 6264.330000] sdc: unknown partition table
[ 6264.330000] sd 3:0:0:0: [sdc] No Caching mode page found
[ 6264.340000] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 6264.340000] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[ 6267.670000] EXT4-fs (sdc): recovery complete
[ 6267.670000] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts:
[ 6556.980000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 6557.000000] scsi4 : usb-storage 1-1.4:1.0
[ 6558.020000] scsi 4:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
[ 6558.030000] sd 4:0:0:0: [sdc] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
[ 6558.040000] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ 6558.040000] sd 4:0:0:0: [sdc] Write Protect is off
[ 6558.050000] sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 6558.050000] sd 4:0:0:0: [sdc] No Caching mode page found
[ 6558.060000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 6558.070000] sd 4:0:0:0: [sdc] No Caching mode page found
[ 6558.070000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 6558.100000] sdc: unknown partition table
[ 6558.110000] sd 4:0:0:0: [sdc] No Caching mode page found
[ 6558.110000] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 6558.120000] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[ 6558.400000] EXT4-fs (sdc): recovery complete
[ 6558.400000] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts:
[ 6561.360000] EXT4-fs (sdc): re-mounted. Opts: data=ordered,commit=60,max_batch_time=1000000,min_batch_time=1000000,errors=remount-ro

This then repeats approximately one hour later.

{9882.080000] sd 4:0:0:0: Device offlined - not ready after error recovery
[ 9882.080000] sd 4:0:0:0: [sdc] Unhandled error code
[ 9882.090000] sd 4:0:0:0: [sdc]
[ 9882.090000] Result: hostbyte=0x05 driverbyte=0x00
[ 9882.090000] sd 4:0:0:0: [sdc] CDB:
[ 9882.100000] cdb[0]=0x2a: 2a 00 00 00 01 f0 00 00 08 00
[ 9882.100000] end_request: I/O error, dev sdc, sector 496
[ 9882.110000] Buffer I/O error on device sdc, logical block 62
[ 9882.110000] lost page write due to I/O error on sdc
[ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
[ 9882.120000] sd 4:0:0:0: [sdc] killing request
[ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
[ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
[ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
[ 9882.120000] sd 4:0:0:0: rejecting I/O to offline device
[ 9882.150000] sd 4:0:0:0: [sdc] Unhandled error code
[ 9882.150000] sd 4:0:0:0: [sdc]
[ 9882.160000] Result: hostbyte=0x01 driverbyte=0x00
[ 9882.160000] sd 4:0:0:0: [sdc] CDB:
[ 9882.160000] cdb[0]=0x2a: 2a 00 00 00 02 28 00 00 08 00
[ 9882.170000] end_request: I/O error, dev sdc, sector 552
[ 9882.170000] Buffer I/O error on device sdc, logical block 69
[ 9882.180000] lost page write due to I/O error on sdc
[ 9882.190000] Aborting journal on device sdc-8.
[ 9882.190000] sd 4:0:0:0: rejecting I/O to offline device
[ 9882.200000] JBD2: Error -5 detected when updating journal superblock for sdc-8.
[ 9882.200000] usb 1-1.4: USB disconnect, device number 6
[ 9882.220000] journal commit I/O error
[ 9882.220000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm databased: reading directory lblock 0
[ 9882.230000] EXT4-fs (sdc): Remounting filesystem read-only
[ 9882.340000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
[ 9882.360000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm databased: reading directory lblock 0
[ 9882.460000] EXT4-fs error (device sdc): ext4_wait_block_bitmap:466: comm databased: Cannot read block bitmap - block_group = 5, block_bitmap = 66
[ 9882.470000] EXT4-fs error (device sdc): ext4_discard_preallocations:3935: comm databased: Error loading buddy information for 5
[ 9883.210000] usb 1-1.4: new high-speed USB device number 7 using ehci-platform
[ 9883.490000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 9883.490000] scsi5 : usb-storage 1-1.4:1.0
[ 9883.710000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm test5m.sh: reading directory lblock 0
[ 9884.170000] EXT4-fs error (device sdc): ext4_find_entry:1309: inode #2: comm loggerd: reading directory lblock 0
[ 9884.880000] scsi 5:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
[ 9884.900000] sd 5:0:0:0: [sdd] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
[ 9884.910000] sd 5:0:0:0: Attached scsi generic sg1 type 0
[ 9884.930000] sd 5:0:0:0: [sdd] Write Protect is off
[ 9884.940000] sd 5:0:0:0: [sdd] Mode Sense: 43 00 00 00
[ 9884.980000] sd 5:0:0:0: [sdd] No Caching mode page found
[ 9884.980000] sd 5:0:0:0: [sdd] Assuming drive cache: write through
[ 9885.010000] sd 5:0:0:0: [sdd] No Caching mode page found
[ 9885.020000] sd 5:0:0:0: [sdd] Assuming drive cache: write through
[ 9885.130000] sdd: unknown partition table
[ 9885.140000] sd 5:0:0:0: [sdd] No Caching mode page found
[ 9885.140000] sd 5:0:0:0: [sdd] Assuming drive cache: write through
[ 9885.150000] sd 5:0:0:0: [sdd] Attached SCSI removable disk
[ 9889.940000] EXT4-fs (sdd): recovery complete
[ 9889.950000] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts:
[10183.140000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[10183.140000] scsi6 : usb-storage 1-1.4:1.0
[10184.150000] scsi 6:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
[10184.160000] sd 6:0:0:0: Attached scsi generic sg1 type 0
[10184.160000] sd 6:0:0:0: [sdd] 1965056 512-byte logical blocks: (1.00 GB/959 MiB)
[10184.170000] sd 6:0:0:0: [sdd] Write Protect is off
[10184.180000] sd 6:0:0:0: [sdd] Mode Sense: 43 00 00 00
[10184.180000] sd 6:0:0:0: [sdd] No Caching mode page found
[10184.190000] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[10184.200000] sd 6:0:0:0: [sdd] No Caching mode page found
[10184.200000] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[10184.210000] sdd: unknown partition table
[10184.220000] sd 6:0:0:0: [sdd] No Caching mode page found
[10184.220000] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[10184.230000] sd 6:0:0:0: [sdd] Attached SCSI removable disk
[10184.310000] EXT4-fs (sdd): recovery complete
[10184.310000] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts:
[10187.660000] EXT4-fs (sdd): re-mounted. Opts: data=ordered,commit=60,max_batch_time=1000000,min_batch_time=1000000,errors=remount-ro
Mattk
Platinum Boarder
Platinum Boarder
Posts: 1387
Joined: Mon Sep 22, 2014 3:24 am

Re: Internal DB storage is dropped after xxx time since upgrade to 6.1

Post by Mattk »

...How can I provide access ?...
As per the FAQ viewtopic.php?t=9885

Send URL and Password credentials to ,,info(at)meteobridge.com“
robr57
Senior Boarder
Senior Boarder
Posts: 43
Joined: Fri Jan 03, 2020 2:37 pm
Contact:

Re: Internal DB storage is dropped after xxx time since upgrade to 6.1

Post by robr57 »

Hi, send info with PDF of latest logs. The internal storage is currently offline due to the error. If needed I can do a cold reboot.

Thanks for your support and I hope it is a driver problem.
robr57
Senior Boarder
Senior Boarder
Posts: 43
Joined: Fri Jan 03, 2020 2:37 pm
Contact:

Re: Internal DB storage is dropped after xxx time since upgrade to 6.1

Post by robr57 »

Many many thanks to Boris to fix the HW of my Meteobridge PRO.
It has been repaired as a service, that is outstanding support !
After I received it back, he helped in an excellent way to restore my data as well.

Thanks again !
Issue can be closed.
Post Reply