Thanks to Stan, Linh, and Darren, my /kernel/drv/sd.conf was overwritten with the upgrade. I just needed to replace with the original and reboot. Thanks Again, billd. -----Original Message----- From: Pietkiewicz, Stan - ITSD/DSTI Sent: May 8, 2003 3:38 PM To: Pietkiewicz, Stan - ITSD/DSTI; 'bill@lexys.com' Subject: RE: Can't see all disk on a A1000 after 64 bit upgrade Aha!! The installation of Raid Manager *does* make changes to /kernel/drv/sd.conf!! (at least it did on the third machine I checked)... Oops... The keyboard was in motion before the brain was in gear!! I had a look at a couple of systems, and neither have any changes to sd.conf... I was thinking of a situation where a 3rd-party FC-AL disk enclosure needed changes to sd.conf for the scsi targets that it was using (17-24 if I recall) Are the other LUNs visible from a probe-scsi-all? Stan Pietkiewicz Stan.Pietkiewicz@statcan.ca Informatics Technology Services Division - Statistics Canada It may be statistically possible that my opinion is the same as someone else's - but it is still my opinion! -----Original Message----- From: Pietkiewicz, Stan - ITSD/DSTI Sent: May 8, 2003 3:29 PM To: 'bill@lexys.com' Subject: RE: Can't see all disk on a A1000 after 64 bit upgrade Check /kernel/drv/sd.conf.... You might need to specify the existence of any LUNs other than LUN 0. Stan Pietkiewicz Stan.Pietkiewicz@statcan.ca Informatics Technology Services Division - Statistics Canada It may be statistically possible that my opinion is the same as someone else's - but it is still my opinion! -----Original Message----- From: Darren Dunham [mailto:ddunham@taos.com] Sent: Thursday, May 08, 2003 3:20 PM To: bill@lexys.com Subject: Re: Can't see all disk on a A1000 after 64 bit upgrade Did you reinstall raid manager after the upgrade? It looks like your /kernel/drv/sd.conf got reset back to the original copy. That would only have support for disks with lun number 0, not higher. From: Trinh, Linh T. [C] [mailto:TrinhL@nima.mil] Sent: Thursday, May 08, 2003 3:21 PM To: 'bill@lexys.com' Subject: RE: Can't see all disk on a A1000 after 64 bit upgrade Try to restore the /kernel/drv/sd.conf, reboot then it will see all the disks. You can compare the old and new upgrade to see the diff. Good luck, Linh -----Original Message----- From: Bill Davern [mailto:bill@lexys.com] Sent: May 8, 2003 3:14 PM To: sunmanagers@sunmanagers.org Subject: Can't see all disk on a A1000 after 64 bit upgrade I have a E420r running Solaris 8 01/01 and Oracle 8i. The 420 has 2 18 GB internal drives and a StorEdge A1000 with 4 18 GB disks attached. I need to upgrade Oracle to 9i 64 bit, but the system was originally configured as 32 bit Solaris. So yesterday I used Solaris 8 2/02 disks to upgrade the system and add the 64 bit support. After doing the upgrade I can only see one of the disks on the A1000, c2t5d0s0, but none of the other 3. When I boot the system I get the following message : /dev/rdsk/c2t5d1s0: No such device or address Can't open /dev/rdsk/c2t5d1s0 /dev/rdsk/c2t5d1s0: CAN'T CHECK FILE SYSTEM. /dev/rdsk/c2t5d1s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/rdsk/c2t5d2s0: No such device or address Can't open /dev/rdsk/c2t5d2s0 /dev/rdsk/c2t5d2s0: CAN'T CHECK FILE SYSTEM. /dev/rdsk/c2t5d2s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/rdsk/c2t5d3s0: No such device or address Can't open /dev/rdsk/c2t5d3s0 /dev/rdsk/c2t5d3s0: CAN'T CHECK FILE SYSTEM. /dev/rdsk/c2t5d3s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. When I try to run fsck -y /dev/rdsk/c2t5d1s0 I get : Can't open /dev/rdsk/c2t5d1s0 . When I boot and do a format only the 2 internal an one disk on the array are showing. Any help would be greatly appreciated as this is a production machine. _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu May 8 17:35:26 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:12 EST