NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
VFS: Unable to mount root fs on unknown-block(104,7)hi. My friend try to install etch but installer is not opening. He's get -- |
VFS: Unable to mount root fs on unknown-block(104,7)
On Sun, Feb 04, 2007 at 03:29:07AM +0200, Onur Aslan wrote:
> hi. My friend try to install etch but installer is not opening. He's get
> this error message: http://img220.imageshack.us/img220/7485/isopa8.png .
> He tried root=/dev/sdb1 etc. Its'nt worked. Do you any have idea?
based on the messages *before* it can't find root, the initrd image is
not correct. You need to boot a rescue cd, chroot into the system and
rebuild the initrd.
hth
A
VFS: Unable to mount root fs on unknown-block(104,7)
Thanks for help. The downloaded disc image md5 does not match source
disc image md5. He is downloading again.
--
VFS: Unable to mount root fs on unknown-block(104,7)
--- Onur Aslan wrote:
> hi. My friend try to install etch but installer is not opening.
> He's get
> this error message:
> http://img220.imageshack.us/img220/7485/isopa8.png .
Some debian-user recipient access this mailing list on the
command-line and pictures don't help much. Besides, they don't get
indexed by Google and that may prevent other users to benefit from
your post. Please post the error message in plain text and I could
try to help you.
--
Ottavio Caruso
I will not purchase any computing equipment from manufacturers that recommend Windows Vista or any other Microsoft® products.
http://www.pledgebank.com/boycottvista
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
--
VFS: Unable to mount root fs on unknown-block(104,7)
--- Onur Aslan wrote:
>> hi. My friend try to install etch but installer is not opening.
>> He's get
>> this error message:
>> http://img220.imageshack.us/img220/7485/isopa8.png .
>>
>>
I got this same message when I recompiled my first kernel, the cause is
your filesystem requires and initrd RAM disk. From a LiveCD you can try
mounting and chrooting into your friend's computer, then:
/# cd /boot
# uname -r
# ls -la
/(At this point look for something like initrd.img-kernelversion,
replacing kernelversion with the output of /uname -r/)
/# mkinitrd -o /boot/initrd-kernelversion kernelversion
# vim grub/menu.lst
/
You'll have to add the initrd line to your kernel list at the bottom of
the file. Mine, for example, looks like this:
/
title Debian GNU/Linux, kernel 2.6.15-1-486 (on /dev/hda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-1-486 root=/dev/hda1 ro
*initrd /boot/initrd.img-2.6.15-1-486 *
savedefault
boot
/Add the initrd line to both your normal kernel and recovery kernel,
unmount your friend's filesystem and hope that it works.
--