[7.1-release] crash under menu -> sett...
Pike_Bishop 5 Aug 2019
Hi,
i have the following crash if i want to go in menu -> settings -> flash image (for online flash);
No handlers could be found for logger "AT" [eDVBPESReader] ERROR reading PES (fd=79): Value too large for defined data type [eDVBPESReader] ERROR reading PES (fd=79): Value too large for defined data type [eDVBPESReader] ERROR reading PES (fd=42): Value too large for defined data type [eDVBPESReader] ERROR reading PES (fd=44): Value too large for defined data type [eDVBPESReader] ERROR reading PES (fd=44): Value too large for defined data type [eDVBPESReader] ERROR reading PES (fd=44): Value too large for defined data type [eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type Traceback (most recent call last): File "/usr/lib/enigma2/python/Screens/FlashImage.py", line 88, in getImagesList OSError: [Errno 2] No such file or directory: '/media/net/WZ-BOX_cifs'
whereby /media/net/WZ-BOX_cifs is a cifs mount to the harddisc from another e2 box, and if this box isn't on it crashes.
it looks similar to this crash here;
https://forums.openp...dpost&p=1078519
regards
Pike
littlesat 5 Aug 2019
Pike_Bishop 6 Aug 2019
Hi littlesat,
thanks - found it;
https://github.com/O...11424335fd0317e
now i can go in menu -> settings -> flash image without crash.
here it needs ca. 2 minutes till this menu is open, but i think this is another problem here, i found in dmesg that;
<3>[ 4702.508278] ata1.00: exception Emask 0x10 SAct 0xf SErr 0xd80000 action 0x6 frozen <3>[ 4702.515892] ata1.00: irq_stat 0x08000000, interface fatal error <3>[ 4702.522042] ata1: SError: { 10B8B Dispar Handshk LinkSeq } <3>[ 4702.527564] ata1.00: failed command: WRITE FPDMA QUEUED <3>[ 4702.532890] ata1.00: cmd 61/00:00:10:5b:23/04:00:15:00:00/40 tag 0 ncq 524288 out <3>[ 4702.532890] res 40/00:04:10:5b:23/00:00:15:00:00/40 Emask 0x10 (ATA bus error) <3>[ 4702.548460] ata1.00: status: { DRDY } <3>[ 4702.552366] ata1.00: failed command: WRITE FPDMA QUEUED <3>[ 4702.557648] ata1.00: cmd 61/00:08:10:5f:23/04:00:15:00:00/40 tag 1 ncq 524288 out <3>[ 4702.557648] res 40/00:04:10:5b:23/00:00:15:00:00/40 Emask 0x10 (ATA bus error) <3>[ 4702.573314] ata1.00: status: { DRDY } <3>[ 4702.577012] ata1.00: failed command: WRITE FPDMA QUEUED <3>[ 4702.582372] ata1.00: cmd 61/00:10:10:63:23/04:00:15:00:00/40 tag 2 ncq 524288 out <3>[ 4702.582372] res 40/00:04:10:5b:23/00:00:15:00:00/40 Emask 0x10 (ATA bus error) <3>[ 4702.597924] ata1.00: status: { DRDY } <3>[ 4702.601739] ata1.00: failed command: WRITE FPDMA QUEUED <3>[ 4702.606989] ata1.00: cmd 61/00:18:10:67:23/04:00:15:00:00/40 tag 3 ncq 524288 out <3>[ 4702.606989] res 40/00:04:10:5b:23/00:00:15:00:00/40 Emask 0x10 (ATA bus error) <3>[ 4702.622504] ata1.00: status: { DRDY } <6>[ 4702.626321] ata1: hard resetting link <6>[ 4702.898255] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) <6>[ 4702.917532] ata1.00: configured for UDMA/133 <6>[ 4702.922030] ata1: EH complete <3>[ 4712.685278] ata1.00: exception Emask 0x10 SAct 0x4000001f SErr 0xd80000 action 0x6 frozen <3>[ 4712.693489] ata1.00: irq_stat 0x08000000, interface fatal error <3>[ 4712.699429] ata1: SError: { 10B8B Dispar Handshk LinkSeq } <3>[ 4712.704939] ata1.00: failed command: WRITE FPDMA QUEUED
maybe that is the reason (drive or sata-cable) for the problem or openmultiboot, but i don't know.
anyway if i start the gui (enigma2) new, it also needs often a long time till tv-picture is coming again, but not always (sometimes it needs only a few seconds).
regards
Pike
Edited by Pike_Bishop, 6 August 2019 - 19:55.
betacentauri 6 Aug 2019
That doesn’t look very good. In best case cable is damaged. In worst case hard disk fails in near future.
Do you know whether these entries are new? So they weren’t visible weeks/months ago. In rare cases a hdd is not “compatible” with drivers/hardware. I had it once, but with a PC and not with a box.
Pike_Bishop 7 Aug 2019
Hi betacentauri,
Do you know whether these entries are new? So they weren’t visible weeks/months ago
i don't know - yesterday i have seen it first time, but it looks good or ?
root@vuultimo4k:~# smartctl -a /dev/sda1 smartctl 5.42 2011-10-20 r3458 [armv7l-linux-3.14.28-1.12] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000LM003 HN-M201RAD Serial Number: S377J9AH104409 LU WWN Device Id: 5 0004cf 211bca843 Firmware Version: 2BE10001 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Wed Aug 7 01:30:30 2019 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (22680) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_V ALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 092 091 025 Pre-fail Always - 2721 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5383 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 6278 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1645 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 055 000 Old_age Always - 34 (M in/Max 17/51) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 095 095 000 Old_age Always - 2656 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 11 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 27 225 Load_Cycle_Count 0x0032 094 094 000 Old_age Always - 66847 241 Total_LBAs_Written 0x0032 098 094 000 Old_age Always - 31873 36 242 Total_LBAs_Read 0x0032 095 094 000 Old_age Always - 75510 72 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. root@vuultimo4k:~#
if it is the sata cable is it possible that this comes because i connect a fan at the sata cable ?
regards
Pike
betacentauri 7 Aug 2019
measure 199 (UDMA_CRC_Error_Count), 200 (Multi_Zone_Error_Rate) and maybe 223 should be zero, but they are not zero.
You could start a short or long self-test. A long test will last several hours. I would only do it without much load.
But even if a test is successfully, it doesn’t mean that the hdd won’t fail in near future.
If you have modified the sata cable it might cause these troubles. Well, you can remove the fan again and check whether errors still occur.
Edited by betacentauri, 7 August 2019 - 06:42.
Pike_Bishop 7 Aug 2019
Hi betacentauri,
thanks, ok then i will first backup my movies from this hdd and then i make tests.
If you have modified the sata cable it might cause these troubles. Well, you can remove the fan again and check whether errors still occur.
hmm, it's a combined cable sata and power in one cable, so i modified the power connection not the sata, but no problem i change the cable for test.
regards
Pike
Edited by Pike_Bishop, 7 August 2019 - 21:25.
Pike_Bishop 21 Aug 2019
Hi,
feedback meanwhile;
i have home-made me a cable ( i hate the combo cables) now i have a cable for power and a second cable for sata, and the fan is also working.
the output of dmesg now looks good as i think;
root@vuultimo4k:~# dmesg | grep ata [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Kernel command line: root=/dev/mmcblk0p4 rootfstype=ext4 rootflags=data=journ al rootwait rw coherent_pool=2M vmalloc=622m bmem=630m@394m bmem=383m@1665m bmem=443m@2625m [ 0.000000] Memory: 1600504K/3145728K available (5764K kernel code, 332K rwdata, 1888K ro data, 252K init, 188K bss, 1528840K reserved, 16384K cma-reserved, 1255412K highmem) [ 0.000000] .data : 0xc07c2000 - 0xc0815398 ( 333 kB) [ 0.045963] libata version 3.00 loaded. [ 1.193717] ata1: SATA max UDMA/133 mmio [mem 0xf045a000-0xf045aa9b] port 0x100 irq 62 [ 1.201652] ata2: SATA max UDMA/133 mmio [mem 0xf045a000-0xf045aa9b] port 0x180 irq 62 [ 1.475261] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.481777] ata1.00: ATA-8: ST2000LM003 HN-M201RAD, 2BE10001, max UDMA/133 [ 1.481781] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 1.488321] ata1.00: configured for UDMA/133 [ 1.659256] ata2: SATA link down (SStatus 0 SControl 300) [ 2.564463] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [ 2.610313] EXT4-fs (mmcblk0p4): mounted filesystem with journalled data mode. Opts: data =journal [ 3.317385] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.768090] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [ 9.439628] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. P lease run fsck. [ 10.296333] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 25.755657] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 25.879567] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) root@vuultimo4k:~#
regards
Pike
Edited by Pike_Bishop, 21 August 2019 - 19:33.
betacentauri 21 Aug 2019
And you can check smart values(the raw ones) in some weeks whether they have changed.
Pike_Bishop 21 Aug 2019
Hi betacentauri,
i have checked dmesg again a few minutes ago, and all is ok again, the box is on since 4 hours and recorded 3 times in this time, looks good.
but i will check it anyway frequently in the next days , and as you said in some weeks i check the smart values, thanks for the tips.
regards
Pike