[EMAIL PROTECTED](Eric Delaunay) 12.09.07 19:51
>Rainer Zocholl wrote:
>> Package: scsitools
>> Version: 0.9-1.1
>>
>> After upgrading to the current stable version, scsiinfo seems to
>> become unable to read *any* scsi pages (see below).
>> Previous version works used in a cronjob to check for grown defects
>> (which is now broken and litters the logfile).
>>
>> How can i make scsitool run again?
>> What will happen if the box is rebooted?
>> The kernel is monolytic, no loadable modules are supported by
>> intension.
>>
>> After some investigation in READ.Debian and the (new) init scripts:
>> It would have been nice apt giving a warning that updating
>> scsitools requires a reboot(, a kernel with devfs?) and
>> editing of /etc/fstab. (I could have pinned them to the old version,
>> as there is only one user on the box, root)
>>
>> Maybe "scsiinfo -l" could issue a warning or use /dev/scsi too
>> or list both raw and scsi devices?
>Hello Rainer,
> scsiinfo is not designed to deal with /dev/scsi/ devices,
That'S ok. i don't have "/dev/scsi"
>only /dev/sd*.
That does not work anymore.
It simply find no scsi devices anymore!
(But the box is running happily using "/dev/sd" ;-)
I have a cronjob running dumping grown defects table.
(The ssystem is quite old).
Afte update that script is complaining.
Maybe an ls /dev/sd* would be helpfull?
>But I don't know why after your upgrade you
>lost /dev/sd* access. Could you give me more details?
What more details? I thought i'd sent all i can get.
>Maybe a bug in scsitools. I will try to look at it as soon as
>I reach my computer at home (i.e. next week).
>> What will happen to the "needscsidev" tests
>> if /etc/ftab uses "LABEL=" to name the partition (very likely to
>> find to avoid the scsi-ID problem)?
>>
>> A more comprehensive error meassage like "no /dev/scsi/... found,
>> pls reboot" would be nice too ;-)
>/dev/scsi is only filled up at boot time by scsidev if
>/etc/scsi.alias is configured. It is an alternative to labels
>to get around scsi-ID allocation troubles.
Yes.
>Either use one or
>the other, not both.
>Nevertheless, scsiinfo should still work
>with no or empty /dev/scsi.
Not on that box.
I not yet rebootet that server.
>Btw, scsidev still work with 2.6 kernels without devfs support
>(it uses sysfs when available).
That's an old 2.4!
Rainer---<=====> Vertraulich
//
//
<=====>--------------ocholl, Kiel, Germany ------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
