Re: Cannot open root device "hda1" or unknown-block(0,0)
Francois Duranleau(xiao.bai.xiong@gmail.com) is reported to have said:
> On 8/24/07, Douglas A. Tutty <dtutty@porchlight.ca> wrote:
> > On Thu, Aug 23, 2007 at 09:49:52PM -0400, Francois Duranleau wrote:
> > >
<--<snip>-->
> > Is the disk really a PATA or is it SATA? 2.4 kernels will see them as
> > /dev/hd* whereas 2.6 kernels will see them as /dev/sd*
>
> It's an old system: AMD Athlon Thunderbird 1.1GHz with 1.25GB RAM and
> an 80GB Western Digital drive, for sur not SATA, I bought this
> computer in december 2000. The motherboard is an ABIT KT7 (no RAID,
> VIA chipsets). Right now I am not using the kernel's VIA chipset
> driver because it causes me some troubles (see
> http://lists.debian.org/debian-user/2007/08/msg00252.html and the rest
> of the thread).
I am using the same MB with less Mem but 160G HD to write this. I
would like to see the contents of the /boot dir.
The menu.lst looks ok, if you are not using an initrd image. I have
both methods in my menu.lst.
-----------
title Debian GNU/Linux, kernel 2.6.18y Default-------------- SID - HDA2
root (hd0,1)
kernel /boot/bzImage-2.6.18y root=LABEL=SID vga=792 ro
savedefault
title Debian GNU/Linux, kernel 2.6.18-3-k7 --------------- ETCH - HDB1
lock
root (hd1,0)
kernel /boot/vmlinuz-2.6.18-3-k7 root=/dev/hdb1 vga=792 ro
initrd /boot/initrd.img-2.6.18-3-k7
savedefault
---------------
I found something yesterday while working on another box that _might_ help.
In the title line had Debian GNU/Linux, kernel 2.6.18 but got an error similar
to what you are seeing. When I checked /boot I had a bzImage-2.6.18y but not a
bzImage-2.6.18. I corrected the title line in menu.lst and it then
worked, of course.
Wayne
--
Excuse me for butting in, but I'm interrupt-driven.
_______________________________________________________
Reply to: