34 replies to this topic

[speed]

so I should do a

e2fsck -f /dev/sda1

 

or just leave now as is?

[betacentauri]

@mattiL: As it now looks clean, you need to use -f switch to check filesystem.

@speed: As the tool said "everything is repaired and fine" it shouldn't be necessary. If you want to be sure, do it. It takes only a few minutes.

[speed]

root@vusolo2:~# e2fsck -f /dev/sda1
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 4460/953984 files (81.5% non-contiguous), 73853074/244190645 blocks
root@vusolo2:~#
 

[mattiL]

So it looks fine now, but has it made any difference to the problem?

[speed]

don't know yet

time will tell

 

before sometimes it worked ok for days

then it started crashing again

so I guess we will need to wait to see if it stopped crashing

[speed]

and its stil happening now?

so what else could it possibly be?

[mattiL]

Can you check the had disk again?

Perhaps there are new issues (errors) now..

 

If so, it might indicate a disk that is failing.

 

Do you have another disk to try with?

[speed]

already checked

no new errors

 

no I dont have another disk to try

[speed]

and another crash today

anyone any ideas?

 

or is it possible its the harddisk? even do there are no errors reported?

[speed]

and another crash today

it happened when I was watching channel a

channel b was recording half way

then suddenly picture stopped sound continued for +-10 seconds

then sound also stopped and system was frozen

 

so whats the next step I should take?

[speed]

bought and installed a new harddisk

but same problem?

 

what else I can try?

[Erik Slagter]

Sudden freezes are not caused by a corrupt filesystem nor a defective harddisk (well at least, almost never in that case).

 

Freezes are caused by either defective hardware or by "something" that is running inside the linux kernel. As the linux kernel is used by millions of people all over the world, this means that real kernel bugs must (and are) solved very quickly. Leaves the manufacturer's drivers, which also run inside the kernel.

 

From the older VU+ models we are familiar with the sudden freezes/crashes, for the solo2/duo2 it's much less likely to happen (long story).

 

So in short, either defective hardware or you do "something" that triggers a bug in the drivers.

 

1) do you play media often (mp4, mkv etc.)?

2) are you using the transcoding features?

 

Both of these are sensitive to crashing in the drivers.

[speed]

I do play from time to time some files

mostly .avi, sometimes mp4

 

no I dont use any transcoding at all

 

I do however have permanent timeshift running?

[Erik Slagter]

Yes that may very well heavily account to the freezing. It's a very long story, quite complex too, but you might want to consider to restart the receiver more often.

[speed]

update

so no transcoding

I have disabled permanent timeshift

only watched some recorded programs (.ts)

and still freezing?

 

any other suggestions?