Hi listers,

I've got a problem which I can't tell, if it's hardware or OS relatet. So I 
crosspost this.

I've built a DEC3000/300 with 5 buses (base board tcds, 2 PMAZC-AA in slot 0 
and slot 1 of the tc bus).
The configuration of the SCSI buses is as follows (I don't like the dynamic 
SCSI device numbering, so I hard wired everything).

tcds0	at	tc? slot 4 offset ?
tcds1	at	tc? slot 0 offset ?
tcds2	at	tc? slot 1 offset ?
asc0	at	tcds0 chip 0
asc1	at	tcds1 chip 0
asc2	at	tcds1 chip 1
asc3	at	tcds2 chip 0
asc4	at	tcds2 chip 1

# SCSI bus support
scsibus0 at	asc0
scsibus1 at	asc1
scsibus2 at	asc2
scsibus3 at	asc3
scsibus4 at	asc4

# SCSI: disks, hardwired
sd0     at      scsibus0    target  0    lun  0
sd1     at      scsibus0    target  1    lun  0
sd2     at      scsibus0    target  2    lun  0
sd3     at      scsibus0    target  3    lun  0
sd4     at      scsibus0    target  4    lun  0
sd5     at      scsibus0    target  5    lun  0
sd6     at      scsibus0    target  6    lun  0
sd10    at      scsibus1    target  0    lun  0
sd11    at      scsibus1    target  1    lun  0
sd12    at      scsibus1    target  2    lun  0
sd13    at      scsibus1    target  3    lun  0
sd14    at      scsibus1    target  4    lun  0
sd15    at      scsibus1    target  5    lun  0
sd16    at      scsibus1    target  6    lun  0
sd20    at      scsibus2    target  0    lun  0
sd21    at      scsibus2    target  1    lun  0
sd22    at      scsibus2    target  2    lun  0
sd23    at      scsibus2    target  3    lun  0
sd24    at      scsibus2    target  4    lun  0
sd25    at      scsibus2    target  5    lun  0
sd26    at      scsibus2    target  6    lun  0
sd30    at      scsibus3    target  0    lun  0
sd31    at      scsibus3    target  1    lun  0
sd32    at      scsibus3    target  2    lun  0
sd33    at      scsibus3    target  3    lun  0
sd34    at      scsibus3    target  4    lun  0
sd35    at      scsibus3    target  5    lun  0
sd36    at      scsibus3    target  6    lun  0
sd40    at      scsibus4    target  0    lun  0
sd41    at      scsibus4    target  1    lun  0
sd42    at      scsibus4    target  2    lun  0
sd43    at      scsibus4    target  3    lun  0
sd44    at      scsibus4    target  4    lun  0
sd45    at      scsibus4    target  5    lun  0
sd46    at      scsibus4    target  6    lun  0

Due to a suspicious mains peak a SCSI disk showed some errors. I decided to 
stress the disk a bit (using dd/bonnie - only to continuously write a read 
data from the disk). But I have problems to access the disk. The disk is on 
scsibus 1, target 4 - due to the naming scheme the disk would be recognized 
as /dev/{r}sd14. The kernel is reporting this. But I can not access the 
partitions.

If I label the disk with the following label (saved to /tmp/sd14.label)
# /dev/rsd14c:
type: SCSI
disk: DDYS-T18350N
label: fictitious
flags:
bytes/sector: 512
sectors/track: 395
tracks/cylinder: 6
sectors/cylinder: 2370
cylinders: 15110
total sectors: 35843670
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0		# microseconds
track-to-track seek: 0	# microseconds
drivedata: 0 

3 partitions:
#        size    offset     fstype  [fsize bsize cpg/sgs]
 a:  35841622      2048     unused      0     0
 b:  35841622      2048     unused      0     0
 c:  35843670         0     unused      0     0

and by using the following command

disklabel -R -r /dev/rsd14c /tmp/sd14.label

I can not access /dev/rsd14b. The kernel keeps telling me: 

/dev/rsd14b: device not configured

when I try dd'ing some data to partition b:
dd if=/dev/zero bs=10k count=1 of=/dev/rsd14b

What am I doing wrong here?

Thanks for your thoughts.
-- 


Uwe Lienig
----------
fon: (+49 351) 462 2780
fax: (+49 351) 462 3476
mailto:uwe.lienig@fif.mw.htw-dresden.de

Forschungsinstitut Fahrzeugtechnik
<http://www.fif.mw.htw-dresden.de>
parcels: Gutzkowstr. 22, 01069 Dresden 
letters: PF 12 07 01,    01008 Dresden

Hochschule für Technik und Wirtschaft Dresden (FH)
Friedrich-List-Platz 1, 01069 Dresden