Problem umounting disk one in 11i installation

[Sandy Paton]

Hello hp folk,
Sure I'm just being dense again, but I'm having problems installing 11i on an A-class due to the a umount error which occurs at the end of the first stage of the installation (OS build is March 2003 and comes on two disks).
Once all of disk one has been processed it issues a umount command which fails:
umount: cannot unmount /tmp/ign_configure/SD_CDROM : Device busy
The installation then prompts me to load disk 2 to complete installation, but I can't because disk one won't release. As a last resort I tried power cycling the cd device, which then allowed me to eject the cd, however when I try running the second disk I get:
mount: /dev/dsk/c0t1d0 is already mounted on /tmp/ign_configure_SDCDROM
get_dir_rec: bad dir entry
get_dir_rec: bad dir entry
...
Any suggestions on what I'm doing wrong?
If the problem's unavoidable is there a way I can escape to shell when I'm prompted to enter the second disk and do a manual fuser/umount? (I think the fact that this error is occuring half way through an OS install may make this impossible...)

[Sanjay_6]

hi,

Are you trying to do an upgrade or a fresh install ?

Thanks
Sanjay

[Zinky]

Simply repeat your ignite.. if it persists.. you either have a bad CDROM medium (disk 1) or a bad CDROM drive.

[Sandy Paton]

Thanks for the replies. I'm trying to do a fresh install on the box. I ran the install twice yesterday, both times it failed to umount cd 1, and I had to start again from scratch. The disk's are originals and the cd rom seems to be working normally. The only errors encountered during the first disk install were some STM messages about IO failures. These didn't look too serious though and the first 560 steps (of 650) had completed successfully.
Thinking if no one has any ideas I may try installing version 11.0 then upgrade to 11i.

[John Carr_2]

Sandy

can you post the STM errors

:-) John.

[Sandy Paton]

Short answer - no. I'm afraid I was using a web console and failed to get them down in time. They were talking about IO failure, and I'm pretty sure it was along the lines of the following:
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive errors from the I/O subsystem. I/O error entries will be lost until the cause of the excessive I/O logging is corrected.

I've seen this before on machines and believed it might have been produced here following the stm software install as part of the build. The error didn't look like one that would cause a problem with umount.

[Sandy Paton]

Sorry folk, turns out it must have been a dodgy media or version bug. I tried an earlier release of the OS (v11i September 2002) and re-ran the install and this time it unmounted without issue. Many thanks to all who responded, sorry to have taken up your time needlessly. Cheers -Sandy