udev not creating /dev/sda

[sglow]

For several months now I've been using the 2.6 kernel series and udev with great success. I'm not using the tar file to populate my /dev directory, I'm using udev to create all the files on startup. Everything is working great.

I just added a couple SATA disks to my system (I boot off an older parallel ATA drive). These drives are using the libata drivers and therefore show up as a scsi drives. When I first added the drives I compiled the drivers as modules and udev created my /dev/sda, /dev/sdb devices correctly on boot up. I then added the drivers into the kernel (no longer modules) and udev will no longer create my device files for me.

The devices are definately loading correctly, and I can see entries in /sys/class/scsi_host/ and /sys/class/scsi_device/ for them. I don't however get anything under /sys/block.

I have found however that if I manually create a device file for one of the disks and access it, udev suddenly kicks in and creates the device files. For example, if I execute these commands:

mknod /dev/sda b 8 0
fdisk /dev/sda

Then suddenly I have /sys/block/sda and /sys/block/sdb and udev creates /dev/sdb for me.

Can anyone suggest what I'm missing here? There must be something I need to do on startup to kick off udev, but I can't find any reference to it in the docs.

Thanks,
Steve[/code]

[sglow]

No luck trying to figure this out myself.

Any thoughts anyone?

S