crashing and green screen

Tik33

New Member
#1
hi everyone,

I've just discovered this amazing forum.

I have an old HDR fox t2 1tb. It has been experiencing crashes which have become ever more frequent. It is not normally connected to a network (but I did connect it to install the custom firmware).

I have done the following:
1. taken the box apart, cleaned off all the dust - and crashes were still happening (between a few minutes apart and about an hour at most)
2. I have now had time to install the custom firmware - I used the latest version 1.03.12 and it installed fine.
3. I had wanted to install the fan package as I had seen on one post that running the fan at 30 or 40% all the time might help.
4. after i installed - the diagnostics said that there may be an error with the internal hard drive - here are the specs - I'm afraid that they don't mean much to me!
5. I then tried to install the fan package and the machine froze. When i turned it back on, I got the green screen.
6. I left it a few minutes and it came back on.
7. I have managed to install the fan package and set it at 50%.

Question: is there anything else I could try? is there anything in the below that suggests I need to do something urgently?

thank you!



Disk Information
SMART Status PASSED
Model Family Seagate Video 3.5 HDD
Device Model ST1000VM002-1CT162
Serial Number W1G0EAN4
LU WWN Device Id 5 000c50 0535bc55b
Firmware Version SC23
User Capacity 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes 512 bytes logical, 4096 bytes physical
Rotation Rate 5900 rpm
Form Factor 3.5 inches
Device is In smartctl database [for details use: -P show]
ATA Version is ATA8-ACS T13/1699-D revision 4
SATA Version is SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is Tue Feb 6 16:17:27 2018 GMT
SMART support is Available - device has SMART capability.
SMART support is Enabled
Attributes
ID Name Flags Raw Value Value Worst Threshold Life Left Notes
1 Raw_Read_Error_Rate POSR-- 190348840 118 099 006 -
3 Spin_Up_Time PO---- 0 097 097 000 -
4 Start_Stop_Count -O--CK 5407 095 095 020 94% -
5 Reallocated_Sector_Ct PO--CK 0 100 100 036 100% -
7 Seek_Error_Rate POSR-- 350747173 085 060 030 -
9 Power_On_Hours -O--CK 11939 087 087 000 87% -
10 Spin_Retry_Count PO--C- 0 100 100 097 100% -
12 Power_Cycle_Count -O--CK 5407 095 095 020 94% -
184 End-to-End_Error -O--CK 0 100 100 099 -
187 Reported_Uncorrect -O--CK 0 100 100 000 -
188 Command_Timeout -O--CK 0 100 100 000 -
189 High_Fly_Writes -O-RCK 161 001 001 000 -
190 Airflow_Temperature_Cel -O---K 31 069 (31°C) 037 (63°C) 045 (55°C) In_the_past
191 G-Sense_Error_Rate -O--CK 0 100 100 000 -
192 Power-Off_Retract_Count -O--CK 5406 098 098 000 98% -
193 Load_Cycle_Count -O--CK 5407 098 098 000 98% -
194 Temperature_Celsius -O---K 31 031 063 000 -
197 Current_Pending_Sector -O--C- 0 100 100 000 -
198 Offline_Uncorrectable ----C- 0 100 100 000 -
199 UDMA_CRC_Error_Count -OSRCK 0 200 200 000 -
Self-test logs
No. Description Status Remaining When First Error LBA
# 1 Short offline Completed without error 00% 0 -
Rendered in: 0.82 seconds
 

MartinLiddle

Super Moderator
Staff member
#2
Question: is there anything else I could try?
I am sure Black hole will be along shortly to point you at his guide to sorting out this sort of problem.

is there anything in the below that suggests I need to do something urgently?
The hard drive has got a bit hot in the past but apart from that I don't see anything of concern in the data.
 
OP
OP
T

Tik33

New Member
#6
hi Trev

