LinHES Forums
http://forum.linhes.org/

fsck.ext3: no such device /dev/hda4
http://forum.linhes.org/viewtopic.php?f=6&t=7185		 Page 1 of 1
Author:  BSquared [ Fri Dec 02, 2005 9:10 pm ]
Post subject:  fsck.ext3: no such device /dev/hda4
Whenever I reboot (after a successful KnoppMyth R5a26 install) I receive the following error:

fsck failed. please repair manually
fsck.ext3: No such device or address while trying to open /dev/hda4. Possibly non-existant or sway drive?

I performed a manual install and created the recommeded partitions (though I set up /cache and /myth a logical partition) as:
hda1 / ext3
hda2 swap
hda5 /cache ext2
hda6 /myth ext3

My question is this, why would I be getting this error? Is KnoppMyth looking for something specific on /dev/hda4? Can I fix this error without reinstalling and how?

Ok, that was three questions. Any help would be appreciated.

Cheers,
-Bill
Author:  tjc [ Fri Dec 02, 2005 11:34 pm ]
Post subject: 
Edit you /etc/fstab to match your real mount points and partitions.
Author:  BSquared [ Tue Dec 06, 2005 6:32 pm ]
Post subject: 
Thanks tjc. That was what I was missing.

-Bill
Author:  BSquared [ Tue Dec 06, 2005 7:06 pm ]
Post subject: 
Ok. I made the changes and the resulting /etc/fstab file is:

Code:
# /etc/fstab: filesystem table.
#
# filesystem  mountpoint  type  options  dump  pass
/dev/hda1  /  ext3  defaults,errors=remount-ro  0  1
/dev/hda5  /cache  auto  defaults,auto  0  2
/dev/hda6  /myth  ext3  defaults,auto  0  2

proc  /proc  proc  defaults  0  0
sysfs /sys   sysfs defaults  0  0
/dev/fd0  /floppy  vfat  defaults,user,noauto,showexec,umask=022  0  0
/dev/cdrom /cdrom  iso9660  defaults,ro,user,noexec,noauto  0  0
/dev/cdromhdb /cdromhdb  iso9660  defaults,ro,user,noexec,noauto  0  0
# Added by KNOPPIX
/dev/hda2 none swap defaults 0 0
# Added by KNOPPIX
/dev/hda5 /mnt/hda5 ext2 noauto,users,exec 0 0
# Added by KNOPPIX
/dev/hda6 /mnt/hda6 ext3 noauto,users,exec 0 0


The changes I made were from:
/dev/hda3 /cache auto defaults,auto 0 2
/dev/hda4 /myth ext3 defaults,auto 0 2

to
/dev/hda5 /cache auto defaults,auto 0 2
/dev/hda6 /myth ext3 defaults,auto 0 2

The problem now is that I can't connect to mythbackend. I receive an error stating "Could not connect to the master backend server -- is it running? Is the IP address set for it in the setup program correct?"

when I look at /var/log/mythtb/mythbackend.log I see
/myth/tv/nfslockfile.lock: No such file or directory
Unable to open lockfile!
Be sure that '/myth/tv' exists...

Which, when I cd to /myth, all I see is lost+found.

Did I not make the correct changes in the /etc/fstab file? Do I need to rerun myth-setup?
Author:  tjc [ Tue Dec 06, 2005 8:15 pm ]
Post subject: 
You installed into /myth which was "just a subdirectory" on /dev/hda1, then you mounted /dev/hda6 over the top of it which hid the existing contents of the directory. To fix it:

Code:
umount /myth
ls -al /myth   # you should see all the files
cd /
tar jcvf  /tmp/myth.saved.tar.bz2  /myth
rm -rf /myth/*
mount /myth
tar jxvf /myth.saved.tar.bz2


Corrected to protect the unwary.
Author:  BSquared [ Thu Dec 08, 2005 5:44 pm ]
Post subject: 
Thanks again, tjc - I now have a functional KnoppMyth install once again.

For those who might be experiencing the same problem, the last line from tjc's solution should be changed to:

Code:
tar jcxf /tmp/myth.saved.tar.bz2

(replacing the 'c' with 'v' to extract the files from the archive).

Also, I had to repeat the same process or the /cache directory as well since I had /cache as a separate mount point.

Cheers,

-Bill
Author:  BSquared [ Thu Dec 08, 2005 5:46 pm ]
Post subject: 
Sorry, that last line should have read:

Code:
tar jxvf /tmp/myth.saved.tar.bz2
Author:  tjc [ Thu Dec 08, 2005 7:33 pm ]
Post subject: 
Sorry, you're absolutely correct. My brain must have dropped a bit. Wish I could blame cosmic rays, but lack of sleep is far more likely.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/