Maintenance Mode

[hummybee]

Hi all

Maintenance shown on the Humax display so assume that shows it is actually running, correct?. When finished does it automatically reboot?

If needed, how do I stop the process without corrupting the disk?

Thanks for your help.

 

[prpr]

When finished does it automatically reboot?

No.

If needed, how do I stop the process without corrupting the disk?

Which process? Fix-disk? I probably wouldn't, but I guess Ctrl-C.
Unmounting the disk partitions may be a good idea if you are paranoid:

humax# umount /mnt/hd[1-3]

 

[Black Hole]

Hi all

Maintenance shown on the Humax display so assume that shows it is actually running, correct?. When finished does it automatically reboot?

If needed, how do I stop the process without corrupting the disk?

Thanks for your help.

I think you have misunderstood something. Entering maintenance mode does not do any maintenance - it stops the normal processes so that the disk can be examined. You then have to initiate some maintenance activity by accessing the Telnet menu - which provides options to start a disk check, or enter manual commands, and there is an "exit maintenance mode" option.

There's no point just staring at the "maintenance" message on the VFD - it will be there forever unless you do something about it (a forced reboot resumes normal operation).

 

[hummybee]

Hi prpr and Black Hole.


To back track, I'm trying to find a fix for the following:-


'!! WARNING !!

There appear to be some hardware problems with the internal hard disk on this device.

Disk pending sector count is: 120

Disk offline sector count is: 120

Go to disk diagnostics '


I updated to the latest firmware in the hope it would somehow fix this but there are errors as follows:-

'Web interface version: {1.2.3-4 Collected} {errors: } * rm_r: Failed to open dir : No such file or directory.
Custom firmware version: 3.03 (build 2368)
Humax Version: 1.03.12 (kernel HDR_CFW_3.03)
Serial Number: xx xxxxxxx xxxxx
Last Boot Reason: Unknown (0)'


Can you suggest how I go about fixing these problems and errors please.

Thanks for your help.

 

[prpr]

There appear to be some hardware problems with the internal hard disk on this device.

You were right to go to maintenance mode.
Do so again i.e. telnet to the box then run "fix-disk". You need to do it twice from normal operation mode, as the first one just puts it in to maintenance mode.

I updated to the latest firmware in the hope it would somehow fix this but there are errors as follows:-

Bizarre. Does putting petrol in your car pump up the tyres too?

 

[af123]

Do so again i.e. telnet to the box then run "fix-disk". You need to do it twice from normal operation mode, as the first one just puts it in to maintenance mode.

Assuming that you haven't enabled expert telnet mode, then connect to the box when it's in normal mode and choose option 1 from the menu:

  /-------------------------\
  |  T E L N E T  M E N U  |
  \-------------------------/

  [ Humax HDR-Fox T2 (humax) 1.03.12/3.03 ]

  1 - Restart into maintenance mode.

and once it has come back in maintenance mode, telnet again and choose option 1 again.

  /---------------------------------------------\
  |  M A I N T E N A N C E  M O D E  M E N U  |
  \---------------------------------------------/

  [ Humax HDR-Fox T2 (humax) 1.03.12/3.03 ]

  1 - Check and repair hard disk (fix-disk).

 

[hummybee]

Hi prpr and af123

When I connect using PuTTY I get 'HumaxHDRFoxT2one#' before a green curser without any headings or options.

If I input 'fix-disk' it finds an error at LBA 533470400 with the option to repair.

I enter yes and get re-writing sector succeeded.

It then runs a short disk self test and error at LBA 533470400 with the option to repair again and repeats.

Is ''Web interface version: {1.2.3-4 Collected} {errors: } * rm_r: Failed to open dir : No such file or directory.' a separate problem or part of the error at LBA 533470400?

Thanks for your help.

 

[Black Hole]

If you don't get a PIN prompt and a menu when accessing Telnet, it means you have selected expert mode in the WebIF settings. Typing "tmenu" at the command prompt will return you to the Telnet menu system.

You need to be in maintenance mode to run fix-disk, both of which are available via the menus.

 

[hummybee]

Thank you Black Hole.

That brings up the menu but it still gets stuck in the error at LBA 533470400 with the option to repair repeated loop.

Although the box looks like it is recording it dose not save the file so I am using my other Humax box for all recordings.

Would you recommend a disk format and reinstall the latest firmware (after I have viewed the few remaining recordings)?

 

[DRooster]

Although the box looks like it is recording it dose not save the file ...

