• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

PVR-9150T - Recent recordings don't appear in list

J

Jackfruit1000

New Member
Hello,

My mum's 9150T appeared to have stopped recording programmes since mid-September.

I thought I'd extract all the old recordings, reformat the HD, reset the whole device, reload the recordings, and see if that got things back to normal.

I've just plugged the drive into my linux laptop and run humaxrw (sudo ./humaxrw /dev/sdc -l), and weirdly it's showing programmes right up until yesterday on the drive! Humaxrw says there are 127 files on there, but when you look at the list of available recordings on the TV it's only showing 64 of them, up until the 21st September...

Before I carry out plan A, and reset everything, has anyone else had this problem and/or know what's gone wrong?

Thanks,

Piers.
 
Jackfruit1000 said:
Before I carry out plan A, and reset everything, has anyone else had this problem and/or know what's gone wrong?
Click to expand...
The first thing I would do is look at the SMART data for the drive. For Linux you will need the smartmontools package.

From the command line: sudo smartctl -a /dev/sdX where X is a placeholder for the drive designation.
If you are not familiar with interpreting the output then post it here.
 
Hello,

While viewing the list of programmes on the TV I thought I'd delete one and see if that made any difference. It didn't appear to, but when I ran humaxrw again it only showed 63 files. Listing in recovery mode didn't show them either, so the recent ones appear to have gone!

I will check the smart data, but I'm currently extracting all the remaining recordings to my laptop, so that I've got them if any further testing turns out not to be non-destructive. Will report back when that's finished.

As an aside, when I tried downloading them in the Linux partition I came up with the same problem another person described, where any programmes with a colon in the title got rejected (lots starting with "New:..."). It's odd, because I don't remember that being an issue using humaxrw with my own 9200T. So, currently running under Win10, where the colons get converted to underscores.

Piers.
 
Here are the results from smartctl:


Code: 
piers@piers-Latitude-E6410:~$ sudo smartctl -a /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-163-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital AV-GP
Device Model:     WDC WD1600AVVS-63L2B0
Serial Number:    WD-WCAUZ0327501
LU WWN Device Id: 5 0014ee 15737b6ef
Firmware Version: 01.03A01
User Capacity:    160,041,885,696 bytes [160 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.5, 3.0 Gb/s
Local Time is:    Sat Dec 13 17:33:38 2025 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:  (0x84)    Offline data collection activity
                    was suspended by an interrupting command from host.
                    Auto Offline Data Collection: Enabled.
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:         ( 4380) 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:      (  55) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x303f)    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_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       6224
  3 Spin_Up_Time            0x0027   157   151   021    Pre-fail  Always       -       3141
  4 Start_Stop_Count        0x0032   093   093   000    Old_age   Always       -       7614
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   001   001   000    Old_age   Always       -       75125
 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   093   093   000    Old_age   Always       -       7612
192 Power-Off_Retract_Count 0x0032   190   190   000    Old_age   Always       -       7611
193 Load_Cycle_Count        0x0032   198   198   000    Old_age   Always       -       7614
194 Temperature_Celsius     0x0022   111   083   000    Old_age   Always       -       32
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      -       2
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       35
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       2

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]

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.
 
Jackfruit1000 said:
what's gone wrong?
Click to expand...
Humax's proprietary filesystems are flaky (polite term for what I really think). The worst was the 9200 which just became unusable for me. I believe the 9150 and the 9300 are better but still suffer. Thankfully they went to standard ext3 for the HDR Fox-T2.
Jackfruit1000 said:
when I ran humaxrw again it only showed 63 files. Listing in recovery mode didn't show them either, so the recent ones appear to have gone!
Click to expand...
Nice. Just what you need, eh?
I'm currently extracting all the remaining recordings
Click to expand...
A very good idea. I guess you wish you'd done that first. I don't think you can put extracted recordings back on the machine though.
I came up with the same problem another person described, where any programmes with a colon in the title got rejected (lots starting with "New:..."). It's odd, because I don't remember that being an issue using humaxrw with my own 9200T
Click to expand...
I had that when recovering a 9300 for someone. I think I had to use recovery mode and then manually rename the files - a right bl@@dy faff it was too.
 
I would say that for a drive with 75000 power on hours the drive is in pretty good condition. You need to fix the 2 sectors shown in attributes 197 and 198. Try smartctl -t
 
Jackfruit1000 said:
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 2
Click to expand...
Those need fixing. I would do a long SMART test to identify the first sector. Then you need to manually rewrite it and repeat with a Selective test to find the next one and rewrite that. Or you could just blat the whole thing with dd and start again, as you'll probably have to format it on the Humax anyway.
Only 160GB so it shouldn't take too long (and check the SMART again afterwards).
 
MartinLiddle said:
I would say that for a drive with 75000 power on hours the drive is in pretty good condition.
Click to expand...
I've had lots of old drives (40 and 80 GB typically) with well over 100000 hours and no bad sectors. They went to their WEEE graves in perfect working order, unlike the modern cr@p.
 
