VectorLinux This forum is for the discussion of VectorLinux.
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
04-20-2011, 01:13 AM
#1
Member
Registered: Jan 2011
Location: Berlin
Distribution: Manjaro
Posts: 43
Rep:
kernel panic - not syncing:vfs:unable to mount root fs on unknown-block (8.2)
Hello,
i have installed vl 6.0 standard on first hd and a newly i installed vl 7.0 on second hd..when i try to start first hd i get error message above..but when i start second hd and runs without problems..
does anyone knows about this error message?
many thanks for your posts..
greetings
04-20-2011, 02:46 AM
#2
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,410
This is during boot up:
It has grabbed the kernel, and initrd if you specified one. Next thing it does is mount / ro - all before init is started.
It can't find /. Causes: Wrong drive specified, pathname error, unable to read filesystem, i/o error, that sort of thing
04-20-2011, 07:54 AM
#3
Member
Registered: Jan 2011
Location: Berlin
Distribution: Manjaro
Posts: 43
Original Poster
Rep:
maybe this caused by diffrent names.../dev/hda2 (VL6.0).../dev/sda2 (VL7.0)...tried to change lilo.conf but there are no results
04-20-2011, 11:35 AM
#4
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,410
Double check that your kernel can read trhe root filesystem. It has to be compiled in, or in an initrd. A module isn't enough; it lands you in catch-22 - you need the module to read the filesystem the module is on.
Then you have the root drive specified wrong. root=/dev/??? on the boot line. Modern kernels should have /dev/sda, etc.
04-20-2011, 01:18 PM
#5
Member
Registered: Jan 2011
Location: Berlin
Distribution: Manjaro
Posts: 43
Original Poster
Rep:
vl 6.0 uses kernel 2.6.27.12 and vl 7.0 kernel 2.6.38
wonder why the /proc dir is empty
Quote:
vector://media/a3031b5a-505c-11e0-97e7-8fb77fed5d3c/proc
root:# ls -lh
total 0
Quote:
vector://proc
root:# ls -lh
total 0
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 10/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1001/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1059/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1065/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1116/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1223/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1224/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1235/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1236/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1316/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1351/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1874/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 1877/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2/
dr-xr-xr-x 7 messagebus messagebus 0 Apr 20 20:09 2074/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2101/
dr-xr-xr-x 7 root root 0 Apr 20 20:08 2182/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2198/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2201/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 23/
dr-xr-xr-x 7 avahi avahi 0 Apr 20 20:09 2348/
dr-xr-xr-x 7 avahi avahi 0 Apr 20 20:09 2349/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2379/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2406/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2408/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2485/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2493/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2497/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2499/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2517/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2518/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2520/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2521/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2522/
dr-xr-xr-x 7 root gdm 0 Apr 20 20:09 2563/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2565/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2592/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2602/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2651/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2652/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2654/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2662/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2667/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2669/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2674/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2676/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 2678/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 2680/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2684/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2686/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 2696/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2697/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2699/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2701/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2704/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2707/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2710/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2719/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 2723/
dr-xr-xr-x 7 root root 0 Apr 20 18:23 2728/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2729/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2732/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2776/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2778/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2779/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 2784/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 2797/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2799/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2808/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2816/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 2838/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2906/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 2923/
dr-xr-xr-x 7 nobody nogroup 0 Apr 20 20:09 2926/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 3/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 398/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 400/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 402/
dr-xr-xr-x 7 test test 0 Apr 20 20:00 4039/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 4081/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 4091/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 410/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 4128/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 4142/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 4150/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 4158/
dr-xr-xr-x 7 test test 0 Apr 20 20:08 4161/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 418/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 4180/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 4186/
dr-xr-xr-x 7 test utmp 0 Apr 20 20:09 4188/
dr-xr-xr-x 7 test test 0 Apr 20 20:09 4189/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 4205/
dr-xr-xr-x 7 root root 0 Apr 20 20:12 4227/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 423/
dr-xr-xr-x 7 test test 0 Apr 20 20:12 4265/
dr-xr-xr-x 7 root root 0 Apr 20 20:12 4279/
dr-xr-xr-x 7 root root 0 Apr 20 20:18 4320/
dr-xr-xr-x 7 root root 0 Apr 20 20:18 4372/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 523/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 542/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 548/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 549/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 6/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 619/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 621/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 644/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 656/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 657/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 658/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 664/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 665/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 666/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 667/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 670/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 671/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 674/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 680/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 681/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 686/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 688/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 7/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 8/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 875/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 880/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 894/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 9/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 901/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 902/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 903/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 906/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 994/
dr-xr-xr-x 7 root root 0 Apr 20 20:09 997/
-r--r--r-- 1 root root 0 Apr 20 20:18 apm
dr-xr-xr-x 5 root root 0 Apr 20 20:18 asound/
-r--r--r-- 1 root root 0 Apr 20 20:18 buddyinfo
dr-xr-xr-x 6 root root 0 Apr 20 18:21 bus/
-r--r--r-- 1 root root 0 Apr 20 20:18 cgroups
-r--r--r-- 1 root root 0 Apr 20 20:18 cmdline
-r--r--r-- 1 root root 30K Apr 20 20:18 config.gz
-r--r--r-- 1 root root 0 Apr 20 20:18 consoles
-r--r--r-- 1 root root 0 Apr 20 20:18 cpuinfo
-r--r--r-- 1 root root 0 Apr 20 20:18 crypto
-r--r--r-- 1 root root 0 Apr 20 20:18 devices
-r--r--r-- 1 root root 0 Apr 20 20:18 diskstats
-r--r--r-- 1 root root 0 Apr 20 20:18 dma
dr-xr-xr-x 2 root root 0 Apr 20 20:18 driver/
-r--r--r-- 1 root root 0 Apr 20 20:18 execdomains
-r--r--r-- 1 root root 0 Apr 20 20:18 fb
-r--r--r-- 1 root root 0 Apr 20 20:18 filesystems
dr-xr-xr-x 8 root root 0 Apr 20 20:18 fs/
dr-xr-xr-x 2 root root 0 Apr 20 20:18 i2o/
-r--r--r-- 1 root root 0 Apr 20 18:23 interrupts
-r--r--r-- 1 root root 0 Apr 20 20:18 iomem
-r--r--r-- 1 root root 0 Apr 20 20:18 ioports
dr-xr-xr-x 18 root root 0 Apr 20 20:18 irq/
-r--r--r-- 1 root root 0 Apr 20 20:18 kallsyms
-r-------- 1 root root 1016M Apr 20 20:18 kcore
-r--r--r-- 1 root root 0 Apr 20 20:18 key-users
-r--r--r-- 1 root root 0 Apr 20 20:18 keys
-r-------- 1 root root 0 Apr 20 18:22 kmsg
-r-------- 1 root root 0 Apr 20 20:18 kpagecount
-r-------- 1 root root 0 Apr 20 20:18 kpageflags
-r--r--r-- 1 root root 0 Apr 20 20:18 loadavg
-r--r--r-- 1 root root 0 Apr 20 20:18 locks
-r--r--r-- 1 root root 0 Apr 20 18:23 mdstat
dr-xr-xr-x 2 root root 0 Apr 20 20:18 megaraid/
-r--r--r-- 1 root root 0 Apr 20 20:18 meminfo
-r--r--r-- 1 root root 0 Apr 20 20:18 misc
-r--r--r-- 1 root root 0 Apr 20 20:18 modules
lrwxrwxrwx 1 root root 11 Apr 20 20:18 mounts -> self/mounts
dr-xr-xr-x 2 root root 0 Apr 20 20:18 mpt/
-rw-r--r-- 1 root root 0 Apr 20 18:22 mtrr
lrwxrwxrwx 1 root root 8 Apr 20 20:18 net -> self/net/
-r--r--r-- 1 root root 0 Apr 20 20:18 pagetypeinfo
-r--r--r-- 1 root root 0 Apr 20 20:18 partitions
-r--r--r-- 1 root root 0 Apr 20 20:18 sched_debug
dr-xr-xr-x 4 root root 0 Apr 20 20:18 scsi/
lrwxrwxrwx 1 root root 64 Apr 20 18:29 self -> 4372/
-r--r--r-- 1 root root 0 Apr 20 20:18 slabinfo
-r--r--r-- 1 root root 0 Apr 20 20:18 softirqs
-r--r--r-- 1 root root 0 Apr 20 20:18 splash
-r--r--r-- 1 root root 0 Apr 20 20:18 stat
-r--r--r-- 1 root root 0 Apr 20 20:18 swaps
dr-xr-xr-x 1 root root 0 Apr 20 20:09 sys/
--w------- 1 root root 0 Apr 20 20:18 sysrq-trigger
dr-xr-xr-x 2 root root 0 Apr 20 20:18 sysvipc/
-r--r--r-- 1 root root 0 Apr 20 20:18 timer_list
-rw-r--r-- 1 root root 0 Apr 20 20:18 timer_stats
dr-xr-xr-x 4 root root 0 Apr 20 20:18 tty/
-r--r--r-- 1 root root 0 Apr 20 20:18 uptime
-r--r--r-- 1 root root 0 Apr 20 20:18 version
-r-------- 1 root root 0 Apr 20 20:18 vmallocinfo
-r--r--r-- 1 root root 0 Apr 20 20:18 vmstat
-r--r--r-- 1 root root 0 Apr 20 20:18 zoneinfo
Last edited by raleeha; 04-20-2011 at 01:28 PM .
04-21-2011, 02:02 AM
#6
Member
Registered: Jan 2011
Location: Berlin
Distribution: Manjaro
Posts: 43
Original Poster
Rep:
the problem bootloader lilo uses *h*da in vl 6.0 and *s*da in vl7.0...so probably i need to change the lilo.conf file on vl 7.0 with the content of lilo.conf vl 6.0..but i dont know if vl 7.0 already will work then
04-21-2011, 02:48 AM
#7
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,410
Quote:
Originally Posted by
raleeha
vl 6.0 uses kernel 2.6.27.12 and vl 7.0 kernel 2.6.38
wonder why the /proc dir is empty
Because it's a backdoor to ram.
All times are GMT -5. The time now is 09:30 AM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News