[js0873]

I have a Western Digital 1.5TB EHD connected to my Hopper with about 1 TB of recorded programming. I've found that the nightly system update takes a very long time, upwards of 25 minutes or more with it connected. It says it's doing a system integrity check that should take no more than 10 minutes, but it takes at least 20 or so and usually 25 minutes or longer counting the reboot process. If I disconnect the EHD the whole process takes less than 4 minutes.

What does nightly update process do with the EHD that takes it so long? Why must it check something on it every night? Is there a way around this, other than disconnecting the EHD which I finally did last night?

 

[Charise]

I noticed this for the first time last week. My EHD is connected to a 622 (original with which I haven't had problems), and though the update is set for the standard 3:00 a.m., the receiver is starting and restarting for over 1/2 hour beginning around 6:30. I don't know if it's doing the update at 3:00 also.

I have unplugged the EHD but left the USB intact between the EHD and 622, and I don't think this was happening--at least it wasn't waking me up--so I'll go back to that.

EHD is important with the 622 due to less space on the HD.

I haven't heard of this happening before, but an easy fix in my estimation.

 

[JmC]

I think this has been mentioned a couple of times in regards to 722s.

 

[domingos35]

I have a 2TB EHD connected to one of my hoppers and the nighty update takes only 5 minutes at the most

 

[js0873]

I have a 2TB EHD connected to one of my hoppers and the nighty update takes only 5 minutes at the most

Any idea how much programming is on your 2TB? Maybe we don't have the same amount of programming on it.

 

[P Smith]

It's doing fsck().

 

[3HaloODST]

Yep fsck. This is why Dish needs to allow us to set an update time just like on the older receivers, because sometimes when I turn on a hopper it's "fscked" up and I can't watch it until it's done :nono: .

 

[domingos35]

Any idea how much programming is on your 2TB? Maybe we don't have the same amount of programming on it.

right now the EHD is empty

 

[js0873]

right now the EHD is empty

Well, that would explain it then. FSCK time is dependent on the number of files in use. My question is why fsck must be done on a nightly basis. Any idea?

 

[P Smith]

Well, that would explain it then. FSCK time is dependent on the number of files in use. My question is why fsck must be done on a nightly basis. Any idea?

Isn't post#7 had the answer ?