just to follow on on the guide to freezes - what are your thoughts about the below? Have I made too many assumptions? PS. is it strange that on start up there is either a full green screen (and then nothing happens) or a thin green line on the right hand side of the TV (and then it boots up):
1 - I have assumed that this isn't relevant - as while there are occasions where it freezes on start up - if I leave the machine for longer than a few seconds - then it does appear to start up, if only for about 1-60 minutes (i.e. it's not an immediate freeze 100% of the time)
2a. was on bbc1 - no difference
2b. changed to channel 250 (bbc red button) - it froze, turning on and off immediately caused green screen
2c. I have discounted as it wasn't connected to a network when it started freezing
2d. similar to 2c
2e. I haven't done this yet as am waiting for Humax to stay on long enough
2f. done previously
3a. have opened up and checked for fluff and cleaned out. haven't done the paper test as unit crashes too quickly
3b. haven't done this yet
3c. haven't done this yet
3d. haven't done this yet

thank you!
 

Trev

The Dumb One
#8
No prob. But have you any comments on Tik's post as I haven't a clue, but just knew where to find your guide.
 
OP
OP
T

Tik33

New Member
#9
update to this on part 2e - I think that the fixdisk has stopped - but can't be sure - it seems to be stuck on 13.8% for the last 2 hours. Is it possible that the machine has frozen in the middle of a disk repair? if it's stuck, should I restart everything?

here is what it says so far:

Checking disk sda (4096 byte sectors)
Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3
Running short disk self test
No pending sectors found - skipping sector repair
Checking partition tables...
MBR Status: MBR only
GPT Status: not present
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Tue Feb 6 20:51:01 GMT 2018: Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 8.54/ 3.34/ 2.45
Pass 1: I/O read: 164MB, write: 0MB, rate: 19.21MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (259k/82k), time: 0.01/ 0.00/ 0.00
Pass 2: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (259k/82k), time: 9.20/ 3.61/ 2.50
/lost+found not found. Create? yes
Pass 3A: Memory used: 340k/0k (263k/78k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (262k/79k), time: 0.73/ 0.06/ 0.05
Pass 3: I/O read: 1MB, write: 0MB, rate: 1.38MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (57k/284k), time: 0.98/ 0.98/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 340k/0k (53k/288k), time: 1.84/ 1.83/ 0.00
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
14 inodes used (0.00%, out of 655776)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/2/0
305959 blocks used (11.67%, out of 2622611)
0 bad blocks
1 large file
3 regular files
1 directory
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
4 files
Memory used: 340k/0k (53k/288k), time: 12.85/ 6.49/ 2.57
I/O read: 166MB, write: 1MB, rate: 12.91MB/s
Tue Feb 6 20:51:15 GMT 2018
Tue Feb 6 20:51:15 GMT 2018: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (61k/80k), time: 1.65/ 0.25/ 0.44
Pass 1: I/O read: 17MB, write: 0MB, rate: 10.33MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time: 0.00/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 950.57MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time: 2.32/ 0.28/ 0.45
/lost+found not found. Create? yes
Pass 3A: Memory used: 140k/0k (72k/69k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 140k/0k (72k/69k), time: 0.38/ 0.01/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 2.62MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (51k/90k), time: 0.11/ 0.11/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 140k/0k (50k/91k), time: 0.26/ 0.26/ 0.00
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
15 inodes used (0.02%, out of 65808)
1 non-contiguous file (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/2/0
16262 blocks used (6.18%, out of 263064)
0 bad blocks
1 large file
3 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
5 files
Memory used: 140k/0k (50k/91k), time: 3.09/ 0.66/ 0.46
I/O read: 17MB, write: 1MB, rate: 5.50MB/s
Tue Feb 6 20:51:18 GMT 2018
Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=dce9c52b-0acc-4c5f-9aa4-4c2bd4eefa45
Tue Feb 6 20:52:01 GMT 2018: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
/dev/sda2: |========
 

MartinLiddle

Super Moderator
Staff member
#12
update: I'm pretty sure that this has frozen and so will turn off, leave overnight and start again tomorrow.
Keep in mind that the first partition sda1 is quite small; sda2 is the largest partition where recordings are stored and so takes much longer to check than sda1.
 
OP
OP
T

Tik33

New Member
#13
Have you done the "disconnect the HDD" part of the diagnostics?

See Newbies' Guide to the Forum (click) for instruction on posting screen dumps.
thanks - no - not yet - was doing the list 'in order'

Keep in mind that the first partition sda1 is quite small; sda2 is the largest partition where recordings are stored and so takes much longer to check than sda1.
thanks - as of this morning - the machine seems to have frozen as soon as I got it into maintenance mode and ran the main function - as I can no longer connect via Telnet.

I will therefore leave it again and disconnect the HDD as my next task (hopefully tonight or tomorrow night) and see if that improves matters - if it is the HDD, I assume I'll be able to test this by seeing if the Humax stays on, and responds to channel changes etc.

thanks for your help thus far and I will report back with results.
 
OP
OP
T

Tik33

New Member
#15
Hi everyone,
it's been a while since I last posted- in the meantime we have managed to do without Humax (it's sat unloved) and have been using Amazon Prime instead - but it's nearly Christmas and
a) I'm realising the downsides of Amazon Prime
b) It would be good to retrieve my recordings from my old box
c) it might be time to buy a new Humax.

