[mythtv-users] Mythbackend System lockup; Checking root filesystem

[Tim Tait]

Are you using a Journaled file system, or ext2? Becausing checking ext2 
could take some time.

The disk diagnostics check out the disk itself, but don't do much for 
the interface to the system.

I had a similar problem once, it turned out to be a problem with the 
nForce2 chipset and the interrupt handler combined with some powersaving 
features, once in a while just lock up with the disk light on. Could be 
minutes to days before it happened. Turning off the powersave mode 
stopped it. Eventually a newer kernel fixed it. Not that that is the 
problem you have.

Are you using an 80 wire cable? Are those Maxtors trying to run ATA-133? 
Have you tried slowing down the IDE bus? Is your power supply up to the 
load? Are the disks getting too hot?

More hardware info could be helpful.

Tim

James Pifer wrote:
> On Thu, 2005-05-26 at 12:21, Tim Tait wrote:
> 
>>Is the console still responsive? (does capslock still toggle the LED?)
>>
>>What filesystem(s) do you have?
>>
>>Are you running Raid?
>>
>>What motherboard/IDE controller?
>>
>>
>>Tim
>>
> 
> 
> I think it has something to do with one of the hard drives. I have three
> drives, two of which are Maxtor 160 gig. I rebooted the machine and ran
> the quick tests of the drives using the Maxtor utility. Then I was able
> to reboot the machine and get into FC3. Weird thing is that both drives
> pass all tests, including the long tests. 
> 
> The drives are just a LVM, no redundancy. 
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/mapper/VolGroup00-LogVol00
>                      313022168 204470268  92651228  69% /
> /dev/hda1               101086     12077     83790  13% /boot
> 
> 
> When this was happening the console was not responsive and the machine
> was not accessible over the network. Not sure about capslock. 
> 
> Not sure what my plan is at this point. 
> 
> Thanks,
> James
>