LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-21-2014, 09:43 PM   #1
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Rep: Reputation: Disabled
Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0)


SLACKWARE LINUX 14.0

/dev/sda1 = /boot
/dev/sda2 = LVM Partition
/dev/lvfelix/swap = swap
/dev/lvfelix/var = /var
/dev/lvfelix/root = /
/dev/lvfelix/usr = /usr
/dev/lvfelix/opt = /opt
/dev/lvfelix/home = /home

After the installation finished and i boot the operating system this message shows up(see link below)

(picture)
http://postimg.org/image/3nvdh48ex/
 
Old 01-22-2014, 01:08 AM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Hello fjur94, welcome to LQ,

I suppose you're using a generic kernel?

Seems your missing either the driver for the filesystem (ext4?) or the disk (ahci or ide?) in your initrd.

In general your errormessage means that the kernel cannot mount the / partition due to missing drivers.

I'd recommend to post Slackware-related issues in the Slackware-forums at LQ. I'll report this thread and ask for moving to the Slackware-Forums.

Markus
 
Old 01-22-2014, 04:34 AM   #3
ChrisAbela
Member
 
Registered: Mar 2008
Location: Malta
Distribution: Slackware 14.1
Posts: 467

Rep: Reputation: 89
/var on a separate partition might not have been a good idea but I cannot locate the document I vaguely remember recommending against it so I cannot be sure.

Did you build an initrd? How?
Did you include the entry for initrd it in /etc/lilo.conf?
Did you run lilo -v after editing /etc/lilo.conf
 
Old 01-22-2014, 06:21 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
http://www.linuxquestions.org/questi...9/#post5103222

Please don't double post your problem in the forum again.
 
Old 01-22-2014, 08:25 PM   #5
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
Sorry Richard

Chris, no i have not done that :S
 
Old 01-22-2014, 08:48 PM   #6
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
No problem, it's just slightly annoying to have to post a reply in two different places.
 
Old 01-24-2014, 02:02 PM   #7
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
i made this vídeo during the installation, the most important part is when it is installing packages

See link below
http://www.youtube.com/watch?v=CsXP3Lb54ao

Note: i'm speaking spanish in the video
 
Old 01-24-2014, 02:12 PM   #8
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Hi,

at least one problem is quite obvious. You use a partition with only 1 GB of size for your /usr directory, this is way too small. I don't know how lvm comes into play, but there are errormessages about "no space left on device". But I would recommend to create only three partitions, /, /home and /swap (if necessary) and you should know that after a complete installation, there are about 7GB used on /

Markus

Last edited by markush; 01-24-2014 at 02:13 PM.
 
Old 01-24-2014, 02:16 PM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
One of your disk partitions filled up during the install. At that point, your system is insane. See which of the partitions is close to full, make it larger and reinstall from scratch.

(By the way, I've been there and done that.)

I've installed other things on this Slackware64 14.1 machine, but my current partition use is
Code:
~$ df -h
Filesystem                    Size  Used Avail Use% Mounted on
/dev/mapper/vg1-rootlv         10G  1.2G  8.8G  12% /
/dev/sda2                     488M   39M  415M   9% /boot
/dev/mapper/vg1-homelv         32G  1.5G   31G   5% /home
/dev/mapper/vg1-varlv          20G  829M   20G   5% /var
/dev/mapper/vg1-optlv          16G  2.2M   16G   1% /opt
/dev/mapper/vg1-usrlv          20G  7.5G   13G  38% /usr
/dev/mapper/vg1-libvirtstore  121G   60M  115G   1% /var/lib/libvirt/images
tmpfs                         3.8G     0  3.8G   0% /dev/shm
tmpfs                         3.8G   33M  3.7G   1% /tmp
You'll note that a lot of stuff goes into /usr, which tends to be the one that fills up. My use of tmpfs for /tmp is not considered standard behavior but I reboot this laptop often.
 
Old 01-24-2014, 11:56 PM   #10
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
i resized the /usr partition, everything seems to be well with the installation but while booting another message appeared

See link below
http://postimg.org/image/o7ggy2zij/
 
Old 01-25-2014, 03:49 AM   #11
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Please boot your install-CD and post the ouput of
Code:
fdisk -l
and then mount your /
Code:
mkdir /mnt/tmp/
mount /dev/rootpartition /mnt/tmp
where rootpartition is the device where your / resides. Then postthe output of
Code:
cat /mnt/tmp/etc/fstab
Furthermore I'd like to see the output of
Code:
ls -lh /mnt/tmp/boot
And please don't put your screenshots on external sites, LQ allows for upload of images, when you're writing your post look below at "Manage Attachments"

Markus
 
Old 01-25-2014, 06:55 AM   #12
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
The OP will have to run
Code:
/sbin/vgchange -ay --ignorelockingfailure
prior to attempting to mount the root directory.

I would also like to know the mkinitrd command used to create the initrd.
 
Old 01-25-2014, 01:02 PM   #13
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
mkinitrd command:
chroot
$( /usr/share/mkinitrd/mkinitrd_command_generator.sh -r )

Changed lilo.conf

Code:
image = /boot/vmlinuz-generic-smp-3.2.29-smp
initrd = /boot/initrd.gz
root = /dev/lvfelix/root
label = Linux
read-only
i reinstalled again, but i have not reboot yet(im not sure how to boot from cd with vmware, thats why i reinstalled.)

(pictures shows fdisk -l and df -h)
Attached Images
File Type: png cap1.PNG (11.8 KB, 9 views)
File Type: png cap2.PNG (20.1 KB, 10 views)
File Type: png cap3.PNG (21.6 KB, 8 views)

Last edited by fjur94; 01-25-2014 at 01:03 PM.
 
Old 01-25-2014, 01:29 PM   #14
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
markush /mnt/tmp already exist

note: Have not rebooted yet, the system will be damaged again if i start it :s

picture shows (ls -lh /mnt/tmp/boot) and (cat /mnt/tmp/etc/fstab)
Attached Images
File Type: png cap6.PNG (15.5 KB, 6 views)

Last edited by fjur94; 01-25-2014 at 01:37 PM.
 
Old 01-25-2014, 01:31 PM   #15
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Don't forget to run lilo again after creating a new initrd!

I use to have a "failsafe" option in my lilo.conf which means that I have also the huge-kernel available. This helps when there is something wrong with the initrd or the modules. Here the lines of my lilo.conf
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
  initrd = /boot/initrd.gz
  append = "resume=/dev/sda9"
  root = /dev/sda5
  label = Slack64-current
  read-only
###
image = /boot/vmlinuz-huge-3.10.17
  append = "resume=/dev/sda9"
  root = /dev/sda5
  label = failsafe
  read-only
# Linux bootable partition config ends
I can't help with lmv. But I would recommend to boot the huge kernel in order to find out if the problem is related to initrd or lvm.

Markus
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0) fjur94 Slackware 1 01-22-2014 06:05 PM
kernel panic - not syncing:vfs:unable to mount root fs on unknown-block (8.2) raleeha VectorLinux 6 04-21-2011 02:48 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) anjanesh Ubuntu 9 01-27-2011 12:00 PM
kernel panic - not syncing: VFS unable to mount root fs on unknown-block(8,3) AllShk Linux - Newbie 3 11-28-2009 12:56 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block akaUr Linux - Kernel 10 06-18-2009 06:59 AM


All times are GMT -5. The time now is 07:28 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration