Solaris 9 cdrom issues
2007-12-24 23:06:00
I 've rebooted again since then. Made sure vold was running and issued a
volcheck command. nothing. I've scanned through my messages file and did
notice this. Does this mean anything to anybody?
Jul 2 09:59:28 hsdird01 glm: [ID 923092 kern.warning] WARNING:
ID[SUNWpd.glm.sync_wide_backoff.6014]
Jul 2 09:59:28 hsdird01 scsi: [ID 107833 kern.warning] WARNING:
/pci at 4,4000/scsi at 6 (glm0):
Jul 2 09:59:28 hsdird01 got SCSI bus reset
Jul 2 09:59:28 hsdird01 genunix: [ID 408822 kern.info] NOTICE: glm0: fault
detected in device; service still available
Jul 2 09:59:28 hsdird01 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI
bus reset
Jul 2 09:59:28 hsdird01 scsi: [ID 107833 kern.warning] WARNING:
/pci at 4,4000/scsi at 6/sd at 0,0 (sd0):
Jul 2 09:59:28 hsdird01 SCSI transport failed: reason 'reset':
retrying command
Jul 2 09:59:28 hsdird01 scsi: [ID 107833 kern.warning] WARNING:
/pci at 4,4000/scsi at 6/sd at 0,0 (sd0):
Jul 2 09:59:28 hsdird01 SCSI transport failed: reason 'timeout':
retrying command
Jul 2 12:46:12 hsdird01 automountd[886]: [ID 367356 daemon.error]
svc_tli_create: could not bind to requested address: ad
dress mismatch
Jul 2 12:46:12 hsdird01 automountd[886]: [ID 436217 daemon.error] svc_create:
svc_tli_create failed
Jul 2 12:46:12 hsdird01 automountd[886]: [ID 668993 daemon.error] unable to
create service
Jul 2 13:03:02 hsdird01 pseudo: [ID 129642 kern.info] pseudo-device: tod0
On Tuesday 02 July 2002 13:29, you wrote:
> If you installed using the install disk (not disk 1) as the boot disk and
> you are talking about this machine having a CDROM automount issue after the
> _first_ reboot after install, you are seeing this issue because vold does
> not load on the _first_ reboot after the initial install as the installer
> runs a final time for add on product installs (and the installer wants full
> control of the cdrom). Try rebooting one more time to get a full system
> startup =)
>
> -Wade Stuart
>
> <orig>
> Sungurus,
>
> Has anyone experienced any issues/troubles with the cdrom device after the
> solaris 9 install? We have two machines (e220r and blade 100) that have the
> same issues after upgrading/installing solaris 9. After the install and
> first
> reboot automount doesn't see the cdrom device and it seems that the cdrom
> isn't recognized anymore by the operating system. I recall that there was
> an
> alias in solaris 8 /vol/dev/aliases/cdrom (not sure) that would point to
> the
> cdrom. Is this not the case for solaris 9?
>
> Any help or suggestions would be greatly appreciated.
>
> Many thanks in advance,
>
> -Charles Funderburk
Comments
Got something to say?
You must be logged in to post a comment.
