SRDB ID |
|
Synopsis |
|
Date |
17448 |
|
2.5.1 to 2.6 upgrade cannot see new Photons (A5000) disks |
|
10 Jan 2000 |
After upgrading to Solaris 2.6 from 2.5.1 HW8/97, cannot see the A5000 disks
However, booting from CD-ROM sees the disks.
All A5000 (Photon) patches are up to date.
SOLUTION SUMMARY:
NOTE: The information below can also be used to as an aid in
debugging other Photon issues where the disks cannot be 'seen'.
The root cause of this is often the bug reported in bug id 4067860 which
causes duplication of major number in /etc/name_to_major file.
These duplications (which can cause a panic if key parts needed
by the OS are duplicated) will prevent a boot -r from working
correctly.
To correct, do the following:
1. Boot system in single user mode, either from disk (if works) or cdrom
and cd into the etc directory on the system disk.
2. Edit the path_to_inst file and remove all entries with the word socal
(remember we are in the system disk's etc directory).
3. Check the name_to_major file for duplicate numbers (the second column).
For the Photon we are looking for the following drivers:
ssd
ses
socal
sf
Remove any duplicates using either vi or the rem_dev(1m) command. Other
duplicates (i.e. other drivers with the same number) that you may find
are not covered in this document.
4. If you used the rem_dev(1m) command you should now see that the
duplicate driver number entries are removed from the name_to_major
file.
5. Check to see if the file called driver_aliases in the etc directory
(on the system disk) has the following two lines. Add them if not. No
leading spaces or tabs (it is indented here only for clarity).
Use a space to seperate the two parameters on each line
socal SUNW,socal
ssd SUNW,ssd
NOTE: You need both entries
6. Now cd to the dev directory on the system disk and do the following:
a. Remove all entries in the es directory that start with ses (do not
remove the directory).
b. For completeness, check the dev/dsk and dev/rdsk
for any entries that point photon disks and remove them.
c. Finally, check the devices directory for any entry that
has SUNW,socal and remove them using rm -r .
i.e. we do not want any entries in devices tree that
has the string SUNW,socal.
7. Now re add these drivers using the add_drv(1m) command. ie
add_drv ssd
add_drv ses
add_drv socal
add_drv sf
You can ignore any warning messages
8. Check to see that the file name_to_major (in the system disk etc directory)
now has those drivers listed and there are no duplicate numbers.
9. Reboot using the command
reboot -- -rv
10. You should now have the Photons visible.
TRICKS:
If you cannot reboot you can try the above steps (1-8) but you must
use the rem_drv(1m) command in step 2 and the system must not complain
that the device is busy.
Now after doing steps 1-8, run the modload -p command for each driver. i.e.
modload -p drv/ssd
modload -p drv/ses
modload -p drv/socal
modload -p drv/sf
Note no leading / . If modload complains, you can omit
the -p and give the complete path for the driver. All but
the driver called sf are in /kernel/drv. Driver sf is in
/platform/`arch -k`/kernel/drv . Note that arch -k returns
the correct kernel arch type which is used to determine which
kernel directory the system uses. Also note the backward quotes.
Now run the following commands:
drvconfig -i sf
drvconfig -i ses
drvconfig -i ssd
disks
You should now have the photons
You should try a boot -r to make sure everything
comes back when you can arrange a time to reboot the system.
INTERNAL SUMMARY:
Please note there are several problems with the various
kernel drv commands at 2.5.1 and this procedure has not been tested
on 2.5.1 systems
The noted bug in the Solution section details the problems
with the add[rem]_drv commands
SUBMITTER: Stephen Taylor
APPLIES TO: Operating Systems/Solaris/Solaris 2.6, Storage
ATTACHMENTS:
Copyright (c) 1997-2003 Sun Microsystems, Inc.