my initial thoughts when I looked at new Humax boxes were:
a) they are still expensive (£200+) for 1TB of storage (which is what I have on my old one - and surprised that it's not 2TB as standard)
b) not the same solid 5 stars as they got before - wondering if quality is falling
c) can I get my old Humax back to life.

so, I have gone back to this great forum for advice.

in terms of salvaging the old Humax - I disconnected the HD and it seems to work fine (flicking through channels etc.) - So I think the problem must be the drive itself.

I have managed to get it into maintenance mode and got about 15-20 mins into the maintenance mode. Here's what it outputted so far (it seems to have stopped at 19.0% on the front panel of the Humax)

any thoughts on next steps or ways in which I can complete the fix disk?

thank you!

Code:
Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3


Running short disk self test

No pending sectors found - skipping sector repair

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3


Sun Dec 16 08:31:34 GMT 2018: Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 11.58/ 5.27/ 2.60
Pass 1: I/O read: 165MB, write: 0MB, rate: 14.25MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (259k/82k), time:  0.01/ 0.00/ 0.01
Pass 2: I/O read: 1MB, write: 0MB, rate: 118.25MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time: 12.23/ 5.53/ 2.66
Pass 3A: Memory used: 340k/0k (259k/82k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (259k/82k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (53k/288k), time:  0.98/ 0.98/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 340k/0k (53k/288k), time:  2.62/ 1.95/ 0.04
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.38MB/s

          15 inodes used (0.00%, out of 655776)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 3/3/0
      568360 blocks used (21.67%, out of 2622611)
           0 bad blocks
           1 large file

           4 regular files
           2 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           6 files
Memory used: 340k/0k (53k/288k), time: 15.88/ 8.47/ 2.70
I/O read: 167MB, write: 1MB, rate: 10.52MB/s
Sun Dec 16 08:31:50 GMT 2018

Sun Dec 16 08:31:50 GMT 2018: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (62k/79k), time:  0.81/ 0.25/ 0.44
Pass 1: I/O read: 17MB, write: 0MB, rate: 21.10MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time:  0.00/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 570.13MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time:  0.90/ 0.27/ 0.44
Pass 3A: Memory used: 140k/0k (72k/69k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 140k/0k (71k/70k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (50k/91k), time:  0.11/ 0.11/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 140k/0k (50k/91k), time:  0.32/ 0.26/ 0.00
Pass 5: I/O read: 1MB, write: 0MB, rate: 3.13MB/s

          16 inodes used (0.02%, out of 65808)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 3/2/0
       16732 blocks used (6.36%, out of 263064)
           0 bad blocks
           1 large file

           4 regular files
           3 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           7 files
Memory used: 140k/0k (50k/91k), time:  1.36/ 0.65/ 0.45
I/O read: 17MB, write: 1MB, rate: 12.52MB/s
Sun Dec 16 08:31:52 GMT 2018

Sun Dec 16 08:31:55 GMT 2018: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
^[[A^[[A^[[A^[[A^[[A^[[A/dev/sda2: |                                            ^[[A/dev/sda2: |                                                        /  0.2% Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 16400395 was part of the orphaned inode list.  FIXED.
Inode 16400396 was part of the orphaned inode list.  FIXED.
Inode 16400760 was part of the orphaned inode list.  FIXED.
 

Black Hole

May contain traces of nut
#16
I have managed to get it into maintenance mode and got about 15-20 mins into the maintenance mode. Here's what it outputted so far (it seems to have stopped at 19.0% on the front panel of the Humax)
How long have you been waiting for it to go any further? Who says it won't?

not the same solid 5 stars as they got before - wondering if quality is falling
Not so much the quality of the hardware as the quality of the software. Plus, of course, a minus is that we only have customisation on the HDR-FOX.
 

MartinLiddle

Super Moderator
Staff member
#17
any thoughts on next steps or ways in which I can complete the fix disk?
Just be very patient. It has checked the two small partitions and is now working on the partition used for recordings which will take much longer. It is impossible to say how long because it depends on a lot of factors (size of hard drive, how the hard drive was formatted, how severe the damage is to the file system). When it has finished post the output from the drive diagnostic (under Diagnostics in the web interface). Some people have reported it taking more than 24 hours.
 
OP
OP
T

Tik33

New Member
#18
Just be very patient. It has checked the two small partitions and is now working on the partition used for recordings which will take much longer. It is impossible to say how long because it depends on a lot of factors (size of hard drive, how the hard drive was formatted, how severe the damage is to the file system). When it has finished post the output from the drive diagnostic (under Diagnostics in the web interface). Some people have reported it taking more than 24 hours.
thank you @Martin - I'll run it overnight tonight. The reason I thought it had crashed is that there was no response on anything. Also, when it started the screen on the TV was frozen on a channel and then it went black. Is there any way to know whether or not it's crashed or it's just taking a long time?

Does it matter if my laptop goes into hybernation/sleep? Can I use my laptop for other tasks while it's going on?

thanks

Gus
 

MartinLiddle

Super Moderator
Staff member
#19
the reason I thought it had crashed is that there was no response on anything. Also, when it started the screen on the TV was frozen on a channel and then it went black.
The whole point of going into maintenance mode is that the Humax binary is not running so none of the PVR features will be available.
Is there any way to know whether or not it's crashed or it's just taking a long time?
If you haven't seen any output for a really long time (say an hour or two) then it may have crashed.
Does it matter if my laptop goes into hybernation/sleep? Can I use my laptop for other tasks while it's going on?
Providing you have a recent version of the custom firmware then it doesn't matter if your laptop is disconnected see https://hummy.tv/forum/threads/fix-disk-continue-running-if-connection-dies.7656/#post-104254 Best advice would be to upgrade the custom firmware to the latest version before trying again because there have also been improvements to fix-disk.
 
OP
OP
T

Tik33

New Member
#20
If you haven't seen any output for a really long time (say an hour or two) then it may have crashed.
thanks - I've been running it all afternoon while away - have come back and it's showing this:
Code:
Sun Dec 16 14:47:40 GMT 2018: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
/dev/sda2: |===                                                     -  5.9%
if it stays like that for the next hour - is there any other fix? as it kept crashing last time I tried to use the fixdisk.
I'm running the latest custom firmware I believe (couldn't see any more recent than 2017).

the disk is readable for a while before it crashes - any other thoughts on how to salvage?

thanks!
 
Top