TruCluster
Showing results for 
Search instead for 
Do you mean 

Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

Occasional Advisor

Problems mounting a CD-ROM under TCS V5.1B (3 nodes)


Hello,

I've reached an apparent impasse on this issue with a customer of mine, so here goes:

Problem:
---------
3-node cluster (ES40's) running Tru64 UNIX V5.1B (recently upgraded to PK#6 from PK#3)

Customer is unable to mount any CD-ROM media on any member of the cluster, but the same physical CD media mounts fine on other (i.e. standalone) Tru64 systems in their office.

NOTE: This problem existed in their PK#3 environment as well.

Mount syntax used is as follows:

#mount /dev/disk/cdrom*c /mntpnt
#mount -r /dev/disk/cdrom*c /mntpnt
#mount -r -t cdfs( or ufs) -o noversion \
/dev/disk/cdrom*c /mntpnt
#mount -r -t ufs (or cdfs) -o rrip \
/dev/disk/cdrom*c /mntpnt

Errors encountered from the above syntax are as follows:

1. "UFS filesystem not supported"
2. "CDFS filesystem not supported"
3. "No such device or address"

Analysis:
----------
1. Checked that CDFS and UFS are in /sys/conf/HOSTNAME on each member (YES).

2. Used hwmgr (del comp -id HWID, del scsi
-did SCSI_DID, scan scsi) and dsfmgr (-R hwid scsi_did, -vFV) to remove and re-add all CDROM-specific device files in /dev/disk and
/dev/rdisk, yet the problem still remains.

NOTE: I was able to to replicate and fix this problem on a 2-node DS10L (5.1B pk#6) cluster in my office using the steps above, but my customer did not have the same success.

3. A check of /dev/disk/cdrom* and
/dev/rdisk/cdrom* yields no strange output that I can see (below):

# file /dev/disk/cdrom*

/dev/disk/cdrom5a: block special (19/1689)
/dev/disk/cdrom5c: block special (19/1693)
/dev/disk/cdrom6a: block special (19/1694)
/dev/disk/cdrom6c: block special (19/1698)
/dev/disk/cdrom7a: block special (19/1710)
/dev/disk/cdrom7c: block special (19/1714)

# file /dev/rdisk/cdrom*

/dev/rdisk/cdrom5a: character special (19/1690)
/dev/rdisk/cdrom5c: character special (19/1678)
/dev/rdisk/cdrom6a: character special (19/1695)
/dev/rdisk/cdrom6c: character special (19/1699)
/dev/rdisk/cdrom7a: character special (19/1711)
/dev/rdisk/cdrom7c: character special (19/1715)

# ls -l /dev/disk/cdrom*

brw------- 1 root system 19,1689 Mar 22 08:18 /dev/disk/cdrom5a
brw------- 1 root system 19,1693 Mar 22 08:18 /dev/disk/cdrom5c
brw------- 1 root system 19,1694 Mar 22 08:47 /dev/disk/cdrom6a
brw------- 1 root system 19,1698 Mar 22 08:47 /dev/disk/cdrom6c
brw------- 1 root system 19,1710 Mar 22 08:57 /dev/disk/cdrom7a
brw------- 1 root system 19,1714 Mar 22 08:57 /dev/disk/cdrom7c

# ls -l /dev/rdisk/cdrom*

crw------- 1 root system 19,1690 Mar 22 08:18 /dev/rdisk/cdrom5a
crw------- 1 root system 19,1678 Mar 22 08:18 /dev/rdisk/cdrom5c
crw------- 1 root system 19,1695 Mar 22 08:47 /dev/rdisk/cdrom6a
crw------- 1 root system 19,1699 Mar 22 08:47 /dev/rdisk/cdrom6c
crw------- 1 root system 19,1711 Mar 22 08:57 /dev/rdisk/cdrom7a
crw------- 1 root system 19,1715 Mar 22 08:57 /dev/rdisk/cdrom7c

# file /dev/disk

/dev/disk: symbolic link to ../../../../devices/disk

# file /dev/rdisk

/dev/rdisk: symbolic link to ../../../../devices/rdisk

4. My latest suggestion is to boot each member from genvmunix, run "hwmgr v d" to find the applicable CDROM, and try mounting a CD (the idea being that perhaps the appropriate device drivers aren't built into the running kernel). This won't happen until mid-April though, due to their production schedule.

Am I on the right track?
Is there anything else I should be checking?
Is there anything that I am missing?

Thanks in advance for any/all replies.

Regards,

John Lanier
PARSEC Group
Email: jlanier@parsec.com
AIM ID: JLparsec
WWW: http://www.parsec.com
11 REPLIES
Honored Contributor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

> #mount /dev/disk/cdrom*c /mntpnt

Why the wildcard? The shell will expand that
wildcard into multiple device names. What
sense would this result make?:

mount /dev/disk/cdrom5c /dev/disk/cdrom6c /dev/disk/cdrom7c /mntpnt

If you have only one CD-ROM device, I suppose
that this would work, but it seems like a
_horrible_ habit to cultivate.

Or am _I_ confused?
Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)


Sorry, I'm not literally specifying a wildcard; that was just to indicate some number for the CDROM itself.

The actual CDROM drives that we're trying to mount are:

/dev/disk/cdrom5c
/dev/disk/cdrom6c
/dev/disk/cdrom7c

Regards,

--John Lanier
Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)


I need to be even more clear here.

Here are the CDROM devices on each member:
-------------------------------------------
Member1: mount /dev/disk/cdrom5c /mntpnt
Member2: mount /dev/disk/cdrom6c /mntpnt
Member3: mount /dev/disk/cdrom7c /mntpnt

All of these devices fail to mount as previously mentioned.

Regards,

--John Lanier
Honored Contributor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

Hi John,

You say that the drives fail to read any media, but is it really *any*.

I've been having fun with a DS20 recently that failed to boot off any home burnt CDs, but worked fine with a pressed CD. I know the media was fine because other servers booted off it OK. Something in the drive obviously didn't like CD-Rs.

Probably not the answer as all three servers have the problem, but its another idea to cross off the list.

Cheers,

Rob
Valued Contributor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

try the cluster mount option "-o server_only"
Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

Thanks for the replies. We have already tried the "mount -o server=servername \
/dev/disk/cdromNc /mntpnt" but not the "mount -o server_only" syntax, so we will try that and see what happens. I will also confirm the media type being used.

Thanks again,

--John Lanier
Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)


