This is a discussion on devfsadm doesn't see newly installed disks in D1000 within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> Hi group I'm desperate for help and I'm hoping a guru is out there waiting to help. I have ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi group I'm desperate for help and I'm hoping a guru is out there waiting to help. I have just installed 4 new hard disks into an existing D1000 but Solaris cannot see them. They are visible to the OBP when running a probe-scsi-all : /pci@8,700000/scsi@2 Target 0 Unit 0 Disk SEAGATE ST336704LSUN36G 032C Target 1 Unit 0 Disk SEAGATE ST336704LSUN36G 032C Target 2 Unit 0 Disk SEAGATE ST336704LSUN36G 0326 Target 3 Unit 0 Disk SEAGATE ST336607LSUN36G 0307 Target 4 Unit 0 Disk SEAGATE ST336607LSUN36G 0307 Target 8 Unit 0 Disk SEAGATE ST336704LSUN36G 032C Target 9 Unit 0 Disk SEAGATE ST336704LSUN36G 032C Target a Unit 0 Disk SEAGATE ST336704LSUN36G 0326 Target b Unit 0 Disk SEAGATE ST336607LSUN36G 0307 Target c Unit 0 Disk SEAGATE ST336607LSUN36G 0307 Target e Unit 0 Processor SYMBIOS D1000 2 Target f Unit 0 Processor SYMBIOS D1000 2 (The new disks all have the 0307 firmware) But whenever I run a devfsadm, touch reconfigure boot or a boot -- -r they are never visible to format, only the original disks in the D1000 and the 2 internal root disks. I'm now starting to run out of ideas of what to try, there is nothing to change in /kernel/drv/sd.conf as these targets are already defined by default. I have done a boot net -s off of my jumpstart server and the disks are immediately visible to format but not through the OS on the root disk. So I believe the problem is with the OS rather than being a hardware fault. Can anyone give me some other places to look?? I've searched sunsolve and net to no avail. Thanks in advance, Paul. |
| ||||
| Paul wrote: > Hi group > > I'm desperate for help and I'm hoping a guru is out there waiting to help. > > I have just installed 4 new hard disks into an existing D1000 but Solaris > cannot see them. They are visible to the OBP when running a probe-scsi-all > : > > /pci@8,700000/scsi@2 > Target 0 > Unit 0 Disk SEAGATE ST336704LSUN36G 032C > Target 1 > Unit 0 Disk SEAGATE ST336704LSUN36G 032C > Target 2 > Unit 0 Disk SEAGATE ST336704LSUN36G 0326 > Target 3 > Unit 0 Disk SEAGATE ST336607LSUN36G 0307 > Target 4 > Unit 0 Disk SEAGATE ST336607LSUN36G 0307 > Target 8 > Unit 0 Disk SEAGATE ST336704LSUN36G 032C > Target 9 > Unit 0 Disk SEAGATE ST336704LSUN36G 032C > Target a > Unit 0 Disk SEAGATE ST336704LSUN36G 0326 > Target b > Unit 0 Disk SEAGATE ST336607LSUN36G 0307 > Target c > Unit 0 Disk SEAGATE ST336607LSUN36G 0307 > Target e > Unit 0 Processor SYMBIOS D1000 2 > Target f > Unit 0 Processor SYMBIOS D1000 2 > > (The new disks all have the 0307 firmware) > > But whenever I run a devfsadm, touch reconfigure boot or a boot -- -r they > are never visible to format, only the original disks in the D1000 and the 2 > internal root disks. > > I'm now starting to run out of ideas of what to try, there is nothing to > change in /kernel/drv/sd.conf as these targets are already defined by > default. > > I have done a boot net -s off of my jumpstart server and the disks are > immediately visible to format but not through the OS on the root disk. So I > believe the problem is with the OS rather than being a hardware fault. > > Can anyone give me some other places to look?? I've searched sunsolve and > net to no avail. > > Thanks in advance, Paul. > > By the above, did you mean you did a 'reboot -- -r'? I would do this first, if you have not already. Get to the OBP promt and do the following: ok setenv auto-boot? false ok reset-all When it comes back to the OBP prompt: ok probe-scsi-all (you have already done this but being redundant) ok boot -r If format still fails to see the disks try this: # drvconfig # disks At this point I would need more info. I know it sounds like you have already done all this. One other thing is to look at /etc/path_to_inst, sometimes that file can get gummed up if you do frequent reconfig boots. -Chuck |