Mine got into that state with the "delete" loop message.
First run of FixDisk didn't fix it, just hung.
Third run of FixDisk fixed it and got to the end of the process, giving me the option to fix the "delete loop".

Before FixDisk became successful I used putty to navigate to the correct directory and deleted the "delete loop" file myself,
I can't immediately find you the thread on here with the correct instructions, but I can copy/paste from my own txt file ;
_________________________________
Problem

The Humax displays '* Deleting' message permanently, preventing many normal functions from operating including recording etc.

Solution

Run the Fix Disk Utility built into Custom Firmware 2.12 and answer 'Yes' to the question "Are you having problems with a delete loop [Y/N]?". Fix-Disk has a 'Deleting Fix', which performs FIX 1 below :-

Fix 1

If the Custom Firmware is installed then delete the following corrupted file using Telnet :-
/etc/init.d/S90settop shut
rm /mnt/hd1/filebglastop.dat
/etc/init.d/S90settop resume
reboot

Fix 2

A reported '*Deleting' fix that does not require Custom Firmware to be installed, is to download and install version 1.01.09 via USB flash (Details Here) check to see that the '*Deleting' message is no longer being displayed and then download and install your desired (Latest) version, however it has also been reported that the '*Deleting' message can sometimes re-appear when the latest firmware is re-installed
_________________________________________
Ulfric fix
Telnet using Putty.exe enter 192.168.0.2 (or 3) set to Telnet mode
0000
Enter MAINTENANCE mode
cli
ls -al (list all files in root dir)
cd hd2 (or wherever, but was wrong dir)
cd ..
cd ..
ls -al (now showed a hd1 dir, bingo!)
cd hd1
ls -al (now showed the evil fileblastop.dat, eyay!)
rm filebglastop.dat
reboot

That worked!!

_________________________________

 

[MartinLiddle]

Would you recommend a disk format and reinstall the latest firmware (after I have viewed the few remaining recordings)?

You could try but if fix-disc can't fix the problem then a Humax format may well not help. A security erase might have more chance of success.

 

[prpr]

That brings up the menu but it still gets stuck in the error at LBA 533470400 with the option to repair repeated loop.
Would you recommend a disk format and reinstall the latest firmware (after I have viewed the few remaining recordings)?

No. I think the only thing you can do is copy anything off you want to keep and (as Martin said) do a security erase (search the forum for instructions).
If that doesn't work it's new disk time.
Changing the firmware is pointless, as is what DRooster suggested (for this particular probem).

 

[hummybee]

Thank you all for your help.

I'll give it another go later and see if I can get any further.

 

[HarveyB]

I had a "disk pending sector count" error yesterday.
I am currently running Maintenance/Disk check.
It has repaired one sector but subsequently raised the following file problem:

The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.

debugfs 1.42.10 (18-May-2014)
Inode   Pathname
12871310        /mnt/hd2/mod/tmp/redring.log

If I just delete the redring.log will a new (uncorrupt) one be created automatically or do I need to create one myself?
To delete the log can I just hit the "red X" on the WEBif maintenance screen or do I need to do it some other way?

 

[af123]

red X is fine. It will just be re-created (maybe following a reboot).

 

[hummybee]

Hi all

I have now backed up the files I want to keep so ready to try a security erase and would appreciate details of the steps I need to take to do this.

Once done, do I just let the Humax format the disk and reinstall the custom firmware?

Thanks for your help.

 

[MontysEvilTwin]

The procedure is here, with more info here. You will then be able to reformat using the remote: you'll probably get an on-screen prompt asking you to format the disk. The custom firmware will still be installed (its in flash) but you will have to reinstall most of your packages: it will be like a new install when you try and open Web-If. Use Web-If to check your sectors have been reallocated (look in Diagnostics), and I would also run fix-disk again from maintenance mode.

 

[hummybee]

Thanks MontysEvilTwin.

Followed the procedure from the first link but when I rebooted no on-screen prompt asking me to format the disk.

Iirc there is a format disk option under the Installation menu but the Installation menu is greyed out and not accessible.

Is there a way to format the disk via the Web Interface?

Thanks again for your help.

 

[MontysEvilTwin]

Thanks MontysEvilTwin.

Followed the procedure from the first link but when I rebooted no on-screen prompt asking me to format the disk.

Iirc there is a format disk option under the Installation menu but the Installation menu is greyed out and not accessible.

Is there a way to format the disk via the Web Interface?

Thanks again for your help.

