Problem disk information

Climber

Climber

Member
I’m experiencing a problem with my HDFoxT2.
The first sign of a problem gave me the impression that an attached disk had an issue.
The disk was a wd blue 750gb hd connected via a Sabrient caddy for usb connection.
I suddenly got the following message:

Humax HD Fox T2.jpg

There is no SMART Status to be seen, but on clicking the wike.hummy.tv link gives this response:

Diskalert.jpg

The above suggested that the disk had more or less ended its useful life, even though it was only a few years old with minimal use.

I immediately ordered a replacement disk which once delivered was formatted and the custom firmware/webif and previous recorded files were installed. (The replacement disk installed in the Sabrient caddy).

The result of the new disk etc. being installed resulted in exactly the same issue being repeated once more. Thankfully I’d not discarded the WD Blue and on checking it with various formats, all tests on the disk showed it to be healthy.

My first thought was it was the Sabrient caddy that somehow was causing the issue. This has now been ruled out as when I use a Toshiba dedicated USB disk the same issue presents itself.

I presently only use the Humax for downloading Iplayer and viewing earlier saved t.v. files and everything in that respect works okay. I cannot check the tv broadcast side of things as where I am in a temporary location, there’s no signal available and that does not bother me. The continued display of the issue on the screen is very annoying.

I may add that I’m accessing the Humax via my laptop and no monitor/tv is connected or available.

Any help appreciated.

Web interface version: 1.4.9-9
Custom firmware version: 3.13 (build 4028)
Humax Version: 1.02.20 (kernel HDR_1.02.20)
Loader Version: L7.27
System ID: 806c.7000
 
The problem is caused by the caddy used. The web interface is written around the internal disk of an HDR and currently doesn't support external USB caddies.

The web interface typically uses the following command to get the SMART status smartctl -A /dev/sda. From a telnet window you may be able to get the information from the disk using smartctl -A -d sat /dev/sda. This is very much dependent on the chipset used by the caddy. If that also fails then lsusb -v may gives some clues as to the chipset and we may be able to give alternative options to try.
 
  • Like
Reactions: /df
Tests done

Using Sabrient 2.5 inch caddy – 2.5 inch HD

smartctl –A /dev/sda
/dev/sda: Unknown USB bridge [0x152d:0x1561 (0x204)]

Please specify device type with the -d option.

smartctl -A -d sat /dev/sda
Read Device Identity failed: empty IDENTIFY data
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

lsusb –v
No response

Using Toshiba USB (sealed case 1TB)

smartctl -A /dev/sda
/dev/sda: Unknown USB bridge [0x0480:0x0901 (0x000)]
Please specify device type with the -d option.

smartctl -A -d sat /dev/sda
Read Device Identity failed: empty IDENTIFY data
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options

lsusb –v
No response

Using a UGREEN caddy with Seagate 3.5 inch HD

There is no issue when using this set up and has been in use for quite a few years.

smartctl -A /dev/sda
This gives a long list of SMART attribute data.
I replaced the 3.5 inch HD with the first tested 2.5 inch HD ((also a Seagate) taken from the Sabrient caddy)

This results in no issue regarding disk error/s on the webif and also:

smartctl -A /dev/sda
Also gives a long list of SMART attribute data

My conclusion – I have to agree with and be grateful for your superior knowledge that the issue is indeed with the Sabrient caddy.
The issue came about after I decided to have a backup/reserve of the Webif etc. I now will only have the slight inconvenience of swapping the 3.5 hd with the 2.5 hd in the UGREEN caddy if and when ever required.

The Toshiba 2.5 USB disk was normally used for storing the recorded programs and connected directly to my laptop and will revert solely to that role. I only tested that to see if I was getting the same result as when the Sabrient caddy was used.

The Sabrient caddy can now be utilised elsewhere.

It has been a long time since I ever requested help from the forum, but I am a regular visitor and as per usual the help given is A1, so thank you.

My HD has been acting as a reserve and was my first Humax. My 2 HDR's have been locked up in storage for nearly a year - long story!
 
Climber said:
The continued display of the issue on the screen is very annoying.
Click to expand...
Some work has recently been done on SMART reporting, but it's not in the version of WebIf you're currently running.
It wouldn't have made any difference if you were running the current WebIf beta though, as this is not one of the problems that was addressed.
Out of interest, is there anything relevant in the /tmp/webif-error.log file?
Climber said:
smartctl -A -d sat /dev/sda
Click to expand...
Maybe try usbjmicron instead of sat.
 
Last edited:
There was no info in the error log initially.

As the Sabrent caddy disk had shown up okay when inserted in the UGREEN it initially shows up as being okay again in the Sabrient until I ran disk diagnostics, then the error warning returns.

when I recreated the warning I got this in the log:

18at file "/mod/webif/html/diag/disk.jim", line 33
17
16Use smartctl -h to get a usage summary
15
14Please specify device type with the -d option.
13/dev/sda: Unknown USB bridge [0x152d:0x1561 (0x204)]
12
11Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
10/mod/webif/html/diag/disk.jim:33: Error: smartctl 6.4 2015-06-04 r4109 [7405b0-smp-linux-2.6.18-7.1] (local build)
9at file "/mod/webif/html/diag/disk.jim", line 33
8
7Use smartctl -h to get a usage summary
6
5Please specify device type with the -d option.
4/dev/sda: Unknown USB bridge [0x152d:0x1561 (0x204)]
3
2Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
1/mod/webif/html/diag/disk.jim:33: Error: smartctl 6.4 2015-06-04 r4109 [7405b0-smp-linux-2.6.18-7.1] (local build)


----

smartctl -A -d usbjmicron /dev/sda

This returns:

Smartctl open device: /dev/sda [USB JMicron] failed: No device connected

The usb disk was certainly connected to the humax
 
For info. this is the SMART info from a WDElements drive connected to an HD.
[Admittedly this is running a modified kernel and modified CF - so this may not be fully representative].
Code: 
hd# smartctl -iA /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

/dev/sda: Unknown USB bridge [0x1058:0x25a3 (0x1013)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

hd# smartctl -iA -d sat /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 ===
Device Model:     WDC WD40EZRZ-00WN9B0
Serial Number:    WD-XXXXXXXXXXXX
LU WWN Device Id: 5 0014ee 2637ae6b8
Firmware Version: 80.00A80
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Apr 25 08:16:21 2022 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
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       -       0
  3 Spin_Up_Time            0x0027   170   167   021    Pre-fail  Always       -       8500
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1255
  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   099   099   000    Old_age   Always       -       739
 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   099   099   000    Old_age   Always       -       1255
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       534
193 Load_Cycle_Count        0x0032   199   199   000    Old_age   Always       -       3723
194 Temperature_Celsius     0x0022   127   104   000    Old_age   Always       -       25
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      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

hd#
 
As I had nothing to lose, I decided to install the Beta webif 1.5.1-0 and repeat the tests carried out earlier under webif 1.4.9-9.
I've only done the further tests for your information only.

Using the Sabrent caddy and the Seagate 500 GB HD (2.5 inch)
Both warning boxes displayed previously no longer appear.

Disk Diagnostics - Smart Status = dev/sda Unknown USB bridge [0x152d:0x1561 (0x204)]
Attributes and Self test logs both only list menu items. Acknowledge any disk faults – Is also present

The smartcl checks done previously were repeated and they gave exactly the same results as before.

There is no info this time @ /tmp/webif-error.log file.

Even though this particular caddy and disk was only initially used as a backup and now, at present, for expermenting with the Beta Webif, which with limited use has not appeared to give me any issues.
I'm not overly concerned about the Disk Diagnostic issue with the Sabrent caddy, as I will in the future use the disk in the Ugreen caddy that works perfectly well with Disk Diagnostices.

Thanks for previous help.
 
You must log in or register to reply here.
Back
Top