Information lacking about drive when creating volumes

[bsdimp]

The user is presented only with 'ad0' for a disk, rather than giving more details such as size, manufacturer, etc.

[bsdimp]

We provide the easy size now...

pc-bsd's pc-sysinstall greps dmesg to find manufacturer info out, but I'm not sure how reliable that is.

[axel_2078]

Having the drive's serial numbers listed (as previous releases did) is also beneficial for replacing a failed drive if you have more than one in your system. I have 4 in mine and being able to grab the serial number from the GUI in 0.7.1 saved me lots of troubleshooting time because I was able to tell right away which disk was bad.

[rsoltys]

++

[Stefanc]

Would "camcontrol identify <device>" be safe to use? It seems to provide nice intel on my disks at least.

[gcooper]

+++

camcontrol devlist would be stellar too for determining the device info.

Having this enhanced would make identifying multiple targets with ada(4) in particular more sane (because the drive locations aren't necessarily fixed) when creating a volume; it would definitely make troubleshooting easier as well.

dmesg provides annoyingly inconsistent data from camcontrol.. I would recommend using camcontrol, but there some scenarios where camcontrol may or may not provide the necessary visibility for determining which disk is which.

[gcooper]

Untake.