On Jan 25, Kay Sievers wrote: > Sure, vol_id does look at the raid signature and ignores it, that's the > reason your raid did not show up in the past. Does the degration of the > device means that the raid signature is no longer valid? Yes. Indeed, vol_id gets EIO when trying to read the superblock. I think that in this case it should report the error and exit, because as I showed if the partition really is an array member then it will report wrong information which if used will cause data loss. vol_id[8597]: main: BLKGETSIZE64=1999839744 vol_id[8597]: volume_id_probe_linux_raid: probing at offset 0x0, size 0x77332200 vol_id[8597]: volume_id_get_buffer: get buffer off 0x77320000(1999765504), len 0x800 vol_id[8597]: volume_id_get_buffer: read seekbuf off:0x77320000 len:0x800 vol_id[8597]: volume_id_get_buffer: read failed (Input/output error) vol_id[8597]: volume_id_probe_intel_software_raid: probing at offset 0x0, size 0x77332200 vol_id[8597]: volume_id_get_buffer: get buffer off 0x77331e00(1999838720), len 0x200 vol_id[8597]: volume_id_get_buffer: read seekbuf off:0x77331e00 len:0x200 vol_id[8597]: volume_id_get_buffer: got 0x200 (512) bytes [...] -- ciao, Marco