topic Re: installation device scan - vs - ioscan in Operating System - HP-UX

installation device scan - vs - ioscan

Kim Kendall — Sat, 14 Sep 2002 16:29:30 GMT

Rebuilding a system (L)... Before I started the install, I captured a lot of info from the machine (in case I encountered problems) including an "ioscan -fnC disk".

The ioscan showed me all the internal devices were "CLAIMED" and showed device files.

When I started the install, it scanned available devices, but it saw that there were 2 drives with a 0 (zero) size and only the other 2 drives were available to install the OS onto.

I moved the disks around and backed up the install and "rescanned" the devices. Sure enough, the problem followed the drives.

So, my question is.... What kind of scan is taking place during the install that discovered the problem -and- is it a command line scan command that I can do on other (L) systems?

Re: installation device scan - vs - ioscan

Wodisch — Sat, 14 Sep 2002 17:00:40 GMT

Hi Kim,

is it only drives or is about those drives' controller(s)?
Some controllers are not supported by the install kernels, so will only be able to see them "claimed" after having booted a kernel with the neccessary drivers linked into it!

HTH,
Wodisch

Re: installation device scan - vs - ioscan

Kim Kendall — Sat, 14 Sep 2002 17:20:23 GMT

ioscan shows all of the drives to be the same. I could have installed the OS onto a drive on either controller (as long as a good drive was on that controller... I moved disks around and saw the available devices move with the good drives, on both controllers)

I think it's a different scan that the system does before it decides which drives are available for installing an OS onto.

Re: installation device scan - vs - ioscan

Sridhar Bhaskarla — Sat, 14 Sep 2002 21:24:28 GMT

Hi,

I would do a ioscan -fnC disk followed by a diskinfo on each of the disks. Put it in a script to give you a good picture.

for i in `ioscan -fnC disk |grep "/dev/dsk" |awk '{print $2}'`
do
DISK=$i
SIZE=`diskinfo $i |grep size: |awk '{print $2}'`
echo $DISK - $SIZE
done

This may take a litte longer if you have a CD-ROM drive but will give you a good idea.

-Sri

Re: installation device scan - vs - ioscan

Kim Kendall — Mon, 16 Sep 2002 13:20:20 GMT

diskinfo must be what the install does.

So far, I've seen 2 completely seperate symptoms of a failed drive. One, where I do an ioscan and can see that is says NO_HW instead of CLAIMED.

The other way is that it says CLAIMED in the ioscan, but diskinfo shows it as a 0 (zero) size.

Time for a script. If I try the example above, it will go through all the drives I have mounted from the EMC as well... will have to fine tune it a little, but... That's what I was looking for.

Thanks!

Re: installation device scan - vs - ioscan

Ravi_8 — Mon, 16 Sep 2002 13:34:30 GMT

Hi Kim

ioscan shows CLAIMED since the drive exist at the scsi location. if you removed the drive and run ioscan, it shows NO_HW.
diskinfo shows only the information about that disk. while installing diskinfo will be used since it also gives info about it's scsi location and size

Re: installation device scan - vs - ioscan

Kim Kendall — Mon, 16 Sep 2002 13:58:17 GMT

Yeah...

I've had disks in the slot, but ioscan said NW_HW... = bad disk

I've had disks show up as CLAIMED by ioscan, but diskinfo says 0 size... = bad disk