On Thu, Feb 24, 2005 at 12:32:59AM +0100, Mathieu Segaud wrote:
> Andrew Morton <[EMAIL PROTECTED]> disait derni??rement que :
> 
> > Helge Hafting <[EMAIL PROTECTED]> wrote:
> >>
> >> This kernel came up, but my boot script complained about no /dev/hdb3
> >>  when trying to mount /var.
> >>  (I have two IDE disks on the same cable, and an IDE cdrom on another.)
> >>  They are usually hda, hdb, and hdc.
> >> 
> >>  MAKEDEV hdq did not help.  Looking at sysfs, it turns out that
> >>  /dev/hdq1 is at major:3 minor:1025 if I interpret things right. 
> >>  (/dev/hda1 is at 3:1, which is correct.)
> >>  These numbers did not work with my mknod, it created 7:1 instead.
> >>  So I didn't get to test this mysterious device.
> >> 
> >>  But I assume this is a mistake of some sort, I haven't heard about any
> >>  change in the IDE numbering coming up?  2.6.1-rc3-mm1 works as expected.
> >> 
> >>  It may be interesting to note that my root raid-1 came up fine,
> >>  consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
> >
> > I don't know what could be causing that.  Please send .config.  If you set
> > CONFIG_BASE_FULL=n, try setting it to `y'.
> 
> I've got the same problem here on my box, udev creates hds and hdu
> entries when running 2.6.11-rc4-mm1, whereas it creates correctly hdf
> et hdh, on other kernels.

Are these misnamed and misnumbered devices mountable? If not, can you
mknod device nodes at the proper major:minor location and have them
work?

Seems ->disk_name is getting modified between ide_setup() and
add_disk() somehow, giving us:

hdb: ...
 hdq: hdq1 hdq2...

-- 
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to