Checking disk media in 2.0 final

Posted by: Lemmy

Checking disk media in 2.0 final - 02/04/2003 00:50

... during the first sync after updating seems to take really long?

ok, I got two drives in my empeg, maybe thats the cause.


bye,
[L]
Posted by: Shonky

Re: Checking disk media in 2.0 final - 02/04/2003 02:23

Yeah mine has taken around 20 minutes so far and the bar is still only one pixel wide. I too have two drives but I doubt that is the problem.

The drive indicators show only the right hand drive (the secondary I guess) as spun up but not being read.

I can definitely hear the heads moving about though.

....Hang on ... all of a sudden it's about 85% done now although it seems to have slowed down again. Drive indicators show the same status. At first I thought it was trying to convert the file system into the new format but the release notes would not indicate that.

Oh well it's onto rebuilding the database now. About 30 minutes is probably about right for a fsck though on my total 70G machine.

It would seem that emplode forces a fsck if it detects an upgraded unit.
Posted by: wfaulk

Re: Checking disk media in 2.0 final - 02/04/2003 07:04

Nope. I have a recently upgraded empeg and everything went fine with it. No extraordinary fsck lengths.
Posted by: Shonky

Re: Checking disk media in 2.0 final - 02/04/2003 07:09

Perhaps it was just the two of us who got (un)lucky and had a fsck forced onto us when sync after we upgraded - I don't think mine was particularly long though - just curious as to why it happened after the upgrade.

Now that I think about it, according to the FAQ a fsck happens every 20-30 syncs so the odds are pretty high given the number of players out there (assuming most haven't turned this option off...)
Posted by: Micman2b

Re: Checking disk media in 2.0 final - 02/04/2003 08:21

I noticed the same thing the last time I synced with v2.0b13. It took 4 hours to check media on the eMpeg. I just upped 10gig of new "toons" the last sync and I went back in to change some tags for this sync. I figured that it was "reindexing" the database or something. Maybe it was fsck'ing..

Sean