MartinLiddle said:
I would say that for a drive with 75000 power on hours the drive is in pretty good condition. You need to fix the 2 sectors shown in attributes 197 and 198. Try smartctl -t
Click to expand...
I tried 'sudo smartctl -t /dev/sdc'

And it came back with this:

=======> INVALID ARGUMENT TO -t: /dev/sdc
=======> VALID ARGUMENTS ARE: offline, short, long, conveyance, force, vendor,N, select,M-N, pending,N, afterselect,[on|off] <=======

Which of the arguments should I be using?
 
prpr said:
I don't think you can put extracted recordings back on the machine though.
Click to expand...
Humaxrw has the 'put' function for returning extracted recordings, which I've successfully used in the past.

As it happens, my mother has since said that there are only three things on there she really wants to keep, so the process should now be pretty quick!
 
prpr said:
Those need fixing. I would do a long SMART test to identify the first sector. Then you need to manually rewrite it and repeat with a Selective test to find the next one and rewrite that. Or you could just blat the whole thing with dd and start again, as you'll probably have to format it on the Humax anyway.
Only 160GB so it shouldn't take too long (and check the SMART again afterwards).
Click to expand...

My initial assumption was that this is the result of some kind of Humax filesystem corruption, and that reformatting was inevitable (and probably desirable).

If I'm going to do that anyway, will dd fix the 197/198 errors you already highlighted? Or do I need to do the manual rewrites?

Either way, I'd appreciate it if you could tell me what I need to type in. I'm fine with using command line instructions, but don't consider myself nearly qualified enough to be sure of what I'm doing on my own!
 
Jackfruit1000 said:
Humaxrw has the 'put' function for returning extracted recordings, which I've successfully used in the past.
Click to expand...
OK thanks, maybe I'm misremembering what it was I could or couldn't do. Anyway I hope never to have to touch one of those machines again. Having said that, I must get rid of my two 9200 units, so I guess I'll have to check what state they're in and see whether anything I want is left to extract.
 
Jackfruit1000 said:
If I'm going to do that anyway, will dd fix the 197/198 errors you already highlighted? Or do I need to do the manual rewrites?
Click to expand...
The former should fix everything. As I say, check the 197/198 afterwards.
Jackfruit1000 said:
Either way, I'd appreciate it if you could tell me what I need to type in. I'm fine with using command line instructions, but don't consider myself nearly qualified enough to be sure of what I'm doing on my own!
Click to expand...
Double check it's still /dev/sdc (you could use lsblk or similar) and then:
sudo dd if=/dev/zero of=/dev/sdc bs=1M status=progress
assuming it's a modern Linux. If that errors, then remove the status=progress stuff. The bs=1M thing probably makes it go a bit faster (but I've never done any real testing), and could be omitted also.
 
prpr said:
The former should fix everything. As I say, check the 197/198 afterwards.

Double check it's still /dev/sdc (you could use lsblk or similar) and then:
sudo dd if=/dev/zero of=/dev/sdc bs=1M status=progress
assuming it's a modern Linux. If that errors, then remove the status=progress stuff. The bs=1M thing probably makes it go a bit faster (but I've never done any real testing), and could be omitted also.
Click to expand...
The test still has a little longer to run, so I'll come back to this later.

I'm running Linux Mint 21.2, the Cinnamon version. I normally just use the disks utility to check the external drive ID.
 
OK, dd run as follows:

Code: 
piers@piers-Latitude-E6410:~$ sudo dd if=/dev/zero of=/dev/sdc bs=1M status=progress
160027377664 bytes (160 GB, 149 GiB) copied, 6962 s, 23.0 MB/s
dd: error writing '/dev/sdc': No space left on device
152628+0 records in
152627+0 records out
160041885696 bytes (160 GB, 149 GiB) copied, 7012.26 s, 22.8 MB/s


Smartctl rerun, results as follows:


Code: 
piers@piers-Latitude-E6410:~$ sudo smartctl -a /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-163-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital AV-GP
Device Model:     WDC WD1600AVVS-63L2B0
Serial Number:    WD-WCAUZ0327501
LU WWN Device Id: 5 0014ee 15737b6ef
Firmware Version: 01.03A01
User Capacity:    160,041,885,696 bytes [160 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.5, 3.0 Gb/s
Local Time is:    Sat Dec 13 22:35:20 2025 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:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
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:         ( 4380) 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:      (  55) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x303f)    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_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       6224
  3 Spin_Up_Time            0x0027   157   151   021    Pre-fail  Always       -       3141
  4 Start_Stop_Count        0x0032   093   093   000    Old_age   Always       -       7615
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   001   001   000    Old_age   Always       -       75129
 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   093   093   000    Old_age   Always       -       7613
192 Power-Off_Retract_Count 0x0032   190   190   000    Old_age   Always       -       7612
193 Load_Cycle_Count        0x0032   198   198   000    Old_age   Always       -       7615
194 Temperature_Celsius     0x0022   117   083   000    Old_age   Always       -       26
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       35
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       2

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%      9589         311992044

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.
 
You must log in or register to reply here.
Back
Top