FYI: HP-branded media is in use here, so the issue is not with home-grown CD's (the same media is mount-able on a standalone ES40).

I should also note that the CD-ROM drives are all able to be seen from ">>>show dev" and also are able to be booted from, as the cluster was built from CD. This is why I took the path of dsfmgr/hwmgr originally, as the CDROM drives are useable from SRM but not from the OS.

I suppose I could also check the SRM firmware revisions on the standalone and clustered ES40's, to see if there are any differences there.

Regards,

--John Lanier
Frequent Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

"1. Checked that CDFS and UFS are in /sys/conf/HOSTNAME on each member (YES)."

Not to be dense or anything, are you sure that the kernel was then rebuilt, it build cleanly, was moved to the appropriate member boot directory and the system rebooted off the correct vmunix?

Booting off of genvmunix as indicated is a good test to try.

Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)


Thanks for the reply. Yes, the kernels have been confirmed to be correctly linked from /vmunix to their respective locations
in /cluster/members/memberN/boot_partition(per sys_check output).

Regards,

--John Lanier
Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)


As it turns out, the problem was/is due to a kernel configuration problem; when they boot genvmunix they can mount CD's fine, but after building the new kernel(s) and rebooting off of them, the same problem occurs.

We should be able to confirm what is missing via "sizer -n config2" while booted from genvmunix, then incorporate the changes from /tmp/config2 into /sys/conf/HOSTNAME for each node before rebuilding the kernels (doconfig -c HOSTNAME) and copying them into /cluster/members/memberN/boot_partition before rebooting. It looks like the problem can be isolated to a kernel config. issue, so I will close this thread for now.

Again, thanks for all of the replies.

--John Lanier
Occasional Advisor

Re: Problems mounting a CD-ROM under TCS V5.1B (3 nodes)

Kernel configuration problem; when booted from genvmunix, CD's mount fine.
//Add this to "OnDomLoad" event