Le vendredi 15 mai 2009 à 14:13 +0200, Thomas Lange a écrit :
> >>>>> On Fri, 15 May 2009 13:48:17 +0200, Alexander Bugl 
> >>>>> <[email protected]> said:
> 
>     > Hi!
>     >> > So disk-info tests if the group of /dev/sda is disk -- and in my 
> case it is:
>     >> > # ls -al /dev/sda
>     >> > brw-rw---- 1 root floppy 8, 0 May 15 10:36 /dev/sda
>     > dmesg.log:     http://paste.debian.net/36208/
> Your dmesg looks fine. One disk, called sda. So it's not the kernel.
> What does cat /proc/partitions say?
> 
> P.S.: If you join the #fai channel on irc.debian.org help will be much
> quicker than via email.
> 

Hi,

I get the same problem here on an IBM 3950, my sda device belongs to
group floppy.
I use a Lenny nfsroot.

there is something about that in the udev rules : (91-permissions.rules)
# default permissions for block devices
SUBSYSTEM=="block",                             GROUP="disk"
# the aacraid driver is broken and reports that disks removable (see
#404927)
SUBSYSTEM=="block", ATTRS{removable}=="1", \
        DRIVERS!="aacraid",                     GROUP="floppy"

but I doesn't seems to work well...

# udevinfo -a -p `udevinfo -q path -n /dev/sda` |less

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/block/sda':
    KERNEL=="sda"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{range}=="16"
    ATTR{removable}=="1"
    ATTR{size}=="715776000"
    ATTR{capability}=="13"
    ATTR{stat}=="   18411     8485    38139     8224     8355   468795
2432659   946228        0    13240   954448"

  looking at parent device
'/devices/pci0000:01/0000:01:02.0/host0/target0:0:0/0:0:0:0':
    KERNELS=="0:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
ACTION!="add|change", GOTO="permissions_end"

    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
    ATTRS{type}=="0"
    ATTRS{scsi_level}=="3"
    ATTRS{vendor}=="IBM     "
    ATTRS{model}=="A               "
    ATTRS{rev}=="V1.0"
    ATTRS{state}=="running"
    ATTRS{timeout}=="45"
    ATTRS{iocounterbits}=="32"
    ATTRS{iorequest_cnt}=="0x6b48"
    ATTRS{iodone_cnt}=="0x6b48"
    ATTRS{ioerr_cnt}=="0x1"
    ATTRS{modalias}=="scsi:t-0x00"
    ATTRS{evt_media_change}=="0"
    ATTRS{queue_depth}=="256"
    ATTRS{queue_type}=="ordered"
    ATTRS{level}=="RAID5"

  looking at parent device
'/devices/pci0000:01/0000:01:02.0/host0/target0:0:0':
    KERNELS=="target0:0:0"
    SUBSYSTEMS==""
    DRIVERS==""

  looking at parent device '/devices/pci0000:01/0000:01:02.0/host0':
    KERNELS=="host0"
    SUBSYSTEMS==""
    DRIVERS==""

  looking at parent device '/devices/pci0000:01/0000:01:02.0':
    KERNELS=="0000:01:02.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="aacraid"
    ATTRS{vendor}=="0x9005"
    ATTRS{device}=="0x0285"
    ATTRS{subsystem_vendor}=="0x1014"
    ATTRS{subsystem_device}=="0x02f2"
    ATTRS{class}=="0x010400"
    ATTRS{irq}=="28"
    ATTRS{local_cpus}=="0000ffff"
    ATTRS{local_cpulist}=="0-15"

ATTRS{modalias}=="pci:v00009005d00000285sv00001014sd000002F2bc01sc04i00"
    ATTRS{numa_node}=="0"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:01':
    KERNELS=="pci0000:01"
    SUBSYSTEMS==""
    DRIVERS==""



My workaround for now is to accept devices recognised as "floppy"...
/srv/fai/nfsroot/lenny-i386/live/filesystem.dir/usr/lib/fai/disk-info

[ `stat -c %G /dev/$device` = "disk" ] || [ `stat -c %G /dev/$device` =
"floppy" ] || isdisk=0

It's not the best way, but it do the trick...

-- 
Mathieu Alorent
Shell&Core Sophia-Antipolis
AUSY
Pour France Telecom – OPF/PORTAILS/DOP/HEBEX/SOPHIA

Tél: 04 97 12 6226

[email protected]

La signature de ce mail peut être vérifiée en installant les autorités de 
certifications CAcert suivantes :
http://www.cacert.org/certs/root.crt
http://www.cacert.org/certs/class3.crt

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Antwort per Email an