SlackwareThis Forum is for the discussion of Slackware 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.
An error accoured during the root filesystem check.
Installed fresh Slack 13.0 version, at 7GB virtual hdd, with cfdisk, created two primary partitions, 500 mb for swap, whats left, to second partition, made it bootable, installed full software package, used all default selections, only refused to configure network. At first restart, I got a screen with many statements, that looks like errors, and a last one, that looks like critical error. An image
I have been working on Windows my whole life and only worked with already installed linux systems a bit. Installed RedHat and FreeBSD on VirtualPC previously and succesfully.
Now, I stumble upon this error and cant think of next step.
Why on Earth do you use VirtualPC?! VMware Workstation (not for little purses), VMware Player (good enough), VirtualBox (OpenSource).
Where did you set up the Boot Block (maybe superblock?)
Well, VPC is the best for Microsoft or OS/2 guests, but for Linux...
I didn't mean the bootable flag, in "liloconfig"-script it asks you where tu put the boot sector (MBR, Suberblock, or Floppy)
try boot from the CD again, but at the boot prompt, enter:
Code:
boot: hugesmp.s root=/dev/hda2 rdinit= ro
Just like shown above, maybe you have to enter /dev/sda2
By the way, booting from a swap partition can be funny, it was the First time I saw a "Kernel Panic"
If VirtualPC worked on my PC, I could try it also. But it doesn't.
Well, VPC is the best for Microsoft or OS/2 guests, but for Linux...
I didn't mean the bootable flag, in "liloconfig"-script it asks you where tu put the boot sector (MBR, Suberblock, or Floppy)
try boot from the CD again, but at the boot prompt, enter:
Code:
boot: hugesmp.s root=/dev/hda2 rdinit= ro
Just like shown above, maybe you have to enter /dev/sda2
By the way, booting from a swap partition can be funny, it was the First time I saw a "Kernel Panic"
If VirtualPC worked on my PC, I could try it also. But it doesn't.
What kind of hdd controller did you use in Vpc?
ide or sata ?
What kernel did you install ( version ?) or did you use slackware 13 or current ?
in current the kernel doesn't support ide without initrd
Which partions are for what (and what type :83 and 82 )? Must be /dev/sda1 for swap and /dev/sda2 for root after your description.( better the other way round )
In your screenshot it looks to me, that e2fsck tries to open / instead of /dev/sda2,
so I guess you made the mistake in the setup when it asks you for your root partition .
You have to type the full devicename , not only press enter - so you should type sth like /dev/sda2 when setup asks for your root and the full device name for swap also .
You need to install again and give the correct answers in setup ( Slack is not a winbuntu clone - We still need the keyboard to install it ) )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.