Ubuntu
hw-detect package

virtio block devices are detected as SATA RAID devices

Bug #286538 reported by Mathias Gug on 2008-10-20

Affects		Status	Importance	Assigned to	Milestone
	dmraid (Ubuntu)	Fix Released	Medium	Luke Yelavich
	hw-detect (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: hw-detect

If a KVM is guest is started with virtio block devices the installer detects Serial ATA Raid devices. Booting the guest with the *same* files but using ide block devices doesn't show this message.

The output of the command "dmraid -c -s" run in the guest during installation is different:

For a guest with a virtio block device:

# dmraid -c -s
no block devices found

For a guest with an ide block device:

# dmraid -c -s
no RAID disks

Related branches

lp:ubuntu/lucid/dmraid

Revision history for this message

Colin Watson (cjwatson) wrote on 2008-10-20:

dmraid's lib/device/scan.c needs a simple update, attached.

hw-detect could perhaps do with not matching human-readable output from dmraid ...

Changed in dmraid:
assignee:	nobody → themuso
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Colin Watson (cjwatson) wrote on 2008-10-20:

dmraid.286538.patch Edit (460 bytes, text/plain)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-10-21:

This bug was fixed in the package dmraid - 1.0.0.rc14-2ubuntu11

---------------
dmraid (1.0.0.rc14-2ubuntu11) intrepid; urgency=low

  * debian/patches/12_support_virtio_devices.dpatch: Check virtio
    devices for dmraid metadata, patch thanks to Colin Watson
    <email address hidden>. (LP: #286538)

-- Luke Yelavich <email address hidden> Tue, 21 Oct 2008 10:05:02 +1100

Changed in dmraid:
status:	Triaged → Fix Released

Revision history for this message

Phillip Susi (psusi) wrote on 2008-10-22:

It seems to me that this patch misses the real issue. The problem was that dmraid found no disks to scan, and this caused it to print a different message than when it scans disks and does not find any raid sets. The problem then, is with hw-detect, since it still should not report that raid devices are found when there are no ide OR virtual disks.

Revision history for this message

Colin Watson (cjwatson) wrote on 2008-11-20:

Phillip, was this based on actual experience or are you guessing from reading the code? disk-detect won't get to that code if there are no disks at all, so this shouldn't be relevant ...

Revision history for this message

Phillip Susi (psusi) wrote on 2008-11-20:

So you are saying that if there are no physical OR virtual disks, then hwdetect won't call dmraid at all, so the fact that it would misunderstand dmraid's output doesn't matter? Then I guess it's ok, even though hw-detect still should not react like that if it ever DOES call dmraid with no devices which dmraid is willing to scan.

Revision history for this message

Phillip Susi (psusi) wrote on 2010-06-18:

Closing the hw-detect task since it sounds like it did not have a problem, and dmraid was fixed.