Prev: Request for Recommendations - USB2 External Drive Enclosure
Next: Seriously, thinking of dual booting 7 and Linux. How long to set up? hint: 'about two weeks'
From: Jerry Peters on 12 Apr 2010 16:07
Lusotec <nomail(a)nomail.not> wrote:
> terryc wrote:
>> Lusotec wrote:
>>> terryc wrote:
>>>> Under the old linux, after you had unloaded the scsi card driver,
>>>> connected and powered up the hard disk array/whatever, then reloaded
>>>> the modules for the scsi card, if devices were missing, you could then
>>>> run MAKEDEV and create them and it all worked.
>>>>
>>>> No such luck with current kernels as it is controlled by udev, so I can
>>>> not run MAKEDEV.
>>>>
>>>> what are you supposed to do under the current kernels to get udev to
>>>> see that these devices are now connected and it needs to create the
>>>> devices?
>>>
>>> Just load the kernel module for the SCSI card. The device files should
>>> be automatically created by udev.
>>
>> Unfortunately it isn't happening, which is why I am asking.
>
> Ok, something is not working then. :)
>
> I need more information to try and help you.
>
> Do the following:
>
> $ modprobe --remove SCSI_MODULE
> $ dmesg > /tmp/dmesg.before
> $ cat /proc/scsi/scsi > /tmp/scsi.before
> $ modprobe SCSI_MODULE
> $ dmesg > /tmp/dmesg.after
> $ cat /proc/scsi/scsi > /tmp/scsi.after
> $ diff /tmp/dmesg.before /tmp/dmesg.after > /tmp/dmesg.diff
> $ diff /tmp/scsi.before /tmp/scsi.after > /tmp/scsi.diff
>
> Post here the content of /tmp/dmesg.diff and /tmp/scsi.diff
>
> With these two diffs it will be possible to determine if the module is
> actually working and if it finds any drives.
>
> Replace SCSI_MODULE with the name of the kernel SCSI module for your SCSI
> card.
>
> Regards.
>
Right after: modprobe --remove SCSI_MODULE
as root, in a terminal window do: udevadm --monitor
This will show you what events udevd is getting and how it's
processing them. See man udevadm for more details.

Jerry
From: terryc on 18 Apr 2010 13:30
On Sun, 11 Apr 2010 14:04:29 +0000, terryc wrote:


> what are you supposed to do under the current kernels to get udev to see
> that these devices are now connected and it needs to create the devices?

Er, thanks for the reply. The problem turned out to be a NBK (nut behind
the keyboard ) problem. the drives were in an external tower and I think
I failed to give enough time for the drives to spin up(or something)
after power on, before the module was loaded.


From: Wolfgang Draxinger on 19 Apr 2010 04:31
terryc wrote:

> Unfortunately it isn't happening, which is why I am asking.

Maybe the devices aren't properly enumerated. Try rescan-scsi-bus.sh (if
that doesn't come with your distribution, Google for it). If device nodes
still don't appear, trigger udev:

udevadm trigger && udevadm settle


Wolfgang

First  |  Prev  | 
Pages: 1 2
Prev: Request for Recommendations - USB2 External Drive Enclosure
Next: Seriously, thinking of dual booting 7 and Linux. How long to set up? hint: 'about two weeks'