[mythtv-users] Hard drive failure...
johnmythtv at crombe.com
Fri Mar 7 05:35:27 UTC 2003
Ok, here's the scoop...
I booted from the CD, entered "rescue", did e2fsck -c -y /dev/hda5 and it
found and fixed lots of errors. I rebooted when done and all came up just
like it was never messed up. I suspect some files *must* be messed up, but
it's not visible. Myth even came up.
So next, I ran tune2fs -j /dev/hda5 (my 68gb /video partition) and also on
/dev/hda6 (my 3.4gb os partition). I also have a 1gb swap partition (have
512mb ram). That ran fine. Next I put in "ext3,ext2" in my fstab for both
the hda5 and hda6 as suggested. Here's my fstab (feel free to criticize!):
[root at p800 mythtv]# cat /etc/fstab
# WAS: /dev/hda6 / ext2 defaults 1 1
/dev/hda6 / ext3,ext2 defaults 1 1
none /dev/pts devpts mode=0620 0 0
//192.168.0.6/C /mnt/C smbfs credentials=/etc/samba/auth.192.168.0.6.crombej
//192.168.0.6/DVD /mnt/DVD smbfs
credentials=/etc/samba/auth.192.168.0.6.crombej 0 0
none /mnt/floppy supermount
dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0
//c117787-d/C /mnt/p4_C smbfs credentials=/etc/samba/auth.c117787-d.crombej
//192.168.0.6/V /mnt/p4_v smbfs
credentials=/etc/samba/auth.192.168.0.6.crombej 0 0
//c117787-d/X_VIDEO /mnt/p4_x smbfs
credentials=/etc/samba/auth.c117787-d.crombej 0 0
none /proc proc defaults 0 0
# WAS: /dev/hda5 /video ext2 defaults 1 2
/dev/hda5 /video ext3,ext2 defaults 1 2
/dev/hda7 swap swap defaults 0 0
And here's the output from "mount"
[root at p800 mythtv]# mount
/dev/hda6 on / type ext3,ext2 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,mode=0620)
/dev/hda5 on /video type ext2 (rw)
//192.168.0.6/C on /mnt/C type smbfs (0)
//192.168.0.6/DVD on /mnt/DVD type smbfs (0)
//c117787-d/C on /mnt/p4_C type smbfs (0)
//192.168.0.6/V on /mnt/p4_v type smbfs (0)
//c117787-d/X_VIDEO on /mnt/p4_x type smbfs (0)
[root at p800 mythtv]#
Notice how /hda6 shows ext3,ext2 but /hda5 only shows ext2? Why is that?
To prove that I really did the tune2fs -j on it, I ran it again and it
reported "The filesystem already has a journal.". Is that right?
Finally, should I change hda5 and 6 both to be
"defaults,noatime,data=writeback 0 2" or only the OS parition or the Video
one or what? I've read about it but your practical experience is way more
valuable than my books!
P.S. Now that Myth isn't currently running and I'm just sitting at KDE, is
there some "system test" program I should run to just run the heck out of it
(hard drive, memory, video, etc.) to see if all is working well and will
stay up? Hate to start doing some heavy Myth coding and have it crash on me
----- Original Message -----
From: "Cliff Draper" <Cliff.Draper at sun.com>
To: <mythtv-users at snowman.net>
Sent: Thursday, March 06, 2003 3:10 PM
Subject: Re: [mythtv-users] Hard drive failure...
> From: Unit3 <unit3 at demoni.ca>
> Date: Thu, 06 Mar 2003 12:51:01 -0600
> > JC wrote:
> > >This PC had run perfectly for about 2 years with Win2k and never a
glitch of trouble. Do you think turning on the dma stuff as suggested in
> > >setup/faq could have screwed it up? If so, would it really take a few
weeks to screw up?
> > >
> > This is technically possible with older hardware, but I find it highly
> > unlikely with new hardware, unless your IDE controller or something else
> > on your motherboard is also malfunctioning.
> It seems pretty unlikely to me too.
> > >Also, should I try and switch the file system (using linux default
> > >ext2 right?) to some journaled one or something "safer"?
> A journaled filesystem like ext3 works great as a filesystem for
> normal files. For the type of file usage that MythTV does (create a
> huge file once, and then only do reads from it), it really only
> provides 1 big advantage: fast fsck time due to better crash
> tolerance. Running fsck on a 100gig partition takes too long for
> ext2, so I switched to ext3, and I've been pretty happy with it.
> Here's my entry in /etc/fstab:
> /dev/hda7 /data ext3 defaults,noatime,data=writeback 0 2
> > >What's the right/best way to repair the partition if any?
> > I haven't had to do this in a while, but it seems to me that fsck should
> > have some options to do a more exhaustive disk scan... let's check the
> > man page! ;)
> > well, passing -c to e2fsck apparently forces it to run badblocks and
> > mark all corrupt blocks on your disk in the "bad block inode", which I
> > assume just keeps track of bad blocks so the fs doesn't try to use them.
> > Apparently using -c twice will force it to do a non-destructive
> > read-write test to do this, which is probably about as comprehensive as
> > you're going to get. Another possibly useful option is -f, which forces
> > a check even if it thinks it's fine.
> I recently lost the hard drive on my MythTV's machine. I ran the
> badblock's non-destructive read-write test (which takes a long time to
> run), and came up with nothing. Apparently modern hard drives do
> their own bad block reallocation automatically. A lot of hard drives
> have 3 year warranties, and so mine was still covered. I ran Maxtor's
> diagnostic program on it and got a failure. After that, it was as
> simple as RMA.
> Cliff Draper Sun Microsystems, Forte Tools
> My opinions may or may not reflect those of my employer.
> ---------------------------- food for thought ---------------------------
> The meta-Turing test counts a thing as intelligent if it seeks to
> devise and apply Turing tests to objects of its own creation.
> mythtv-users mailing list
> mythtv-users at snowman.net
More information about the mythtv-users