Guys, I need your help...

I encounter error while booting the OS.. error message is

FATAL: Module minix not found
Mount: mouting /dev/hda2 on /root failed: no such deivce
Mount: mouting /root/dev on /dev/.static/dev failed: no such file or directory
mount: muting /dev on /root/dev failed: no such file or directory

Target filesystem doesn't have /sbin/init

BusyBox v1.00-pre10 (Debian 20046623-1ubuntu) Built-in shell (ash)

Enter "help" for a list of built-in commands/.
/bin/sh: Can't access TTY: job control turned off.
#

I am using this OS for a month already.

I used Dell Inspiron 700m notebook computer and running Ubuntu Breezy with KDE 3.5.

Can anybody help me how to fix this problem? I dont want to re-install everything if possible.

Any help would be hightly appeciated.

Thanks

can you post your /etc/fstab and your /boot/grub/menu.lst

you may need to run a live cd to view the files

the grub menu may have a parameter of using /sbin/init which we can edit .....init is a kind of way of starting services at bootup....sometimes faster

the minix is a file system that may have been selected by you in formatting one or more of the linux partitions

This is a live Cd for you : _http://www.knoppix.org/

I am currently downloading the Live CD.

Somebody has solve this problem, unfortunetly, I cannot post a message on that forum or to thay somebody, coz the forum he used to post is currently down and I cant post any message, I just read the article on archives.

his post is:
I have restored the system from scratch - using the disk that used to contain Windows XP - and there are no problems. While searching around I noticed that (somewhere) there is a suggestion that you do not use LVM to include the root directory - but I seem to remember that that was the default on the installation disc. (whenever I first install anything I use the defaults). The suggestion is that some system software can mess up the root / boot areas if you have them in LVM.
===

it said to be the LVN caused the problem. I am not sure whether or not I have LVM on my partition, I dual booted my notebook computer Windows Xp and Ubuntu. How to check whether I have LVM or none? :-) help pls.

anybody help?

I have some questions.

What type filesystem is root? If it is minix, you don't want that. You should not choose minix filesystem for root, or anything else. You want ext3 filesystem for everything.

You have been using this operating system for a month. Did it ever work, or has this been going on the whole month?

If it used to boot, what have you changed? Did you compile a kernel and leave out kernel support for the root filesystem?

Did you forget to make initrd?

Hi, I used ext3 filesystem. I didnt saw any minis choices on the installation. I have been using the OS for a month without any problem. I didnt compile any kernel. I just burn some files to dvd and I shut off my pc.

How'd I know if I used minix filesystem? also, just for curiosity sake, when should we use minix filesystem? is there any advantage over ext3? I am currentky using ext3 filesystem

Thanks

This acticle will help you
_http://www.tldp.org/HOWTO/Filesystems-HOWTO.html

Thanks a lot... I ended up re-installing my OS... but I didnt touch the /home I i didnt lost important files including my mails.

Thanks for the links..

Hello all,

I know this thread is supposed to be dead. But I am having the same problems that whizzkid8 was having before he reinstalled his system. I do not desire to re-install mine. The error messages are the same accept that on my system linux is selected from the dual boot menu to boot to hdb1(which is accurate).

here are the contents of my fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hdb1 / ext3 defaults,errors=remount-ro 0 1
/dev/hdb5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/hda1 /media/windows vfat user,fmask=0111,dmask=0000 0 0

and here is my grub menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hdb1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Ubuntu, kernel 2.6.12-10-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hdb1 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot

title Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hdb1 ro single
initrd /boot/initrd.img-2.6.12-10-386
boot

title Ubuntu, kernel 2.6.12-9-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hdb1 ro quiet splash
initrd /boot/initrd.img-2.6.12-9-386
savedefault
boot

title Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hdb1 ro single
initrd /boot/initrd.img-2.6.12-9-386
boot

title Ubuntu, memtest86+
root (hd1,0)
kernel /boot/memtest86+.bin
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Windows 95/98/Me
root (hd0,0)
savedefault
makeactive
chainloader +1

____________
I am currently posting this from a live CD after mounting my old drive to gain access to these files. I tried to:
grub-install /dev/hda
but that did not correct the problem.
What do the experts think?

-Caleb

can you boot into any of them including MS?

do you mean you have tried to install onto a formatted minix disk?
if so have you considered re-installing onto a more linux friendly system like ext3 or reiserfs?

Hi aus9,

Yes I can boot to MS. The disk is formatted as an ext3 drive. The whole MINIX module thing is misleading i guess, but thats the message I was getting.

I managed to find an error in how I was trying ot fix the problem. Grub needed to be re-installed, but I was installing it to hda instead of hda1. So all is good now. Thanks for the help though. Now I just have to wonder why the grub was corrupted?

thanks again.