SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
(swapper,1,1):ocfs2_fill_super:1039 ERROR: superblock probe failed!
VFS: Cannot open root device "sda1" or unknown-block(8,1)
Please append a correct "root=" boot option; here are the available partitions:
0800 244198584 sda driver: sd
0801 9767488 sda1 00000000-0000-0000-0000-000000000000
0802 19535040 sda2 00000000-0000-0000-0000-000000000000
0803 3903795 sda3 00000000-0000-0000-0000-000000000000
0804 210989677 sda4 00000000-0000-0000-0000-000000000000
0b00 1048575 sr0 driver; sr
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
Pid: 1, comm: swapper Not tainted 184.108.40.206 #3
[<ffffffff81aa213a>] ? printk+041/0x43
[<ffffffff8210fc54>] ? kernel_init+0x0/0x1e2
[<ffffffff8100370d>] ? kernel_thread_helper+0x0/0x10
This started randomly, I had not done any upgrades or changes. I have since tried reloading slackware from disk with no change. Lilo would not write to the mbr at the end of setup. sda1 is the root partition, sda2 is /usr, sda3 is the swap, and sda4 is /home. I'm out of ideas at this point and looking for some help.
trying to boot from a usb disk with /dev/sda1 as root produces the same panic. I formated that partition when I when through the reinstall process and ran a check at the same time so I don't think there is a physical problem with the disk.
I experienced a similar problem about a year ago with my tower PC, except that I was still able to boot from USB drives. What had happened in my case was that the motherboard's SATA controller had gotten confused owing to a faulty cable connection on one of the drives and, even after fixing the cabling, would not properly access the root drive.
Yes, I know that such problems should not theoretically happen, or at least should be recoverable by resetting the BIOS to its defaults; however, resetting the BIOS didn't fix things. Fortunately, I was able to remedy the problem by re-flashing the BIOS (booting the BIOS updater from a USB-connected DVD).
I only mention this as a last resort possibility to consider if all else fails (and assuming you have a means of re-flashing the BIOS).
I ran systemrescuecd and gparted did not recognize any filesystem on sda1 even though I reformatted it during the reinstall. I used gparted to set it back to ext4. I'm going to try the reinstall again.