Re: linux-2.6.x, udev and scsi hard-disk
Hi Mark,
thank you for your quick check and reply.
On Tue, 2006-11-14 at 23:58, Mark Paulus wrote:
> Thomas Walter wrote:
> > Hello,
> >
> > On Fri, 2006-11-10 at 15:57, Mark Paulus wrote:
> >> Thomas Walter wrote:
> >>> Hello All,
> >>>
> >>> is there someone who can give me a hint how to access
> >>> a scsi harddisk (several pertitions sda1, ..., sda14) via udev?
> >>>
> >>> Until now I have investigated in searching and reading some docs and
> >>> code about udev, especially the rules (persistent.rule, ...).
> >>> Comparing the code for hda drives and sda drives looks very similar.
> >>> The partions of the sda drive should be visible.
> >>>
> >>> Then I looked / grepped through the '/sys' directory which is read by
> >>> the udev tools. It seems from my point of view that the issue is
> >>> located here. There are no entries for the sda partitions similar to
> >>> the entries for a hda drive.
> >>>
> >>> Any hint to step forward is welcome.
> >>>
> >>> I also thaught to raise a bug in the Debian BTS, but how to do that from
> >>> a woody-distribution versus sarge/sid?
> >>>
> >>> Kind Regards,
> >>> Thomas
> >>>
> >>>
> >>>
> >>>
> >> One thing you might want to do is attach the output of 'lspci -v' and
> >> 'dmesg'.
> >>
> >>
> >
> > Please the attachements, both outputs compresses with 'gzip'.
> > One strange thing is, my CD/DVD drive is also attached to the same SCSI
> > controller and it works perfectly as I boot the live system from there.
> >
> > Kind Regards,
> > Thomas
> >
> >
>
> The kernel looks like it's finding your SCSI Controller(s), and it's
> finding a Hard Disk and a CD Rom on the controller. But, there seems to
> be a problem with the hard disk:
>
And exactly this is what I don't understand.
This HD was formatted and partitioned ~ 5 years ago using Debian Potato
or Woody can't remember. No related warning or error messages using
linux-2.2.x or Linux-2.4.x.
> SCSI subsystem initialized
> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 15
> PCI: setting IRQ 15 as level-triggered
> ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKB] -> GSI 15 (level,
> low) -> IRQ 15
> ahc_pci:0:13:0: Host Adapter Bios disabled. Using default SCSI device
> parameters
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
> <Adaptec 2902/04/10/15/20C/30C SCSI adapter>
> aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs
> ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKB] -> GSI 15 (level,
> low) -> IRQ 15
> scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
> <Adaptec 29160 Ultra160 SCSI adapter>
> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> Vendor: IBM Model: DDYS-T18350N Rev: S96H
> Type: Direct-Access ANSI SCSI revision: 03
> scsi1:A:0:0: Tagged Queuing enabled. Depth 8
> target1:0:0: Beginning Domain Validation
> target1:0:0: wide asynchronous
> target1:0:0: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 63)
> target1:0:0: Ending Domain Validation
>
> SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
> sda: Write Protect is off
> sda: Mode Sense: cb 00 00 08
> SCSI device sda: drive cache: write back
> SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
> sda: Write Protect is off
> sda: Mode Sense: cb 00 00 08
> SCSI device sda: drive cache: write back
> ***********************************************
> **>>>>> sda: unknown partition table <<<<<<<<**
> ***********************************************
> sd 1:0:0:0: Attached scsi disk sda
> sr0: scsi3-mmc drive: 16x/40x cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> sr 1:0:2:0: Attached scsi CD-ROM sr0
> sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
> sr 1:0:3:0: Attached scsi CD-ROM sr1
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISO 9660 Extensions: RRIP_1991A
The related part from my Woody System in use since several years
currently running linux-2.4.27:
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 2902/04/10/15/20C/30C SCSI adapter>
aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
(scsi0:A:2): 20.000MB/s transfers (20.000MHz, offset 16)
(scsi0:A:3): 20.000MB/s transfers (20.000MHz, offset 7)
Vendor: IBM Model: DDYS-T18350N Rev: S96H
Type: Direct-Access ANSI SCSI revision: 03
Vendor: PIONEER Model: DVD-ROM DVD-305 Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
Vendor: YAMAHA Model: CRW2100S Rev: 1.0H
Type: CD-ROM ANSI SCSI revision: 02
scsi0:A:0:0: Tagged Queuing enabled. Depth 8
NCR53c406a: no available ports found
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
/dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 p11 p12
p13 p14 > p3 p4
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 3, lun 0
sr0: scsi3-mmc drive: 16x/40x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
and the output of 'lspci -v' showing the part related to the scsi
controllers:
0000:00:0d.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
Subsystem: Adaptec AHA-2904/Integrated AIC-7850
Flags: bus master, medium devsel, latency 32, IRQ 15
I/O ports at e400 [disabled] [size=256]
Memory at de001000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 1
0000:00:0f.0 SCSI storage controller: Adaptec AIC-7892A U160/m (rev 02)
Subsystem: Adaptec 29160 Ultra160 SCSI Controller
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 15
BIST result: 00
I/O ports at e800 [disabled] [size=256]
Memory at de002000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Based on this comparison I thaught there must be a problem with the
sysfs and udev introduced in linux-2.6.x.
In the meantime I also searched some forums again and read somewhere
from a few users that they had to switch back to the old scsi driver to
be able to access scsi drives.
As far as I understood, somewhere between linux-2.4.x and linux-2.6.17
the scsi driver was replaced by a new one. But the old can be compiled
in using appropriate config flags when doing the kernel config.
Do you or someone else know more about this driver change?
Kind Regards,
Thomas
Reply to: