Schedule list shows programmes already recorded.
- Thread starter mike_m
- Start date
I kicked it off; I think it's stuck in a loop thus:
Code:
Running select disk self test
Error at LBA 251006816
/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk.
Also checking blocks 251006816 - 251006823 (8 blocks)
Block 251006816 - OK
Block 251006817 - OK
Block 251006818 - OK
Block 251006819 - OK
Block 251006820 - OK
Block 251006821 - OK
Block 251006822 - OK
Block 251006823 - OK
Running select disk self test
Last edited:
Black Hole
May contain traces of nut
Just wait.
How long has it been running? It is impossible to estimate how long a fix-disk run will take. It might be an hour or it might be several days depending on what faults are found.
It has been running for 75 minutes or so now. That does not bother me; it's just the observation that the messages are exactly the same that I found alarming:
Code:
Running select disk self test
Error at LBA 251006816
/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk.
Also checking blocks 251006816 - 251006823 (8 blocks)
Block 251006816 - OK
Block 251006817 - OK
Block 251006818 - OK
Block 251006819 - OK
Block 251006820 - OK
Block 251006821 - OK
Block 251006822 - OK
Block 251006823 - OK
Running select disk self test
Waiting... 7582
Last edited:
prpr
Well-Known Member
That's obviously not good. Can you post your SMART stats.?
humax# smartctl -a /dev/sdaThanks for the interest, everyone. Are we contaminating the thread, is there a better one?
SMART stats (fixdisk still running, if it makes a difference):
SMART stats (fixdisk still running, if it makes a difference):
Code:
Humax HDR-Fox T2 (HumaxOld) 1.03.12/3.13
To return to the menu, type: exit
HumaxOld# smartctl -a /dev/sda
smartctl 6.4 2015-06-04 r4109 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Green
Device Model: WDC WD10EZRX-00L4HB0
Serial Number: WD-WCC4J0771360
LU WWN Device Id: 5 0014ee 2b3de474f
Firmware Version: 01.01A01
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Jan 21 18:52:34 2022 GMT
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: (0x85) Offline data collection activity
was aborted by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 241) Self-test routine in progress...
10% of test remaining.
Total time to complete Offline
data collection: (12660) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 145) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status 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_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 39
3 Spin_Up_Time 0x0027 133 121 021 Pre-fail Always - 4350
4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6452
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 6443
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 094 094 000 Old_age Always - 6449
192 Power-Off_Retract_Count 0x0032 192 192 000 Old_age Always - 6386
193 Load_Cycle_Count 0x0032 176 176 000 Old_age Always - 72512
194 Temperature_Celsius 0x0022 115 082 000 Old_age Always - 28
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 192 000 Old_age Always - 759
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 7 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 7 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 67 0f f6 ee Error: UNC at LBA = 0x0ef60f67 = 251006823
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 01 67 0f f6 ee 0a 00:02:04.171 READ SECTOR(S)
30 00 01 66 0f f6 ee 0a 00:02:04.110 WRITE SECTOR(S)
ec 00 01 66 0f f6 a0 0a 00:02:04.095 IDENTIFY DEVICE
20 00 01 66 0f f6 ee 0a 00:02:04.046 READ SECTOR(S)
30 00 01 65 0f f6 ee 0a 00:02:03.891 WRITE SECTOR(S)
Error 6 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 66 0f f6 ee Error: UNC at LBA = 0x0ef60f66 = 251006822
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 01 66 0f f6 ee 0a 00:02:04.046 READ SECTOR(S)
30 00 01 65 0f f6 ee 0a 00:02:03.891 WRITE SECTOR(S)
ec 00 01 65 0f f6 a0 0a 00:02:03.873 IDENTIFY DEVICE
20 00 01 65 0f f6 ee 0a 00:02:03.816 READ SECTOR(S)
30 00 01 64 0f f6 ee 0a 00:02:03.755 WRITE SECTOR(S)
Error 5 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 65 0f f6 ee Error: UNC at LBA = 0x0ef60f65 = 251006821
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 01 65 0f f6 ee 0a 00:02:03.816 READ SECTOR(S)
30 00 01 64 0f f6 ee 0a 00:02:03.755 WRITE SECTOR(S)
ec 00 01 64 0f f6 a0 0a 00:02:03.740 IDENTIFY DEVICE
20 00 01 64 0f f6 ee 0a 00:02:03.682 READ SECTOR(S)
30 00 01 63 0f f6 ee 0a 00:02:03.622 WRITE SECTOR(S)
Error 4 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 64 0f f6 ee Error: UNC at LBA = 0x0ef60f64 = 251006820
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 01 64 0f f6 ee 0a 00:02:03.682 READ SECTOR(S)
30 00 01 63 0f f6 ee 0a 00:02:03.622 WRITE SECTOR(S)
ec 00 01 63 0f f6 a0 0a 00:02:03.607 IDENTIFY DEVICE
20 00 01 63 0f f6 ee 0a 00:02:03.558 READ SECTOR(S)
30 00 01 62 0f f6 ee 0a 00:02:03.514 WRITE SECTOR(S)
Error 3 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 63 0f f6 ee Error: UNC at LBA = 0x0ef60f63 = 251006819
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 01 63 0f f6 ee 0a 00:02:03.558 READ SECTOR(S)
30 00 01 62 0f f6 ee 0a 00:02:03.514 WRITE SECTOR(S)
ec 00 01 62 0f f6 a0 0a 00:02:03.496 IDENTIFY DEVICE
20 00 01 62 0f f6 ee 0a 00:02:03.438 READ SECTOR(S)
30 00 01 61 0f f6 ee 0a 00:02:03.377 WRITE SECTOR(S)
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 6440 251006816
# 2 Short offline Completed without error 00% 6438 -
# 3 Extended offline Aborted by host 90% 3518 -
# 4 Extended offline Completed without error 00% 3516 -
# 5 Short offline Completed without error 00% 3508 -
# 6 Short offline Completed without error 00% 3496 -
# 7 Short offline Completed: read failure 90% 3496 1142627824
# 8 Short offline Completed: read failure 90% 3496 1142627824
# 9 Selective offline Completed: read failure 90% 3495 963535768
#10 Extended offline Completed: read failure 90% 3495 963535760
#11 Short offline Completed: read failure 90% 3495 963535760
#12 Conveyance offline Completed without error 00% 58 -
5 of 6 failed self-tests are outdated by newer successful extended offline self-test # 4
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
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.
Last edited:
Black Hole
May contain traces of nut
Please edit your ICODE tags to CODE tags. The post toolbar tool looks like </> rather than >_
See Newbies' Guide to the Forum (click)
See Newbies' Guide to the Forum (click)
I created a new thread with some new information to decouple this one. Apologies for the diversion.
JayKayHove
New Member
Hi, I'd just like to add that I'm having exactly the same issue reported here. My machine is not scheduling the next episode of a series link after it has recorded the latest episode. The program is in the EPG if I look ahead in the guide but the recording schedule has the date blanked out - and sometimes last week had the previous episode date as the scheduled episode.
This started happening around Christmas. I'm pointing to the Whitehawk transmitter in Brighton with a signal strength of around 90%.
I have done two things over the last 45 minutes which seem to have solved it for now (Uni Challenge BBC2 HD next week has just been correctly added to my schedule).
A) I left the Humax on BBC1 SD for 30 minutes.
B) I entered maintenance mode and did a disk check. (I am on non-custom 1.03.12)
This started happening around Christmas. I'm pointing to the Whitehawk transmitter in Brighton with a signal strength of around 90%.
I have done two things over the last 45 minutes which seem to have solved it for now (Uni Challenge BBC2 HD next week has just been correctly added to my schedule).
A) I left the Humax on BBC1 SD for 30 minutes.
B) I entered maintenance mode and did a disk check. (I am on non-custom 1.03.12)
Last edited:
Ezra Pound
Well-Known Member
@Aaron is reporting the same :-
Scheduled events no longer working - Refresh events does nothing
These issues sound very much like what some other users (including me) have posted on mike_m's thread (https://hummy.tv/forum/threads/schedule-list-shows-programmes-already-recorded.10474/) regarding the schedule not picking up any future recordings, despite being there in the EPG. It appears to...
Mine has recurred: yesterday it booted correctly. But it had recordings stuck in the schedule from the day before yesterday and it clearly wasn't shutting down.
And I did not have BBC1 SD...
So I went in tunefix and told it to stop removing channel 1 (BBC 1 SD). I rescanned the channel that has BBC1 SD, it went on BBC1 SD and it fixed the schedule within 5 minutes or so.
And then a shutdown actually worked.
And I did not have BBC1 SD...
So I went in tunefix and told it to stop removing channel 1 (BBC 1 SD). I rescanned the channel that has BBC1 SD, it went on BBC1 SD and it fixed the schedule within 5 minutes or so.
And then a shutdown actually worked.
prpr
Well-Known Member
It won't.
Users over at MyHumax.org are reporting this problem is no longer occurring on the FVP-5000T. Is that also true for the HDR-FOX T2?
Black Hole
May contain traces of nut
People will have to revert their BBC StDef reminder schedules to find out...
OP
mike_m
Active Member
I've instigated a forced channel change to SD every night on my HDR-FOX T2s to get a refreshed EPG, in order to get Series Link to work properly. Since then the problem I originally posted about has not re-occurred, though I'm not sure if the two things are causally linked. As Black Hole says, I don't really want to undo the scheduled reminders to find out!
JayKayHove
New Member
I haven't had this issue for the last fortnight as I have been leaving it tuned into BB1 SD at the end of the day.
I thought it was fixed but last night I left it tuned into BBC2 HD and I've just looked at the recording schedule. Next week's University Challenge hasn't been picked up and it's saying it's going to record yesterday's episode - even though it actually did record yesterday's episode when it aired.
The top of my schedule looks likes this
7/2 University Challenge
8/2 Toast of London
So it's not fixed yet.
Update: After leaving it tuned into BBC1 SD for five minutes the schedule has repaired itself and has changed the University Challenge schedule to next week.