LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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
 
LinkBack Search this Thread
Old 05-30-2004, 08:23 PM   #1
takehora
LQ Newbie
 
Registered: May 2004
Location: Tokyo, Japan
Distribution: Slackware 9.1
Posts: 2

Rep: Reputation: 0
Question VFS: Cannot open root device "1601" or unknown-block(22,1)


I downloaded kernel 2.6.6 source, patched 2.6.7-pre2 and compiled as below.

# make
# cp /usr/src/linux-2.6.6/arch/i386/boot/bzImage /boot/vmlinuz-2.6.6
# cp /usr/src/linux-2.6.6/System.map /boot
# make modules_install

After installation kernel image to /boot, I edit /etc/lilo.conf as below and issued command "lilo".

LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdc
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.6
root = /dev/hdc1
label = Linux
read-only

image = /boot/vmlinuz-xfs-2.4.26
root = /dev/hdc1
label = Linux2.4.26
read-only
# Linux bootable partition config ends

After reboot my machine, and select 2.6.7-pre kernel at select screen, my machine indicates

VFS: Cannot open root device "1601" or unknown-block(22,1)

and kernel paniced.

If I try to use 2.4.26 kernel image, it boot up normally.

I upgraded all packages in my machine from slackware-current.
Also, I already try to use /testing/packages/linux-2.6.6/kernel-generic-2.6.6-i486-1 and kernel-modules-2.6.6-i486-1, but same error message occurred.

I use Serial-ATA HDD in my machine, and devide 3 partions as below.

Disk /dev/hdc: 164.6 GB, 164696555520 bytes
255 heads, 63 sectors/track, 20023 cylinders
Units = cylinder of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 9726 78124063+ 83 Linux
/dev/hdc2 9727 19999 82517872+ 83 Linux
/dev/hdc3 20000 20023 192780 82 Linux Swap

hdc1 and hdc2 formatted as XFS.
/dev/hdc1 is /, /dev/hdc2 is /home.

I made XFS driver as included in the kernel, not modules.
Of course, I also made Serial-ATA driver in the kernel, not modules.

My machine's spec is
CPU: Pentium4
M/B: MSI 865PE2 NEO2
Chipset: Intel 865PE
Memory: 1GB

I appreciate any suggestions and comments.
 
Old 06-09-2004, 09:21 AM   #2
Astro
Member
 
Registered: Jan 2003
Location: Ballston Lake, NY
Distribution: Slackware, Debian
Posts: 660

Rep: Reputation: 30
I thought I answered this thread? hmmmm I wanna say I replied with asking if you had all your proper filesystems compiled into the kernel. A kernel may not have the right ones by default.
 
Old 06-11-2004, 08:16 PM   #3
takehora
LQ Newbie
 
Registered: May 2004
Location: Tokyo, Japan
Distribution: Slackware 9.1
Posts: 2

Original Poster
Rep: Reputation: 0
XFS module built in the kernel, but...

didn't work.
 
Old 06-11-2004, 08:34 PM   #4
Astro
Member
 
Registered: Jan 2003
Location: Ballston Lake, NY
Distribution: Slackware, Debian
Posts: 660

Rep: Reputation: 30
Try making it a module, just in case it wants to be picky.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
VFS: Cannot open root device "cobd1" or unknown-block(117,1) lorenzobalan Linux - General 4 12-12-2007 06:19 PM
FC2; VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) Starchild Fedora 11 01-18-2006 03:39 AM
VFS: Cannot Open Root Device "Label=/" abefroman Red Hat 4 05-03-2005 09:03 AM
New kernel - VFS: Cannot open root device "301" or unknown block(3,1) j0y Debian 2 04-30-2005 09:14 PM
Kernel Panic:VFS: Cannot open root device "hda3" or 00:10 shivendnrab Linux - General 1 07-01-2004 03:08 AM


All times are GMT -5. The time now is 05:02 AM.

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