Did you allow enough time for the security erase to run; it is not quick? During the procedure you get an estimate of how long the erase will take, but once you set it running you might not get a message to say it is complete. I allowed extra time to make sure it had finished before doing anything else (as described in the second link).
If you can't format the disk from the Installation menu (option greyed out), the HDR-FOX is not recognising that a disk is attached.
I don't know what happens if you reboot during the security erase procedure; does it just continue when the unit is turned back on?

 

[hummybee]

Have run fix-disk again and this time it struggled through after answering 'n' rather than 'y' to repair bad blocks.

I can now access the Smart data via Web Interface which shows the following:-

SMART data read from device /dev/sda
Disk Information
SMART Status PASSED
Device Model ST1000VM002-1CT162
Serial Number S1G12JAQ
LU WWN Device Id 5 000c50 060d2153b
Firmware Version SC23
User Capacity 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes 512 bytes logical, 4096 bytes physical
ATA Version is 8
ATA Standard is ATA-8-ACS revision 4
Local Time is Tue Aug 18 12:33:39 2015 BST
SMART support is Available - device has SMART capability.
SMART support is Enabled
Attributes
ID Name Flags Raw Value Value Worst Thresh Type Updated When Failed
1 Raw_Read_Error_Rate POSR-- 150654945 099 097 006 Pre-fail Always -
3 Spin_Up_Time PO---- 0 097 097 000 Pre-fail Always -
4 Start_Stop_Count -O--CK 1495 099 099 020 Old_age Always -
5 Reallocated_Sector_Ct PO--CK 16 100 100 036 Pre-fail Always -
7 Seek_Error_Rate POSR-- 136570978 081 060 030 Pre-fail Always -
9 Power_On_Hours -O--CK 7397 092 092 000 Old_age Always -
10 Spin_Retry_Count PO--C- 0 100 100 097 Pre-fail Always -
12 Power_Cycle_Count -O--CK 1495 099 099 020 Old_age Always -
184 End-to-End_Error -O--CK 0 100 100 099 Old_age Always -
187 Reported_Uncorrect -O--CK 172 001 001 000 Old_age Always -
188 Command_Timeout -O--CK 4295032833 100 099 000 Old_age Always -
189 High_Fly_Writes -O-RCK 32 068 068 000 Old_age Always -
190 Airflow_Temperature_Cel -O---K 38 062 045 045 Old_age Always In_the_past
191 G-Sense_Error_Rate -O--CK 0 100 100 000 Old_age Always -
192 Power-Off_Retract_Count -O--CK 1494 100 100 000 Old_age Always -
193 Load_Cycle_Count -O--CK 1495 100 100 000 Old_age Always -
194 Temperature_Celsius -O---K 38 038 055 000 Old_age Always -
197 Current_Pending_Sector -O--C- 112 100 100 000 Old_age Always -
198 Offline_Uncorrectable ----C- 112 100 100 000 Old_age Offline -
199 UDMA_CRC_Error_Count -OSRCK 0 200 200 000 Old_age Always -
Self-test logs
No. Description Status Remaining When First Error LBA
# 1 Short offline Completed: read failure 90% 7396 148905168
# 2 Short offline Completed: read failure 90% 7396 148905168
# 3 Short offline Completed: read failure 90% 7396 148905168
# 4 Short offline Completed: read failure 90% 7396 148905168
# 5 Short offline Completed: read failure 90% 7396 148905168
# 6 Short offline Completed: read failure 90% 7396 148905168
# 7 Short offline Completed: read failure 90% 7396 148905168
# 8 Short offline Completed: read failure 90% 7396 148905168
# 9 Short offline Completed: read failure 90% 7380 148905168
#10 Short offline Completed: read failure 90% 7380 148905168
#11 Short offline Completed: read failure 90% 7380 148905168
#12 Short offline Completed: read failure 90% 7380 148905168
#13 Short offline Completed: read failure 90% 7380 148905168
#14 Short offline Completed: read failure 90% 7380 148905168
#15 Short offline Completed: read failure 90% 7380 148905168
#16 Short offline Completed: read failure 90% 7380 148905168
#17 Short offline Completed: read failure 90% 7380 148905168
#18 Short offline Completed: read failure 90% 7380 148905168
#19 Short offline Completed: read failure 90% 7380 148905168
#20 Short offline Completed: read failure 90% 7380 148905168
#21 Short offline Completed: read failure 90% 7380 148905168

Rendered in: 0.568 seconds



Is this fixable (how?) or can I reformat (how?) or do I need a new disk?