UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having a problem when booting. I've been up and running for a couple of months then this problem appeared when booting up. Here's what I'm seeing on boot.
Loading, please wait...
FATAL: module unknown not found.
mount: Mounting /dev/hdb1 on /root failed: No such device
mount: Mounting /root/dev on /dev/ .static/dev failed: No such file or directory
mount: Mounting /dev on /root/dev failed: No such file or directory
Target filesysetm doesn't have /sbin/init
BusyBox v1.00-pre10 (Debain 20040623-1ubuntu22) Built-in shell (ash)
Enter 'help' for a list of built-in commands
sudo gedit /etc/fstab I get the fstab off the cd. Checked the file sys etc/fstab the same. When into the system>administration>disks and can see the hd and partitions.
Everything has been running great and I've done nothing unusual...
I loaded the live cd and went into Gparted and looked at the partitions and here's what I have.
/dev/hdb1
/dev/hdb2 (and the following under this partition)
/dev/hdb6 swap
/dev/hab7 ext3
/dev/hdb5 ntfs - this is the other partition on the secondary.
Went and checked the partitions. The only one that is questionable is /dev/hdb1 and I'm getting the followin info.
/dev/hdb1
-unknown
-warning unable to detect the file system
-damaged
-unknown to libparted
-unformatted
FYI-the secondary is split into 2 (20/20 gb per partition) one for Linux and the other as extra storage for Windows.
Hi. I am new to linux, but I have to say that sounds like a hard-drive problem, ie, not being seen. (as opposed you your software). I would think that it worth just going into your BIOS on your next boot, just to see whether BIOS sees your hard drive before going any further. No real effort and a quick answer to exclude it. But as I say, I am no linux expert.
Hope it helps, and good luck.
will show up all the disks and partitions as they are "found" and "known" by the Linux. This is more relevant than what the BIOS call them. If the BIOS couldn't find any of them then the Linux will not have it in "fdisk -l".
Try "fsck -y /dev/hdb1" from the livecd, your root partition may have errors. Does windows still boot?
Please also post your /etc/lilo.conf file, to do this (if fsck finnishes clean) issue the following from the livecd:
Code:
mount /dev/hdb1 /mnt
less /mnt/etc/lilo.conf
or
Code:
less /mnt/boot/grub/menu.lst
If "mc" works you can use that to browse the filesystem in a terminal.
Can you see anything at all after mounting /dev/hdb1?
try "ls -al /mnt" and "ls -al /mnt/etc" (if it exists).
Things aren't looking good at the moment if you don't see any files. If you do see a directory called "lost & found" or similar look in there, all your files may be there - and that's bad too :~(
edit: your filesystem was definitely corrupted somehow, probably a power outage?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.